Worked example: statute of limitations in Delaware

Example inputs

This worked example walks through how DocketMath’s statute of limitations calculator would model a common, general Delaware limitations period for a civil claim.

Here is a simple illustration for Delaware. These values are for demonstration only and should be replaced with your actual inputs.

• Principal or amount: contract claim
• Rate or cap: N/A
• Start date: undefined
• End/as-of date: N/A

Delaware rule used (general/default)

Delaware’s general statute of limitations for many civil actions is 2 years, found in 11 Del. C. § 205(b)(3). The Delaware Code text is available here: https://delcode.delaware.gov/title11/c002/index.html?utm_source=openai

Important scope note: no claim-type-specific sub-rule was identified for this example, so the calculator uses the general/default 2-year period as the model outcome. This means the example is meant to show the baseline mechanics, not a special limitations period for a specific cause of action.

Scenario

Assume a plaintiff files a civil complaint in Delaware based on an event that triggered the claim.

We’ll use these inputs:

• Jurisdiction: Delaware (US-DE)
• Trigger event date (accrual date): January 15, 2024

  • For limitations modeling, the “trigger” is the date the claim is treated as accruing (i.e., the simplified date the limitations clock starts).
• Claim filing date: January 10, 2026

  • This is the date we compare against the calculated deadline.
• Statute of limitations period used: 2 years (general/default)
• Citation backing the period: 11 Del. C. § 205(b)(3)

Why accrual date matters in a worked example

Even small changes to the accrual date (for example, January 15 vs. January 16) can shift the modeled deadline by a day, which can move a case from “timely” to “late” depending on the filing date.

To keep this concrete, we’ll calculate the “latest filing date” from the accrual date and then compare it to the filing date.

Example run

This is the walkthrough of a typical DocketMath run that leads to a straightforward “timely vs. time-barred” outcome under the general/default 2-year model.

If you want to try it directly, use DocketMath here: **/tools/statute-of-limitations

Inputs entered into DocketMath (conceptual)

• Jurisdiction: **US-DE (Delaware)
• General SOL period: 2 years
• Accrual date: 01/15/2024
• Filing date: 01/10/2026
• Rule applied: 11 Del. C. § 205(b)(3) (general/default)

Step-by-step SOL math (baseline model)

1. Start date: January 15, 2024
2. Add 2 years: January 15, 2026
3. Compute deadline: In this standard “two-year-from-accrual” model, the calculated deadline is January 15, 2026.
4. Compare filing date to deadline:

   • Filing date: January 10, 2026
   • Deadline: January 15, 2026
   • Result: Filing is within the 2-year general period.

Output interpretation

Under this worked baseline:

• Timely: Yes (filed before the modeled deadline)
• Time remaining (from filing date to deadline): 5 days

For a quick visual timeline:

Sensitivity check

Now let’s see how the outcome changes when you adjust key inputs. These are mechanical sensitivity tests using the same general/default 2-year rule from 11 Del. C. § 205(b)(3) (because no claim-type-specific sub-rule was identified for this example).

Sensitivity 1: Filing date changes (holding accrual constant)

Keep accrual date fixed at January 15, 2024.

Under the baseline model, filing on January 15, 2026 is treated as timely because it matches the modeled last day.

Sensitivity 2: Accrual date changes (holding filing constant)

Now hold the filing date at January 10, 2026, and shift the accrual date.

Small accrual differences can flip the outcome. For example, moving the accrual date by about two weeks can shift the modeled deadline enough to change whether a filing is timely.

Sensitivity 3: Rule scope confirmation (general/default vs. claim-specific)

For this example, the calculator uses the general/default 2-year period stated in 11 Del. C. § 205(b)(3) because no claim-type-specific sub-rule was found for the inputs used here.

If a claim-specific rule applies to your particular cause of action, the effective limitations window may be different from 2 years—so the baseline results here could be overly strict or overly optimistic.

Practical pitfall: A “2-year” baseline is most reliable when your claim fits the general category the statute covers. If your cause of action is governed by another limitations period, you should re-run the calculator (or apply the correct rule) for that specific claim type rather than relying on the general example.

Quick checklist to use before relying on the output

Use this checklist with the DocketMath result:

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