How to calculate pain and suffering damages in Massachusetts

Direct answer

In Massachusetts, pain-and-suffering damages are handled through the state’s civil recovery and joint-tortfeasor framework—starting with Mass. Gen. Laws ch. 231 § 85 and applying Massachusetts’ joint-tortfeasor concepts under Mass. Gen. Laws ch. 231B (Joint Tortfeasors Act) (including Mass. Gen. Laws ch. 231B § 1 and Mass. Gen. Laws ch. 231B § 2) when multiple defendants are involved.

Practically, when you’re using DocketMath’s damages-allocation workflow, you’re not “calculating pain and suffering from scratch” from the statute; you’re organizing a pain-and-suffering pool and then allocating that pool across defendants in a way that stays internally consistent with the Massachusetts allocation structure you’re modeling.

What you need to know

1) Your job is allocation modeling, not invention of the damages figure

In a pain-and-suffering workflow, you generally start with a number your case model is already treating as the “pain-and-suffering” component. The key modeling task is then:

• define the pool (the total pain-and-suffering amount you intend to allocate), and
• split that pool across defendants using a Massachusetts-appropriate joint-tortfeasor allocation approach.

DocketMath’s damages-allocation tool helps you do that by keeping defendant-level outputs consistent with your chosen pool and allocation inputs.

2) Massachusetts authorities you should anchor the allocation workflow to

For a jurisdiction-aware Massachusetts approach, keep these authorities in view:

• Mass. Gen. Laws ch. 231 § 85 (civil recovery framework)
• Mass. Gen. Laws ch. 231B (Joint Tortfeasors Act), including:

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

Even if your pain-and-suffering “dollar amount” comes from evidence, expert work, or your case strategy, the allocation structure—how multiple defendants’ shares relate within the model—should be aligned with the Massachusetts framework above.

3) Inputs drive outputs: what changes the defendant shares

Inside DocketMath, the output you care about (each defendant’s allocated pain-and-suffering share) typically depends on inputs like:

• the total pain-and-suffering pool
• the list of defendants included in the model
• the allocation split you’re applying across defendants (using a Massachusetts-appropriate joint-tortfeasor structure)

Step-by-step

Follow this sequence to calculate and allocate the pain-and-suffering component in Massachusetts using DocketMath and its damages-allocation workflow.

1) Open the right tool

Start at the primary call to action:

• /tools/damages-allocation

2) Add each defendant as its own allocation recipient

In the DocketMath worksheet, create an entry for each defendant you want included in the pain-and-suffering allocation.

Why this matters: if a defendant is missing, DocketMath can’t allocate to them, and your totals will not reflect the complete defendant set you intended.

3) Enter the pain-and-suffering pool amount

In the pain-and-suffering section of the workflow:

• enter the total pain-and-suffering damages amount you want to allocate (the pool)

DocketMath will distribute that pool across defendants according to the allocation logic you set up. It will not generate a pain-and-suffering figure for you; your pool input is the anchor.

4) Choose an allocation method consistent with Massachusetts’ joint-tortfeasor framework

When your case includes more than one defendant, structure your allocation approach around the Massachusetts joint-tortfeasor framework:

• Mass. Gen. Laws ch. 231B (Joint Tortfeasors Act)
• Mass. Gen. Laws ch. 231B § 1
• Mass. Gen. Laws ch. 231B § 2

In practice, this means using a consistent approach for how you split responsibility/recoveries among multiple defendants inside your allocation model.

5) Run the allocation and reconcile totals

Execute the allocation and review:

• the allocated pain-and-suffering amount for each defendant, and
• whether the allocated shares sum back to your pain-and-suffering pool (no gaps, no leakage)

This reconciliation step is where many workflow errors surface—often the result of a mis-entered pool, a missing defendant, or an allocation input that doesn’t match your intended structure.

6) Record the defendant-level results

Once the totals reconcile:

• export or copy the defendant allocations for recordkeeping
• keep a snapshot of the pool and allocation inputs used to generate those outputs

This is important because pain-and-suffering pool and allocation adjustments will naturally change each defendant’s share.

7) Sanity-check consistency with your Massachusetts framework

Before finalizing:

• confirm your workflow is anchored to Mass. Gen. Laws ch. 231 § 85 for the civil recovery framework you’re modeling, and
• confirm your allocation method is aligned with Mass. Gen. Laws ch. 231B (including §§ 1–2) for the multi-defendant allocation structure.

Common check: if you update the pain-and-suffering pool, your defendant-level allocations should update accordingly—while still reconciling to the new pool total.

Key statutes and citations

Use these Massachusetts authorities as your framework anchors for a jurisdiction-aware pain-and-suffering allocation workflow:

Common pitfalls

1. Pool vs. categories confusion

   • If you accidentally treat other damages categories as part of the pain-and-suffering pool, you’ll distort the total you’re allocating and any defendant-level outputs derived from it.

2. Not reconciling allocations to the pool

   • Even when the model “looks right,” always verify that defendant allocations sum to the pain-and-suffering pool you entered.

3. Using a split model that isn’t consistent with the Massachusetts joint-tortfeasor framework

   • If the allocation logic you apply across defendants isn’t aligned with Mass. Gen. Laws ch. 231B (including §§ 1–2), your numbers may be internally consistent but jurisdiction-misaligned.

4. Updating inputs without re-running

   • If you change the pain-and-suffering pool, defendant list, or allocation inputs, re-run and re-check totals. Otherwise, you can end up presenting old allocations against a new pool.

Run the numbers

Here’s a practical way to confirm your DocketMath workflow is behaving the way you expect.

1) Run Allocation Pass #1 (baseline)

• Enter your pain-and-suffering pool amount
• Use your Massachusetts-appropriate joint-tortfeasor-consistent allocation setup
• Review defendant shares and verify they sum back to the pool

2) Run Allocation Pass #2 (controlled change)

Change only one input—most commonly the pain-and-suffering pool amount—and re-run:

• keep the same defendants
• keep the same allocation split logic
• confirm:

  • the new allocations change in a way consistent with the model’s split logic
  • the allocations still reconcile to the updated pool total

3) Recordkeeping table (simple and effective)

After the run, record results like this:

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