The structural asymmetry nobody names

In a third-party liability claim, the adjuster works for a company with no relationship to your client and every incentive to close the file cheaply and quickly. That is a clean adversarial posture, and it is easy to work against because everyone understands the game.

An underinsured motorist claim is not that. The carrier is your client's own insurer. It has a contract with your client, it has been taking premium, and it owes duties of good faith that a third-party carrier simply does not owe. That should make the UIM claim easier. In practice it frequently makes it slower, because the carrier is operating on a set of assumptions that a third-party adjuster cannot afford to make:

• The claimant is unlikely to sue. Suing your own insurer feels different to a client than suing a stranger who rear-ended them. Carriers know this. Attrition is a live strategy on UIM in a way it is not on liability.
• The file has already been evaluated once. By the time the UIM claim opens, the underlying liability carrier has usually tendered its limits. The UIM adjuster inherits that number, and it anchors them, often below where the file actually values.
• Coverage questions can be raised late. Offsets, exhaustion, consent-to-settle and stacking issues give the carrier legitimate reasons to hold a file open. Some of those reasons are real. Some are timing.

None of this is villainy. It is a claims department working its incentives. But it does mean that a UIM file which is handled reactively, waiting for the adjuster, responding when contacted and demanding when treatment ends, will settle for less and take longer than the same file handled forward.

The behavior pattern, in order

Across Washington UIM files, the sequence is consistent enough to plan around.

Weeks 1-6: fast, friendly, and procedural. Acknowledgment letters, a recorded statement request, a medical authorization request that is invariably broader than it needs to be. This phase is genuinely cooperative and it is also where the carrier acquires the material it will use to reduce the claim eighteen months later. The overbroad authorization is the single most common unforced error we see in files that come to us mid-stream. A signed unlimited release means a decade of unrelated records, and a decade of records means a prior-complaint argument that would not otherwise have existed.

Months 2-6: silence. Treatment is ongoing, so the carrier waits. This is defensible. It is also the period in which most firms go quiet in return, and that symmetry is the mistake. A file with no claimant-side activity for four months is a file the adjuster has mentally shelved and a reserve nobody has revisited.

Months 6-12: the first evaluation, and it is low. When the demand lands, the initial response is frequently a fraction of the demand and is justified by some combination of: treatment gaps, degenerative findings on imaging, the underlying tender as a valuation anchor, and a soft-tissue characterization of an injury that is not soft-tissue. These four arguments account for the overwhelming majority of first-round UIM reductions we see, and every one of them is preventable at the file-building stage rather than arguable at the negotiation stage.

Months 12+: movement, but only against a record. Carriers move on UIM when the cost of not moving becomes concrete. In Washington that cost has a name, and we will come to it.

Three things we do before the demand is drafted

1. Narrow the authorization, in writing, on day one

The medical authorization is negotiable and most claimants never learn that. We respond to the carrier's blanket authorization with a limited one: providers relevant to the body parts at issue, a defined date range beginning a reasonable period before the collision, and an express reservation as to anything outside it. If the carrier insists on broader access we ask them to state in writing why the additional records are necessary to evaluate the claim.

That exchange does two things. It usually protects the client's unrelated history. And if the carrier refuses to explain itself, you now have a documented instance of a carrier demanding material it will not justify, which is a useful piece of paper later.

2. Build the causation opinion while the client is still treating

The most expensive gap in a UIM file is a treating physician who never puts a causation opinion in the chart. Once treatment ends and the patient stops coming in, obtaining that opinion becomes a records request, then a phone call, then a fee, then a delay of six weeks, and sometimes it never arrives at all.

While the client is actively treating, a short, specific, respectfully worded letter to the treating physician, asking whether, to a reasonable degree of medical certainty, the findings are causally related to the collision and whether further material improvement is expected, is answered far more often than the same request sent after discharge. We send it at the point the diagnostic picture stabilizes, not at the point we start drafting.

Two sentences in a chart note are worth more than four pages of our advocacy, because we are counsel's agent and the physician is not.

3. Address the gap before the carrier finds it

Every real file has a treatment gap. Clients lose jobs, lose childcare, lose insurance, get scared of needles, or simply feel better for six weeks. The gap is not the problem. The unexplained gap is the problem.

We document the reason contemporaneously with a dated client declaration, the employer email denying leave or the clinic's own cancellation record, and we put it in the demand affirmatively, in our own section, before the adjuster raises it. A gap you explain is a fact. A gap the carrier discovers is an argument.

