How to run Treble Damages in DocketMath for Washington

Step-by-step

Run this scenario in DocketMath using the Treble Damages calculator.

This guide walks you through running Treble Damages in DocketMath for Washington (US-WA) using jurisdiction-aware defaults—specifically the general statute of limitations (SOL) period of 5 years under RCW 9A.04.080. There is no claim-type-specific sub-rule identified for this walkthrough, so DocketMath should use the general/default 5-year SOL period for this run in Washington.

1) Open the Treble Damages calculator (Washington)

Start here: /tools/treble-damages

Once you’re on the tool page, confirm the jurisdiction context is set to Washington (US-WA). If DocketMath supports jurisdiction selection in the UI, pick US-WA before entering numbers.

2) Enter the damages base amount

In DocketMath’s treble-damages calculator, you’ll typically supply:

• Base damages (the “single damages” amount before trebling)
• Any additional inputs the calculator requests (often dates or timing details)

Use your best available figures for the base damages (for example, the amount of actual damages you’re treating as the starting point). The calculator’s treble output will change directly with this number.

How the output changes

• Increase base damages → treble amount increases proportionally (commonly base × 3).
• Reduce base damages → treble amount decreases proportionally.

3) Set the relevant dates (for SOL timing)

To apply SOL timing in Washington, you’ll need to provide the date context DocketMath expects—commonly:

• Accrual date (or event/incident date)
• Filing date (or claim date)

Because Washington’s default SOL is 5 years under RCW 9A.04.080, your treble-damages scenario should be evaluated against that 5-year window under the tool’s default framework.

Washington default SOL rule used in this run

• General SOL period: 5 years
• General statute: RCW 9A.04.080
• Claim-type-specific sub-rule: None identified (so the tool should use the general/default 5-year period)

4) Run the calculator

After you enter:

• Base damages
• Dates needed to evaluate the limitation window

…click Calculate (or the tool’s equivalent).

5) Review the SOL/timing result and the treble amount

DocketMath should provide outputs in at least two areas:

1. Treble damages calculation
2. Whether the timing is within the applicable SOL window (using the 5-year default in Washington)

What to look for in the output

Use a quick checklist:

6) Make scenario adjustments (sensitivity testing)

Treble damages multiply the base number; SOL timing controls whether the scenario is timely under the default framework. That means small input changes can materially alter what you learn from the run.

Try these adjustments to see how the output changes:

• Scenario A (base damages change):

  • Raise base damages by 10%
  • Expect treble damages to rise by roughly 10%

• Scenario B (date shift change):

  • Move the filing date forward/backward by 30–90 days
  • Watch the SOL outcome toggle around the 5-year boundary (if your dates are near the limit)

This approach helps you understand which part of the tool output is driven by trebling (math based on base damages) versus timing (the SOL window).

Common pitfalls

Treble damages calculations are straightforward mathematically, but Washington timing inputs often introduce avoidable errors. Watch for these issues when running DocketMath for US-WA.

• missing a required input
• using a stale rate or rule
• ignoring calendar or holiday adjustments
• skipping documentation of assumptions

Misapplying the default SOL when a special rule is at stake

DocketMath will use the general/default 5-year SOL for this run based on RCW 9A.04.080 because no claim-type-specific sub-rule was identified. If your theory depends on a different limitations rule, the tool’s SOL result could be misleading in practice.

Confusing “event date” with “accrual date”

Many tools ask for a date that functions like “accrual.” If you enter:

• the wrong trigger date, or
• a date that doesn’t match how the calculator defines accrual,

then the 5-year window calculation may be off.

Forgetting to validate units and formats

Date formatting errors (month/day vs. day/month) can shift timelines by months, pushing you across the 5-year threshold. Before running:

Assuming treble damages only depend on the base number

Even if trebling is just 3× base, the overall “run” may still depend on timing results. If DocketMath shows an SOL risk/outcome outside RCW 9A.04.080’s 5-year window, the scenario output should be treated as a timing feasibility model, not an outcome guarantee.

Try it

Use the primary calculator and run a quick test with a simple set of assumptions. Then tweak one variable at a time.

Open the Treble Damages calculator and follow the steps above: Run the calculator.

If an assumption is uncertain, document it alongside the calculation so the result can be re-run later.

Quick “first run” checklist

What you should see after the run

Under this Washington default framework:

• Treble damages output should scale with your base damages (commonly ×3).
• SOL timing evaluation should apply a 5-year lookback window tied to RCW 9A.04.080.
• If the tool indicates timing outside the 5-year period, that should affect how you interpret the scenario risk under the default framework.

If your scenario is near the 5-year mark, do a sensitivity check:

This is often the fastest way to validate that your date inputs are wired correctly.

Related reading

• Treble Damages Calculator Guide for Alabama
• Treble Damages Calculator Guide for Arizona
• Treble Damages Calculator Guide for Colorado