Why Damages Allocation results differ in Washington

The top 5 reasons results differ

Run this scenario in DocketMath using the Damages Allocation calculator.

If you run the Damages Allocation calculator in DocketMath for Washington (US-WA), you may see different allocation outputs across otherwise similar cases. Those differences almost always come from inputs and jurisdiction-aware rules that affect how the calculator treats time windows, which in turn changes the damages base.

Below are the five most common causes, framed around what DocketMath needs to produce consistent results.

1. Different cutoffs caused by the Washington statute of limitations

   • Washington’s general statute of limitations for many civil claims is 5 years under RCW 9A.04.080.
   • No claim-type-specific sub-rule was found in this jurisdiction dataset—so DocketMath applies the default/general period rather than a special shorter/longer period for particular claim labels.
   • If two runs use different “event dates” or “filing dates,” the included damages window can shift by months or years, changing the denominator used for allocation.

2. **Date arithmetic differences (event date vs. accrual vs. filing date)

   • Even when the same lawsuit is referenced, teams sometimes encode:

     • the date the conduct happened,
     • the date harm was discovered,
     • the date of filing.
   • DocketMath uses these to determine which portions fall inside the 5-year lookback. One swapped or mis-specified date field can swing allocated totals.

3. Damage category inputs not aligned to the same accounting period

   • Damages allocation can change materially when the inputs for damages categories (e.g., economic losses vs. other damages) cover different spans.
   • Example pattern: one dataset includes damages only from the last 24 months, while another includes damages for the full 5-year period (or vice versa). The allocator then redistributes shares across a different denominator even if the “total number” you’re comparing seems similar.

4. **Jurisdiction setting mismatch (US-WA vs. another jurisdiction)

   • DocketMath is jurisdiction-aware. Selecting the wrong jurisdiction code can change time-window logic immediately.
   • In Washington, the calculator uses the general 5-year period under RCW 9A.04.080. A jurisdiction mismatch can produce different results even if the numeric damages inputs look aligned.

5. **Inconsistent normalization of totals (gross vs. net)

   • If one run uses “gross totals” and another uses “net after offsets,” the calculator allocates based on different underlying numbers.
   • This typically doesn’t change the statute logic; it changes the proportions (and any derived allocated outputs).

How to isolate the variable

To pinpoint why two DocketMath outputs differ in Washington, isolate the variable using a controlled comparison checklist.

• Freeze the jurisdiction and tool settings so both runs use the same rule set.
• Compare one input at a time (dates, rates, amounts) and re-run after each change.
• Review the breakdown to see which segment or assumption drives the difference.

Step-by-step test plan

• Ensure the run is labeled US-WA throughout.

  • Pick one rule for each field (e.g., “event date” = the date conduct occurred; “filing date” = complaint filing date).
  • Keep them identical across runs.
  • Keep numeric damages totals the same while changing only one item at a time.
  • Run A: baseline
  • Run B: change only event date (or filing date)
  • Run C: change only damages category inputs (or their covered spans)

Quick diagnostic table

Interpreting the output delta

• If allocated totals change roughly in proportion to the length of time included, the likely cause is date windowing (SOL-driven).
• If allocations change while the included time span looks the same, focus on damages totals and category alignment.

Next steps

Use DocketMath to create a repeatable internal audit trail. A practical workflow:

1. Capture your run settings

   • Save screenshots or notes showing:

     • jurisdiction code (US-WA),
     • key dates used,
     • the damages category totals.
2. Write a “date sanity” note

   • Document which date you treated as the operative cutoff trigger (e.g., conduct/event vs. filing), so teammates don’t later swap “discovery” and “conduct” dates.
3. Run at least 3 comparisons

   • Baseline
   • One date-shift scenario (± 180 days)
   • One damages-normalization scenario (gross vs. net)
4. Reconcile discrepancies to a single root cause

   • In Washington, most differences trace back to:

     • (a) the default 5-year SOL window under RCW 9A.04.080, or
     • (b) mismatched damages category spans.

Primary tool CTA: /tools/damages-allocation

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