Abstract background illustration for How Settlement Allocator rules vary in New York

How Settlement Allocator rules vary in New York

6 min read

Published June 4, 2026 • By DocketMath Team

Under review

missing_or_unverified_packet

What varies by jurisdiction

Settlement Allocator rules in New York are primarily governed by CPLR Article 9 (§§ 901–909), which provides the framework for apportioning settlement proceeds among judgment creditors and other interested parties when the statutory allocation/distribution mechanics are implicated. In practice, the allocator outcome you get from DocketMath can vary based on (1) which Article 9 allocation/distribution pathway your scenario triggers and (2) the timeline window and distribution order assumptions configured for the allocator run.

New York key point: no claim-type-specific sub-rule found

Based on the provided rule set, no claim-type-specific sub-rule was found. That means you should treat the Article 9 period as the general/default period unless you identify a more specific rule tied to a particular procedural posture in your sources. In other words: don’t change allocator timing just because a label like “claim type” differs—start with the Article 9 default/general timing window.

The New York-specific legal framework (high-level)

CPLR Article 9 (§§ 901–909) lays out how courts and parties handle distribution/allocation issues connected to judgments and related settlement administration. Conceptually, it introduces:

  • A statutory structure for allocation/distribution tied to judgments and interested parties
  • A process that can involve court oversight, depending on the procedural context
  • A timeline effect: different dates and events matter because they determine what is included under the statutory scheme

Source: N.Y. C.P.L.R. Article 9 (§§ 901–909)
https://www.nysenate.gov/legislation/laws/CVP/A9

How this affects your DocketMath setup

When using DocketMath’s Settlement Allocator tool (primary CTA: /tools/settlement-allocator), your New York (US-NY) settings should align with the Article 9 framework, including the default/general timing approach noted above.

In practical terms, New York settings typically need to reflect:

  • Jurisdiction: US-NY
  • Statute-driven allocator timing: use the CPLR Article 9 default/general period (because no claim-type-specific sub-rule was found in the provided rule set)
  • Ordering/distribution assumptions: ensure your modeled allocation matches the distribution mechanics you’re intending to simulate under Article 9

If you feed DocketMath inputs that assume a different jurisdiction’s mechanism (e.g., a different statutory timing/distribution approach), the output allocation can change substantially even when the numerical inputs (damages, settlement amount, and percentages) look identical. The allocator is only as consistent as the jurisdiction-aware assumptions behind it.

Note / limitation: This is an operational explanation of how to configure a tool, not legal advice. For any case-specific procedural posture, verify that the Article 9 pathway you model is truly the one implicated by your matter.

What to verify

Before you rely on the results from /tools/settlement-allocator, verify the New York-specific items below. These are the most common places where allocator outputs swing—even when the underlying numbers appear straightforward.

1) Timeline inputs must match the Article 9 default/general period

For New York, your allocator timing should track CPLR Article 9 (§§ 901–909) using the general/default period, since no claim-type-specific sub-rule was identified in the provided rule set.

Practical checks:

  • Confirm the event dates you plan to use (e.g., relevant filings/decisions/settlement-related events you input) fall within the Article 9 allocator window you selected in DocketMath.
  • If your situation involves court-directed allocation steps, confirm your date selection corresponds to the statutory process actually triggered. If you pick dates based on a different workflow, the “confident” output can still be wrong.

2) Confirm the calculator is jurisdiction-aware (US-NY + Article 9 mechanics)

DocketMath is jurisdiction-aware, so confirm:

  • The calculator is configured for New York (US-NY)
  • The allocator mechanism is aligned to CPLR Article 9 (§§ 901–909)

A frequent workflow issue is copying allocator settings from another jurisdiction (e.g., Ohio or another system) and simply swapping in New York labels. Even with correct arithmetic, the statute-driven assumptions about timing/distribution order may differ.

3) Your allocation inputs must be consistent with the statutory distribution order

Settlement allocation is sensitive to what the allocator is “distributing” and who counts as entitled/interested under the modeled logic.

Verify:

  • Which parties/recipients are included in your allocator run
  • Whether you’re mapping amounts as distributable interests under the Article 9 framework you’re modeling
  • Whether your settlement input is treated as gross vs. net for purposes of the allocation (your output can change depending on which basis your scenario requires)

4) Confirm whether your scenario triggers court involvement under Article 9 mechanics

CPLR Article 9 sets up allocation/distribution procedures that may involve court handling depending on the procedural posture. Your DocketMath inputs don’t replace procedure—they model the statutory allocation framework.

Use a quick checklist aligned to the goal of matching the Article 9 mechanics:

  • Allocator inputs reflect the CPLR Article 9 default/general period
  • DocketMath is set to US-NY
  • Parties included match those intended/impacted under the Article 9 distribution logic
  • Date fields correspond to the statutory timeline you’re modeling
  • Settlement amount basis (gross vs. net) matches your scenario

Warning: A very common failure mode is feeding correct-looking numbers with the wrong statutory basis (especially timing window and distribution-order assumptions). That can yield plausible—but incorrect—allocator results.

5) Use the output as diagnostics for data gaps

A practical way to validate your inputs is to treat output patterns as a signal:

  • If certain recipients receive 0, check whether they were mapped to the right statutory interests/recipients in your inputs.
  • If the allocation looks unexpectedly skewed, re-check your timeline/date alignment with the Article 9 default/general period—date misalignment can materially change the allocator’s inclusion logic.

Related reading

Sources and references:

  • N.Y. C.P.L.R. Article 9 (§§ 901–909): https://www.nysenate.gov/legislation/laws/CVP/A9
  • TODO: If you have a specific New York case posture (e.g., a particular CPLR motion type or order), add the corresponding CPLR section(s) implementing the Article 9 timeline/distribution for that posture.