How to run Damages Allocation in DocketMath for New Jersey

Step-by-step

This guide walks you through running Damages Allocation in DocketMath for New Jersey (US-NJ) using jurisdiction-aware rules. You’ll start from the /tools/damages-allocation calculator, enter New Jersey–specific settings, and interpret the results.

1) Open the calculator

• Go to: /tools/damages-allocation

2) Select the jurisdiction

In the calculator’s jurisdiction selector:

• Choose: New Jersey (US-NJ)

DocketMath will use the jurisdiction settings tied to New Jersey’s damages allocation framework, including the governing statutory period from:

• N.J.S.A. § 2A:15-5.1 (see statute details at: https://law.justia.com/codes/new-jersey/title-2a/section-2a-15-5-1/)

3) Enter the allocation inputs

DocketMath’s Damages Allocation flow is driven by the dates and amounts you provide. If you don’t have these ready, gather them first so you don’t have to restart the run.

Use these input categories as your checklist:

• Total damages / total claim amount (the base value to allocate)
• Relevant date range (the start and end dates that define the allocation period)
• Known paid/credited amounts (if your workflow requires credits or prior recovery)
• Allocation parameters (as shown by the tool UI)

If DocketMath asks for dates that look like:

• “From” / “To” dates for allocation, or
• effective period dates,

use the dates that correspond to the timeframe your damages allocation is intended to cover.

4) Confirm the allocation period rule

After you enter your dates, review the tool’s computed “allocation period” (or equivalent output section). For New Jersey, the calculator is expected to apply the general/default allocation period under:

• N.J.S.A. § 2A:15-5.1

Because the dataset indicates no claim-type-specific sub-rule was found, DocketMath should not switch periods based on a claim category inside this run. If the interface presents a toggle for “claim-type sub-rule,” keep it on the default behavior for this jurisdiction unless the tool explicitly provides a supported New Jersey option backed by the statutory scheme above.

5) Run the calculation

• Click Calculate / Run Damages Allocation (wording may vary slightly in the UI)

DocketMath computes:

• the allocated amounts for the required time segments (e.g., portions of the total allocated to different time windows, depending on the calculator design),
• any remaining/unallocated balance, and
• summary figures that help you report or reconcile results.

6) Review outputs and reconcile against your expectations

Go through outputs in this order:

1. Allocation period shown by the tool
2. Allocated totals (make sure they sum to your “total damages” input or to the expected base after credits)
3. Any adjustment lines (for example, “net of payments” if the tool includes it)
4. Final allocated totals for reporting

If the allocated totals don’t reconcile:

• re-check date inputs first (off-by-one-day errors can shift which segment a day belongs to),
• then re-check total amount and credited/paid amounts.

7) Export or capture results for your workflow

Most DocketMath workflows support copying results or using the tool output to populate a downstream drafting or analysis step.

Before you finalize:

• capture the jurisdiction (US-NJ) you selected,
• note the allocation period that DocketMath used, and
• save the input date range you entered.

That metadata is what you’ll need if you later rerun the calculation with revised facts.

Common pitfalls

Below are the mistakes that most often cause New Jersey Damages Allocation runs in DocketMath to produce confusing outputs—especially when the allocation period is governed by N.J.S.A. § 2A:15-5.1.

Date range errors (most common)

• Start date after end date (tool may error or swap, depending on UI)
• Using wrong event dates (e.g., mixing “incident date” vs. “discovery date”)
• Entering exclusive vs. inclusive boundaries without realizing it (a one-day shift can change segment totals)

Accidentally changing the allocation period logic

• Trying to apply a claim-type-specific sub-rule when the jurisdiction data indicates none was found
• Updating inputs in a way that changes the effective allocation windows without realizing it

Mismatch between “total damages” and “net of credits”

• Entering the “gross” total damages while also entering credits/paid amounts that are meant for a “net” figure
• Running once with credits and once without credits, then comparing allocated outputs as if they were for the same base

Reconciliation failure when summarizing results

• Copying only allocated amounts and omitting adjustment lines (e.g., credits)
• Relying on segment numbers without confirming they sum to the tool’s displayed “allocated total”

Try it

You can validate your setup with a quick dry run in DocketMath:

• Open /tools/damages-allocation
• Set jurisdiction to New Jersey (US-NJ)
• Enter:

  • a total damages amount,
  • a date range that defines the allocation window, and
  • any credits/paid amounts if your workflow requires them
• Run the calculation
• Confirm three things:

  1. The allocation period is consistent with the New Jersey default framework under N.J.S.A. § 2A:15-5.1
  2. Segment allocations reconcile to the tool’s stated totals
  3. Any credits/adjustments are reflected exactly once

If you need to align your inputs with what the calculator expects, use the internal links below to tighten your setup before you rerun:

• Review the general damages-allocation approach inside DocketMath: /tools/damages-allocation
• If you want jurisdiction-neutral input structure first, read the Philippines pages for the input checklist and walkthrough patterns (the mechanics of entering inputs carry over, while the statutory periods and rules differ by country/jurisdiction).

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