What actually changes carrier behavior in Washington

Washington gives a first-party claimant something most states do not. Under RCW 48.30.015, a first-party claimant who is unreasonably denied a claim for coverage or payment of benefits may bring an action, and the statute permits the superior court to increase the total award to as much as three times the actual damages, and requires an award of reasonable attorney fees and litigation costs including expert witness fees to a prevailing first-party claimant.

The procedural gate is short and specific: twenty days prior to filing, the first-party claimant must provide written notice of the basis for the cause of action to the insurer and to the Office of the Insurance Commissioner.

Two practical consequences follow, and they are the reason Washington UIM practice differs from UIM practice anywhere else.

First, the fee provision changes the economics of a mid-sized claim. A carrier weighing whether to hold at a lowball number on a $180,000 file is weighing it against a potential trebling plus fees. That calculation is different from the one they run in a state without the statute, and adjusters know the difference.

Second, and this is the part that matters for a paralegal or case manager rather than for trial counsel, the leverage only exists if the file contains a record of unreasonableness. The statute is not a rhetorical device. Writing "this may constitute bad faith" into a demand letter accomplishes nothing. What accomplishes something is a file in which the carrier's own conduct, documented as it happened, looks unreasonable to a reader who was not there.

The claims-handling standards in WAC 284-30-330 give you the vocabulary for that record. Among the enumerated unfair practices are failing to acknowledge and act reasonably promptly upon communications with respect to claims (subsection 2), refusing to pay claims without conducting a reasonable investigation (subsection 4), failing to attempt in good faith to effectuate prompt, fair and equitable settlement of claims in which liability has become reasonably clear (subsection 6), and failing to promptly provide a reasonable explanation of the basis in the policy for a denial or a compromise offer (subsection 13).

Read that list again as a file-building instruction rather than as a litigation theory. Every one of those subsections describes a carrier behavior that is invisible unless somebody on the claimant side was writing it down at the time.

The first letter

All of which produces a specific answer to the question this piece started with. The first letter on a Washington UIM file should do four things, and most first letters do only the first:

1. Establish representation and the claim. Standard, necessary, insufficient.
2. Request the policy, the declarations page and the applicable coverage limits in writing, with a specific date by which you expect them. You need this for the Stowers-equivalent analysis Washington does not have, for the offset math, and because a carrier that will not tell you the limits is a carrier building your record for you.
3. Tender a limited, reasoned medical authorization rather than signing theirs, as above.
4. Open the communications log. Date, time, medium, participant, substance, and what was promised. Every contact from that day forward, including the ones that go well.

That fourth item is the one that feels like busywork and is not. Eighteen months later, the difference between a file that settles at the number and a file that settles at sixty percent of the number is frequently a two-page log showing four unanswered contacts across twenty-one days, next to a regulation that says a carrier must act reasonably promptly upon communications.

Nobody builds that log retroactively. That is the whole point of building it forward.

Not legal advice. This is a practice-operations discussion written for attorneys and their staff. RemPITe is not a law firm and does not provide legal advice. Statutory and regulatory text is quoted or paraphrased as of writing and may change; verify current authority before relying on it. All strategic and legal decisions on any matter rest with the supervising attorney.

The statute, briefly, and then the part that matters

RCW 48.30.015 gives a first-party claimant who is unreasonably denied a claim for coverage or payment of benefits a cause of action. The court may increase the total award to an amount not to exceed three times actual damages, and shall award reasonable attorney fees and actual and statutory litigation costs, including expert witness fees, to a first-party claimant who prevails. Twenty days before filing, the claimant must give written notice of the basis for the cause of action to the insurer and to the Office of the Insurance Commissioner.

That is the whole architecture, and every plaintiff lawyer in Washington knows it. What gets less attention is that the statute rewards a quality the pre-litigation file either has or does not have by the time counsel starts thinking about it: a contemporaneous record of unreasonableness.

Unreasonableness is not a legal conclusion you assert. It is an impression a neutral reader forms from a sequence of documented facts. And the person who determines whether that sequence exists is not the trial attorney. It is whoever was managing the file in months two through fourteen.

Why the retrofitted record fails

Here is the failure mode, and it is depressingly common. Eighteen months into a file, the carrier's offer is insulting. Someone says the word IFCA. The file gets pulled, and it contains: the demand, the carrier's evaluation letter, the offer, a handful of emails, and a case-management system full of notes reading "called adjuster," "LM," "no response," "called again."

