How to run Settlement Allocator in DocketMath for New York

Step-by-step

This guide walks you through running Settlement Allocator in DocketMath for New York (US-NY) using jurisdiction-aware rules. It’s written to help you set up an allocation workflow that matches the New York framework under CPLR Article 9 (§§ 901–909).

Note (New York rules scope): For New York, no claim-type-specific sub-rule was found for Settlement Allocator in the provided jurisdiction dataset, so the general/default period applies under CPLR Article 9 (§§ 901–909). In practice, that means you should not expect the allocator to switch to a separate time rule based on a specific claim type unless your case setup includes additional jurisdiction-specific configuration.

1) Open the calculator

1. Go to the tool page: /tools/settlement-allocator
2. Select Jurisdiction: US-NY (New York).
3. Confirm you’re using the Settlement Allocator calculator (not a different docket tool).

2) Identify the inputs you’ll provide

Before you start entering values, assemble the numbers you plan to allocate. A typical Settlement Allocator run needs:

• Total settlement amount (the money to be distributed)
• Allocated categories / parties you want the allocator to assign amounts to
• Timing inputs that determine the allocation basis under the New York rules in CPLR Article 9 (§§ 901–909)

If DocketMath displays additional fields (for example, date ranges), treat them as inputs that shift the allocator’s results, not optional metadata.

3) Enter the New York timing basis (CPLR Article 9 framework)

New York’s settlement allocation logic in this workflow is anchored to CPLR Article 9 (§§ 901–909).

• Source of rules: https://www.nysenate.gov/legislation/laws/CVP/A9

Because Settlement Allocator is designed to be jurisdiction-aware, ensure your date inputs match the period you intend the allocation to reflect under CPLR Article 9’s general scheme as implemented in the calculator.

Checklist for date fields:

• Dates are entered in the format the calculator expects (avoid accidental swaps like 01/06 vs 06/01).
• You’re not mixing “filing date” and “occurrence date” unless the calculator explicitly asks for each one.
• You’re using the general/default period rather than assuming there’s a claim-type-specific period (no claim-type-specific sub-rule was found from the provided dataset).

4) Map the categories (what gets allocated)

For the allocation to be meaningful, the categories you enter should line up with who/what you intend to distribute funds to. Examples of category mapping (depending on the fields DocketMath offers) can include:

• Parties / claimants
• Time-based buckets
• Other allocation groupings your workflow requires

In general:

• Adding more categories can create more granular output.
• Fewer categories can consolidate allocations and reduce detail.

5) Run the calculation

Click Calculate (or the equivalent button in DocketMath). The output typically includes:

• Allocated amounts per category/party
• Percentages or distribution weights (if displayed by the tool)
• A summary view showing how the timing basis affects the numbers

If DocketMath shows intermediate values, treat those as diagnostics:

• If an intermediate period seems wrong, revisit the date inputs first.
• If totals don’t reconcile to your total settlement amount, confirm you didn’t leave a category out or enter conflicting totals.

6) Review outputs against your workflow expectations

Use this quick review method:

7) Export or record the results

Once satisfied:

• Save or export the calculation results if the tool supports it.
• Record the jurisdiction selection (US-NY) and the dates used so you can rerun quickly later if inputs change.

If you’re iterating (common during settlement conferences), keep a short note on what changed (for example, “updated end date” or “replaced total settlement amount”).

Common pitfalls

These are the mistakes that most often lead to wrong or confusing allocator output when running Settlement Allocator for New York.

1. Assuming claim-type-specific periods exist

   • The provided jurisdiction dataset did not identify claim-type-specific sub-rules for New York.
   • That means the allocator should follow the general/default period under CPLR Article 9 (§§ 901–909) rather than switching logic per claim type.

2. Entering dates in inconsistent roles

   • A common error is mixing up what each field represents (e.g., “start of period” vs “date of event” vs “filing date”).
   • Even a single swapped month/day can materially change period-weight calculations.

3. Mismatching totals when categories change

   • If you add a category after a run, ensure its amount/weight is handled consistently.
   • If DocketMath uses category weights, leaving a category blank (or unintentionally setting a weight to 0) can prevent reconciliation.

4. Treating the allocator output as a legal determination

   • Settlement Allocator is a calculation workflow tied to the jurisdiction framework, not a substitute for legal judgment.
   • Use outputs as a math/allocations baseline, and keep an audit trail of inputs.

5. Using the wrong jurisdiction selection

   • Running the calculator under the wrong jurisdiction (even once) can produce outputs that won’t reconcile with your New York-based workflow.
   • Always verify US-NY before clicking Calculate.

Try it

If you want a low-friction way to test the workflow, run two quick scenarios and compare outputs.

Quick A/B test (recommended)

• Run Scenario A

  • Use your best current total settlement amount
  • Use your intended timing inputs based on the New York framework under CPLR Article 9 (§§ 901–909)
• Run Scenario B

  • Change only one variable (for example, adjust the end date by 1–30 days)
  • Leave every other input unchanged

Then verify:

• Allocations changed in the direction you expect based on the time shift.
• The total reconciliation still equals your Scenario B total settlement amount.
• Category shares update consistently (no category disappears unless you removed it).

Minimal “inputs sanity” checklist

• Jurisdiction is set to US-NY
• Total settlement amount matches what you intend to allocate
• Dates entered are consistent (same format; no swapped day/month)
• You’re using the general/default period logic for New York (no claim-type-specific sub-rule detected in the provided dataset)
• Output totals reconcile and per-category numbers look plausible given the date change

To jump straight in, open the tool: /tools/settlement-allocator

Related reading

• How to calculate Settlement Allocator in Ohio — Full how-to guide with jurisdiction-specific rules
• How to calculate Settlement Allocator in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Settlement Allocator in Philippines — Worked example with real statute citations