Worked example: statute of limitations in United States (Federal)

Example inputs

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

Below is a worked example of how a federal statute of limitations calculation often looks when you’re using DocketMath’s /tools/statute-of-limitations calculator.

Scenario (fictional, for demonstration)

Assume the federal government is considering bringing a criminal charge based on an alleged event.

• Jurisdiction: United States (Federal) (US-FED)
• Offense category: General federal criminal statute of limitations (e.g., charged under a federal criminal statute)
• Statute of limitations length: 5 years (used here as an example; many federal non-capital offenses use a general 5-year rule)
• Alleged offense date (Trigger date): January 15, 2020
• Filing date (Indictment/complaint date): January 20, 2025
• Tolling flags: None (assume no special tolling doctrine applies)
• Accrual rule for the example: “Single trigger date” (assume the offense clock starts on the trigger date)

What the calculator needs (conceptually)

Even when DocketMath presents a simple interface, these are the inputs that typically drive the results:

• Limit period (years): the statutory number (example uses 5 years)
• Trigger date: when the limitations clock starts
• Filing date: when the case is filed (indictment/complaint filing date in this example)
• Tolling assumptions: whether any pause/extension mechanisms are selected (and, if so, their dates)
• Date-handling method: whether the calculator uses inclusive/exclusive counting rules consistent with its computation approach

If you want to compute your own timeline quickly, you can jump straight to the tool: /tools/statute-of-limitations.

Example run

Run the Statute Of Limitations calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.

Step 1: Compute the last permissible filing date (basic math)

Using the inputs above:

• Trigger date: January 15, 2020
• Limit period: 5 years
• Last permissible filing date (computed deadline): January 15, 2025 (under a straightforward “add 5 years” approach)

Now compare to the filing date:

• Filing date: January 20, 2025
• Comparison: January 20, 2025 is 5 days after January 15, 2025

Step 2: Determine whether it’s timely

Under this simplified model:

• Outcome: Not timely (because the filing date is after the computed deadline)

Concrete calculation table

Step 3: How the tool typically reports results

DocketMath’s /tools/statute-of-limitations calculator generally outputs:

• A computed deadline
• A timeliness determination (timely vs. not timely)
• A difference in days (helpful for spotting “close call” deadlines)

In this scenario, expect results along the lines of:

• Deadline: 2025-01-15
• Days late: 5
• Timely: No

Sensitivity check

Statutes of limitations are rarely “just add years.” Small changes—especially around the trigger date and tolling—can flip the outcome. Here are three focused sensitivity checks you can run in DocketMath (or mirror by adjusting the tool inputs).

To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.

Sensitivity A: Filing date moves earlier by 5 days

Keep everything else identical, but set:

• Filing date: January 15, 2025 instead of January 20, 2025

Takeaway: In this example, the outcome flips exactly at the deadline. If the filing lands on the deadline date (and the calculator counts it as allowable), the simplified model treats it as timely.

Sensitivity B: Trigger date shifts later due to “when the clock really starts”

Suppose the relevant fact pattern indicates the clock starts later than January 15, 2020. For example, use:

• Trigger date: February 1, 2020
• Limit period: 5 years
• Computed deadline: February 1, 2025
• Filing date: January 20, 2025

Now the filing occurs before the deadline:

Takeaway: The sensitivity to the trigger date can be larger than expected—here, the outcome changes even though the filing date stays the same.

Sensitivity C: Tolling flags (what toggles change)

DocketMath’s federal calculator may allow modeling tolling assumptions (depending on how the tool is configured). Try running multiple “what-if” versions:

• No tolling selected: deadline = trigger + 5 years
• Tolling enabled for a period: deadline moves forward by the tolled duration
• Different tolling start/end dates: deadline can shift by a different number of days, which may change “days late” vs. “days early”

For example, if a tolling option effectively adds 60 days to the computed deadline:

• Original deadline: 2025-01-15
• Adjusted deadline: ~2025-03-16
• Filing date: 2025-01-20
• Result: the filing may become timely under the adjusted deadline

Because tolling is highly fact-specific, treat tolling toggles as scenario modeling, not definitive conclusions.

Quick checklist for your next run in DocketMath

Before trusting a computed result, verify:

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