Abstract background illustration for How to run Settlement Allocator in DocketMath for New Jersey

How to run Settlement Allocator in DocketMath for New Jersey

6 min read

Published June 4, 2026 • By DocketMath Team

Partially verified

older_than_packet

Step-by-step

This guide walks you through running Settlement Allocator in DocketMath for New Jersey (US-NJ), using jurisdiction-aware rules driven by N.J. Ct. R. 4:32. The process is the same whether you’re allocating a single lump-sum settlement or reconciling multiple payments—you’re aiming to ensure the allocator uses the correct default timing framework for New Jersey.

Important note (jurisdiction/timing scope): DocketMath’s jurisdiction-aware configuration applies the general/default period because no claim-type-specific sub-rule was found within the cited rule reference. In other words, you should not expect the tool to switch to different timing periods by claim type for New Jersey; it will use the default framework described by N.J. Ct. R. 4:32.

1) Open the Settlement Allocator tool

  1. Navigate directly to the calculator: /tools/settlement-allocator
  2. Confirm the jurisdiction selection is set to New Jersey (US-NJ).

If you’re already using DocketMath navigation, the same entry point applies:

  • /tools/settlement-allocator

2) Identify the settlement inputs you’ll need

Before running the allocator, gather the inputs from your case materials (or your internal spreadsheet). Typical inputs include:

  • Total settlement amount (the lump sum to allocate)
  • Payment structure (single payment vs. multiple payments, if your tool flow supports that)
  • Known allocation bases (e.g., amounts tied to categories you want to allocate across)
  • Relevant dates (where the tool asks for them)

In DocketMath, some fields may be required, while others act as optional refinements. Regardless, your output will change based on:

  • the total amount (scale effect), and
  • the time-sensitive components governed by N.J. Ct. R. 4:32 (timing/period effect), and
  • any category weights/bases or constraints you enter.

3) Enter dates according to New Jersey’s default timing framework

For New Jersey, use this rule reference:

When you provide dates to the tool, make sure they match the event you’re modeling (for example, the start/end of the period the rule applies). Because the allocator is operating under the general/default period (and no claim-type-specific sub-rule was found), you should expect the same timing framework across categories.

Date entry checklist:

  • Dates are in the format the tool expects (avoid swapping month/day)
  • Start and end dates align to the timeframe you intend to model
  • You’re using the default timing approach under N.J. Ct. R. 4:32 (not different time windows by claim type)

Gentle reminder: This is procedural guidance on using the calculator. It’s not legal advice. If you’re unsure how a rule is intended to apply to your specific facts, consider consulting a qualified attorney.

4) Run the calculation

  1. Verify the jurisdiction label reads New Jersey (US-NJ).
  2. Review any intermediate/computed values shown by the tool (if displayed).
  3. Click Calculate / Run (button naming may vary).

5) Review the allocation output and how it changes with inputs

After the run completes, DocketMath will display an allocation breakdown. Focus on:

  • Allocated amounts by category (or buckets) based on the bases/weights you entered
  • Time-period-driven calculations tied to the N.J. Ct. R. 4:32 framework
  • Totals and reconciliation to confirm the allocation matches your settlement amount (subject to rounding/precision settings)

Quick sanity checks:

  • Do categories reflect the relative weight or base you entered?
  • If you adjust a date slightly (within a reasonable range), do only the timing-dependent components move as expected?
  • Does the allocation sum to the total settlement you provided?

Warning (reconciliation): If the allocation totals don’t reconcile to the settlement amount, it’s usually due to one of the following:

  • a missing category/base input,
  • a fixed amount placed in one bucket without updating the remainder logic,
  • or rounding/precision behavior.

Treat the results as “draft math” until the totals reconcile cleanly.

6) Save/export your run (if supported)

If DocketMath offers saving or export features:

  • Save the run with a descriptive name such as “NJ settlement allocator – 2026-06 run”
  • Export to PDF/CSV if available, to keep an audit trail
  • Record the key date inputs and settlement totals in your case notes so the output can be reproduced later

Common pitfalls

These are the issues that most commonly lead to confusing results when running Settlement Allocator for New Jersey (US-NJ).

Input-date mismatch

If the tool requests a start/end date and you enter dates for the wrong modeled event, the period under N.J. Ct. R. 4:32 will be applied to the incorrect timeframe.

Quick check:

  • Start date is the beginning of the modeled period
  • End date is the end of the modeled period
  • You’re using the general/default period framework (no claim-type-specific sub-rule was found)

Expecting claim-type-specific time rules (but none are included)

Because no claim-type-specific sub-rule was found in the cited rule reference, the allocator should behave consistently across categories for timing.

Pitfall pattern:

  • you input multiple claim types and expect different time windows per claim type, but
  • the output looks “wrong” because it’s applying the same default timing framework.

Omitting a bucket/base or entering weights inconsistently

If you provide a total settlement but only some categories have bases/weights (or fixed amounts), the allocation may not match your expectations.

Checklist:

  • Every intended bucket has a base/weight (or is explicitly fixed)
  • You understand which buckets are fixed vs. computed

Misreading rounding behavior

Allocation tools often round after calculating intermediate values. That can create small differences (e.g., a few dollars).

Resolution:

  • Compare the sum of displayed bucket amounts to the total settlement
  • Check whether the tool provides a rounding/precision option

Using the wrong jurisdiction

This happens especially when templates are reused.

Guardrail:

  • Confirm US-NJ is selected before running

Try it

You can run Settlement Allocator in DocketMath here:

  • /tools/settlement-allocator

Before clicking Calculate, do a quick pre-flight check:

  • Jurisdiction is New Jersey (US-NJ)
  • Dates reflect the period you intend to govern under N.J. Ct. R. 4:32
  • You’re using the general/default period (no claim-type-specific sub-rule found)
  • Total settlement amount is correct
  • Buckets/categories match how you want the settlement allocated

Fast validation loop:

  1. Run once with your best estimates.
  2. Adjust one input date slightly (e.g., move the end date forward one day) and rerun.
  3. Confirm only the timing-linked pieces change, while other bucket logic remains consistent with your entered bases/weights.

Related reading