How to run statute of limitations in DocketMath for United States (Federal)

Step-by-step

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

This guide shows you how to run a statute of limitations calculation in DocketMath for United States (Federal) matters (jurisdiction code US-FED). You’ll enter a few dates and the tool will compute key time windows used for limitations analysis. This is workflow guidance—not legal advice.

1) Open the statute-of-limitations calculator

Start at the primary call-to-action:

• /tools/statute-of-limitations

When you’re working inside DocketMath later, you can also use the same internal link from your site navigation (where available) to jump back to the tool:

• /tools/statute-of-limitations

2) Confirm you’re in the right jurisdiction (US-FED)

In the calculator’s jurisdiction selector, choose:

• **United States (Federal)

Behind the scenes, DocketMath ties the calculation to Federal timing rules rather than state time rules. That distinction matters because Federal limitations periods are set by statute and can vary by offense type—and by whether you’re dealing with civil versus criminal claims.

3) Select the case type your workflow needs

Choose the option that best matches what you’re evaluating in your document set, typically along the lines of:

• Criminal (limitations for prosecution)
• Civil (limitations for filing a civil action)

If you’re unsure, match the selection to the procedural posture you’re reviewing (for example, prosecution/charging timelines versus filing/complaint timelines). DocketMath will use the appropriate limitations structure for the window you’re modeling.

4) Enter the trigger date (the “event” date)

The calculator will ask for the date that starts the clock (the “trigger”). In practice, this is often one of the following:

• date of the alleged act or omission
• date of the last relevant act
• date of discovery (in certain contexts where a discovery concept is part of the rule)

Use the date that best fits your document record for the specific trigger described by the rule you’re applying, then enter it in the required format (typically month/day/year).

How inputs change the output

• Earlier trigger dates generally yield later expiration dates.
• Later trigger dates generally yield earlier expiration dates.
• If you select a discovery-based trigger option, the expiration date typically tracks the discovery date rather than the act date.

5) Add the reference date for comparison (“filed” / “charged” / “action date”)

DocketMath typically compares the limitations window to a second date, such as:

• charge date (criminal)
• filing date (civil)
• or another “comparison” date option the calculator provides

Enter the date that corresponds to when the relevant government action occurred (criminal charge) or when the civil action was filed.

6) Review computed outputs

After you submit, you should see outputs that typically include:

• Expiration date (the last day the limitations window remains open under the inputs)
• A distance measure (for example, days/weeks/months remaining), if provided
• Whether the comparison date falls within the window (for example, “within limitations” vs. “outside limitations”)

Use the output as a timeline anchor for further review of the record dates in your case file.

7) Run multiple scenarios (date sensitivity)

Because limitations often turns on specific facts and dates, rerun the calculator with alternate assumptions to see what changes.

A practical approach is to run scenarios like:

• Scenario A: event/act date as the trigger
• Scenario B: last act date as the trigger
• Scenario C: discovery date as the trigger (only if the tool offers that trigger logic)

When you compare results, keep a simple record for each run:

• trigger date used
• comparison/action date used
• expiration date returned

8) Capture results for your case workflow

Once you have the outputs you need, save or export the results using whatever options DocketMath provides in your workflow. If you’re building a case chronology or drafting a litigation memo, the most useful “pair” is usually:

• the expiration date, and
• the trigger definition you selected (because that explains what the window is measuring)

If the tool shows a breakdown of the calculation basis, use it to document why the time window is measured the way it is for each scenario.

Common pitfalls

Even strong date entry can produce misleading results if the inputs don’t match the legal characterization you’re using. Here are the most frequent issues to check in Federal limitations workflows within DocketMath.

• Federal timing rules differ materially from state timing rules; ensure you’ve selected United States (Federal) / US-FED.

• Some limitations structures begin at the act; others track discovery. Confirm the tool setting that governs the trigger you selected.

• Criminal and civil limitations are structured differently. Make sure your selection matches your procedural posture.

• For instance, if the criminal comparison should be the charge date, but you enter an “investigation start” date instead, the outcome can flip.

• Many window calculations treat expiration as inclusive (through a final date). Use the tool’s reported method; don’t manually adjust the date unless the tool explicitly instructs you to.

• If you later confirm the “last relevant act” date differs from your first assumption, rerun immediately with the corrected trigger date.

Quick checklist before you submit in DocketMath

Try it

Follow this mini-exercise to build confidence with DocketMath:

1. Go to /tools/statute-of-limitations
2. Select United States (Federal) (US-FED)
3. Pick a case type option that matches your workflow
4. Enter:

   • a trigger date from your case notes (the alleged act/last act or discovery date—depending on what you selected)
   • a comparison/action date (charge date for criminal, filing date for civil)
5. Submit and note:

   • the expiration date
   • whether the comparison date lands inside or outside the limitations window

Then, run one second pass:

• Change only the trigger date (for example, switch from an “act date” to a “last act date” or to “discovery date,” if your chosen option supports that logic).
• Keep the action/argument comparison date constant.
• Confirm that the expiration date changes in the direction you expect.

If outputs behave counterintuitively, revisit:

• the selected case type
• the trigger option
• whether you entered dates into the correct fields

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