That is not a record. It is a memory of a record. It cannot establish when the call was made, what was asked, what was promised, what was received, or how long the silence ran, because none of those facts were captured in a form that survives.

Compare a file where the same eighteen months produced a dated log with time stamps, the actual emails with headers, the certified-mail receipts, and four specific incidents written up on the day they occurred. Identical carrier conduct. Completely different evidentiary posture. The difference cost about six minutes a week.

The four documented moments that carry the weight

Not every carrier behavior belongs in an IFCA record. Padding it with routine friction weakens it. In our experience four categories do the work, and each maps to language in WAC 284-30-330.

Moment one: the unanswered communication, counted

WAC 284-30-330(2) identifies as an unfair practice failing to acknowledge and act reasonably promptly upon communications with respect to claims. That standard is only usable if the communications and the intervals are documented with precision.

What we capture on every contact attempt: date, time to the minute, method (direct dial, main line, email, portal message), who was reached or not reached, whether a voicemail was left and what it said, and any commitment made in response. When an adjuster says "I'll have an evaluation to you by the fifteenth," that sentence goes in the log in quotation marks with the date it was said, and it is followed up in writing the same day: "Confirming our call this morning: you indicated an evaluation by March 15. We'll look for it then."

That confirming email is the single highest-value habit in this whole discipline. It converts a phone call into a document, it is entirely courteous, and it makes a missed commitment provable rather than assertable.

Moment two: the investigation that did not happen

WAC 284-30-330(4) addresses refusing to pay claims without conducting a reasonable investigation. The record that supports this is built by giving the carrier everything and then noting what they did not do with it.

When we transmit records, we transmit them with a cover index setting out what is enclosed, how many pages, which providers and which dates, and we keep proof of transmission. If the carrier's later evaluation letter mischaracterizes the treatment, misses a provider, or asserts that something is undocumented that was in fact enclosed at a specific page of a specific exhibit sent on a specific date, that discrepancy is worth more than any adjective we could write.

The most useful IFCA fact we have ever put in a notice was not dramatic. It was: the carrier's evaluation letter described the claimant as having "no orthopedic follow-up after August," and the orthopedic records for September, October and November had been transmitted, indexed, in a package the carrier's own portal confirmed receiving in December.

Moment three: the offer with no explanation

WAC 284-30-330(13) requires an insurer to promptly provide a reasonable explanation of the basis in the policy for a denial or a compromise offer.

So when a lowball offer arrives with no reasoning, we ask for the basis, in writing, politely, once. Specifically: which medical findings the carrier accepts and which it disputes, what value it has assigned to each category of damages, and what policy language supports the position. We give a reasonable date for the response.

The carrier either explains, which is useful because now their reasoning is fixed and can be dismantled with their own IME, or does not explain, which is useful for a different reason. Either way the request must be reasonable, singular, and genuinely answerable. A request designed to be refused reads as manufactured to any neutral, and it should, because it was.

Moment four: liability reasonably clear, and still no movement

WAC 284-30-330(6) speaks to failing to attempt in good faith to effectuate prompt, fair and equitable settlement of claims in which liability has become reasonably clear.

The pre-litigation task here is to fix the date on which liability became reasonably clear and make that date undeniable. A rear-end collision with a police report assigning fault, an admission in the recorded statement, or a liability carrier tendering its limits. Each is a discrete, dateable event. We note it, and where appropriate we write to the UIM carrier confirming it: "The underlying carrier tendered its $50,000 limits on June 4. Liability is not in dispute. We look forward to your evaluation of the UIM exposure."

From that date forward, every week of silence is a week of silence after liability was reasonably clear. That is a materially different fact than delay during a genuine liability investigation, and the difference exists only because somebody drew the line at the time.

What the file physically contains

Concretely, an IFCA-ready pre-litigation file on our side has:

• A communications log as a standalone document, not scattered case notes. Chronological, one row per contact, exportable.
• A correspondence binder with every letter and email in full, headers intact, plus transmission proof: certified mail receipts, portal confirmations, fax confirmations, read receipts where available.
• A records-transmission index showing exactly what the carrier received and when.
• Confirming emails memorializing every substantive phone call, sent the same day.
• A dated liability-clarity note identifying the event and the date.
• A carrier-conduct memo updated as incidents occur, running to four or eight entries over the life of the file, each one paragraph, each dated, each tied to a specific WAC subsection.

