Statute of repose in New York

Direct answer

In New York, the statute of repose / limitations timing used for this guide is generally 5 years, based on N.Y. Crim. Proc. Law § 30.10(2)(c) (using your provided jurisdiction data that reflects a general/default period of 5 years). DocketMath’s statute-of-limitations calculator can help you model how a 5-year deadline affects whether a charge (or other action) is brought in time.

A jurisdiction-aware note: your dataset indicates no claim-type-specific sub-rule was found for this repose/limitations-focused summary. So this guide uses 5 years as the default rule, rather than attempting to break it into offense-specific categories.

What you need to know

A statute of repose (and related statute of limitations concepts people often discuss together) sets a deadline for when a government or plaintiff can initiate action. Even if the words get used interchangeably in everyday conversation, the key practical point is the same for your timing analysis: there is a cutoff date, and the cutoff depends on how the clock is defined and which dates you compare.

For this New York-focused guide, the anchor timing period is:

• N.Y. Crim. Proc. Law § 30.10(2)(c) — treated here as the general/default 5-year period.

Inputs you’ll typically need to model timing

To use DocketMath effectively, you’ll usually provide:

• Trigger date: the date that starts the relevant timing clock for your scenario (often tied to when the underlying event occurred or when the statute’s framework begins for the analysis you’re running).
• Action date: the date you’re testing—commonly the date the charging instrument is filed/issued or another procedural “initiation” milestone that you decide is the relevant comparison point.
• Period: the duration you’re applying—here, 5 years as the general/default period from N.Y. Crim. Proc. Law § 30.10(2)(c).

Output you can expect from DocketMath

DocketMath’s statute-of-limitations calculator is designed to:

• compute a deadline date using your trigger date + period; and
• help you compare that deadline to the action date to see whether the action appears within or outside the modeled timing window.

Because your dataset reports no additional claim-type-specific sub-rule found, the model in this guide assumes only the 5-year general period.

Step-by-step

Follow these steps to run a clean, reproducible New York timing calculation with DocketMath.

1. Identify the governing statute for the period used in this guide

   • Use N.Y. Crim. Proc. Law § 30.10(2)(c) as the anchor for the general/default timing rule.
   • In this brief, that statute is represented as a 5-year default period (per your jurisdiction data).

2. Choose the trigger date you want to test

   • Select the date that corresponds to the start of the timing framework for your purpose.
   • If you aren’t sure which date the clock starts for your exact procedural posture, run multiple scenarios (e.g., earliest plausible trigger vs. latest plausible trigger).

3. Confirm the period = 5 years

   • Use 5 years consistently in the model.
   • Do not apply offense-specific carve-outs in this guide, because your dataset states no claim-type-specific sub-rule was found.

4. Enter the action date you’re testing

   • Define “action date” in a way that matches what you’re testing:

     • the date charges were initiated/issued, or
     • the date a relevant procedural step occurred (depending on how you frame the timing comparison).
   • Consistency matters: the comparison is only as accurate as the meaning of the date you choose.

5. Run DocketMath’s statute-of-limitations calculator

   • Set the jurisdiction to US-NY.
   • Apply the 5-year period tied to N.Y. Crim. Proc. Law § 30.10(2)(c).
   • Confirm that the calculator is using the dates you entered as trigger date and action date.

6. Interpret the output

   • If the action date is on or before the calculator’s computed deadline, the timeline you modeled appears within the 5-year window.
   • If the action date is after the computed deadline, the modeled timeline appears outside the 5-year window.
   • Always reconcile the model with the real-world procedural timeline: some “initiation” milestones can differ by context.

7. Document your inputs for reproducibility

   • Write down:

     • trigger date,
     • action date,
     • period (5 years),
     • and the statute used (CPL § 30.10(2)(c)).
   • This makes it easier to re-run the numbers if you later decide a different trigger date definition applies.

Key statutes and citations

This brief uses New York’s general/default timing anchor period reflected in your jurisdiction data.

Reminder: Your dataset specifically notes no claim-type-specific sub-rule was found for this brief. That’s why the model stays with the 5-year general/default period.

Common pitfalls

Timing disputes often come from mixing up dates or assumptions—not from the math itself. Avoid these common issues when using DocketMath for a New York repose/limitations-style analysis.

Pitfalls to avoid (with practical checks)

• Using the wrong trigger date

  • The model is extremely sensitive to the trigger date.
  • Quick check: confirm what date you’re intentionally modeling as the start of the clock for your scenario.

• Assuming the period is something other than 5 years

  • This guide uses 5 years because your dataset indicates no claim-type-specific sub-rule was found.
  • If your situation genuinely requires a different subcategory rule, you’d need a different statute selection than the one used here.

• Using an inconsistent action date

  • Filing/issuance milestones can differ.
  • Quick check: define your action date up front and keep it consistent across runs.

• Forgetting boundary behavior

  • Deadlines can turn on whether you’re comparing “on” versus “after” the computed cutoff.
  • Quick check: note whether the calculator output treats the boundary as inclusive for “on or before.”

• Treating “repose” and “limitations” as the same thing

  • They can be discussed similarly, but the legal framework can differ.
  • Quick check: keep your tool usage tied to the statute and period you’ve cited here (CPL § 30.10(2)(c)).

Run the numbers

Use DocketMath’s statute-of-limitations calculator to model whether a given timeline appears within the 5-year default period under N.Y. Crim. Proc. Law § 30.10(2)(c).

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

Example scenario (5-year default)

Assume:

• Trigger date: January 15, 2020
• Period: 5 years
• Action date to test:

  • Scenario A: January 14, 2025
  • Scenario B: January 16, 2025

With a 5-year period, DocketMath will compute a deadline around January 15, 2025 (exact formatting may depend on the tool’s boundary logic). The comparison concept is:

• On/before the deadline → modeled as within
• After the deadline → modeled as outside

Change one input and watch the result

Hold trigger date constant and change only the action date:

If you’re not sure which date to use

Run two calculations:

• one using the earliest plausible trigger date, and
• one using the latest plausible trigger date.

Then compare which modeled timeline is closer to (or crosses) the computed deadline. This is often the fastest way to identify where the timing dispute would matter most—without changing the period (still 5 years per CPL § 30.10(2)(c)).

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