Statute of Limitations for Oral Contract in District of Columbia

6 min read

Published April 8, 2026 • By DocketMath Team

Overview

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

For an oral contract in the District of Columbia, the statute of limitations (SOL) is 3 years under D.C. Code § 23–113(a)(1).

In practice, this means a plaintiff generally must file a lawsuit within 3 years after the legal “clock” starts running—otherwise the claim may be time-barred. DocketMath’s statute-of-limitations calculator can help you model the deadline by using key dates you choose (such as the date of breach or another accrual/trigger date).

Note: This page covers the general/default SOL rule for oral contracts in D.C. No additional oral-contract-specific sub-rule was identified beyond the general provision cited below.

Limitation period

The general SOL period for covered contract claims in the District of Columbia is 3 years.

  • General Statute: **D.C. Code § 23–113(a)(1)
  • General SOL Period: 3 years

What that means for an oral contract claim

For many contract disputes, the SOL is measured from the date the claim accrues. Accrual is often tied to events such as:

  • the breach (for example, nonpayment or failure to perform), or
  • a time when the plaintiff knew or reasonably should have known about the facts underlying the injury connected to the breach (depending on how accrual is treated in your specific situation).

Because the exact “clock start” can depend on accrual facts, DocketMath focuses on turning your chosen start date into a concrete last day to file deadline so you can plan and compare scenarios.

Inputs you’ll need for DocketMath

To get a usable output, you’ll typically enter:

  • Jurisdiction: United States — **District of Columbia (US-DC)
  • Claim type / basis: contract (treated under the general rule when no special oral-contract sub-rule is identified)
  • Start date for the SOL clock: the date you want to use for when the claim “accrues” for purposes of the timeline you’re modeling

DocketMath then calculates:

  • Last day to file (based on the 3-year period), and
  • a timeline window you can use to sanity-check deadlines and documentation.

How the output changes when dates change

The deadline is sensitive to the start date you provide:

  • If you move the SOL start date by 30 days, the last day to file generally shifts by about 30 days as well (because the period is a fixed 3 years).
  • If you move the start date by 1 year, the deadline generally shifts by about 1 year, preserving the same 3-year structure.

If you have more than one plausible accrual/breach date (for example, different performance dates or payment refusals), DocketMath lets you run multiple scenarios so you can compare deadlines side-by-side.

Key exceptions

The 3-year rule above is the baseline, but SOL results can change based on exception doctrines, including doctrines that pause (toll) the clock or otherwise extend the filing deadline.

Tolling concepts to keep on your radar

Even though this page focuses on the general rule in D.C. Code § 23–113(a)(1), common categories of exceptions that can affect SOL calculations include:

  • Tolling due to incapacity (for periods when a person is legally unable to sue)
  • Equitable tolling (for situations where a plaintiff is prevented from filing despite diligence)
  • Fraudulent concealment (where the defendant’s actions keep the plaintiff from discovering necessary facts)
  • Accrual-related timing details (where installment structures, continuing obligations, or performance triggers can affect when the claim accrues)

Important: Exception application is fact-specific. Don’t treat exceptions as automatic. Use DocketMath for timeline modeling, and then verify whether any exception could realistically apply based on the details of your situation.

Don’t assume tolling just because a deadline passed

Warning: Do not assume tolling automatically applies because a deadline was missed. Whether the clock pauses or extends depends on the legal standard and the facts.

No special oral-contract SOL sub-rule found

For this jurisdiction and claim category, you should treat D.C. Code § 23–113(a)(1) as the default. That means you should not build your timeline on a separate “oral contract” SOL term unless you find a specific statute or binding authority stating one.

Statute citation

The general statute of limitations for the relevant category is:

  • D.C. Code § 23–113(a)(1)3 years

Codification/reference source:
https://law.justia.com/codes/district-of-columbia/2014/division-iv/title-23/chapter-1/section-23-113/

For timeline planning, this citation is the backbone: 3 years is the baseline SOL length reflected in DocketMath’s calculator for District of Columbia contract claims under the general/default rule.

Use the calculator

Run your timeline in DocketMath here: /tools/statute-of-limitations

Step-by-step

  1. Open /tools/statute-of-limitations
  2. Select:
    • Jurisdiction: **District of Columbia (US-DC)
  3. Set the basis to contract (for an oral contract treated under the general rule where no special oral-contract sub-rule is identified)
  4. Enter the SOL start date (the date you’re using as the clock start/accrual date)
  5. Review:
    • the calculated deadline (last day to file), and
    • the results for any additional scenarios you run

How to choose the start date in practice

If you have multiple relevant dates (for example, date of partial payment, date performance was due, date of complete nonperformance), consider running multiple scenarios. The goal is to see how sensitive the deadline is to the accrual date you select.

Checklist to help you pick a start date:

Practical note: This is a planning tool, not legal advice. If you’re unsure about the accrual trigger for your facts, consider getting legal guidance.

Example timeline (illustrative)

If you set the SOL start date as March 1, 2022, DocketMath applies the 3-year period under D.C. Code § 23–113(a)(1). The modeled deadline would land around March 1, 2025 (the precise “last day” can depend on how the calculator counts days/calendar conventions).

Rather than guessing, you can let DocketMath calculate the exact modeled deadline for each scenario you enter.

Related reading