Inputs you need for Damages Allocation in New Jersey

Inputs you will need

Run this scenario in DocketMath using the Damages Allocation calculator.

DocketMath’s Damages Allocation workflow is designed to take the core facts you already use to explain how damages get split among competing theories (and, where relevant, among multiple categories). For New Jersey, the most common “starting point” for timing questions in contract-style damages work is the general statute of limitations of 4 years under N.J.S.A. 12A:2-725—but that is only a default input, not a substitute for claim-theory-specific limitation analysis.

Before running the tool, gather these inputs. Treat them like a minimum “fact bundle” so DocketMath can allocate amounts consistently.

Gentle disclaimer: This is not legal advice. Use these inputs to structure a model; limitation periods and accrual can be fact- and theory-dependent.

Core damages and allocation inputs (nearly always required)

• ☐ Claim start date / accrual date (or the breach date, depending on how your theory frames accrual)
• ☐ Calculation end date (often “as of” the date damages are quantified, or the date you want to cap/reflect)
• ☐ Total damages amount (dollars)
• ☐ Damages category breakdown—how you want the total split, such as:

  • ☐ Contract / UCC-related damages (if applicable to the theory you’re using)
  • ☐ Incidental damages (if applicable)
  • ☐ Consequential damages (if applicable)
  • ☐ Other components you want treated as separate buckets
• ☐ Allocation weights or drivers—how the tool should distribute the total across categories:

  • ☐ Fixed dollar amounts per bucket, or
  • ☐ Percentages per bucket, or
  • ☐ Another measurable basis you’ve chosen for the split

Jurisdiction-aware timing input (default/general rule for NJ)

Even when your primary goal is allocation, timing can influence what portion of damages your model includes (for example, when you apply a limitations cap inside the workflow).

• ☐ Jurisdiction: **New Jersey (US-NJ)
• ☐ Statute of limitations period to apply: 4 years (default/general)

Important default rule (as reflected in your brief): No claim-type-specific sub-rule was found. The workflow should therefore use the general/default 4-year period rather than attempting to branch into special limitation rules for different claim types.

Statutory reference (for the default period):

• N.J.S.A. 12A:2-725 (general SOL period used here): https://law.justia.com/codes/new-jersey/title-12a/section-12a-2-725/

Supporting factual constraints (recommended)

These aren’t always required, but they make results easier to defend and reproduce:

• ☐ Whether damages are one-time vs. periodic

  • If periodic: provide frequency and duration
• ☐ Known offsets you intend to subtract before allocation
• ☐ Currency and rounding preferences (e.g., round to nearest dollar)

Where to find each input

Pull each input from your existing case materials, then convert it into a clean “tool-ready” format.

Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.

Dates and limitation period (New Jersey timing)

• Accrual / breach date: commonly in

  • ☐ the complaint allegations,
  • ☐ discovery responses,
  • ☐ deposition summaries,
  • ☐ or your internal damages memo.
• Default 4-year period for this workflow: apply N.J.S.A. 12A:2-725 as the general/default limitation period:

  • General SOL period used here: 4 years
  • Source: https://law.justia.com/codes/new-jersey/title-12a/section-12a-2-725/

Total damages and category breakdown

• Total damages amount: typically in

  • ☐ a damages report,
  • ☐ an expert declaration,
  • ☐ a valuation spreadsheet,
  • ☐ or a litigation budget summary.
• Category components: locate the line items that make up your total, such as:

  • ☐ invoices / purchase-price computations
  • ☐ repair / replace costs
  • ☐ lost profits model outputs
  • ☐ incidental costs
  • ☐ clearly labeled “other” buckets with dollar figures

Allocation weights/drivers

Use whatever method you can justify in your damages narrative:

• ☐ “We allocate 60% to X / 40% to Y because…”
• ☐ “We treat this as fixed dollar amounts per component…”
• ☐ “We allocate pro rata based on each component’s contribution…”

If you don’t have a justification yet, build one before entering numbers—DocketMath can only allocate based on the basis you supply.

Run it

1. Open DocketMath Damages Allocation

   • Go to: /tools/damages-allocation
2. Set jurisdiction

   • Choose US-NJ so the workflow uses New Jersey timing inputs in the modeled default approach.
3. Enter the default SOL period

   • Set the limitation period to 4 years (general/default), per the workflow guidance and N.J.S.A. 12A:2-725.
   • Source (for the default period used here): https://law.justia.com/codes/new-jersey/title-12a/section-12a-2-725/
4. Input your damages structure

   • Select an allocation mode:

     • ☐ Fixed bucket amounts, or
     • ☐ Percentage splits
5. Provide date logic

   • Enter the accrual/start date and the end date through which damages are measured in your model.
6. Review output buckets

   • Confirm DocketMath is allocating:

     • total → category buckets, and
     • (when configured by the workflow) trimming/excluding portions outside the limitation window based on your provided dates.

How outputs change when you change inputs

Use these common “what-if” effects while testing your run:

Pitfall to watch: If you enter bucket percentages that don’t add to 100%, DocketMath may scale the result in a way you didn’t intend. Normalize percentages before running.

When your run looks right, export/save the allocation results for your damages memo, settlement analysis, or internal review workflow.

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