How to calculate Damages Allocation in Massachusetts

Quick takeaways

• In Massachusetts, damages allocation among multiple liable parties is guided by Mass. Gen. Laws ch. 231 § 85.
• DocketMath’s “Damages Allocation” calculator (configured for US-MA) helps you turn your case’s damages figures into a repeatable allocation worksheet.
• The most reliable workflow is to start with a single total damages figure and pair it with a consistent allocation basis for each party, so the calculator’s outputs reconcile cleanly back to your starting total.
• If your matter involves joint tortfeasors, you may also want to review how Mass. Gen. Laws ch. 231B is relevant to the parties and your internal documentation workflow (the calculator helps organize numbers, not provide legal advice).

Inputs you need

Before you run DocketMath’s Damages Allocation (US-MA) calculator, gather the inputs that you’ll map into the Massachusetts allocation workflow tied to Mass. Gen. Laws ch. 231 § 85.

Core inputs (usually required)

• Total damages amount you intend to allocate (the number your final allocation table should reconcile to)
• Allocation basis for each party (i.e., the values or basis fields you will enter for each party so the tool can compute party shares)
• List of parties to allocate across (each party you want represented should have consistent allocation-basis inputs)

Multi-party / joint context inputs (often relevant)

• Whether joint-tortfeasor concepts are part of your scenario, so you can decide whether to incorporate Mass. Gen. Laws ch. 231B into your documentation workflow
• Whether you have multiple theories or components that contribute to the total damages—if so, make sure your allocation basis values consistently reference the same overall damages pool

DocketMath setup actions

• Select the Massachusetts (US-MA) jurisdiction inside the Damages Allocation tool
• Open the calculator at: /tools/damages-allocation
• Enter party-by-party allocation inputs using the same basis structure across all parties
• Save or export the worksheet output so you can reconcile totals to the damages figure you started with

How the calculation works

DocketMath’s Damages Allocation tool takes your Massachusetts inputs and produces a party-level allocation table. Conceptually, the workflow is:

1. Start with one total damages “pool.”
2. Apply a consistent party allocation basis across all parties.
3. Compute shares that reconcile back to the total damages pool.
4. Run a reconciliation check to confirm the allocation table matches your entered total (accounting for any rounding behavior the tool displays).

1) Start with a single damages “pool”

DocketMath assumes there is one total damages figure that the allocation output should reconcile to. In practice, that means:

2) Apply Massachusetts allocation workflow (ch. 231 § 85)

Your tool configuration for US-MA is designed to reflect the Massachusetts approach referenced in Mass. Gen. Laws ch. 231 § 85. Practically, this shows up as:

• You enter party allocation basis inputs in a structured way
• The calculator applies the Massachusetts rule set for how to generate an allocation table from those inputs
• The output is a party-level allocation table intended to reconcile to your total damages entry

To keep the workflow accurate, focus on input consistency: if your allocation basis for one party is derived from a different damages concept than another party’s basis, the resulting shares may not reconcile the way you expect.

3) Reconcile totals (don’t skip)

After you generate results, verify reconciliation before relying on the numbers in a judgment worksheet, settlement exhibit, or internal model.

In the output, check:

• The sum of allocated amounts equals the total damages you entered (or, if the tool indicates it, the output reflects rounding/adjustment in a way you can document)
• Each party has a clear allocation basis input tied to the same overall damages pool concept
• No party was omitted or included without an allocation basis value

This reconciliation step is where most data-entry problems surface (wrong totals, missing parties, or inconsistent basis definitions).

4) Joint-tortfeasor context check (ch. 231B)

If your scenario involves joint tortfeasor concepts, Mass. Gen. Laws ch. 231B may be relevant to how you think about the parties in your workflow. The provided authorities include:

• Mass. Gen. Laws ch. 231B
• Mass. Gen. Laws ch. 231B § 1
• Mass. Gen. Laws ch. 231B § 2

A practical approach that keeps your worksheet clean:

• Run the allocation using the Massachusetts workflow tied to Mass. Gen. Laws ch. 231 § 85
• If joint-tortfeasor issues are part of your fact pattern, review ch. 231B concepts for how you want to describe/structure the allocation documentation
• Keep the calculator output as the numbers layer, and treat statutory relevance as the documentation and framing layer

Again, the tool supports calculation workflow; it does not replace legal review.

Common pitfalls

Below are the most common issues that cause allocations to be incorrect or unusable—especially in a US-MA workflow.

Pitfall checklist

• Using an incorrect total damages pool (e.g., entering a subset total when your allocation should reconcile to the full damages figure)
• Mismatched parties (missing a party that you later include in your narrative, or including a party without a corresponding allocation basis entry)
• Copying allocation basis values without verifying they tie back to the same overall damages concept used elsewhere in the worksheet
• Ignoring reconciliation (skipping the check that allocated shares sum to the total damages you entered)
• Overlooking joint-tortfeasor context in documentation when Mass. Gen. Laws ch. 231B is relevant to your scenario’s framing

DocketMath workflow safeguards

• Do the reconciliation check immediately after generating output
• Keep a simple mapping: Party → allocation basis input values → allocated share
• Export or screenshot the results so you can reproduce the calculation steps later

Sources and references

• Mass. Gen. Laws ch. 231 § 85 — https://malegislature.gov/Laws/GeneralLaws/PartIII/TitleII/Chapter231/Section85
• Mass. Gen. Laws ch. 231B — https://malegislature.gov/Laws/GeneralLaws/PartIII/TitleII/Chapter231B
• Mass. Gen. Laws ch. 231B § 1 — https://malegislature.gov/Laws/GeneralLaws/PartIII/TitleII/Chapter231B/Section1
• Mass. Gen. Laws ch. 231B § 2 — https://malegislature.gov/Laws/GeneralLaws/PartIII/TitleII/Chapter231B/Section2

Next steps

1. Open DocketMath’s calculator: /tools/damages-allocation
2. Confirm you’re using Massachusetts (US-MA) in the tool settings.
3. Enter:

   • your Total damages amount, and
   • the allocation basis for each party you want in the output
4. Generate the allocation and verify:

   • the allocated amounts reconcile to your total damages entry, and
   • each party has a basis input filled in consistently
5. If joint-tortfeasor concepts are relevant, review Mass. Gen. Laws ch. 231B as part of your documentation workflow (while keeping the calculator output as your numbers baseline).

If you want, share a sanitized list of your input fields (number of parties and what you’re using for each “allocation basis” entry), and I can help you sanity-check the calculation structure before you run it.

Related reading

• How to calculate Damages Allocation in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Damages Allocation in Philippines — Worked example with real statute citations
• Inputs you need for Damages Allocation in Philippines — Input checklist with sourcing guidance