Statute of Limitations for Child Sexual Abuse / Assault in District of Columbia

Overview

In the District of Columbia, the statute of limitations (SOL) for filing a lawsuit or criminal charge tied to child sexual abuse or sexual assault generally follows a default limitation period—the provided jurisdiction data did not identify a separate, child-specific sub-rule. That means the same baseline SOL applies unless a recognized exception or tolling rule changes the timeline in a particular case.

DocketMath’s statute-of-limitations calculator helps you map the deadlines that flow from D.C.’s general SOL. It’s a practical way to see how changing key dates—like the date of the offense and the date you plan to file—affects whether a claim may fall inside or outside the limitations window.

Limitation period

General SOL period (default): 3 years

• General statute: **D.C. Code § 23–113(a)(1)
• General SOL period length: 3 years
• Default rule applied here: The jurisdiction data provided does not indicate a separate claim-type-specific SOL for child sexual abuse/assault. So, the 3-year period below is treated as the general baseline.

How to think about the deadline (the “inputs”)

To use DocketMath effectively, you typically need at least these dates:

• Date of occurrence (event date): the date the alleged sexual abuse/assault occurred
• Target filing date: the date you want to file a civil lawsuit (or otherwise initiate the relevant action)

Because SOL rules often depend on how time is counted, your output changes when either date changes. For example:

• If you move the target filing date earlier by months, you may move from “outside” to “within” the limitations window.
• If the event date is later than originally believed, your SOL deadline also shifts later.

Simple deadline model (conceptual)

Using the default 3-year SOL as a baseline:

• Baseline SOL deadline ≈ event date + 3 years

That baseline is what DocketMath models, unless you select/consider an applicable exception in the calculator (if available for your use case).

Key exceptions

The DocketMath workflow is strongest when you identify whether any exception/tolling doctrine could change the counting of time. With the jurisdiction data provided, the safe approach is:

1. Start from the default: 3 years under **D.C. Code § 23–113(a)(1)
2. Then check for exceptions: whether any legal mechanism pauses, tolls, or otherwise alters the limitations period based on your facts

Because exceptions can be fact-specific and may depend on the claim’s procedural posture (civil vs. criminal), the most practical way to proceed is to use DocketMath to compute the baseline deadline and separately confirm whether an exception applies before relying on that computed date.

Here are common categories to look for (not an exhaustive list):

• Tolling based on specific conditions (e.g., certain legal disabilities)
• Discovery-related adjustments (when the law ties the start of the SOL to when the claimant knew or should have known critical facts)
• Statutory revival or extended windows created by later legislation
• Potential differences by cause of action (even when your initial source suggests “general/default,” downstream rules sometimes affect particular claims)

Practical checklist before relying on any deadline

Use this checklist to prepare inputs for the calculator and any follow-up research:

Statute citation

The default limitations period referenced in the provided jurisdiction data is:

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

  • General SOL period: 3 years
  • Source (code text): https://law.justia.com/codes/district-of-columbia/2014/division-iv/title-23/chapter-1/section-23-113/

This page uses the general/default period from that statute because no claim-type-specific sub-rule was found in the provided jurisdiction data.

Use the calculator

You can calculate the baseline SOL timeline using DocketMath’s statute-of-limitations tool.

Recommended workflow in DocketMath

1. Open the calculator: /tools/statute-of-limitations
2. Select jurisdiction: **District of Columbia (US-DC)
3. Enter key dates:

   • Event date (the alleged abuse/assault date)
   • Filing/target date (when you want to initiate the action)
4. Review the output:

   • Baseline deadline based on 3 years
   • Whether the filing date falls within or outside the default window

How outputs change with inputs (examples)

These illustrate the kind of changes you should expect:

• If the event date moves later by 90 days: the baseline SOL deadline typically moves later by roughly the same amount (because the calculation starts from the event date).
• If the target filing date moves later: the result may switch from “within” to “outside” the 3-year period.
• If you’re unsure about the event date: run multiple scenarios using a date range to see how sensitive the outcome is.

If you want a quick way to start without overthinking the inputs, begin with the most conservative event date you can support (latest plausible event date) and compare it to a more conservative earlier date scenario.

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