Deadline Calculator Guide for Washington

What this calculator does

Run this scenario in DocketMath using the Deadline calculator.

DocketMath’s Deadline Calculator for Washington (US-WA) helps you compute key time deadlines under Washington law using the RCW 9A.04.080 lookback/limitations framework.

At a high level, the calculator:

• Takes a start date (typically when the conduct occurred or when the relevant clock begins for the specific scenario you’re analyzing).
• Applies the Washington statute of limitations periods reflected in your chosen option (defaulting to the general 5-year period).
• Outputs a deadline date—the last day the action/filing must be made under the selected limitation period.

Washington’s baseline rule for limitations in this space is:

• 5 years under RCW 9A.04.080
• Plus specific shorter “exception” periods:

  • 3 years under RCW 9A.04.080(1)(j) (labeled as exception V1 in this guide)
  • Another 3-year variant referenced as exception V2 (per your jurisdiction data)

When to use it

Use the DocketMath deadline calculator for Washington when you’re trying to answer questions like:

• “Given a known date of the incident, what is the outer deadline under RCW 9A.04.080?”
• “How does the deadline change if exception V1 (RCW 9A.04.080(1)(j)) applies instead of the general 5-year rule?”
• “If the scenario matches exception V2, what would the last permissible date be under the shortened 3-year period?”

Good fits

Check these boxes if they describe your workflow:

When you should slow down

The calculator is best for straightforward deadline computation. You should be extra cautious if:

• The “clock start” is uncertain (for example, different interpretations of when the relevant event occurred).
• You’re unsure whether the conduct fits RCW 9A.04.080(1)(j) (exception V1) or another 3-year variant (exception V2).
• There are procedural deadlines layered on top of limitation deadlines (the calculator focuses on the limitations period you select, not every subsequent procedural requirement).

Step-by-step example

Below is a practical walk-through using the Washington limitations periods from RCW 9A.04.080.

Example: Compare 5-year vs. 3-year deadlines

Assume:

• Start date (clock start): January 15, 2021
• You want the “last day” under each limitation option.

Step 1: Choose the limitation period

In DocketMath, you’ll use the tool at /tools/deadline and select the period corresponding to your scenario:

Step 2: Enter the start date

Enter January 15, 2021 as the calculator’s start date.

Step 3: Run each scenario

Now compute three outcomes:

• General 5-year (RCW 9A.04.080):
  Deadline = January 15, 2026

• Exception V1 (RCW 9A.04.080(1)(j), 3 years):
  Deadline = January 15, 2024

• Exception V2 (3 years):
  Deadline = January 15, 2024

Step 4: Interpret the results in plain language

Here’s what the comparison tells you immediately:

• Selecting the general rule pushes the deadline out by 2 additional years compared with the 3-year exceptions.
• The two 3-year options (V1 and V2) produce the same calendar deadline in this simple example because both are 3 years according to your jurisdiction data.

Common scenarios

Real-world deadline work usually involves one of a few patterns. Use the lists below to map your situation to the calculator settings.

Scenario A: You know the event date and want the outer limit (5-year)

Typical use case:

• You’re looking for the general limitation deadline under RCW 9A.04.080 (5 years).

Calculator setting:

• Choose the 5-year option tied to RCW 9A.04.080.

What to check before computing:

• Confirm the date you’re entering is the intended clock start for your analysis.
• If you’re preparing a timeline for internal review, document the exact date you used.

Scenario B: The facts appear to fit RCW 9A.04.080(1)(j) (exception V1)

Typical use case:

• Your fact pattern suggests the shorter period may apply under RCW 9A.04.080(1)(j).

Calculator setting:

• Select exception V1 (3 years).

How output changes:

• The deadline becomes 3 years from the clock start instead of 5 years.

Scenario C: Another 3-year pathway (exception V2)

Typical use case:

• Your process flags a “3-year variant” as exception V2 based on internal categorization or prior determinations.

Calculator setting:

• Select exception V2 (3 years).

How output changes:

• The deadline becomes 3 years from the clock start.
• In a basic calendar subtraction, it will align with any other 3-year option (like V1) producing the same end date.

Scenario D: You’re comparing deadlines to prioritize next steps

Typical use case:

• You need to know whether there’s still time under multiple possible limitation periods.

Calculator workflow:

• Run all applicable options (5-year, V1, V2) and compare dates.
• Create a “latest possible” vs. “earliest risk” view.

To make that comparison systematic, use this checklist:

Tips for accuracy

Small input choices and date-handling conventions are the difference between a reliable deadline and a misleading one. Follow these accuracy controls when using DocketMath’s Washington deadline calculator.

1) Lock down your “clock start” date definition

Before you type anything into the calculator:

• Write down your intended start-date rule in one sentence in your notes.
• Use the same rule consistently across every computation in the matter.

Common approach:

• If your timeline is fact-based, use the event date you’re confident is the relevant start point.
• If you’re using an operational convention (for example, “date of discovery”), document that convention and ensure it aligns with how you selected RCW 9A.04.080 vs. exceptions.

2) Be explicit about which statutory period you selected

DocketMath’s output changes based on the limitation period option you choose. Use this quick mapping:

• General rule: 5 years — RCW 9A.04.080
• Exception V1: 3 years — **RCW 9A.04.080(1)(j)
• Exception V2: 3 years — labeled as V2 in your jurisdiction data

3) Use a “compare then decide” workflow

If there’s any uncertainty about whether V1 or V2 applies, run all plausible options and compare results. That gives you:

• A best-case (later) deadline under 5 years
• A worst-case (earlier) deadline under a 3-year exception

4) Validate against your calendar before trusting the date

After you generate the deadline:

• Check the month/day visually.
• If you’re working with year boundaries (leap years, end-of-month behavior), confirm the date rolled correctly.
• If the deadline falls on a weekend/holiday, decide how your workflow treats “last permissible day.” (The calculator focuses on limitations periods; it doesn’t automatically resolve procedural “business day” effects.)

5) Keep an audit trail in your notes

You can make your deadline computations more defensible in reviews by recording:

• Start date you used
• Limitation option selected (General / V1 / V2)
• Calculator output deadline date
• Any reason for choosing the exception (even a short one)

Sources and references

Start with the primary authority for Washington and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

• WA Rev. Code § 2.06.030

Related reading

• Why deadlines results differ in Canada — Troubleshooting when results differ
• Worked example: deadlines in New York — Worked example with real statute citations
• Deadlines reference snapshot for New Hampshire — Rule summary with authoritative citations