Settlement Allocator Guide for Washington

What this calculator does

Run this scenario in DocketMath using the Settlement Allocator calculator.

DocketMath’s Settlement Allocator helps you allocate a settlement amount across multiple categories (for example: medical bills, lost wages, general damages, interest, or attorney-fee reimbursements), using the timing rules that can affect how statutes of limitation apply in Washington.

In Washington, statutes of limitation can turn on when the claim accrued and how long the claim must be brought. For this guide, the key statute is:

• RCW 9A.04.080 — 5 years as the default limitations period

  • RCW 9A.04.080 — 5 years — exception P1
  • RCW 9A.04.080(1)(j) — 3 years — exception V1
  • null — 3 years — exception V2

Because settlements often bundle several issues, the settlement allocator is designed to help you allocate amounts to categories you can track against time windows—so you can see how the allocation interacts with the Washington limitations framework that follows from RCW 9A.04.080.

When to use it

Use DocketMath’s Settlement Allocator when you have a Washington settlement that includes more than one component and you want to model how those components might line up with Washington’s limitations periods tied to RCW 9A.04.080.

Common triggers

• A settlement agreement breaks payment into multiple buckets, such as:

  • past economic damages,
  • non-economic damages,
  • reimbursement items (sometimes framed separately),
  • or damages tied to distinct events.
• You need to decide how much of the total settlement is attributable to categories with different timing rules, including the 5-year default and 3-year variants referenced in RCW 9A.04.080(1)(j) and related sub-rules.
• You’re preparing settlement documentation for internal tracking, mediation files, or tax/accounting review, where the allocation method must be consistent and repeatable.

Practical “fit” checklist

Step-by-step example

Below is a concrete walkthrough using DocketMath’s Settlement Allocator for a Washington settlement. The example uses RCW 9A.04.080 timing concepts (5 years by default; 3 years in specific sub-rule situations) to demonstrate how inputs change outputs.

Assumptions for the example (Washington)

• Settlement date: March 1, 2026
• Total settlement: $180,000
• Components:

  1. Past medical expenses: $70,000 (event occurred April 15, 2019)
  2. Lost wages: $60,000 (last wage date September 1, 2021)
  3. Non-economic damages: $50,000 (injury event June 30, 2022)

Step 1: Choose a limitations period basis (calculator input)

DocketMath’s allocator groups claims into timing windows derived from RCW 9A.04.080:

• Default: 5 years (referenced as RCW 9A.04.080 — 5 years — exception P1)
• Alternatives: 3 years when a category fits a 3-year variant (including RCW 9A.04.080(1)(j) — 3 years — exception V1, and another 3-year variant shown as null — 3 years — exception V2)

For the example:

• Medical expenses are treated as a component that falls under the default 5-year model for this demonstration.
• Lost wages and non-economic damages are treated as potentially subject to 3-year variants in this demonstration to show the allocation effect.

Step 2: Enter component dates and categories

You’d enter (per component):

• Amount
• Event/accrual date (or last relevant date)
• Category/timing bucket (the calculator uses your selection to apply 5-year vs 3-year logic drawn from RCW 9A.04.080)

Let’s compute “time elapsed” to the settlement date (March 1, 2026):

1. Medical expenses: April 15, 2019 → March 1, 2026

   • Roughly 6 years 10 months
2. Lost wages: September 1, 2021 → March 1, 2026

   • Roughly 4 years 6 months
3. Non-economic damages: June 30, 2022 → March 1, 2026

   • Roughly 3 years 8 months

Step 3: Apply the selected Washington time windows

Using the allocator’s timing logic:

Scenario outputs (modeled)

• If a component is tested under the 5-year window:

  • It “fits” if the component date is within 5 years of March 1, 2026.
• If a component is tested under the 3-year window:

  • It “fits” if the component date is within 3 years of March 1, 2026.

Now apply:

In this particular example, all components are outside both windows, so the model would show all components as timing-mismatched under the chosen periods.

Step 4: Adjust inputs to reflect alternative plausible timing buckets

A settlement allocator is most useful when you can test alternative assumptions based on how dates map to claims. Suppose you refine your categorization so:

• Medical expenses fall under a 5-year bucket you treat as the relevant model for those damages.
• Lost wages are treated as a 3-year bucket (RCW 9A.04.080(1)(j) reference used as the calculator’s 3-year model for that category in your setup).
• Non-economic damages fall under the default 5-year bucket.

Even then, with the dates in this example, many components remain outside.

Step 5: Interpret the allocator output

The allocator’s output typically answers questions like:

• “How much of the settlement amount is allocated to components that fit within the selected limitation window?”
• “How much is allocated to components outside the window?”
• “If I switch a component from the 5-year model to the 3-year model (or vice versa), what changes?”

Example interpretation:

• If all components are outside the limitations windows, the allocator’s “within window” total would be $0, and “outside window” would be $180,000.

That output doesn’t decide your legal outcome—it provides a structured, statute-aware allocation model aligned with RCW 9A.04.080’s timeline framework (5 years and 3-year variants).

Common scenarios

Below are common real-world patterns where settlement allocation gets tricky in Washington, and how the calculator helps you structure the model consistently.

1) Settlement agreement uses multiple line items but includes a lump-sum total

Many settlements list:

• one total number,
• plus narrative allocations in exhibits.

DocketMath helps you convert that into a component-based allocation, then attaches timing analysis based on RCW 9A.04.080:

• 5-year default (RCW 9A.04.080 — 5 years — exception P1)
• 3-year variants (RCW 9A.04.080(1)(j) — 3 years — exception V1, and the other 3-year variant labeled V2 in the calculator’s rule set)

Checklist:

2) Different damages components have different last-dates

Lost wages often use a “last day worked” or “last wage payment” concept, while property or medical categories use different dates.

With the allocator:

• You input separate last dates per component.
• The output changes depending on whether each component falls within 5 years or a 3-year bucket tied to RCW 9A.04.080.

3) The settlement date is used as a decision anchor for time-window modeling

Even if litigation events occurred earlier, the allocator can model timing relative to a chosen anchor date (commonly the settlement date in a workflow).

Practical use:

• If you’re negotiating, you can quickly see whether shifting dates or recharacterizing categories changes the “within window” totals under RCW 9A.04.080.

4) 3-year variants appear for certain categories (RCW 9A.04.080(1)(j))

If your claim type fits **RCW 9A.04.080(1)(j

Related reading

• Settlement Allocator Guide for Alabama
• Settlement Allocator Guide for Arizona
• Settlement Allocator Guide for California