Statute of Limitations for Written Contract in District of Columbia

Overview

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

In the District of Columbia, the statute of limitations (SOL) for a written contract claim is 3 years under D.C. Code § 23–113(a)(1).

For written contracts, D.C. applies a general/default limitation period rather than a separate, written-contract-specific clock. In other words, when your claim is based on a written agreement, you generally start from the same baseline period that applies to covered civil actions under § 23–113(a)(1).

This page is designed to be practical: it explains how the SOL timeline generally works in D.C., what inputs matter for your calculation, and how to use DocketMath to estimate the likely deadline. It is not legal advice, and SOL outcomes can change based on details such as when the claim accrued and whether tolling (pauses/extensions) applies.

Limitation period

The SOL period for written contract claims in D.C. is 3 years.

What the “3 years” generally means

Under D.C. Code § 23–113(a)(1), covered actions must typically be filed within 3 years. A practical way to think about the timeline is:

• Choose a starting date (commonly the breach date or the accrual date—the date the claim is deemed to have accrued based on your facts).
• DocketMath adds 3 years to that starting date.
• The result is the latest target filing date within the limitations window (before considering potential tolling or accrual arguments).

Because accrual rules and tolling doctrines can vary with the facts, DocketMath’s role is to translate your timeline inputs into a concrete deadline; the legal rules determine what date should be used for “accrual” in your situation.

Quick timeline example (how the math changes)

Assume a written contract breach occurs on:

• January 15, 2026
• SOL period: 3 years (per D.C. Code § 23–113(a)(1))

A straightforward calculation would target a latest filing date around:

• January 15, 2029 (subject to how accrual is treated in your specific circumstances)

If your starting date shifts by 30 days, the deadline shifts by about the same amount—so accuracy in the date you input matters.

Inputs you should prepare

To calculate a SOL deadline with DocketMath, gather these facts first:

• Breach date or your best estimate of the claim accrual date
• Any facts that may affect accrual
• Possible tolling events (if applicable)
• Your intended filing date (to compare against the computed deadline)

Key exceptions

D.C. SOL calculations can change when doctrines like tolling or other statutory adjustments apply. That’s where a “3-year” baseline may become longer in practice (or, in certain circumstances, the effective timeline may differ depending on accrual arguments).

Tolling: when the clock may pause or extend

Common tolling-related scenarios can include:

• Fraudulent concealment, where the defendant’s conduct prevents timely discovery of the claim
• Legal disabilities that can delay when the clock starts
• Contractual or procedural events that may affect timing in specific ways

Whether a tolling doctrine applies depends heavily on facts—especially what was known, when it was known, and what actions were taken during the relevant period.

Baseline vs. exception structure

Keep this distinction clear:

• Baseline SOL: 3 years for covered civil actions under **D.C. Code § 23–113(a)(1)
• Exception/tolling: may change

  • when the clock starts (accrual timing), and/or
  • whether time pauses, and/or
  • the effective deadline based on the modeled timeline

Practical checklist for exceptions

Before treating any deadline as fixed, confirm:

If you can answer these questions with dates (even approximate ones), your DocketMath calculation becomes much more useful.

Statute citation

The general/default SOL period for covered civil actions in the District of Columbia is 3 years under:

• D.C. Code § 23–113(a)(1) (stating the period as 3 years)
  Source: https://law.justia.com/codes/district-of-columbia/2014/division-iv/title-23/chapter-1/section-23-113/

How to use this citation in your workflow

When documenting your timeline:

• Note that you’re using the 3-year window because your claim falls under D.C. Code § 23–113(a)(1).
• Tie your starting date (breach/accrual) to the facts you’re using.
• Apply the 3-year period to generate the target filing deadline.

This keeps your reasoning consistent with the governing SOL rule while you evaluate whether any exceptions might apply.

Use the calculator

Use DocketMath’s Statute of Limitations Calculator here: /tools/statute-of-limitations.

What you’ll do in DocketMath

In the calculator flow, you will typically:

1. Select District of Columbia (US-DC).
2. Enter your starting date (commonly the breach/accrual date you’re using).
3. Review the computed 3-year deadline associated with D.C. Code § 23–113(a)(1).
4. If needed, adjust the starting date to match your best view of the accrual date.

You can access the calculator at: /tools/statute-of-limitations.

How outputs change based on inputs

DocketMath’s deadline is mainly driven by:

• Starting date

  • Moving it forward generally moves the deadline forward.
  • Moving it backward generally moves the deadline earlier.
• **Tolling-related adjustments (if you model them)

  • If tolling is applicable and you enter the appropriate dates/events, DocketMath can reflect an extended effective deadline based on your timeline inputs.

To keep the calculation defensible, you may want to:

• test an earliest plausible accrual date for a conservative deadline, and/or
• test a most favorable plausible accrual date to stress-test your position

Quick “sanity check” before relying on the result

After you run the calculator:

• Does the deadline land roughly 3 years after your selected starting date (before any tolling adjustments)?
• Did you enter the correct date format and correct starting event?
• Are you confident the selected starting date matches how your facts support “accrual”?

Then save your input dates so you can explain exactly how the deadline was generated.

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