How Settlement Allocator rules vary in New York
4 min read
Published October 26, 2025 • Updated April 23, 2026 • By DocketMath Team
Trust release 4
This page has legal or numeric text that still needs claim-level inventory before we can treat it as verified.
What varies by jurisdiction
Run this scenario in DocketMath using the Settlement Allocator calculator.
In New York, Settlement Allocator results can shift even when the underlying timing number appears constant, because the tool’s outputs depend on (1) the jurisdiction-aware timing window and (2) the inputs you use to represent “when the clock starts.” DocketMath’s Settlement Allocator helps you model those inputs consistently, but the rules behind the scenes can vary when you switch jurisdictions.
For New York (US‑NY), the key jurisdiction-specific timing rule to ground your runs is the general criminal statute of limitations period. Under N.Y. Crim. Proc. Law § 30.10(2)(c), the general period is 5 years.
The practical meaning of “5 years” in New York (US‑NY)
Here’s how this generally affects your allocator modeling:
Default limitation period (general/default): If your workflow uses a timing window to evaluate whether a claim theory is still within a limitations period, New York’s general reference point is 5 years under N.Y. Crim. Proc. Law § 30.10(2)(c).
No claim-type-specific sub-rule found (important): In this brief, no claim-type-specific timing sub-rule was identified. That means you should not automatically assume different limitations periods for different claim types in New York. Treat § 30.10(2)(c) as the general/default period unless you have separate, New York-specific authority establishing a different time period for a particular category.
Where allocator “rules” show up in practice (even with the same number)
Even when the limitation period is 5 years, allocation calculations can still vary because your inputs can differ. In New York, the most common input drivers to check are:
- Accrual/event dates (e.g., date of incident vs. date discovered)
- Filing-related dates (e.g., complaint/indictment timing—depending on how your workflow defines “filing” in the model)
- Category labels (e.g., whether you’re conceptually modeling everything under a single general/default bucket vs. trying to apply category-specific timing)
Note: For this content, the verified default is 5 years under N.Y. Crim. Proc. Law § 30.10(2)(c). If your DocketMath setup includes category-based timing overrides, verify that assumption using New York-specific authority before treating those overrides as accurate.
To start modeling in DocketMath, use the tool here: /tools/settlement-allocator.
What to verify
Use this checklist to make sure your DocketMath run reflects the New York (US‑NY) timing approach described above. This is practical guidance—not legal advice—and it’s meant to help you validate assumptions before relying on outputs.
- The governing rule or statute for the jurisdiction.
- Any local rule overrides or administrative guidance.
- Effective dates and whether amendments apply.
1) Confirm you’re using the correct “limitation period concept”
Because this brief is built around New York’s general/default period, confirm your run is aligned with that scope.
2) Match dates to the event logic your allocator expects
Settlement allocation models typically rely on a consistent definition of when the clock starts. In DocketMath, verify what your worksheet/date inputs represent.
Common date choices teams use (and that can change allocator results):
- Incident/event date
- Notice/discovery date
- Filing date (or another workflow “step date” that your allocator interprets as relevant)
If your team swaps one date type for another, the tool may effectively move cases “within the window” versus “outside the window,” changing allocation outputs.
3) Ensure the jurisdiction setting is correct
DocketMath’s jurisdiction-aware logic can differ by jurisdiction code. Make sure you’re running the correct one.
4) Validate the “general/default” assumption across categories
This brief explicitly notes no claim-type-specific sub-rule was found. As a result:
5) Record what changed between runs
To keep results defensible and easier to explain internally, track differences such as:
That way, if outputs move, you can pinpoint whether it was the timing window logic or simply different date inputs.
Sources and references
Start with the primary authority for New York and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.
