What this calculator does

DocketMath’s Settlement Allocator helps you divide a settlement amount into separate categories—such as compensatory damages, interest, attorneys’ fees, and costs—so the allocation is easier to document for tax preparation and reporting workflows.

You enter assumptions, then the calculator produces an allocation schedule you can copy into your case file or settlement worksheet. The output is not a court order, and it doesn’t determine liability; it’s a practical organization tool that helps you model how different settlement components might be treated under commonly used reporting practices.

Because this guide is for Massachusetts (US-MA), it also includes a Massachusetts-specific statute of limitations checkpoint. In particular:

• General limitations period: 6 years under Mass. Gen. Laws ch. 277, § 63.
• Notable carve-out described for this guide: Jenkins v. Jenkins, 15 Mass. App. Ct. 934, 935 (1983) references a 3-year limitations period for a narrower category (listed here as exception M5 for this tool’s workflow).
• The Massachusetts data you provided also includes an explicit exception V1 tied to Mass. Gen. Laws ch. 277, § 63 (6 years).

When to use it

Use the DocketMath Settlement Allocator when you have a settlement figure and you need to create a clean breakdown that matches how people typically document settlements for filings, accounting, and tax-related workflows.

Common triggers include:

• You received a lump-sum settlement and need an allocation memo for internal records.
• You need to separate interest or fees from principal amounts because your workflow tracks them differently.
• You’re preparing documentation for a payment distribution (e.g., among parties, counsel, or lienholders) and want a consistent structure.
• You’re working with a Massachusetts matter and want a built-in prompt to consider the 6-year limitations window under Mass. Gen. Laws ch. 277, § 63.

To connect the tool to Massachusetts timing, here’s what the calculator workflow will help you sanity-check:

Massachusetts limitations checkpoint (workflow prompt)

Base rule (for this guide)

• 6 years under Mass. Gen. Laws ch. 277, § 63 (listed as “exception V1” in your jurisdiction data).

Narrow carve-out referenced

• 3 years referenced in Jenkins v. Jenkins, 15 Mass. App. Ct. 934, 935 (1983) (listed as “exception M5” in your jurisdiction data).

In practice, you should treat this as:

• A prompt to confirm which “type” of claim you’re dealing with, and
• A reminder to keep settlement allocation records aligned with the timeframe your documentation relies on.

Step-by-step example

Below is a concrete walkthrough using typical settlement inputs for a Massachusetts case. You can follow the same structure even if your amounts differ.

Scenario setup

Assume you settle for a total of $120,000 in a Massachusetts matter.

You want to allocate:

• Compensatory damages (principal): $95,000
• Prejudgment interest: $20,000
• Attorneys’ fees: $4,000
• Costs: $1,000

Quick inputs checklist (what you’ll enter)

• Total settlement amount: $120,000
• Category amounts (or % splits):

  • Compensatory damages: $95,000
  • Interest: $20,000
  • Attorneys’ fees: $4,000
  • Costs: $1,000
• Payment date (optional, if your workflow uses it for your worksheet timing notes): March 1, 2026

To launch the tool, use: **/tools/settlement-allocator

Run the tool

Open the DocketMath Settlement Allocator and enter the amounts (or percentages if you prefer). After calculation, verify that category sums match the total.

Output you should expect (allocation schedule)

The calculator will generate a schedule similar to this:

Massachusetts documentation checkpoint (time limit prompt)

Now add a basic record-keeping check tied to Massachusetts limitations.

Say the “accrual” or relevant event date you track is April 15, 2018. The Massachusetts base limitations window for this guide is:

• 6 years under Mass. Gen. Laws ch. 277, § 63.

From April 15, 2018 to March 1, 2026 is just under 8 years. That mismatch means your file should clearly document the basis for why the settlement is still within an applicable limitations period (if it is), or why a different limitations concept applies.

If your situation resembles the narrower time frame described in Jenkins v. Jenkins, 15 Mass. App. Ct. 934, 935 (1983) (listed as exception M5 in your jurisdiction data), you would similarly want your records to reflect that characterization.

Common scenarios

Settlement allocations tend to cluster into a handful of repeatable patterns. Use these scenarios to choose your inputs and avoid avoidable reconciliation headaches.

1) Pure lump-sum with no stated components

You know the total (e.g., $50,000) but the settlement agreement doesn’t break it down.

Typical approach in the tool:

• Use a single “Compensatory damages” bucket unless you have a stated basis for interest, fees, or costs.

Checkboxes to confirm before running the model:

If you don’t have the supporting basis, keep the allocation conservative (single category) so later documentation doesn’t conflict.

2) Settlement that expressly distinguishes principal and interest

Many settlements list interest separately (especially when the communications reflect a calculation).

Tool inputs:

• Compensatory damages: principal
• Interest: computed or stated interest
• Fees/costs: only if you have a stated breakdown or a consistent invoice basis

This scenario is where allocation percent changes most clearly affect your reporting worksheet.

3) Fees and costs paid out of settlement, not separately

Sometimes the settlement amount includes amounts “for” attorneys’ fees and costs, but they are actually paid to different recipients.

Use the tool to produce:

• A category breakdown that totals the settlement amount, and
• A notes line in your internal worksheet identifying who ultimately receives each category.

Even if payment mechanics are handled elsewhere, the allocation schedule helps keep internal records aligned.

4) Multiple claims resolved together (composite settlement)

If your settlement resolves multiple issues, the tool can still help by allocating among categories (damages/interest/fees/costs). What it won’t do is allocate by claim type automatically unless you provide category totals consistent with your documentation.

Workflow suggestion:

5) Massachusetts timing review baked into the record

Use the statute checkpoint to prompt file hygiene.

• Base: 6 years under Mass. Gen. Laws ch. 277, § 63
• Narrow reference: 3 years referenced in Jenkins v. Jenkins (exception M5 in your jurisdiction data)

Tips for accuracy

These practical steps will improve the quality and consistency of your DocketMath allocation output.

Align your totals before you interpret results

• Make sure your entered category amounts sum to your entered Total settlement amount.
• If you use percentages, ensure they sum to 100% (including interest/fees/costs if you’re splitting them).

Use source-aligned numbers

Better inputs lead to cleaner output:

• Use the numbers stated in the settlement agreement when available.
• If fees or costs are in invoices, use invoice totals that correspond to the representation period described in your matter file.
• For interest, use the worksheet computation or stated interest formula rather than estimating.

Treat the limitations checkpoint as a documentation control

For Massachusetts workflow, keep a dated record reflecting:

• The relevant event date you’re using,
• Why 6 years under Mass. Gen. Laws ch. 277, § 63 is applicable in your file, or
• Why a narrower 3-year concept referenced in Jenkins v. Jenkins, 15 Mass. App. Ct. 934, 935 (1983) (exception M5) might be relevant.

Related reading

• Settlement Allocator Guide for Alabama
• Settlement Allocator Guide for Arizona
• Settlement Allocator Guide for California