How to run Settlement Allocator in DocketMath for New York

Step-by-step

To run Settlement Allocator in DocketMath for New York (US-NY), follow this workflow. The goal is to produce allocation outputs using jurisdiction-aware rules, including New York’s general statute of limitations (SOL) baseline.

1) Open the Settlement Allocator tool

1. Go to the primary CTA: **/tools/settlement-allocator
2. Confirm you’re using the calculator: settlement-allocator.

If you don’t yet know what to enter, use the checklists in later steps to collect the key data points before proceeding.

2) Set jurisdiction to New York (US-NY)

Look for a Jurisdiction selector in the tool and choose:

• US-NY — New York

This selection matters because the calculator will apply New York’s SOL timing framework to the allocation logic.

3) Understand the SOL rule DocketMath will apply (New York default)

For this New York setup, DocketMath uses New York’s general/default SOL period:

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

Because your brief specifies that no claim-type-specific sub-rule was found, DocketMath should treat this as the general baseline rather than selecting a special SOL bucket for a specific claim category.

How that impacts allocation outputs

In practical terms, the tool will typically treat the relevant “timing window” as 5 years measured from the date field(s) you provide (often an accrual/occurrence or filing-related date—depending on the calculator’s input fields).

As a result:

• If the event date you enter is within 5 years, the output may allocate more under “timely” assumptions.
• If the event date is older than 5 years, the output may allocate less (or mark a portion as outside the SOL window), depending on how the calculator presents results.

4) Enter the inputs required by Settlement Allocator

While the exact field names can vary slightly, you’ll generally be asked for inputs that let DocketMath estimate an allocation based on timing and amounts. Use this checklist:

If the tool supports multiple date entries (e.g., several events), add them in the order the tool expects, because date order can change the computed SOL inclusion/exclusion.

5) Review how the outputs shift when you change dates

Before you finalize anything, run a quick “what-if” comparison:

• Run Scenario A with a key date that is clearly within the 5-year window.
• Run Scenario B with a key date that is just outside the window (for example, move the date forward by 1–90 days past the 5-year mark).

Then compare:

• Total allocated amount(s)
• Any “timely vs. time-barred” indicators
• Any breakdown by component (if displayed)

This helps confirm the calculator is applying the New York general/default SOL period of 5 years for US-NY rather than using a different timing assumption.

6) Capture outputs for your workflow

After running the calculator:

• Copy the final allocation results from the output panel.
• If the tool allows exporting or copying a summary, save it immediately.

Because settlement allocation can be sensitive to input selection, keep a record of:

• The exact dates you entered
• The exact jurisdiction selection (US-NY)
• The settlement amounts used

This makes later review faster and reduces the chance of mismatch if you rerun the allocator.

Common pitfalls

Most allocation errors in the tool don’t come from the math—they come from input mismatch or misunderstandings about what “SOL” means in the calculator’s logic. Watch for these issues:

• missing a required input
• using a stale rate or rule
• ignoring calendar or holiday adjustments
• skipping documentation of assumptions

1) Assuming a claim-type-specific SOL when DocketMath has a general default

Your brief notes: no claim-type-specific sub-rule was found, so the 5-year general/default period applies.

2) Using the wrong “key date” field

If the tool asks for a particular date type (event date vs. filing date vs. accrual date), using the wrong one can shift whether the event falls inside or outside the 5-year window.

Quick test:

• If you enter what you believe is a recent event but the output says “outside SOL,” re-check which date field you populated.

3) Running only one scenario

A single run can hide whether the tool is sensitive to SOL boundaries. Two-run checks (within window vs. outside window) make it much easier to validate output behavior.

4) Date boundary confusion (leap years and day counts)

When you move from “within” to “outside” SOL, small differences matter. If you’re adjusting dates, do it systematically:

• Move by days (e.g., +30, +90) rather than guessing months.

5) Not recording inputs before rerunning

If you rerun with changed dates or amounts and don’t save the earlier run, you can lose track of what drove the difference. Consider copying:

• Scenario A inputs
• Scenario B inputs
• Output comparison notes

Try it

To validate your DocketMath setup for New York (US-NY):

1. Go to **/tools/settlement-allocator
2. Set Jurisdiction = US-NY
3. Enter:

   • A key event date that you know is within 5 years
   • A settlement amount (and any other required components/fields)
4. Run the allocator and note:

   • Total allocation output
   • Any SOL/timing-related indicators
5. Change only the key event date so it becomes just outside 5 years
6. Run again and compare the differences

If the output meaningfully changes around the 5-year boundary, that’s a strong sign DocketMath is applying the New York general/default SOL period of 5 years under N.Y. Crim. Proc. Law § 30.10(2)(c).

Related reading

• Settlement Allocator Guide for Alabama
• Settlement Allocator Guide for Arizona
• Settlement Allocator Guide for Colorado