How to run Settlement Allocator in DocketMath for Massachusetts

Step-by-step

Follow these steps to run Settlement Allocator in DocketMath for Massachusetts (US-MA), using jurisdiction-aware rules aligned to the general settlement-allocation framework for Massachusetts class actions.

1) Open the Settlement Allocator tool

1. Go to /tools/settlement-allocator .
2. Select the jurisdiction as Massachusetts (US-MA).
3. Confirm the calculator mode is Settlement Allocator.

If you’re using the UI, you’ll typically see fields for:

• Claimants / claimed amounts
• Allocation basis (how shares are computed)
• A time-window or rule-based period selector (when enabled)
• Output preferences (rounding, formatting, export)

2) Gather the Massachusetts inputs you’ll need

Settlement allocation depends on two things:

• The allocation base (what the settlement is paying out for)
• The claim cohort (who is eligible during the relevant period)

For Massachusetts class actions, DocketMath’s jurisdiction-aware rules rely on Mass. R. Civ. P. 23 and consumer-protection class-action references under Mass. Gen. Laws ch. 93A, § 9(2).

Before you compute, collect:

• The class definition (who qualifies)
• The settlement fund amount available for distribution (or any per-category pools)
• Any formula parameters in the settlement terms (e.g., weighting, caps, claim minimums)
• The default rule period (or the period your settlement uses) for tool selection

Important default period rule (Massachusetts):
No claim-type-specific sub-rule was found. That means DocketMath should use the general/default period for the configured rule set (i.e., the “default period” described by the calculator’s Massachusetts configuration, rather than a claim-type-specific special period). If your settlement specifies a different eligibility window, you should select the tool’s period option that matches that window.

3) Select the Massachusetts rule configuration in DocketMath

Within the tool:

• Set Jurisdiction: US-MA (Massachusetts)
• Enable jurisdiction-aware rules (if available)
• Choose the period option that matches your settlement’s eligibility window

Because Massachusetts uses the class-action baseline in Mass. R. Civ. P. 23, the tool’s Massachusetts rule logic is intended to stay consistent with that framework. For consumer-protection class actions, it also references Mass. Gen. Laws ch. 93A, § 9(2).

4) Enter claimant data (or import it)

You can usually input claimants in one of these patterns:

• Manual entry (best for small lists)

  • Add each claimant row with required values (claimed amount, weighting factor if applicable, and eligibility indicators if the tool asks for them)
• Import / bulk upload (best for larger dockets)

  • Upload a spreadsheet/CSV using the column structure expected for the Settlement Allocator mode

Practical tip: Before uploading, check the tool’s required columns. Missing or misnamed eligibility fields can cause claimants to be treated as ineligible or assigned to the wrong cohort.

5) Set the settlement pool amount and allocation basis

Now define what funds are being allocated and what it means to “earn” a share.

In most settlement allocator workflows, you’ll set:

• Total settlement amount (or the total allocable portion)
• Allocation basis, which controls how shares are calculated

Common allocation bases include:

• Proportional to each claimant’s documented loss/claim value
• Proportional to weighted claim value (claim value multiplied by a weight such as severity or other agreed factors)
• Capped shares or constrained allocation when the settlement applies caps/minimums

How the output changes (in plain terms):

• If allocation is proportional to claim value, claimants with higher documented losses generally receive larger shares.
• If allocation is weighted, the tool multiplies values by weights, which can change the ranking of who receives more—especially when weights vary across claimants.

Use the allocation basis that matches the settlement agreement’s allocation methodology, not just what “looks close.”

6) Run the calculation and review outputs

Click Calculate (or the equivalent action). After the run completes, review:

• Per-claimant allocated amount
• Eligibility / inclusion status
• Total allocated sum (typically should equal the allocable pool, subject to rounding rules)
• Any remainders or rounding adjustments the tool applies

A practical review workflow:

• Sort results by allocated amount to see the top recipients.
• Validate that excluded claimants align with your expected eligibility window (especially if you used a custom period selection).

7) Export results for recordkeeping

Use DocketMath’s export options (CSV/PDF/summary table, depending on what’s available). When you save outputs, keep them organized by:

• Jurisdiction (US-MA)
• Rule period selection (confirm it’s the intended general/default period unless your settlement specifies otherwise)
• Settlement pool amount
• Allocation basis

If the settlement agreement references a named allocation schedule, label your exports using the same schedule name to avoid confusion later.

Common pitfalls

These issues commonly cause Massachusetts runs to look “wrong” even when the math is working:

• Using the wrong period selection

  • Even though Massachusetts uses the general/default period (because no claim-type-specific sub-rule was found), the tool may still require you to select the correct period option in the UI.
  • If your settlement defines a specific eligibility window, select the matching period setting.

• Misalignment between settlement terms and tool inputs

  • If the settlement uses caps, weights, or a specific allocation base, but you select a different allocation basis in DocketMath, totals may still reconcile while individual shares differ materially.

• Missing eligibility flags during import

  • Bulk uploads sometimes omit an eligible indicator or a cohort/date field.
  • Depending on configuration, the tool may treat all rows as eligible, exclude them, or bucket them into an unintended cohort.

• Rounding expectations

  • Allocators often round per claimant.
  • Expect small differences between “sum of individually rounded amounts” vs. the exact unrounded pool. Review how the tool handles rounding/remainders.

• Over-assuming that consumer-protection class actions create special sub-rules

  • This guide is based on the general/default period approach: no claim-type-specific sub-rule was found.
  • So, don’t expect the tool to automatically apply a special period just because the matter involves consumer protection under Mass. Gen. Laws ch. 93A, § 9(2).

Try it

To validate your Massachusetts setup quickly in DocketMath:

1. Open /tools/settlement-allocator .
2. Set:

   • Jurisdiction: US-MA
   • Rule period: the general/default period selection consistent with your settlement eligibility window
   • Allocation basis: proportional/weighted exactly as your settlement describes
3. Run with a small test set (3–10 claimants) first.

While reviewing test results, check:

• Directionality: Do higher claimed amounts (and/or higher weighted values) correspond to higher allocations?
• Inclusion/exclusion: Do eligibility flags and period logic match your expected cohort?
• Totals: Does the tool allocate the full allocable pool (allowing for rounding)?

Mini checklist:

• Massachusetts (US-MA) is selected
• Period uses the general/default period (no claim-type-specific sub-rule found)
• Claimant eligibility fields are populated for each row (or your cohort/date inputs are correct)
• Allocation basis matches the settlement agreement’s allocation method
• You export results that record jurisdiction, period selection, and allocation basis labels

If something looks off, adjust inputs one at a time—commonly period first, then allocation basis, then claimant eligibility fields.

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