How to run Damages Allocation in DocketMath for Washington
How to run Damages Allocation in DocketMath for Washington
DocketMath’s Damages Allocation calculator helps you model comparative/contributory fault impacts on recovery in a way that aligns with Washington’s proportional reduction rule for compensatory damages. This walkthrough shows a practical workflow for using jurisdiction-aware settings for Washington (US-WA) and turning your inputs into outputs you can discuss for case evaluation, settlement discussions, or drafting.
Note: This is a practical software workflow, not legal advice. DocketMath applies the jurisdiction rules you select to your inputs, but case-specific facts still control what arguments or findings are appropriate.
Step-by-step
1) Open the right tool and select Washington
- Go to /tools/damages-allocation
- Choose the jurisdiction as Washington (US-WA).
- Confirm you are using the Damages Allocation calculator (not a separate damages or liability tool).
Why this matters: Washington’s comparative fault effect on recovery is grounded in RCW 4.22.005, which addresses how contributory fault diminishes damages.
2) Know the Washington rule DocketMath will apply
For Washington, the statute provides (in relevant part):
- In an action seeking damages for injury or death to person or harm to property,
- Any contributory fault chargeable to the claimant
- diminishes proportionately the amount awarded as compensatory damages for the injury attributable to the claimant’s contributory fault.
Source: RCW 4.22.005 — https://app.leg.wa.gov/rcw/default.aspx?cite=4.22.005
Important workflow impact: To produce a meaningful output, DocketMath needs inputs that represent how fault is apportioned—especially the claimant’s contributory fault %—because the output is a proportionate reduction of compensatory damages.
Note: No claim-type-specific sub-rule was found. That means this Washington setup reflects the general/default comparative-fault approach described in the statute, rather than separate branches for different claim types.
3) Enter the compensatory damages base (the amount before reduction)
In the calculator, locate the field(s) for the unreduced compensatory damages amount (sometimes labeled as something like base damages, total compensatory damages, or similar).
- Enter the amount before applying the claimant’s contributory fault reduction.
If the tool lets you input multiple components (e.g., medical expenses and wage loss), you can:
- enter the component breakdown if supported, or
- enter a combined total if the UI expects a single figure.
Goal of this step: DocketMath applies the proportional reduction rule to the “base” compensatory amount you provide.
4) Add fault contributors and assign percentages
Next, enter fault allocation inputs. You’ll typically see fields such as:
- Claimant’s contributory fault %
- Other parties’ fault % (e.g., defendant(s), additional parties—depending on the UI)
If there are multiple defendants/other parties, distribute the “other party” fault across them based on the scenario you’re modeling.
Sanity-check the math conceptually:
- If claimant contributory fault is 20%, then—under the proportional reduction model—compensatory damages are reduced by 20%, leaving 80% of the base.
Checklist for this step
- Claimant’s contributory fault % is entered (not defendant fault).
- Other parties’ fault % is entered if the tool requires it.
- Fault totals align with the calculator’s expectation (commonly 100%).
5) Run the calculation
Click Calculate (or the tool’s equivalent).
DocketMath should output values reflecting Washington’s proportional reduction behavior, commonly including:
- Claimant’s reduced recovery
- Dollar reduction attributable to claimant contributory fault
- Any totals/sanity checks the UI provides
6) Interpret the outputs through RCW 4.22.005 framing
After you run the calculation, interpret it consistently with the statutory concept:
- Higher claimant fault % → lower reduced recovery
- Lower claimant fault % → higher reduced recovery
- 0% claimant fault → reduced recovery equals base compensatory damages
- 100% claimant fault → reduced recovery approaches $0 (assuming the tool permits/handles that scenario)
Warning: Fault percentages used in a model are scenario inputs, not findings of fact. In real cases, fault apportionment depends on evidence and how the factfinder is instructed.
7) Iterate scenarios quickly (what-if analysis)
Use DocketMath to test different assumptions and see how sensitive the reduced recovery is to claimant fault.
A practical approach is to run at least three scenarios, such as:
- Optimistic for claimant: lower claimant contributory fault (e.g., 10%)
- Mid-range / neutral: moderate claimant fault (e.g., 25%)
- Conservative for claimant: higher claimant fault (e.g., 40%)
When you change claimant contributory fault, your output generally shifts in a direct proportion manner because the rule is “diminishes proportionately” the compensatory damages.
8) Keep a simple record of your inputs
To make your results reviewable and repeatable, record:
- the base compensatory damages amount
- claimant contributory fault %
- other parties’ fault % (if applicable)
- a short scenario label (e.g., “Assumed 15% claimant fault”)
This makes it much easier to compare outputs after you update facts or settlement assumptions.
Common pitfalls
Entering claimant fault as if it were defendant fault.
RCW 4.22.005 focuses on contributory fault chargeable to the claimant, which diminishes the claimant’s compensatory damages.Applying reduction to the wrong figure.
The statute is about diminishing compensatory damages. If the tool separates categories, ensure your “base” input is what the tool treats as compensatory damages.Fault totals that don’t match the calculator’s workflow.
If DocketMath expects fault percentages to sum to a particular total (commonly 100%) and you enter mismatched values, outputs can become internally inconsistent. Normalize your scenario to the tool’s expected format.Over-interpreting a single numeric output.
DocketMath gives a model result based on the inputs you provide. It is not a substitute for evidence-based fault determination.Assuming a special claim-type sub-rule exists without checking the rule set.
For this Washington setup, no claim-type-specific sub-rule was found, so the calculator reflects the general/default proportional-contributory-fault behavior.Running multiple what-ifs without tracking versions.
Even small input changes can materially affect results. Save scenario labels and the input percentages so you can compare reliably.
Try it
- Open the calculator at /tools/damages-allocation
- Set jurisdiction to Washington (US-WA).
- Enter:
- your base compensatory damages amount
- claimant contributory fault %
- other party fault % (as applicable)
- Click Calculate
- Compare at least:
- Scenario A: lower claimant fault (e.g., 10%)
- Scenario B: midpoint claimant fault (e.g., 25%)
- Scenario C: higher claimant fault (e.g., 40%)
As you compare results, focus on how the output changes with claimant fault percentage—reflecting the proportional reduction concept in RCW 4.22.005.
Related reading
- How to calculate Damages Allocation in Philippines — Full how-to guide with jurisdiction-specific rules
- Worked example: Damages Allocation in Philippines — Worked example with real statute citations
- Inputs you need for Damages Allocation in Philippines — Input checklist with sourcing guidance
Run the numbers for your matter against the verified rule for this jurisdiction.
Run the allocation