Inputs you need for Damages Allocation in New York

Inputs you will need

When you use DocketMath’s Damages Allocation calculator for New York (US-NY), the goal is to convert the key factual “ingredients” into an allocation-ready damages view. New York has a 5-year general statute of limitations for many civil damages claims, and DocketMath uses jurisdiction-aware rules to help apply that timing logic consistently.

Below is a practical checklist of the inputs you’ll typically need to run an allocation workflow for New York.

Core allocation inputs (the “math” fields)

These are the fields that drive the allocation result—think of them as the data DocketMath needs to divide totals across time and/or categories.

Timing inputs (jurisdiction-aware fields)

Even though you’re calculating damages allocation (not arguing timeliness), timing inputs can affect what portion of damages falls within the tool’s modeled window and how you interpret the period-by-period breakdown.

For New York, DocketMath’s default uses the general 5-year period described by:

• N.Y. Crim. Proc. Law § 30.10(2)(c) — https://www.nysenate.gov/legislation/laws/CPL/30.10

Important clarity: the brief indicates no claim-type-specific sub-rule was found, so this workflow treats the 5-year general/default period as the baseline. If your matter involves a potentially different rule in a specific context, you’ll want to confirm that separately.

Evidence-to-input mapping (turn case facts into tool fields)

This part is about translating what you have in your record into what DocketMath can calculate.

If you don’t have a one-to-one mapping (for example, you have totals but not period-by-period detail), you can still run the calculator—just be consistent about your chosen allocation basis and document your assumptions.

Where to find each input

To keep this actionable, use the checklist below to locate your data inside common document sets and workflows.

Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.

Dates

• Event date / damages start date

  • Look in: complaint allegations, incident reports, accounting timelines, or discovery summaries
• Filing date

  • Look in: court filing confirmations, e-file receipts, or the docket’s “filed”/entry date
• Time windows

  • Look in: damages expert reports, billing records, project schedules, or ledger exports

Practical tip: Don’t mix date systems (for example, “month-ending” versus “day-precision” dates) across categories. A one-day shift can change how much falls inside (or outside) the modeled window.

Damages categories and amounts

• Claim amounts

  • Look in: damages demand letters, the complaint’s damages section, spreadsheets attached to filings, or expert damage schedules
• Allocation bases

  • Look in: contract schedules, responsibility charts, project calendars, or “who did what when” exhibits

Weights / allocation drivers

If your allocation method uses weights (percentages or proportional bases), gather:

Run it

Use this step-by-step flow to enter inputs and interpret the result.

1. Open DocketMath and select the Damages Allocation calculator: /tools/damages-allocation.
2. Set jurisdiction to New York (US-NY) so the calculator applies the jurisdiction-aware default timing logic.
3. Enter your minimal dataset to start (you can refine later):

   • Event/damages start date
   • Filing date
   • At least one damages category with an amount
   • Allocation basis (for example, period split or weighted drivers)
4. Confirm the timing window behavior:

   • The workflow is based on a general 5-year default because no claim-type-specific sub-rule was found in the brief.
   • This general/default timing period is anchored to N.Y. Crim. Proc. Law § 30.10(2)(c): https://www.nysenate.gov/legislation/laws/CPL/30.10
5. Review the allocation output:

   • DocketMath will typically show how portions of your modeled damages fall into the time window you entered, and how your allocation drivers distribute totals across categories/periods.

Quick input-to-output guide

Use these “what changes when” rules of thumb while you’re modeling:

Practical checklist before you finalize

For direct access, start here:

• Run DocketMath Damages Allocation: **/tools/damages-allocation

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