None of this is exotic. All of it is ordinary discipline applied consistently. And the reason it usually does not exist is not that firms do not know it matters. It is that the person with the bandwidth to do it every week is exactly the person the firm does not have.

On the twenty-day notice itself

The notice is trial counsel's document and the decision to send it is a legal judgment that belongs to the attorney, full stop. But it is worth understanding what the notice is drawing on, because it clarifies what the pre-litigation file is for.

The statute requires written notice of the basis for the cause of action to the insurer and to the Office of the Insurance Commissioner, twenty days before filing. A notice whose basis is "the offer was too low" is a weak notice. A notice whose basis is a dated sequence, with liability clear on this date, records transmitted on that date and indexed at this page, four contacts across twenty-one days unanswered, an evaluation letter asserting a fact contradicted by records the carrier confirmed receiving, a written request for the basis of the offer that went unanswered for thirty days, is a notice that describes conduct rather than characterizing it.

The second notice is not better writing. It is a better file. The writing took an afternoon; the file took fourteen months of somebody caring on a Tuesday.

Not legal advice. RemPITe is not a law firm and provides paralegal and case-management support only. Nothing here creates an attorney-client relationship or substitutes for the judgment of the supervising attorney, who retains sole authority over whether and when to send any statutory notice. Statutory and regulatory citations are as of writing and may change.

What the doctrine actually asks

The Stowers duty comes from G.A. Stowers Furniture Co. v. American Indemnity Co. and was given its working test in American Physicians Insurance Exchange v. Garcia. A settlement demand activates the insurer's duty only if three conditions are met:

1. At the time the offer is made, the claim against the insured must be within the scope of coverage.
2. The amount demanded must be within the insured's policy limits.
3. The terms of the demand must be such that an ordinarily prudent insurer would accept it, considering the likelihood and degree of the insured's potential exposure to a judgment in excess of limits.

Read those three conditions as a checklist rather than a doctrine and something becomes obvious: the first is a coverage question you investigate, the second is arithmetic, and the third is drafting. Element three is where competent letters die, and it dies on details that have nothing to do with how badly your client was hurt.

The failure modes, in order of frequency

1. Conditional language

An offer an insurer cannot simply accept is not an offer that triggers the duty. Words like if, provided that, subject to, upon confirmation that and in reliance upon convert an unconditional settlement offer into a negotiation position.

The most common version is a demand conditioned on the carrier producing something: a policy, a limits affidavit, a coverage confirmation. The instinct is understandable; you want the limits verified. But a demand that says "we will settle for policy limits upon your production of a sworn limits affidavit" is a demand the carrier cannot accept by simply paying, and that is the whole ballgame.

The fix is sequencing, not language. Request the policy, the declarations page and a limits affidavit in a separate, earlier letter. Get the answer. Then send the demand as an unconditional, self-contained offer. This is a pre-litigation workflow problem, and it is why we treat the limits request as a distinct step with its own deadline and its own follow-up cadence, weeks before anyone drafts a demand.

2. A demand that is not clearly within limits

"An amount within your policy limits" is not a demand. Neither, usually, is a demand that leaves the carrier to do math about erosion, stacking, multiple claimants or multiple policies.

The demand should state a specific dollar figure. Where limits are genuinely uncertain because the carrier has not confirmed them, one workable construction is a figure stated in the alternative, being the specific number or the applicable limits, whichever is less. But this is precisely the situation you avoid by getting limits confirmed first.

Where there are multiple claimants against a shared limit, the analysis gets harder and it is genuinely the attorney's call. What the file can do is make the call answerable: identify every known claimant, every known policy, every layer, and any erosion by payment, before the demand is drafted rather than after the carrier raises it.

3. A release that does not release enough

An ordinarily prudent insurer accepts a demand because acceptance buys peace. A demand offering to release one insured but not another, or one claim but not a derivative claim, or that is silent on parties the carrier also insures, leaves the carrier exposed after paying its full limits. No prudent insurer accepts that, and a court asking whether one would has an easy answer.

The release should be full and final as to all claims arising from the occurrence, against the insured and any additional insureds within the scope of that policy. Derivative claims matter: loss of consortium, a spouse's claim, a parent's claim on behalf of a minor. If a family member has a claim that is not being released, the carrier is being asked to pay limits and remain exposed.

