Statute of repose in Washington

Direct answer

Run this scenario in DocketMath using the Statute Of Limitations calculator.

Washington’s statute of repose (using the default rule provided) is 5 years under RCW 9A.04.080. That means a claim can be time-barred if it is not brought within 5 years from the statute’s triggering event, even if relevant facts are discovered later.

This Washington overview treats RCW 9A.04.080 as the general/default period because no claim-type-specific statute-of-repose sub-rule was found in the materials you provided. Practically, that means the 5-year baseline is what DocketMath should test unless your claim category has a different, more specific repose rule.

What you need to know

A statute of repose acts like a hard cutoff. Even if the facts only become clear years later, the repose clock can still expire and bar the claim.

To use DocketMath effectively for Washington (US-WA), you’ll generally need:

• Start date (trigger date): the event date that starts the repose clock in your situation
• A decision on strategy: for example, whether you want the latest safe filing date based on the chosen trigger date

Default rule used here (important)

Based on the jurisdiction data you provided:

• General SOL / repose period: 5 years
• General statute/citation: RCW 9A.04.080
• Claim-type-specific statute-of-repose sub-rule: not found in the provided materials

So the calculator logic should apply the default 5-year period to the repose trigger date you supply.

Inputs that change the outcome

These are the main factors that shift the “last day to file” result:

• Trigger date accuracy
  Since the rule is exactly 5 years, changing the event date by weeks/months typically shifts the computed deadline by a similar amount.

• Repose vs. limitations framing
  DocketMath’s statute-of-limitations tool is designed for timing analysis. If repose is implicated, you still use the tool to compute an end-date, but you must make sure you’re applying it to the repose trigger date concept rather than a discovery-based start.

• Tolling assumptions (verify carefully)
  Tolling can interact differently with limitations and repose. This post is not legal advice, but it will help you surface which inputs you need to verify.

Step-by-step

Follow these steps to compute a Washington 5-year repose deadline using DocketMath (jurisdiction-aware, US-WA), applying RCW 9A.04.080 as the general/default period.

1) Confirm you’re using the right clock

Start by identifying what counts as the trigger date for the repose clock in your situation. Ask:

• What was the relevant event date?

  • completion/termination of a project or activity?
  • final act tied to the statutory trigger?
  • another statutory-defined event?

If you’re not sure which date qualifies, don’t guess blindly—capture multiple plausible trigger candidates and compute deadlines for each.

2) Gather the key date

You need one anchor date for the math:

• **Trigger date (YYYY-MM-DD)

Example (illustrative only):

• Trigger date: 2021-06-15
• Repose period: 5 years
• Citation baseline: RCW 9A.04.080 (general/default period)

3) Open DocketMath

Use the calculator from the primary CTA:

• /tools/statute-of-limitations

Then select:

• **Washington (US-WA)

4) Enter the trigger date and apply the default 5-year rule

In DocketMath, enter:

• Start date = your trigger date
• Period = 5 years (general/default rule)

Because no claim-type-specific statute-of-repose sub-rule was found in the materials provided, do not switch to a different repose length unless your claim category clearly fits another specific rule outside this default.

5) Read the output as a “latest filing date”

Use the tool’s computed end/expiration date to determine your deadline:

• If your filing is after the computed date, the default 5-year repose window may have passed.
• If you’re on or before the computed date, you’re within the default window (still verify other deadlines and procedural requirements).

Practical tip: Save the calculator output (or screenshot it) for your internal timeline so you can update quickly if the trigger date changes.

6) Run “what-if” scenarios (recommended)

If multiple trigger dates are plausible, calculate more than one deadline:

• earliest documented candidate trigger date
• latest documented candidate trigger date
• best-documented candidate trigger date

This produces a deadline range and helps you prioritize which facts to confirm first.

Key statutes and citations

Baseline rule used in this Washington overview

• RCW 9A.04.080 — General statute period: 5 years

Per your jurisdiction data:

• The calculator/testing approach uses RCW 9A.04.080 as the general/default period.
• No claim-type-specific statute-of-repose sub-rule was found, so the post applies the 5-year baseline unless a different, more specific statute applies to your claim category.

How to document the rule in your workflow

When you track timelines, capture:

• Statute: RCW 9A.04.080
• Period: 5 years
• Trigger date used: (your event/trigger date)
• Output end/expiration date: (DocketMath result)

This helps avoid a common error: accidentally using a discovery-based start date when repose is involved.

Common pitfalls

1. Using discovery timing as the clock start
   Repose is often keyed to an outside event window, not when you discovered the issue.

2. Treating repose like a limitations analysis
   Limitations analysis can be knowledge-based; repose commonly is not.

3. Misidentifying the trigger date
   “Start” can mean different things depending on the underlying facts. A project start date vs. completion date can materially change the outcome.

4. Assuming there is only one deadline
   Multiple statutory clocks can overlap depending on the cause of action and claims asserted. It can be worth calculating multiple timing theories, not just one.

5. Skipping updates when key dates change
   If you’re close to the edge of the window, even a date correction can shift the result.

Pitfall to avoid: If the trigger date is uncertain, treat a single computed deadline as a tentative placeholder. Compute a range and update once the facts are confirmed.

Run the numbers

Use the 5-year default under RCW 9A.04.080 to compute an expiration date from your chosen trigger date.

Example A: Single trigger date calculation

• Trigger date: 2021-06-15
• Repose period: 5 years (RCW 9A.04.080)
• Expiration date: 2026-06-15

How to interpret:

• If the claim is filed after 2026-06-15, the default 5-year repose window likely has passed.

Example B: Multiple plausible trigger dates

Assume two trigger candidates:

• Candidate 1: 2021-01-10 → expiration 2026-01-10
• Candidate 2: 2021-11-05 → expiration 2026-11-05

Result:

• The deadline shifts by about 10 months depending on which trigger date the statute uses for your situation.

Quick change-impact table (general rule)

To run these in DocketMath:

• Jurisdiction: **Washington (US-WA)
• Period: 5 years
• Start date: the trigger date you’re testing

Related reading

• Choosing the right statute of limitations tool for Vermont — How to choose the right calculator
• Statute of limitations in Singapore: how to estimate the deadline — Full how-to guide with jurisdiction-specific rules
• Choosing the right statute of limitations tool for Connecticut — How to choose the right calculator