Damages Allocation rule lens: New York

The rule in plain language

Run this scenario in DocketMath using the Damages Allocation calculator.

In New York, the damages allocation “rule lens” starts with the statute of limitations (SOL) clock you use for time-based calculations. Using the general/default SOL period reflected in the New York criminal procedure statute, the period is 5 years under N.Y. Crim. Proc. Law § 30.10(2)(c).

A careful read of the provision you’re anchoring to shows it sets a general period—and no claim-type-specific sub-rule was found in the material provided. So, when you apply this New York lens in DocketMath, treat the 5-year default as the operative time boundary for calculations that depend on SOL inclusion.

For quick reference, here’s the citation and the rule parameter you should plug into your workflow:

• General SOL Period (default): 5 years
• Statute: **N.Y. Crim. Proc. Law § 30.10(2)(c)
• Source: https://www.nysenate.gov/legislation/laws/CPL/30.10

Why it matters for calculations

Damages allocation models often depend on when damages are considered “in-period.” The SOL boundary acts like a filter: it affects which portions of a damages timeline are included versus excluded in practical calculations.

When you run allocation calculations in DocketMath for New York (US-NY), this SOL lens typically influences:

1. Start/end date for the included damages window
   With a 5-year default, damages periods older than the SOL cutoff are commonly treated as outside the included window for timeline-based computations.

2. How allocation splits across partial periods
   If damages accrue daily, monthly, or by event, a SOL cutoff can split the timeline into:

   • an included segment (within 5 years), and
   • an excluded segment (older than 5 years).

3. Sensitivity to date changes (moving the trigger date)
   Shifting the “trigger” date forward or backward—even by months—can move the SOL cutoff date and change the number of included days/months. That can directly change totals when the model uses time-proportional allocation.

4. Handling “claim type” assumptions
   Because no claim-type-specific sub-rule was found in the provided jurisdiction data, you should avoid assuming multiple SOL lengths based on claim labels within this lens. Apply the consistent 5-year general/default boundary unless you have independently identified a controlling, different provision.

Quick example: how the 5-year boundary changes totals

If your model allocates damages by time-weighting (e.g., a fixed amount per month), the SOL cutoff shifts which months count:

• Scenario A: Trigger date = January 1, 2020 → SOL window ends January 1, 2025
• Scenario B: Trigger date = January 1, 2019 → SOL window ends January 1, 2024

If your dataset includes damages through mid-2025, Scenario B may exclude an additional ~6 months relative to Scenario A. That difference can be significant if the per-period allocation is material.

DocketMath inputs to think about (jurisdiction-aware)

When using DocketMath’s damages-allocation calculator for US-NY, structure inputs so the calculator can apply the 5-year default SOL lens:

• Trigger/start date (the relevant starting point for your modeled damages timeline)
• Cutoff / event date (the modeled reference point that ends the timeline for allocation measurement)
• Allocation basis (e.g., per day, per month, or event-based)
• Damages distribution

  • either period-by-period amounts, or
  • a total amount + distribution logic (if supported by the calculator UI)

Use the calculator

To apply this New York damages allocation rule lens in your workflow, use DocketMath:

• Primary CTA: /tools/damages-allocation

You can jump in directly here: /tools/damages-allocation (New York / US-NY lens).

Run the Damages Allocation calculation in DocketMath, then save the output so it can be audited later: Open the calculator.

Step-by-step workflow (calculation-ready)

• Step 1 — Set the jurisdiction

  • Choose US-NY so the calculator applies the 5-year general/default SOL lens tied to N.Y. Crim. Proc. Law § 30.10(2)(c).

• Step 2 — Enter your relevant dates

  • Provide the trigger/start date for your modeled damages timeline.
  • Provide the timeline end reference date your allocation is measured against.

• Step 3 — Confirm the allocation basis

  • If allocation is time-based, specify whether weighting is by day, month, or another unit.

• Step 4 — Feed in damages distribution

  • Either:

    • enter period-by-period amounts, or
    • enter a total amount plus the distribution logic your workflow assumes (if supported by the calculator UI).

• Step 5 — Review SOL-window inclusion results

  • The calculator should reflect the default 5-year window and compute allocations accordingly.

How outputs change as inputs change

Use the calculator for “what-if” scenarios. Common tests include:

• Trigger date moved ± 6 months
  Expect a change in the count of included periods (and therefore totals), because the SOL cutoff moves.

• Timeline end moved forward
  If the end date extends into additional months, totals may increase only to the extent those added months remain within the 5-year default.

Scenario testing checklist:

Related reading

• Damages Allocation Guide for Alabama — Comparative Fault Rules
• Damages Allocation Guide for Alaska — Comparative Fault Rules
• Damages Allocation Guide for American Samoa — Comparative Fault Rules