Minor claimants add court-approval mechanics that the attorney must handle. The pre-litigation job is to surface, early, that a minor is involved, so the demand is structured with that in mind rather than amended after it is out.

4. Liens left as the carrier's problem

Hospital liens, health-plan subrogation and Medicare or Medicaid interests are the quiet killer of otherwise sound demands. An insurer that pays limits and then faces a lienholder asserting an independent claim has not bought peace.

The demand should address liens head-on: identify known liens and state how they will be handled, typically that the claimant will satisfy or otherwise resolve them out of the settlement proceeds and indemnify accordingly, subject to the attorney's judgment on the appropriate formulation. Medicare interests in particular deserve their own explicit sentence rather than silence.

This is heavy pre-litigation work, covering lien identification, hospital lien filings pulled from county records, plan documents requested and conditional-payment letters obtained, and it is exactly the work that gets skipped when a case manager is carrying eighty files. It is also the work that determines whether the letter functions.

5. An unreasonable deadline

The demand must give the insurer a reasonable time to evaluate and accept. What is reasonable depends on the file's complexity and on what the carrier already has, which is the operative point: a carrier that has held the complete medical package for four months can reasonably respond faster than a carrier receiving eleven hundred pages for the first time.

Two weeks on a file the carrier has been sitting on with a full record is generally defensible. Two weeks on a file where the demand is the carrier's first sight of the medicals invites the argument that no prudent insurer could have accepted in the time allowed, and that argument, if it lands, undoes everything.

Again, the fix is upstream. Transmit records as they come in, indexed and with proof of delivery, so that by the time the demand goes out the carrier has had the file for months and the clock you set is manifestly fair.

The pre-litigation checklist behind the letter

Almost everything above is an operational problem rather than a drafting problem. Before a Stowers demand is drafted on a file we manage, this is complete:

• Coverage confirmed in writing: policy, declarations page, limits, and any excess or umbrella layer identified. Requested early, followed up on a fixed cadence, documented.
• Every potential claimant identified, including derivative claims and minors, and every potential insured, so the release can be drawn completely.
• Every lien identified and quantified, covering hospital liens, health plan, Medicare or Medicaid and letter-of-protection providers, with documentation in the file.
• The complete medical record transmitted and receipt proven, well in advance, with a transmission index.
• Causation and permanence opinions in the chart, in the treating physicians' own words, obtained while the client was still treating.
• Every treatment gap documented and explained contemporaneously.

With that file assembled, the demand itself is a two-hour document. Without it, no amount of drafting skill produces a letter an ordinarily prudent insurer is obliged to accept.

The uncomfortable part

A Stowers demand is not a form letter, and there is no version of this work that a general-purpose virtual assistant does correctly. The failure modes above are invisible to someone who has not seen a demand rejected on them. That is not a knock on anyone's intelligence; it is a statement about what experience in this specific work is for.

The final decision on every element, whether the number, the deadline, the release language or the lien treatment, is the attorney's, always. What a senior pre-litigation team does is ensure that when the attorney sits down to make those decisions, every fact they need is already in the file, verified and dated, and nothing is waiting on a records request nobody followed up.

Not legal advice. This is a practice-operations discussion for attorneys and their staff. RemPITe is not a law firm, does not provide legal advice, and does not decide whether or how a demand is made. Case citations and doctrinal descriptions are summaries as of writing; verify current authority. All decisions rest with the supervising attorney.

The two regimes

Washington is a pure comparative fault state. Under RCW 4.22.005, contributory fault diminishes a claimant's recovery proportionately but does not bar it. A claimant found 80% at fault recovers 20% of their damages.

Texas uses proportionate responsibility with a bar. Under Texas Civil Practice and Remedies Code § 33.001, a claimant may not recover damages if their percentage of responsibility is greater than 50 percent. At 50% they recover half. At 51% they recover nothing.

Every practitioner knows this. What gets less thought is that the difference is not merely a multiplier applied at the end. It changes the shape of the risk, and therefore what the pre-litigation file has to accomplish.

Washington: fault is a discount. Texas: fault is a cliff.

In Washington, a comparative fault argument reduces the claim. Painful, but continuous: every point of fault you defeat is worth a proportional amount of money, and the file is never worthless.

In Texas, comparative fault is a step function. Between 50% and 51% lies the entire value of the case. Everything below the cliff is a discount; everything at or above it is zero.

