Damages Allocation rule lens: Washington

The rule in plain language

In Washington, many civil claims that seek recovery of money damages run into a 5-year statute of limitations, measured from the date the claim “accrues.” The general/default limitations period is set by RCW 9A.04.080.

Key takeaway: For Washington calculations that don’t have a claim-type-specific limitations sub-rule, the general 5-year period is the starting point. Per the jurisdiction notes for this lens, no claim-type-specific sub-rule was found, so the general/default period controls.

Here’s how to translate that into working “lens” logic for damages allocation modeling:

• Limitations period: 5 years (general/default)
• Source: RCW 9A.04.080
• Modeling purpose: when you build a damages timeline, you typically separate damages that fall within the limitations window from those that fall outside the window (or treat out-of-window items differently), because older items may be time-barred depending on accrual and the dates used.

What “accrues” usually means for modeling

Even when no claim-type-specific sub-rule is identified, your calculator and allocation schedule still needs an anchor for the limitations clock: a start date for accrual.

In practice, teams operationalize accrual using one of several legally recognized triggers tied to the case facts, such as:

• the date of the last wrongful act,
• the date the harm was discovered (where applicable), or
• another accrual trigger based on the legal theory and timeline.

For purposes of this DocketMath lens, treat accrual date (A) as the input that determines the start of the limitations window. Then allocate damages according to whether each damages component falls inside or outside A + 5 years.

Why it matters for calculations

Damages allocation in Washington often boils down to a computational question:

Which parts of the damages timeline fall inside the 5-year limitations window set by RCW 9A.04.080?

That matters because damages models commonly include items with different dates (and therefore different “window” outcomes), such as:

• occurrence date (or service date),
• payment/charge date,
• injury/delivery date, and
• the claim accrual date used to calculate the limitations cutoff.

Once you set an accrual date, the 5-year window becomes deterministic, and your allocation outputs can change sharply if you move the accrual input—even by months.

The limitations window (Washington default)

Using RCW 9A.04.080 (general/default): 5 years.

Define:

• Accrual date: A
• Limitations end date: A + 5 years
• In-window vs. out-of-window: classify damages entries based on whether the relevant damages date lands before/after the cutoff according to your model’s cutoff rule (for example, “on or before” vs. “strictly before,” depending on your implementation)

Practical allocation impact: quick example

Assume:

• Accrual date (A): January 15, 2021
• 5-year end date: January 15, 2026

Then (illustrative only):

• A damages component dated March 1, 2024 is likely in-window.
• A damages component dated April 20, 2026 is likely out-of-window and may be treated as potentially time-barred in the allocation schedule.

Even if the underlying damages formula stays the same, the inclusion/exclusion window can change the portion of damages that your model considers recoverable (or assigns differently).

Input sensitivities you should model

In DocketMath’s damages-allocation workflow, the inputs that most strongly affect results are typically:

• Accrual date (A) (start of the limitations clock)
• Damages entries (each entry’s date + amount)
• Which date you map to the limitations clock

  • e.g., whether you classify using a charge/transaction date vs. an occurrence/harm date

For sensitivity, you can test how classification shifts when accrual moves:

Modeling warning: don’t treat accrual as a default placeholder like “the filing date.” In limitations modeling, the accrual date should reflect the case facts and legal theory used to determine when the limitations clock starts.

Use the calculator

Use DocketMath to apply the Washington default limitations window and allocate damages across your timeline.

Primary CTA: damages allocation

Run the Damages Allocation calculation in DocketMath, then save the output so it can be audited later: Open the calculator.

What to enter (Washington US-WA rule lens)

Use the calculator with this jurisdiction-aware framing:

• Jurisdiction: US-WA
• Statute of limitations period: 5 years (general/default under RCW 9A.04.080)
• Accrual date (A): the start date of the limitations clock based on your case timeline
• Damages entries:

  • the date for each damages component (for example, charge/occurrence/harm—use the same basis consistently)
  • the amount for each component
• Allocation logic preference for items near the cutoff:

  • e.g., “include if on or before cutoff” vs. “strictly before” (follow your implementation’s definition consistently)

If you have multiple damages categories, you can model them separately and sum—just ensure the date basis and accrual anchor are consistent for classification.

How outputs change as inputs change

After running the calculation, you’ll typically be able to review:

• Total allocated inside the limitations window
• Total allocated outside the limitations window
• Net allocated amount based on your selection of inclusion/exclusion rules

To sanity-check results:

• Move the accrual date by ±30 days and confirm the cutoff boundary shifts accordingly.
• Verify that items close to A + 5 years are classified as expected under your cutoff definition.

Common modeling workflow (repeatable)

1. Set accrual date (A).
2. Confirm the calculator’s computed cutoff: A + 5 years.
3. Enter damages entries (date + amount) using the same “limitations-relevant date” basis throughout.
4. Run allocation.
5. Review classification of entries near the cutoff.
6. Adjust only one input at a time—start with accrual date—to understand sensitivity.

Pitfall to avoid: mixing different “date meanings” (e.g., some entries classified by payment date while others by occurrence date) can distort which damages fall inside vs. outside the 5-year period under the general/default rule in RCW 9A.04.080.

Reference check: Washington default period (status)

• General SOL period: 5 years
• General statute: RCW 9A.04.080
• Claim-type-specific sub-rule: none found for this lens
  → therefore, use the general/default period.

Sources and references

Start with the primary authority for Washington and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

• Primary authority reference

Related reading

• Damages Allocation Guide for Alabama — Comparative Fault Rules
• Damages Allocation Guide for Alaska — Comparative Fault Rules
• Damages Allocation Guide for American Samoa — Comparative Fault Rules