Why Damages Allocation results differ in New York

4 min read

Published April 15, 2026 • By DocketMath Team

The top 5 reasons results differ

When DocketMath runs the damages-allocation calculator for New York (US-NY), the output can diverge across matters even when the “story” looks similar. Here are the most common drivers.

  1. Different treatment of damages that don’t fit neatly into a single bucket

    • DocketMath’s allocation mechanics typically require that damages elements be mapped into categories (for example, “compensatory” vs. other elements). If your case mixes categories, uses broad pleading labels, or you map an item differently, the calculator may allocate portions differently—while still producing a mathematically consistent result.
  2. Jurisdiction-aware eligibility windows (New York: general 5-year rule)

    • New York uses a 5-year general lookback tied to N.Y. Crim. Proc. Law § 30.10(2)(c).
    • Important nuance: based on the jurisdiction data provided, no claim-type-specific sub-rule was found. That means you should apply the general/default period rather than assume a shorter or longer window for particular claim types. This one choice often explains why otherwise similar inputs produce different allocation results.
  3. Input timing mismatches (key dates)

    • Allocation results can change dramatically when the relevant date inputs differ—such as event date, assessment/discovery date, or filing/notice date (depending on how your dataset is entered into DocketMath).
    • Even small differences (months, not years) can move amounts into or out of the 5-year general period, changing the eligible portion and therefore the allocation proportions.
  4. Inconsistent assumptions about the damages base

    • Two runs can use the same label (“annual damages,” “total damages,” etc.) but rely on different underlying bases—such as gross vs. net-of-offset figures, or including/excluding certain components.
    • DocketMath will compute based on what you provide; differences are usually in the inputs you consider equivalent, not in the tool.
  5. Offsets, credits, or prior awards applied unevenly

    • If mitigation, reimbursements, settlement credits, or earlier determinations exist, they need consistent treatment across runs.
    • One run that includes offsets and another that omits them can shift both totals and the effective allocation split—even if you only compare headline numbers at the end.

Pitfall to avoid: Don’t assume two DocketMath outputs “disagree” merely because the total damages figure differs. In New York, a large part of the variation often comes from which portion lands inside the 5-year general period under N.Y. Crim. Proc. Law § 30.10(2)(c), plus how dates and categories are mapped in your entries.

How to isolate the variable

To pinpoint what’s driving the difference, use a controlled, one-change-at-a-time workflow in DocketMath.

Checklist (run multiple times, changing only one factor per run):

  • Because no claim-type-specific sub-rule was found, you should not swap in a different lookback period unless you have another documented basis.
  • If you adjust amounts while you test dates, you won’t be able to tell whether the delta is coming from eligibility timing or from a changed damages base.
  • Make one run with the earliest plausible date, and another with the later date. Then observe how much eligible value shifts into/out of the 5-year general window.
  • Check that each damages element is tagged the same way in both runs. Even one mislabeled item can redirect allocation logic.
  • Ensure offsets are entered consistently across runs (same items, same treatment). This prevents “silent” differences that distort allocation proportions.

Practical tip: When debugging, compute the 5-year window first, then check which damages elements fall inside it. Once eligibility is clear, remaining differences usually come from category mapping and arithmetic inputs.

If you want a reproducible workflow, start from the tool here: DocketMath Damages Allocation.

Note: This is meant to help you debug allocation outputs in DocketMath using New York’s general timing rule. It’s not legal advice, and it won’t replace a case-specific analysis.

Next steps

  1. Run a baseline

    • Use your best current set of dates, categories, and damages base inputs.
  2. Produce contrast runs

    • Contrast Run A: alter only dates
    • Contrast Run B: alter only category mapping
    • Contrast Run C (if needed): alter only offsets/credits
  3. Compare output components, not just totals

    • Focus on:
      • eligible amount within the 5-year general period
      • allocated proportions by category
      • any residuals outside the window
  4. Document what changed

    • Keep a change log, e.g.:
      • “Changed event date from X to Y”
      • “Reclassified item A from category 1 to category 2”
      • “Added offset Z”
  5. Confirm the statutory anchor

Related reading