Inputs you need for Damages Allocation in Washington

Inputs you will need

Run this scenario in DocketMath using the Damages Allocation calculator.

Damages allocation in Washington gets much easier when you collect the same core facts every time. DocketMath’s damages-allocation calculator is built around those inputs, so the goal is to gather them in a consistent way before you run the calculation.

Because your question is about Damages Allocation (not just the lawsuit’s filing deadline), this post focuses on what the calculator needs and how Washington’s 5-year general statute of limitations rule (RCW 9A.04.080) fits into the workflow. No claim-type-specific sub-rule was found, so the guidance below uses the general/default period unless your matter’s specific law clearly overrides it. (This is not legal advice—use this as a practical starting point and confirm the governing law for your claim.)

Checklist of required inputs (input-checklist)

The jurisdiction-aware timing input (Washington)

Washington’s general statute of limitations is 5 years under RCW 9A.04.080. In this workflow, you use that period to decide whether the alleged harm dates fall within the actionable window for your evaluation date.

• General/default SOL period: 5 years
• Statute: RCW 9A.04.080
• Claim-type-specific sub-rule: No claim-type-specific sub-rule was found, so the calculator workflow should use the general/default period unless your matter’s specific law clearly overrides it.

Where to find each input

This is where you can reduce time wasted hunting for facts. Gather inputs from the sources you already have in typical litigation workflows.

Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.

Timeline inputs

• Date(s) of alleged harm

  • Look for: complaint allegations, incident reports, employment records, medical/therapy start dates, contract performance start/end, or billing/ledger timestamps.
  • Range tip: If harm happens repeatedly, capture the earliest and latest relevant dates.

• Filing date or evaluation date

  • Filing date: the first pleading date on file.
  • Evaluation date: your “as-of” date for settlement valuation or internal case review.

Damages component amounts

Use your case’s damages worksheet, discovery summaries, or accounting documents:

• Economic damages

  • Typically comes from: invoices, payroll records, receipts, bank statements, expert damages reports, or ledgers.
• Non-economic damages

  • Often comes from: damages narratives, witness statements, or internal scoring models (if you use one).
• Other categories

  • Common examples: pre-judgment interest (if you track it as a component), costs, or any specialized category your internal model uses.

Apportionment method

• Apportionment method

  • Where to find it: your firm’s prior templates, prior allocation memos, expert framework notes, or your standard operating procedure.
  • Keep it consistent: DocketMath’s output depends on the method you select/describe because allocation logic changes the results.

Run it

Once you’ve collected the inputs, the workflow is straightforward: run DocketMath’s damages-allocation calculator and review how changes in dates and amounts affect the allocation output.

Enter the inputs in DocketMath and run the Damages Allocation calculation to generate a clean breakdown: Run the calculator.

Step-by-step workflow

1. Open DocketMath and choose the tool: /tools/damages-allocation

   • If you want to launch it immediately, you can start here: /tools/damages-allocation

2. Enter Washington timing information

   • Use the 5-year default SOL period for the timeline filter, based on RCW 9A.04.080.
   • Confirm you’re using the general/default period because no claim-type-specific sub-rule was found for this workflow.

3. Input the damages components

   • Add each category amount you want allocated.
   • If you’re unsure about a category, run two scenarios:

     • Scenario A: exclude the uncertain category
     • Scenario B: include it with an estimate
   • This gives a quick sensitivity view of how much the output depends on the uncertain element.

4. Select your apportionment method

   • Choose the method you’re using (proportional, time-based, causation-based, etc.).
   • Re-run if your allocation method changes—because the results can shift even when the overall damages total stays similar.

5. Review results

   • Check:

     • Allocation totals by component
     • Allocation totals by timeframe (if the calculator segments by date)
     • Any SOL-based eligibility impact from RCW 9A.04.080’s 5-year window

What to expect when inputs change

Use this quick “change-impact” guide while testing your runs:

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