That asymmetry has a direct operational consequence. In Texas, on any file where fault is genuinely contested, liability investigation is not a parallel workstream to the medical development. It is the priority workstream, because the medical development is worth nothing if the claimant lands on the wrong side of the line. In Washington the same contested file justifies proportional effort, because you are buying percentage points rather than buying the case.

A practical illustration. An unwitnessed lane-change collision where the client may have been partly at fault, with $60,000 in specials:

• In Washington, if fault shakes out at 40/60 against the client, the claim is still meaningful. Investigation is worth doing and worth doing well, but if the intersection camera footage costs $2,000 to chase down, that is a proportionate spend against a proportionate gain.
• In Texas, that same 40/60 finding is the difference between a recoverable claim and nothing at all, and the client's exposure sits perilously close to the bar. That $2,000 of investigation is not proportionate spend. It is the case.

Same facts, same medicine, completely different allocation of the first three weeks.

What changes in week one

In Texas, evidence perishes and the clock is shorter

Because the cliff makes liability existential, the perishable-evidence sweep runs first and runs hard on any contested Texas file: intersection and business surveillance before it overwrites (frequently 7 to 30 days), 911 audio and CAD logs, scene photographs before repairs, vehicle preservation and event data recorder imaging where warranted, witness contact while memories are fresh, and the crash report the moment it is available.

Texas also runs a two-year limitations period for personal injury, against Washington's three. A year of runway is a great deal of runway. It changes how aggressively treatment can be developed before a filing decision has to be made, and it means a Texas file that drifts for eight months is in materially more trouble than a Washington file that does the same.

In Washington, the carrier relationship is the leverage

Washington gives back on a different axis. Because fault is a discount rather than a bar, the negotiation is more often about valuation than about existence, and because RCW 48.30.015 gives first-party claimants a cause of action for unreasonable denial with potential treble damages and a fee award, the carrier's conduct becomes a value driver in a way it simply is not in Texas.

So on a Washington file, disproportionate early effort goes into the communications log, the transmission index and the carrier-conduct record. On a Texas file, that same effort goes into liability proof. Both files get both; the ratio is what differs, and getting the ratio wrong is how a file underperforms without anyone being able to point at a mistake.

Where it shows up in the demand

The Washington demand can concede a point and gain from it. Where the client bears some real share of fault, addressing it directly, setting out the client's share, why it is smaller than you think and the proportional math, is often stronger than pretending otherwise, because the adjuster is going to apply a reduction regardless and a demand that has already priced it in is a demand that looks credible on everything else.

The Texas demand generally cannot afford that posture on a file anywhere near the bar. Conceding 35% in writing on a file the carrier is arguing at 55% hands them the frame. The Texas demand argues liability first, at length, with the evidence attached, and only then values the damages.

This is why we do not use a single demand template across states, and why a chronology built for a Washington file and a chronology built for a contested Texas file emphasize different material even when the medical record is identical. The Texas chronology front-loads mechanism-of-injury and biomechanical consistency because it is doing double duty as liability corroboration. The Washington chronology front-loads treatment continuity and provider causation language because the fight is about value.

The multi-defendant wrinkle in Texas

One more Texas-specific item worth flagging for the pre-litigation file: Chapter 33's proportionate responsibility scheme allocates among all responsible parties, and Texas practice includes the responsible-third-party designation, which lets a defendant put fault on someone who is not a party to the case.

The operational implication is that identifying every potentially responsible actor early is not just about finding additional coverage. It is about not being surprised when a defendant designates a phantom. Employer, vehicle owner, maintenance provider, a road-condition authority, a bar under dram-shop theories: these get mapped in the first weeks on our Texas files, both as coverage sources and as anticipated fault-shifting targets.

Washington's multi-defendant allocation runs on a different framework with its own several-liability rules and fault-free-plaintiff wrinkles, and those are firmly attorney-judgment questions. What the file can do in either state is make sure nobody is discovered late.

The short version

If you take one operational rule from this: in Texas, spend the first three weeks proving the other driver did it. In Washington, spend the first three weeks documenting that the carrier knows it.

Both files eventually need both. But pre-litigation is a resource-allocation discipline more than anything else, and the fault regime tells you where the marginal hour goes.

Not legal advice. RemPITe is not a law firm and provides paralegal and case-management support under attorney supervision. Statutory descriptions are summaries as of writing and may change; limitations periods are subject to numerous exceptions and tolling rules not discussed here. Verify all authority and consult the supervising attorney on any live matter.