Choosing the right Damages Allocation tool for New York

Choose the right tool

Run this scenario in DocketMath using the Damages Allocation calculator.

If you’re in New York and need a Damages Allocation approach, the first question isn’t “which number should I use?”—it’s which allocation tool configuration matches the mechanics of your case model. With DocketMath’s damages-allocation calculator, you can structure your damages inputs consistently, then apply jurisdiction-aware assumptions (including time-window logic) to drive the allocation output.

What DocketMath does well for New York allocations

DocketMath is designed to help you translate a messy damages story into a repeatable set of allocation steps. In practice, you:

• enter case-specific monetary components (such as principal amounts and any other categories you choose to model),
• define a time window for damages measurement/allocation (if your model depends on it),
• set up assumptions so the calculator can produce an allocation breakdown you can use to explain your methodology.

Courts and parties often scrutinize methodology as much as the arithmetic. Using a consistent tool setup (rather than re-creating the approach manually each time) helps you stay coherent when you iterate through different positions.

The key New York jurisdiction-aware rule: default 5-year period

For New York, the default time-based rule you should start from is the general limitations period. Per the brief you provided, no claim-type-specific sub-rule was found for this topic—so the tool setup should clearly reflect that you are using the general/default period, not a specialized variation.

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

Clear statement for this tool-selection context (no claim-type sub-rule identified):

In other words, when your allocation requires a lookback window and you’re using DocketMath’s New York jurisdiction-aware configuration, start with 5 years as the baseline.

Choosing the right configuration within damages-allocation

In a practical workflow, your decision is whether your analysis depends on the legal lookback window (and therefore uses the default 5-year constraint), or whether you’re modeling damages without truncation for limitation-period purposes.

You can think of this as two common configuration choices when running DocketMath’s damages-allocation calculator:

• Time-window constrained allocation (5-year default)
  Use when your damages measurement depends on a lookback window from a filing date, accrual-related date, or other case timing anchor. This setup uses the New York general/default 5-year period as the baseline constraint.

• Full-period allocation (no SOL truncation logic)
  Use when you’re doing internal analysis, forecasting, or a damages framing that does not depend on limitations truncation. You still define your measurement period, but you do not apply the SOL lookback truncation logic.

A simple way to ensure you’re choosing correctly: if your narrative depends on what portion is recoverable within the limitations period, constrain by the time window; if it does not, don’t force truncation into the model.

Inputs that most affect outputs (and how output changes)

The damages-allocation output is sensitive to the inputs that define time and categorization. Use this checklist as a preflight before you rely on the output:

• Time anchor date (the start point for your 5-year window, if you are using the SOL-constrained setup)
• Time window definition (for example, “damages accrued within the past 5 years”)
• Damages components (how you break down categories; principal vs. other modeled categories, if applicable)
• Category exclusions (anything you remove before allocation)
• Interest or carrying cost assumptions (only include these if you intentionally model them in your inputs)

Example of how the same total can allocate differently

Practical takeaway: if you’re changing only the time window behavior (SOL-constrained vs. full-period), expect the allocation to change in a predictable direction—often by shifting emphasis toward more recent components that fall within the window.

Guardrails when applying the 5-year default

Because this setup uses the general/default 5-year period under N.Y. Crim. Proc. Law § 30.10(2)(c), make sure your modeling assumptions clearly state the role of the 5-year window.

Warning (non-legal advice): Using a statute-of-limitations concept as a modeling input does not automatically mean every line item you include is “always allowed” in every circumstance. Your allocation logic should explicitly describe what the 5-year window is doing in your model (e.g., defining an analysis horizon and/or truncating which damages are counted).

DocketMath helps you document the methodology consistently, which is useful when you iterate between settlement positions or litigation stances.

Next steps

Use this step-by-step workflow to choose and run the right DocketMath configuration for New York damages allocation.

Use the Damages Allocation tool to produce a first pass, then share the output with the team for review. You can start directly in DocketMath: Open the calculator.

1) Confirm your damages model’s purpose

Ask which objective you’re meeting:

• Recovery framing where limitations logic matters → choose time-window constrained allocation (5-year default)
• Internal analysis/forecasting where you want full-period output → choose full-period allocation

If you’re unsure, consider running both approaches (next step) and comparing the difference.

2) Lock the time anchor date (this drives the 5-year window)

In DocketMath’s damages-allocation calculator, set the time anchor date that defines the start of your lookback window.

Practical tips:

• Keep a single anchor date consistent across iterations.
• If your case uses a different anchor for different components, run separate calculator scenarios rather than mixing anchor assumptions in one run.

3) Enter damages components in categories you can explain

DocketMath outputs are only as defensible as the categorization you input. If your workflow supports it, enter components separately so you can explain how each component is treated.

A minimal structure to consider:

• component name
• amount
• whether it falls inside your defined window (if SOL-constrained)
• any intentional exclusions

4) Run two versions if you need a sanity check

Before you treat an output as final, compare:

• New York time-window constrained (5-year default)
• Full-period allocation (no truncation logic)

Then check:

• How much shifts due to the window?
• Does the direction of change match your case narrative and expectations?

5) Document the methodology in output-ready terms

After you run the calculator, capture the elements someone reviewing your work would need:

• Jurisdiction mode: US-NY
• Time rule used: general/default 5-year period (and that no claim-type sub-rule was identified for this setup)
• Time anchor date: (the exact date you used)
• Components included/excluded: what changed because of the window behavior

Launch the calculator

Start here: /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