Inputs you need for statute of limitations in Delaware
4 min read
Published April 8, 2026 • By DocketMath Team
Inputs you will need
To run a statute of limitations (SOL) calculation for Delaware (US-DE) in DocketMath, gather the facts below first. This checklist is designed for the general/default SOL period in Delaware—a claim-type-specific sub-rule was not found, so this workflow uses the general rule.
Delaware general SOL rule (default):
- 2 years
- Authority: Delaware Code, Title 11, § 205(b)(3)
Source: https://delcode.delaware.gov/title11/c002/index.html?utm_source=openai
Note: DocketMath’s “statute of limitations” tool is a calculation aid. It helps you estimate an “earliest last day to file” style window based on your selected dates. It’s not a substitute for legal review of your specific claim type and triggering facts.
Your inputs checklist:
If you want the tool to be most accurate, be consistent about what you’re treating as the trigger, for example:
- date of injury / event, or
- date notice was provided, or
- date a contract was breached, or
- another legally relevant trigger tied to your facts.
DocketMath can’t determine which date is legally relevant—the factual selection is what anchors the timeline.
Where to find each input
Use the sources below to locate the exact dates and facts DocketMath needs.
Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.
1) Claim type / cause of action
Look for it in:
- complaint or draft complaint
- demand letter
- case intake notes
- contract sections or alleged conduct descriptions
Even when applying the general/default SOL (2 years), capturing the claim type helps you sanity-check that the default approach fits your workflow.
2) Trigger date (event that starts SOL)
Common places:
- incident report / police report
- medical or treatment records
- email or letter evidencing notice
- contract timeline (e.g., delivery date, performance date, breach date)
- termination notice or rejection notice
Your goal is a single exact calendar date you can justify internally.
3) Filing date
Find it in:
- the filed complaint stamp
- court electronic filing receipt (timestamp/date)
- PACER docket entry (if applicable)
- your internal litigation tracking system
4) Jurisdiction confirmation
Confirm:
- that Delaware law governs the claim timeframe for your purposes, or
- that your case management/workflow is using Delaware as the governing jurisdiction.
DocketMath’s Delaware mode corresponds to US-DE.
5) Supporting description
Add a short note so the trigger date is reproducible, such as:
- “Triggered by breach on 2024-06-01”
- “Triggered by denial letter dated 2023-11-15”
- “Triggered by injury on 2023-08-20”
This does not change the math; it reduces the chance that someone later switches to a different, competing date.
Run it
Use DocketMath’s statute of limitations calculator here: /tools/statute-of-limitations.
In the calculator, you’ll typically enter:
- Delaware (US-DE) selection
- Trigger date
- Filing date
- (If prompted) claim type label and notes
Delaware default SOL period you should expect
When using the default/general rule:
- SOL length: 2 years
- Statute citation: 11 Del. C. § 205(b)(3)
- General rule only: No claim-type-specific sub-rule is applied in this workflow (per the provided inputs).
What the output usually tells you
Depending on the UI, the calculator commonly returns items like:
- computed deadline (the last day to file under the selected SOL framework)
- whether the filing date is before/on/after that deadline
- the elapsed time between trigger and filing
How adjustments affect results:
- Trigger date later → deadline later; filings are more likely to look timely
- Trigger date earlier → deadline earlier; filings are more likely to look late
- Filing date later → risk increases; filings more likely exceed the computed deadline
- Filing date earlier → risk decreases; filings more likely fall within the 2-year window
Quick sequencing checklist (fast workflow)
Warning: Choosing the wrong date is the most common reason SOL outputs become misleading. If your situation involves multiple candidates (e.g., incident date vs. discovery vs. notice), document which one you used as the SOL trigger and why.
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
