How to run Damages Allocation in DocketMath for Massachusetts

Step-by-step

This guide walks you through running Damages Allocation in DocketMath for Massachusetts (US-MA) using the jurisdiction-aware rules built into the damages-allocation calculator.

1) Open the right calculator

1. Go to the primary tool: /tools/damages-allocation
2. Confirm you’re in the Damages Allocation workflow (calculator identifier: damages-allocation).
3. Set Jurisdiction = US-MA (Massachusetts).

2) Gather the minimum inputs DocketMath expects

Before you type anything, collect your case values in one place (spreadsheet, notes, or a single document). Then mirror them in DocketMath.

At a practical level, most Damages Allocation runs require:

• Parties to allocate between (who you’re allocating damages among)
• Total damages amount you want allocated (the pool to distribute)
• Allocation drivers (the factor/weight inputs the calculator asks for)

Massachusetts jurisdiction-aware logic in this workflow is represented by the following authorities (used by the tool):

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

3) Enter inputs in DocketMath (and verify each mapping)

In the DocketMath interface:

1. Create or start a new Damages Allocation run.
2. Enter the total damages figure.
3. Add each party/defendant entry that should receive an allocation share.
4. Input the allocation factors/weights exactly as they appear in your worksheet.
5. Double-check that each party’s values land in the correct field.

Tip: Many UIs include multiple factor fields that look similar. If one number goes into the wrong field, the final allocation can shift substantially. If the tool provides a preview or “allocation basis,” review it before running.

4) Run the calculation

1. Click Calculate (or the calculator’s equivalent action).
2. Wait for DocketMath to compute the allocation results.
3. Review:

   • Allocated amounts per party
   • Any intermediate outputs shown by the tool (such as weights/ratios or jurisdiction-aware reasoning steps)
   • Reconciliation: confirm the total of allocated shares matches the total damages you entered

5) Interpret the results using Massachusetts (US-MA) rules as wired into the tool

Inside DocketMath, the US-MA selection determines how the calculator applies Massachusetts-specific logic tied to:

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

How to sanity-check your interpretation:

• If one party’s driver/weight is higher in your inputs, the tool’s allocated share should generally trend higher as well.
• If results look counterintuitive, re-check:

  • jurisdiction selection (US-MA)
  • party list completeness
  • factor/weight field mapping
  • reconciliation (allocated sum equals the total damages pool)

6) Export or save your results

After you’re satisfied with the run:

• Save the run name using a consistent convention (for example: MA – Damages Allocation – Run 1).
• Keep the inputs next to the output so you can quickly re-run if a driver changes.
• If DocketMath supports export, save the allocation table for later review.

Common pitfalls

Damages allocation workflows are usually won or lost on inputs and mapping. Common Massachusetts-specific issues are often less about “hard-to-find” rules and more about choosing inputs that match how the calculator expects to apply the Massachusetts configuration.

• Wrong jurisdiction setting

  • If US-MA isn’t selected, you may get calculations that do not align with Mass. Gen. Laws ch. 231 § 85 or Mass. Gen. Laws ch. 231B-based logic used by the tool for Massachusetts.
• Allocating the wrong “pool”

  • If the “total damages” you enter is not the same pool you intended to allocate, the entire output becomes misleading. Treat the total damages input as the single source of truth for reconciliation.
• Party list mismatch

  • If you omit a party that should be included in the allocation set, the tool may still reconcile internally—but to the wrong group.
• Swapped factor fields

  • Similar-looking factor inputs can be easy to mix up. A one-field swap can change results materially.
• Assuming missing data is handled the way you expect

  • If the calculator requires specific factor/weight values for the Massachusetts logic, leaving a field blank may trigger defaults that change the output. Always check for reconciliation and review any intermediate summaries the tool provides.
• Failing to verify reconciliation

  • Always confirm that allocated amounts sum to the total damages input. If the UI includes a “sum check” or reconciliation row, treat it as a must-pass gate.

Tip: If you update a factor after an initial run, do not assume DocketMath “remembers” changes in the part you meant. Re-check the party rows and the allocation basis before clicking Calculate again.

Try it

Use this quick practice run to validate your end-to-end workflow in DocketMath.

1. Open /tools/damages-allocation
2. Set Jurisdiction = US-MA
3. Create a new Damages Allocation run
4. Enter:

   • one total damages pool
   • two parties (so you can more easily verify the direction of the split)
5. Use factor/weight inputs where one party is clearly higher than the other (a “high vs. low” contrast)
6. Click Calculate
7. Confirm:

   • The allocation table shows each party’s allocated amount
   • The allocations reconcile to your total damages input
   • The allocation direction makes sense (higher driver → higher allocated share)

Then iterate:

• Change the factor for Party A only
• Re-run
• Confirm Party A’s allocation moves in the expected direction
• If not, stop and re-check the factor-to-field mapping for that party

If your interface shows any jurisdiction-aware rule notes or intermediate calculations referencing Mass. Gen. Laws ch. 231 § 85 and Mass. Gen. Laws ch. 231B concepts, use those as your verification layer—especially when adjusting inputs.

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