How to run Damages Allocation in DocketMath for New York
Step-by-step
This guide walks you through running Damages Allocation in DocketMath for New York (US-NY) using jurisdiction-aware rules. You’ll set the inputs, confirm the applicable New York allocation framework, and then interpret what DocketMath returns.
Note: DocketMath’s calculations are driven by the inputs you provide. This post explains the workflow and the New York rule structure, but it’s not legal advice.
1) Open the Damages Allocation calculator
- Go to the primary calculator CTA: /tools/damages-allocation.
- Confirm the jurisdiction selector is set to New York (US-NY).
2) Understand the New York allocation framework you’re activating
When you select New York in DocketMath, the tool applies the jurisdiction rule structure tied to:
- N.Y. C.P.L.R. § 1411 (proportionate share / comparative responsibility allocation concept)
- N.Y. C.P.L.R. art. 16 (§§ 1600–1603) (general structured regime for apportionment concepts across qualifying actors and claims)
In practice, DocketMath uses these concepts as the “frame” for how it allocates damages across the parties/periods reflected in your entered facts.
3) Choose the allocation basis in DocketMath
In the calculator workflow, select the allocation mode that matches what your case record supports, such as:
- By party responsibility / proportionate fault, and/or
- By damage component and/or time period (only if your inputs distinguish damages that way)
If you’re unsure which mode fits, align it with the structure you’re already using in your damages model/pleadings. DocketMath is meant to follow your model’s structure rather than invent a new one.
4) Enter the factual inputs
Populate the calculator inputs with the values from your case file. Common input types include:
- Parties to allocate to
- Responsibility indicators (e.g., percentages or weights, depending on the tool’s format)
- Damages amounts per component (e.g., economic vs. non-economic) and/or per time segment, if applicable
- Any caps, reductions, or timing flags required by DocketMath’s New York rule mapping
Checklist for clean runs:
- You have a clear list of allocation recipients (the parties/entities the damages are being allocated “to”).
- Your responsibility measures add up correctly in the format DocketMath expects.
- Each damages component is entered in the correct units (typically dollars) and attached to the correct party/time bucket.
- You used New York jurisdiction settings (US-NY).
5) Confirm the allocation period rule (default vs. claim-type-specific)
DocketMath for New York uses a general/default allocation period when a claim-type-specific sub-rule is not identified.
In this New York dataset, no claim-type-specific sub-rule was found, so the tool should follow the general/default period tied to the New York regime described by N.Y. C.P.L.R. § 1411 and Article 16 (§§ 1600–1603).
Concretely, what to do in the UI:
- Look for a period selection or timing selection step.
- If you see an option like “default period” vs. “custom period”, keep default unless you have a documented basis for a specific period that your record supports.
- If the tool allows selecting a claim type, and you don’t have a claim-type-specific rule basis in your dataset, avoid switching away from default—doing so can change the allocation window and therefore the totals.
Warning: Switching from “default period” to a claim-type-specific/custom period without a supporting New York rule basis can materially change the allocation results—even when the parties and responsibility inputs are identical.
6) Run the calculation
- Click Calculate (or the equivalent button).
- Review:
- Total damages allocated
- Allocated shares by party/component
- Any intermediate outputs (e.g., subtotals by component or by period)
If DocketMath shows validation messages, fix them before re-running:
- Percentages/sums match the required format (if the UI requires totals to reach 100%, follow that requirement)
- No negative values unless explicitly allowed by the tool/UI
- Each damages component has a corresponding allocation basis (as required by the calculator)
7) Interpret outputs and adjust inputs intentionally
Use an “input → output” approach:
| If you change… | Expected effect in DocketMath |
|---|---|
| Party responsibility weight/share | Rebalances allocated totals across parties while component totals may remain stable |
| Component damages amount | Changes that component’s contribution to total allocated damages |
| Allocation period/timing settings (only if not default) | Alters what portion of the damages is included in the allocation window |
| Number of parties included | Distributes shares across a larger or smaller set, changing per-party results |
When rerunning:
- Make one change at a time for clean comparison.
- Keep a short note of what changed (e.g., “Party B share increased from 20% to 25%”).
8) Export or save your results
If DocketMath provides export or save options:
- Export the calculation output.
- Save screenshots of key tables (especially if you’ll need them in settlement discussions or internal review).
Even without legal advice, keeping an auditable record of the exact inputs you used makes your damages presentation easier to verify.
Common pitfalls
These issues are frequent when running damages allocation workflows in DocketMath for New York:
Accidentally using the wrong jurisdiction setting
- If New York isn’t selected, US-NY rule logic won’t apply.
Misaligned responsibility input format
- Example: entering responsibility weights as whole numbers when the tool expects percentages (or vice versa).
- Result: allocations can skew even if the values “look right” at a glance.
Unintentionally switching from default period
- Because no claim-type-specific sub-rule was found in this dataset, the calculator should follow the general/default period.
- Result: changing timing settings can change which amounts are included and therefore the totals.
Mixing damages components
- If you enter economic and non-economic damages into the same component field (or attach them to the wrong bucket), you’ll distort the allocation.
Ignoring validation warnings
- Don’t rely on assumptions—confirm what each warning means in the UI before re-running.
Pitfall: If your totals don’t add up after the run, don’t immediately “fix” numbers by guessing. First check whether the calculator expects responsibility inputs to sum to 100%, whether it normalizes weights, and whether any component fields are optional/nullable.
Try it
Run a complete New York allocation pass in DocketMath now:
- Select New York (US-NY).
- Use the default period unless your record clearly supports changing it.
- Enter:
- Parties to allocate to
- Responsibility shares/weights
- Damages by component and/or time buckets (only where supported by your case model)
- Click Calculate and review:
- Total allocated damages
- Per-party allocation table
- Component/period subtotals (if shown)
To pressure-test your run quickly, do one controlled rerun:
- Change one responsibility share by a small amount (e.g., +5 percentage points) and confirm the allocation table updates in the direction you expect.
If you want a smoother workflow next time, pre-compile your inputs into a checklist:
- Parties list
- Responsibility shares/weights in the tool’s required format
- Damages component amounts in dollars
- Period selection left at default (because no claim-type-specific sub-rule was found)
Related reading
- How to calculate Damages Allocation in Philippines — Full how-to guide with jurisdiction-specific rules
- Worked example: Damages Allocation in Philippines — Worked example with real statute citations
- Inputs you need for Damages Allocation in Philippines — Input checklist with sourcing guidance
Run the numbers for your matter against the verified rule for this jurisdiction.
Run the allocation