Statute of Limitations for Written Contract in Washington

7 min read

Published April 8, 2026 • By DocketMath Team

Statute of Limitations for Written Contract in Washington

Overview

Washington’s default statute of limitations for a written contract claim is 5 years. For this jurisdiction page, the controlling general citation provided is RCW 9A.04.080, and no claim-type-specific sub-rule was identified for written contracts, so the 5-year period is the baseline rule to use.

That means a lawsuit based on a written agreement must usually be filed within 5 years of the date the claim accrues. In practical terms, the clock often starts when the other side first breaches the contract, misses a payment, or otherwise fails to perform as promised under the written terms.

A few quick points make this easier to use in real life:

  • The 5-year period is the default for this reference page.
  • The filing deadline is about when the court case is started, not when demand letters go out.
  • The accrual date can change the deadline significantly, especially if the contract uses installment payments, a maturity date, or a written acceleration clause.

Note: This page uses the jurisdiction data provided for Washington: 5 years under RCW 9A.04.080 as the general/default period for written contract claims.

Limitation period

The limitation period for a written contract claim in Washington is 5 years. If a written agreement is breached, the claimant generally has 5 years from accrual to file suit.

Here’s the practical way to think about the timeline:

ItemWhat it meansEffect on deadline
Written contractA contract reduced to writingUses the 5-year default period
Accrual dateThe date the claim becomes enforceable, often the breach dateStarts the limitations clock
Filing dateWhen the complaint is filed in courtMust fall within the 5-year period
Late filingFiling after the deadlineThe claim may be time-barred

Common timing examples

  • One missed lump-sum payment: the clock often starts on the payment due date.
  • Installment contract: each missed installment can trigger its own limitations period.
  • Accelerated debt or payment obligation: the deadline may run from acceleration if the contract and facts support it.
  • Completion-based contract: the clock may start when the promised work should have been completed and was not.

For reference-page use, the key question is usually: “Is the contract written, and when did the breach occur?” If the answer is yes and the breach date is known, the 5-year period is the number most users need to calculate the deadline.

A few checks help avoid mistakes:

Key exceptions

No claim-type-specific sub-rule was found for this Washington written-contract reference page, so the 5-year general period is the default rule. Even so, the real deadline can shift based on the contract’s structure and the facts that trigger accrual.

Here are the most common situations that change how the 5-year period is applied:

SituationWhy it mattersTypical impact on the deadline
Installment contractEach missed payment may be a separate breachDifferent deadlines for different missed payments
Acceleration clauseThe full balance may become due after defaultDeadline may run from acceleration, not the first missed installment
Written extension or amendmentThe parties may alter payment or performance timingAccrual may move to the new deadline
Tolling eventA legal rule may pause the clockThe filing window may extend
Acknowledgment or partial paymentCan affect how the claim is treated in some settingsMay change the timing analysis

A practical example helps:

  • A written services contract requires completion by June 1, 2021.
  • The work is not completed, and the failure to perform is clear on that date.
  • Under the 5-year rule, a lawsuit generally must be filed by June 1, 2026.

If instead the contract required monthly payments and the debtor missed payments over several years, each missed payment could produce its own limitations analysis. That means one missed installment might still be timely while an older one is already outside the 5-year window.

Warning: Do not assume the clock starts on the contract signing date. For many written contracts, the limitations period starts when the breach occurs or when performance becomes due, not when the agreement was first executed.

Statute citation

The cited Washington statute for this reference page is RCW 9A.04.080, with a 5-year general limitations period. That is the statute citation to use for this calculator page’s default written-contract timing rule.

For a reference page like this, users usually need three pieces of information:

  1. The jurisdiction
  2. The claim type
  3. The date the cause of action accrued

In Washington, this page is set up to return the 5-year general/default result for a written contract claim. The citation should be displayed in a way that helps users verify the source rule quickly.

What the statute citation does for the calculator

The statute citation is not just a label. It anchors the calculator’s output to a specific legal time period so users can see:

  • the governing period,
  • the reference authority, and
  • the deadline generated from the input date.

When the user enters the accrual date, the calculator subtracts nothing; it counts forward 5 years from that date to estimate the filing deadline. If the contract has multiple breaches, users may need to test each one separately.

For example:

  • Accrual date: April 15, 2022
  • Period: 5 years
  • Estimated deadline: April 15, 2027

If a user enters a later breach date, the output moves later. If they enter an older date, the deadline moves earlier and may already be expired.

Use the calculator

Use DocketMath’s statute of limitations calculator to estimate the filing deadline from the written contract breach date. The tool converts the 5-year Washington period into a concrete deadline so users can see whether a claim appears timely.

What to enter

Most users will need:

  • Jurisdiction: Washington
  • Claim type: Written contract
  • Accrual date: The date the breach happened or the obligation became due

How the output changes

Input changeResult
Earlier accrual dateEarlier deadline
Later accrual dateLater deadline
Different breach dateDifferent filing window
Multiple missed paymentsSeparate deadline analysis may be needed
Corrected contract dateNo change unless it affects accrual

Best practice workflow

  1. Pull the signed contract and any amendments.
  2. Identify the first date performance was due and not provided.
  3. Enter that date into DocketMath.
  4. Compare the calculated deadline against the planned filing date.
  5. Re-run the calculation for any separate breaches or installment defaults.

For teams handling collections, vendor disputes, or service agreements, this kind of deadline check prevents filing a claim that is already outside the 5-year period. It also helps prioritize older disputes before the limitations period runs.

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.

Related reading