How to run statute of limitations in DocketMath for New York

Step-by-step

This guide walks you through running New York statute of limitations calculations in DocketMath using the Statute of Limitations tool (jurisdiction: US-NY). The tool’s core timing logic is based on N.Y. C.P.L.R. § 214 (primary authority).

Before you start, gather two dates:

• Event date (also described in the tool as an “incident/accrual” date—your best estimate of when the clock starts)
• Filing date (the date you want to compare against the calculated deadline)

Then open the calculator:

• Primary CTA: /tools/statute-of-limitations

1) Select New York (US-NY)

In the tool:

• Confirm the jurisdiction is US-NY
• If the UI asks for claim type, pick the closest matching category.

A quick way to choose:

• If your dispute is fundamentally about contract issues, start with contract-type options
• If it’s centered on fraud, choose the fraud-type option(s)
• If it’s injury/physical harm related (including premises/product/property damage styles), choose the personal injury / premises / product / property-type options

2) Choose the claim type that matches your facts

DocketMath uses claim-type periods to compute a limitations window. For New York, the tool’s verified mapping includes (examples):

Tip: If you’re unsure, re-check that your “core theory” matches the claim type you selected, because choosing the wrong category is one of the fastest ways to produce an incorrect deadline.

3) Turn on discovery/repose settings only when the facts fit

In DocketMath, discovery/repose behavior depends on the verified sub-rule tied to your selected claim type and toggles. For New York, the verified configuration includes:

• Discovery rule enabled for certain scenarios (tool sub-rule logic)
• Max years from incident (outer boundary / repose cap): 7 years

This means:

• Even if you model later discovery, the tool may still limit the effective window using an outer limit of 7 years from the incident, when the relevant discovery/repose sub-rule is active.

Checklist for whether to use discovery-style inputs:

• You have a plausible reason discovery happened later
• Your claim type is one where the tool’s verified discovery logic is intended to apply
• You understand the tool may apply a 7-year max-from-incident cap in those cases

4) Add tolling/exception inputs (infancy/insanity)

For New York, the verified tolling configuration includes:

• Mental incapacity / infancy and insanity tolling enabled: true
• Tolling during infancy/insanity is represented in the tool’s encoded rule set
• The dataset includes a 10-year cap entry for infancy/insanity tolling behavior (as implemented by the tool)

When it matters most:

• the claimant was a minor at the relevant time, or
• you have facts that support the mental incapacity / infancy and insanity type tolling recognized by the tool

Use tolling toggles carefully:

• If your facts support infancy/insanity tolling, enable the matching option
• If not, leave it off—otherwise you can end up with a later deadline than your facts warrant

5) Enter your dates

Fill in:

• Incident/accrual/event date (your best estimate of when the clock begins)
• Filing date (the date you want to test)

If the UI supports a discovery date, only enter it when you’re modeling a claim type and scenario where DocketMath’s discovery logic is intended to apply.

6) Run the calculation and record the result

After you click Calculate, DocketMath will typically show:

• the selected limitations window (based on claim type and selected toggles)
• a calculated deadline date
• a result such as whether your filing date falls within the window (wording can vary)

Record these values from the output:

• Selected claim period (e.g., 6 years, 3 years, 1 year, 2.5 years, or 90 days)
• Whether any discovery/repose constraint appeared (e.g., the 7-year max-from-incident rule)
• Whether infancy/insanity tolling changed the outcome

7) Cross-check with DocketMath’s receipt logic

A practical validation method:

• Re-run the tool with the same claim type but change only one relevant setting at a time (for example: discovery on/off; tolling on/off).
• Compare how the deadline shifts.

If a single toggle causes a major change, that’s a cue to verify that your facts actually support that toggle.

For the tool itself, use:

• /tools/statute-of-limitations

Common pitfalls

These are the most common issues that distort a “deadline” result in DocketMath for US-NY runs.

1. Picking the wrong claim type window A category mismatch can significantly change the limitation period:

• 1 year for libel/slander
• 3 years for personal injury/premises/product/property damage
• 6 years for breach of contract and fraud
• 2.5 years for medical malpractice
• 90 days for government tort claims

Quick check:

• Does your selected claim type match the core theory (contract vs tort vs fraud vs malpractice)?
• Is there a closer tool option for the harm you’re alleging?

1. Using discovery inputs when discovery doesn’t apply to the chosen scenario Discovery-related fields/toggles only affect the calculation when the tool’s verified sub-rule allows it for that claim type and setup.

2. Forgetting that discovery may still be limited by a 7-year max-from-incident rule Even where discovery logic exists in the tool, the verified configuration includes a 7-year max-from-incident boundary in applicable scenarios.

3. Assuming there is one universal “3-year rule” While the tool includes a general baseline concept, the actual limitation period depends on the claim type selected. Always rely on the claim-type period shown/used by the tool.

4. Toggling infancy/insanity without supportable facts If tolling is enabled, it can extend the deadline in ways that may not match your case. Enable tolling only when your facts align with the tolling recognized by the tool.

5. Using an inconsistent filing date Pass/fail outcomes can change quickly if your “filing date” is even slightly off. Make sure:

• Your filing date is the date you want the tool to compare against
• You use the same filing date across reruns

Try it

Use these mini-tests to validate your setup in DocketMath for US-NY.

Mini-test A: Sanity check with a contract-style claim

1. Select a contract claim type (e.g., breach of oral or written contract).
2. Enter:

   • Incident date: the earliest relevant date you have
   • Filing date: a later date
3. Run the tool.
4. Expect a 6-year period in the result (based on the verified claim-type mapping).

Mini-test B: Compare discovery-related outputs

1. Pick a claim type where the tool’s discovery/repose logic is intended to apply (per the tool’s verified sub-rule behavior).
2. Run once with discovery settings that activate the discovery sub-rule.
3. Run again with discovery settings that do not activate that discovery path (or discovery effectively off).
4. Watch for whether:

   • the deadline moves earlier/later, and
   • a 7-year max-from-incident constraint appears.

Mini-test C: Quick tolling impact check

1. Choose a claim type where the limitation period is straightforward in the mapping (for example, 3-year for personal injury or 6-year for contract).
2. Run with tolling disabled.
3. Run again with infancy/insanity tolling enabled.
4. Compare how the deadline shifts.

If the deadline changes dramatically, re-check that the tolling toggle matches your facts.

Related reading

• Statute of limitations in United States (Federal): how to estimate the deadline — Full how-to guide with jurisdiction-specific rules
• Why statute of limitations results differ in United States (Federal) — Troubleshooting when results differ
• Statute of limitations reference snapshot for United States (Federal) — Rule summary with authoritative citations