How to run Damages Allocation in DocketMath for New Jersey

Step-by-step

Run this scenario in DocketMath using the Damages Allocation calculator.

This guide shows how to run Damages Allocation in DocketMath for New Jersey (US-NJ) using jurisdiction-aware rules. It uses New Jersey’s general statute of limitations (SOL) for contract damages—4 years under N.J.S.A. 12A:2-725—and applies it as the default because no claim-type-specific sub-rule was found for this calculator.

1) Open the calculator

1. Go to the primary CTA: /tools/damages-allocation
2. Select Jurisdiction: New Jersey (US-NJ).

In DocketMath, jurisdiction selection matters because the calculator uses jurisdiction-specific assumptions—here, the 4-year SOL baseline tied to N.J.S.A. 12A:2-725.

2) Confirm the SOL baseline used by the tool

DocketMath will apply New Jersey’s general/default period for the analysis:

• General SOL period: 4 years
• Statute: N.J.S.A. 12A:2-725 (UCC statute of limitations for contracts for sale of goods)

Because no claim-type-specific sub-rule was found, the calculator uses this general/default period rather than switching SOL rules by claim category.

You’ll see this reflected in whichever step in the UI asks for timing inputs (often dates or a lookback window).

3) Enter your core case timing inputs

Provide the following (names may vary slightly depending on the UI labels):

• Trigger event date (e.g., the relevant transaction date tied to the damages theory, or the date the goods/contract performance occurred)
• Filing/claim date
• If the tool requests it: additional relevant dates (such as notice or tender-related dates)

How the output changes:

• If the filing/claim date is more than 4 years after the trigger event date, the calculator’s allocation may shift toward reduced recoverable damages (because time-barred portions can’t be included in the recoverable damages window).
• If the filing/claim date is within 4 years, more damages period may be treated as potentially recoverable (again, depending on how the calculator implements allocation).

4) Enter damages and allocation inputs

Next, input the amounts you want allocated. Typical fields in damages allocation workflows include:

• Total damages amount (or components that sum to it)
• Damages categories (if the tool supports splitting into multiple components)
• Attribution ratios / allocation percentages (if required)
• Any deductions the tool supports (such as credits, offsets, or other adjustments—use only what your workflow includes)

How the output changes:

• Adding more categories usually produces a more granular breakdown in the results (e.g., each category’s recoverable vs. non-recoverable portion).
• Changing ratios/percentages directly changes the allocation output. If the tool validates totals, mismatched percentages may either be rejected or normalized depending on the UI.

5) Run the calculation

Click Calculate / Run Damages Allocation.

At this stage, DocketMath typically computes:

• A recoverable window based on the 4-year SOL rule under N.J.S.A. 12A:2-725
• An allocation breakdown across the damages components you supplied
• A final set of totals you can export or reuse in your workflow

6) Review the results for timing and allocation effects

When results appear, look for:

• Recoverable damages total (or similar)
• Time-barred vs. recoverable split (if the tool provides it)
• Category-by-category allocation output
• Any warnings or notes about SOL boundaries

Common pitfall: The most common “wrong output” scenario is giving a trigger event date that’s off by months or years. With a 4-year baseline from N.J.S.A. 12A:2-725, date errors can flip a portion of damages from “inside the window” to “outside the window.”

7) Export or capture the outputs you need

If the tool offers export options (copy, CSV, PDF, share link), capture:

• Total recoverable damages
• The category allocation table
• Any SOL-related breakdown the tool shows

Then use those outputs consistently in downstream steps (drafting, exhibits, or internal case summaries).

Common pitfalls

Below are issues that repeatedly cause allocation results to look “off” in New Jersey workflows using DocketMath’s damages allocation setup.

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

Date-related pitfalls

• Trigger date misalignment: Using the wrong “start” date for the damages period (e.g., contract formation vs. delivery/actual performance) can shift the SOL window.
• Filing date confusion: Mixing up a notice date with a filing date. DocketMath needs the correct one for timing calculations.
• Boundary effects: A case filed just outside the 4-year window under N.J.S.A. 12A:2-725 can substantially reduce recoverable damages.

Input-structure pitfalls

• Totals don’t match: If your damages categories don’t sum to the total damages, the tool may reject inputs or normalize in a way that you didn’t expect.
• Percentages don’t add up: If the UI expects allocation percentages to total 100%, leaving them short or over can produce normalization.
• Using the wrong adjustment fields: Offsets/credits can double-count if you also apply them manually in the damages amount.

Jurisdiction and default rule misunderstandings

• Assuming claim-type-specific SOL rules apply: In this workflow, DocketMath uses the general/default period found for New Jersey—4 years under N.J.S.A. 12A:2-725—because no claim-type-specific sub-rule was found for this calculator.

Try it

1. Navigate to /tools/damages-allocation
2. Choose **New Jersey (US-NJ)
3. Enter:

   • A trigger event date
   • A filing/claim date
   • Your damages components and allocation inputs
4. Click Calculate
5. Verify two things in the results:

   • Whether your damages window is treated as within or outside the 4-year period under N.J.S.A. 12A:2-725
   • That the allocation table matches your intended category breakdown

To sanity-check quickly, use this checklist against your run:

• The time difference between trigger and filing is ≤ 4 years for portions you want treated as recoverable
• Category percentages/ratios align with your internal attribution logic
• Output totals reconcile with the inputs you intended (no missing categories)

If the output seems counterintuitive, adjust only one input category at a time (usually dates first, then allocations) so you can see exactly how the recoverable window and allocation totals respond.

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