How to run Settlement Allocator in DocketMath for United States Federal

How to run Settlement Allocator in DocketMath for United States Federal

7 min read

Published August 27, 2025 • Updated April 23, 2026 • By DocketMath Team

Article claim inventory in progress

Trust release 4

This page has legal or numeric text that still needs claim-level inventory before we can treat it as verified.

Step-by-step

This guide walks you through running Settlement Allocator in DocketMath for United States Federal matters using jurisdiction-aware rules (jurisdiction code: US-FED). The goal is to help you produce an allocation that matches common federal settlement modeling needs—without providing legal advice.

1) Open the correct calculator

  • Go to DocketMath’s Settlement Allocator tool here: **/tools/settlement-allocator
  • Confirm you’re starting a new calculation/run (not editing an older run), so the US-FED rules apply cleanly.

2) Set jurisdiction to United States Federal (US-FED)

In the jurisdiction selector:

  • Choose United States Federal (code: US-FED)

What this typically changes in DocketMath:

  • The tool applies federal-oriented allocation logic (for example, how it groups compensation categories and how it interprets settlement components).
  • Jurisdiction-specific toggles or rule sets may become available for US-FED.

Note: DocketMath is designed to support settlement allocation workflows. Even when the model is jurisdiction-aware, you should still verify that your inputs reflect the actual agreement language.

3) Enter the settlement amount(s)

Settlement Allocator usually needs a total settlement amount and optionally a breakdown, depending on the UI.

Use this approach:

  • Total settlement amount: enter the gross settlement figure you’re allocating.
  • If your settlement agreement lists separate components (for example, “damages” vs. “fees” vs. “costs”), enter them into the corresponding fields so the allocator can distribute correctly.

Checklist:

4) Define the allocation basis

Look for inputs that control how DocketMath divides the settlement. Common patterns include:

  • Claimant/party share fields (how much each claimant receives)
  • Category weights (how the model weights damages vs. other components)
  • Number of claimants and allocation method (equal split vs. custom weights)

If the tool offers multiple methods:

  • Select the one that best mirrors the settlement terms you’re implementing.
  • If you’re unsure, pick the closest match:
    • use custom weights if the agreement references category splits or claimant proportions
    • use equal split only if it truly reflects the settlement terms

5) Add parties and (if prompted) claimant attributes

When the UI requests parties:

  • Enter each party/claimant as a distinct row.
  • Ensure names/identifiers are consistent with the rest of your workflow outputs.

If there are additional fields (for example, “basis,” “share %,” or “allocation weight”):

  • Use the agreement’s stated proportions, or compute shares from the stated numbers.
  • Double-check that percentages add up to 100% when the tool expects it.

6) Review the jurisdiction-aware rule toggles

For US-FED, the tool may include checkboxes or rule toggles that affect the allocation output. Labels vary by UI version, but common examples include:

  • Whether to treat certain amounts as separately allocable components
  • Whether to apply default grouping/classification logic for specific payment types
  • Whether to enforce constraints (like totals must reconcile)

Practical rule:

  • If a toggle explains how the tool “allocates” or “classifies” components, set it to align with how your settlement agreement structures payment categories.

7) Run the calculation

Click the action button (commonly Calculate, Run, or similar).

After the run:

  • Confirm totals reconcile (the sum of allocations equals the settlement total, or equals the expected remainder logic).
  • Verify that each claimant/category line item is populated as expected.

8) Validate outputs before exporting

Review the output sections carefully. A typical Settlement Allocator output includes:

  • Allocation amounts per claimant
  • Allocation amounts by category
  • Summary totals and reconciliation checks

Use this validation checklist:

Gentle reminder: this is an allocation model. If anything looks inconsistent with the agreement, pause and confirm your category mapping and totals before relying on the output.

9) Export results for your workflow

If DocketMath provides export formats (often CSV/PDF/spreadsheet-like views):

  • Export both the summary and the detail view (if available).
  • Use a file naming approach that preserves traceability, for example:
    • US-FED_SA_2026-04-15_v1

10) Keep a run log (recommended)

Operational clarity matters—even when you’re not providing legal advice.

Record:

  • the jurisdiction (US-FED)
  • the settlement totals and any category breakdowns
  • the claimant count
  • the chosen allocation basis/method
  • the exported output from the exact run version

This makes it easier to diagnose discrepancies if you later update claimants or revise category inputs.

Warning: If the settlement agreement’s structure changes (for example, reclassifying amounts from “damages” to “fees”), rerunning Settlement Allocator with modified inputs can produce a materially different allocation. Treat each run as tied to a specific set of terms.

Common pitfalls

These are frequent reasons Settlement Allocator outputs don’t match expected results for US-FED workflows.

  • missing a required input
  • using a stale rate or rule
  • ignoring calendar or holiday adjustments
  • skipping documentation of assumptions

If an assumption is uncertain, document it alongside the calculation so the result can be re-run later.

1) Mixing “total settlement” with “net-of-something” totals

If you enter a net amount (after deductions) but allocate as though it’s gross, the outputs may fail reconciliation.

Quick check:

  • Does the settlement amount field correspond to the figure you intend to distribute before any deductions?

2) Entering categories that don’t match the agreement structure

Settlement Allocator can only allocate what you input. If the agreement separates items such as:

  • damages
  • costs
  • fees
  • interest then entering them into the wrong fields can distort category totals.

3) Claimant shares that don’t sum as required

Depending on the chosen allocation method, DocketMath may require:

  • shares/weights to sum to 100%, or
  • weights to reconcile to the settlement total

If you see reconciliation warnings:

  • fix the inputs first
  • then rerun before exporting

4) Forgetting to re-run after changing jurisdiction

If you switch from another jurisdiction to US-FED:

  • ensure the run is created under US-FED settings
  • avoid relying on a post-hoc edit that doesn’t fully refresh rule application

5) Inconsistent identifiers across runs

If you run multiple iterations:

  • keep claimant names/IDs consistent
  • avoid “John A.” vs “John Anthony” unless you truly intend separate rows

Inconsistency can make comparisons misleading.

6) Using equal split when the settlement terms specify weights

Equal split is convenient, but it rarely matches settlements that allocate by:

  • proportionate damages
  • separate categories
  • negotiated shares per claimant

If the agreement specifies proportions, use the custom weights method.

Pitfall: An allocation that “almost” balances often indicates rounding behavior or a mismatch between category totals and the settlement total you entered. If the UI offers rounding settings, adjust them rather than forcing category numbers to fit manually.

Try it

Ready to run a US-FED allocation in DocketMath?

  1. Open Settlement Allocator: **/tools/settlement-allocator
  2. Select jurisdiction: **United States Federal (US-FED)
  3. Enter:
    • the total settlement amount
    • party/claimant rows
    • category breakdown (if your settlement agreement lists components)
  4. Choose the allocation basis/method that matches your terms (equal split vs. weighted)
  5. Click Calculate
  6. Check:
    • reconciliation totals
    • per-claimant allocations
    • category subtotals

Sanity test before you finalize:

  • run with a small set of claimants (e.g., 2–3) if your UI supports it
  • confirm that category totals and claimant totals reconcile
  • then run the full dataset

Related reading