How to run Settlement Allocator in DocketMath for Washington

Step-by-step

Run this scenario in DocketMath using the Settlement Allocator calculator.

This guide walks you through running Settlement Allocator in DocketMath for Washington (US-WA), using jurisdiction-aware rules grounded in Washington’s general statute of limitations (SOL). The tool helps you allocate settlement components while applying a default SOL framework—so your results reflect Washington’s baseline timing rules rather than assumptions from other jurisdictions.

1) Start at the Settlement Allocator tool

Open the calculator interface by going to /tools/settlement-allocator.

If your workspace includes calculator presets, choose the one intended for settlement allocation. If you don’t see a matching preset, create one (if prompted) so your setup is repeatable.

2) Select the jurisdiction: Washington (US-WA)

In the jurisdiction selector, choose:

• **Washington (US-WA)

With Washington selected, DocketMath will use Washington’s default SOL timing for calculations that depend on SOL assumptions.

Washington default SOL (used here):

• General SOL Period: 5 years
• Statutory basis: RCW 9A.04.080

Important clarity: No claim-type-specific sub-rule was found for this allocator workflow. That means the 5-year general/default period is the rule applied in this context—rather than switching to a different SOL period for specialized claim categories. If DocketMath later offers a claim-type-specific override, you should follow what the tool explicitly provides.

3) Enter the settlement inputs

Settlement Allocator typically relies on several inputs. Exact labels may vary slightly in the UI, but these are the common fields:

• Settlement date (sometimes called allocation effective date)
• Relevant event date (often the date your workflow tracks as accrual/claim start or damages start—use the date that matches your organization’s definition)
• Amount(s) to allocate (for example, total settlement value)
• Allocation categories (if the UI allows you to break the total into components)

Keep your date definitions consistent

If you’re running multiple scenarios (for example, comparing different assumptions), keep the meaning of “relevant event date” consistent across runs. Only change the specific input you intend to test.

4) Confirm how SOL is being used by the tool

In the UI, look for text or sections that reference SOL, timing windows, eligibility thresholds, or “within/outside” timeframes. With Washington (US-WA) selected, DocketMath should treat the SOL baseline as:

• 5 years under RCW 9A.04.080

When you update date fields, outputs that depend on timing should refresh automatically—commonly including:

• Whether a component is treated as within or outside the SOL window (or how the allocator weights categories)
• Derived “time since event” values used to adjust allocation outcomes

5) Review the allocator outputs

After you run the calculation, review what DocketMath displays. Typical output areas include:

• Allocated amounts per category
• Any SOL-related flags or timing indicators
• Summary totals (for example, verifying the allocations sum to the settlement total)

Sanity-check the timing effect

If you move the relevant event date backward by more than 5 years, you should expect allocation results to shift in the direction implied by the tool’s SOL logic. If you move it forward so it falls within 5 years, the results should reflect the “within the general/default SOL period” behavior.

Treat the results as computation outputs and decision-support metrics. They are not a substitute for legal analysis or advice for your particular matter.

6) Export or capture the results for review

To keep your work auditable, export or capture results if the tool offers:

• CSV/PDF download
• Copy-to-clipboard summaries

Also, record the exact input dates used—especially the relevant event date—so you can clearly explain why allocations changed between runs.

Common pitfalls

Settlement allocation workflows can produce surprising results when dates and SOL assumptions aren’t aligned. Watch for these issues when running Washington (US-WA) in DocketMath.

The Washington configuration for this workflow should use the general/default 5-year period tied to RCW 9A.04.080.
No claim-type-specific sub-rule was found for this allocator workflow, so you should not swap in a different SOL period unless DocketMath explicitly provides a claim-type override.

If one scenario uses an “accrual date” and another uses a “discovery date,” the computed timing may cross the 5-year boundary—changing results even if your settlement amounts and categories stay the same.

Date math can be strict. Two date ranges that look similar can land on opposite sides of the cutoff depending on how elapsed time is computed.

DocketMath’s allocator output is a rule-based calculation based on your inputs and jurisdiction selection. Use it to support your internal analysis—not as legal advice.

If the total settlement amount stays constant but you adjust only the relevant event date, allocations may shift non-linearly if SOL-sensitive weighting changes near the boundary.

Pitfall to avoid: If your settlement date is earlier than your relevant event date, the tool may still compute a result, but the inputs can be internally inconsistent for your intended timeline. Always verify date ordering before relying on outputs.

Try it

To validate your Washington setup, run two scenarios in DocketMath with the same amounts and categories. Only change the relevant event date so you can isolate how SOL timing affects the allocator outputs.

Open the Settlement Allocator calculator and follow the steps above: Run the calculator.

Scenario A: Within the 5-year default SOL window

1. Choose **Washington (US-WA)
2. Enter a relevant event date that is less than 5 years before the settlement date
3. Keep the total settlement amount and allocation categories the same
4. Run the calculation
5. Capture/export the allocation results

Scenario B: Outside the 5-year default SOL window

1. Keep everything the same as Scenario A
2. Update only the relevant event date
3. Set it to more than 5 years before the settlement date
4. Run again
5. Compare:

   • allocated amounts per category
   • any SOL timing indicators or flags

If DocketMath applies SOL status to allocation weighting, you should see noticeable differences between the scenarios near the 5-year threshold.

For quick access, use: /tools/settlement-allocator.

Related reading

• Settlement Allocator Guide for Alabama
• Settlement Allocator Guide for Arizona
• Settlement Allocator Guide for Colorado