How to interpret Damages Allocation results in Washington

What each output means

DocketMath’s Damages Allocation calculator helps you translate a set of damage amounts into how a Washington court typically allocates recoverable damages by category based on the inputs you provide. Because this is a results interpreter, focus on (1) the components DocketMath outputs and (2) how those components affect the total.

Common output fields you should expect

While your exact labels can vary depending on the version of the damages-allocation tool, Washington-specific interpretation usually breaks down into these practical buckets:

• **Total allocated damages (sum)

  • The combined number that results after DocketMath applies its allocation rules across the categories you entered (for example, contractual vs. statutory-style components, or other category splits used by the tool).

• Allocated amount by category

  • Each category line shows the dollar amount that will be used as the basis for any downstream calculations (like totals, comparisons, or inclusion/exclusion logic inside the tool).

• Damages basis / included vs. excluded

  • Some outputs reflect whether a particular input was treated as part of the damages base or filtered out according to the tool’s internal logic.

• **Time-limited inclusion (if the tool includes a lookback)

  • If your DocketMath workflow incorporates the statute of limitations (SOL) window, it will typically cap what portion of damages is treated as potentially recoverable based on timing inputs (dates you selected or entered).

How to read the numbers together

Use this quick mental model:

1. Start with each allocated category amount.
2. Confirm that the total equals the sum of the allocated categories shown.
3. If there’s an “included vs. excluded” indicator, interpret it as:

   • Included = treated as part of the recoverable damages base within the tool’s logic
   • Excluded = not counted toward the recoverable total under the tool’s configured rule set

If your totals look “too low” or “too high,” the issue is usually not arithmetic—it’s category mapping (which category an amount fell into) or timing-based inclusion/exclusion.

What changes the result most

In Washington interpretations tied to the Damages Allocation workflow, the biggest swing factors typically fall into two groups: (A) category classification and (B) timing relative to the 5-year window.

These inputs have the biggest impact on the final number. Adjust them one at a time if you need a sensitivity check.

• date range
• rate changes
• assumption changes

A) Category classification: the most common driver

Even small shifts in how you assign an amount to a category can change totals because the calculator’s logic applies different inclusion/aggregation rules per category.

Checklist for category-related changes:

Result impact: Changing a number’s category can move dollars from one “included category” to another, altering the allocated breakdown even when the gross dollar figure stays constant.

B) Timing: RCW 9A.04.080’s 5-year window

When DocketMath incorporates timing, RCW 9A.04.080 (5 years) functions as the default lookback period in Washington.

How timing affects your allocation output (conceptually):

• If a damages-related event or accrual date is more than 5 years before the relevant starting point used by the tool, the portion tied to that older time frame may be treated as outside the potentially recoverable window.
• If the event falls within 5 years, the tool will generally include it in the recoverable damages base.

C) Starting point date: the hidden lever

Even with identical event dates, changing the reference date used by the tool can shift which portions fall inside the 5-year window under RCW 9A.04.080.

Quick sensitivity check:

D) Rounding and aggregation

DocketMath may display totals with rounding depending on the interface. If you see a mismatch between “sum of categories” and “total,” it’s often rounding, not a substantive allocation difference.

Next steps

Turn interpretation into action with a short workflow you can repeat each time you adjust inputs.

Use the Damages Allocation tool to produce a first pass, then share the output with the team for review. You can start directly in DocketMath: Open the calculator.

1) Reconcile totals to categories

• Compare allocated category amounts to total allocated damages
• If there’s a discrepancy, check:

  • whether any category is displayed conditionally,
  • whether exclusions are shown,
  • whether rounding is applied.

2) Validate your 5-year timing logic under RCW 9A.04.080

Because the calculator guidance uses Washington’s general 5-year period under RCW 9A.04.080, confirm your inputs align with that framework:

3) Create a “what-if” record (no guessing later)

Run 2–3 iterations and record:

• which category mappings you changed,
• which date(s) you adjusted,
• how each change moved the total (even roughly).

This makes it much easier to explain why a later output differs from the first run.

4) Use DocketMath outputs to guide documentation, not conclusions

DocketMath is best treated as a modeling and allocation visualization tool. Use results to decide what documents, invoices, receipts, or timeline evidence you’ll need to support each damages component in your Washington analysis workflow. (This is not legal advice.)

If you want to rerun the calculation, start here: /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