Statute of Limitations for Revival / Window Legislation in District of Columbia

Overview

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

In the District of Columbia, “revival” and related “window legislation” concepts typically come up when someone tries to restart or extend the life of a claim after an initial deadline has passed or is about to pass. In DC, the baseline rule for how long you have to bring certain civil actions is set by statute, including a general limitations period of 3 years.

For DocketMath users, this matters because revival-style strategies often turn on dates: when the claim accrued, when a case was filed (or attempted), and whether any statutory carve-outs apply. DocketMath’s Statute of Limitations calculator is designed to model the most common workflow: define the key date(s), enter the claim’s “start” date, and see the computed end date for the limitations period.

Limitation period

Default rule (general SOL)

For the District of Columbia, the general statute of limitations is:

• 3 years for covered civil actions under D.C. Code § 23–113(a)(1).

Based on the statute’s text and the jurisdiction data you provided, there is no claim-type-specific sub-rule identified here. That means this page applies the same default 3-year window unless a separate exception or special statute clearly controls.

How to think about the timeline (practical date mechanics)

When you use the DocketMath tool, you’re translating the law’s “3 years” into a concrete deadline. That normally requires you to choose:

1. Accrual date (or the date you’re treating as the legal start of the limitations clock)
2. Whether you’re measuring from that start date directly (common for straightforward SOL questions)
3. Target event date (optional, for “was it timely?” comparisons)

Common patterns you’ll see:

• If the accrual date is earlier, the calculated deadline is earlier.
• If you move the accrual date forward by even weeks or months, the SOL expiration changes by the same amount—because the end date is anchored to the “start” date plus 3 years.
• If you’re evaluating timeliness, you compare the event date against the computed expiration date.

Quick example (illustrative)

If an event triggers accrual on January 15, 2023, then the default general SOL expiration would fall around January 15, 2026 (using calendar-year arithmetic consistent with standard SOL calculators). Changing the accrual date to March 1, 2023 moves the expiration correspondingly later.

Key exceptions

D.C. limitations disputes often hinge on whether something stopped, paused, or changed the clock. This section flags the typical categories that can matter in DC, even though the only period identified for this page is the general 3-year default.

Check these categories when running a calculation in DocketMath:

• Tolling (pause of the clock)
  Certain circumstances can stop the limitations clock temporarily. The key practical question is whether the statute or case law recognizes tolling for your specific situation and the time period it covers.

• Accrual timing differences
  If the dispute turns on when the claim “accrued” (rather than the date you were aware of harm), the SOL calculation may change even without any formal tolling.

• Statutory windows tied to special legislation
  “Window legislation” sometimes provides a limited time to take action even if the original SOL would have expired. Whether such a window applies depends on the specific act and the covered claim types and deadlines. Because this page does not identify a claim-specific revival/window statute, you should treat the general 3-year calculation as the baseline and then layer on any window law if it clearly applies.

• Procedural events that affect timeliness arguments
  Some procedural facts can influence timeliness (for example, whether a case was filed within the period). Even then, the governing rule must still be grounded in a statute or binding authority.

Statute citation

The general statute of limitations period used as the default in this jurisdiction is:

• D.C. Code § 23–113(a)(1) (General 3-year limitations period)
  Source (code text): https://law.justia.com/codes/district-of-columbia/2014/division-iv/title-23/chapter-1/section-23-113/

This is the period used by DocketMath when you select the jurisdiction’s general SOL basis for DC (unless you enter additional qualifying parameters in the calculator workflow that reflect recognized tolling or special rules).

Use the calculator

Jump to DocketMath’s Statute of Limitations tool here: /tools/statute-of-limitations

When you use DocketMath, focus on these inputs and how they change the output:

Inputs to enter

• Jurisdiction: District of Columbia (US-DC)
• Start date (accrual date): the date the clock begins running for the general SOL
• Calculate end date: typically enabled by default (you’ll get the expiration date)
• Optional comparison date (“was it timely?”): if the tool supports it, enter your filing/action date to check it against the computed expiration

What the output represents

• Expiration date: computed as 3 years from the start/accrual date under **D.C. Code § 23–113(a)(1)
• Timeliness comparison (if enabled): whether your event date is on or before the expiration date

How revival/window scenarios change the workflow

If you’re dealing with a revival or window issue, use DocketMath in two passes:

1. Baseline pass (general SOL):
   Compute the expiration date using the general 3-year rule.
2. Legislation pass (if applicable):
   If a specific window statute applies, compare the window’s deadline to the baseline expiration and/or re-compute using the window’s start/end dates—because a window may override the default filing timeline.

Checklist for this two-pass workflow:

Related reading

• Choosing the right statute of limitations tool for Vermont — Tool comparison
• Statute of limitations in Singapore: how to estimate the deadline — How-to guide
• Choosing the right statute of limitations tool for Connecticut — Tool comparison