How to run Offer Of Judgment Analyzer in DocketMath for Massachusetts

Step-by-step

Follow these steps to run Offer Of Judgment Analyzer in DocketMath for Massachusetts (US-MA). This walkthrough focuses on getting results quickly and ensuring the analyzer uses Massachusetts’s default/general offer timing logic under Mass. Gen. Laws ch. 231, § 59.

Important: Massachusetts’s offer-of-judgment timing uses a general/default period when no claim-type-specific sub-rule applies. Your brief did not identify a claim-type-specific override, so the analyzer should rely on the default logic tied to ch. 231, § 59 rather than a claim-specific rule.

1) Open the analyzer

1. Go to the primary call-to-action: **/tools/offer-of-judgment-analyzer
2. Confirm you’re using Massachusetts via the jurisdiction setting:

   • Select US-MA before entering any dates or amounts.

2) Enter the offer details DocketMath needs

In most setups, the analyzer asks for values tied to the offer’s timing and the resulting amount comparison. Use the interface labels as your guide and enter:

• Offer date (written offer made)
  Enter the date the offer was made in writing.
• Acceptance or judgment date (depending on what the tool prompts)
  Provide the relevant “outcome anchor” date the analyzer requests (for example, acceptance date or judgment/result date—whatever the UI specifies).
• Offer amount
  Enter the dollar amount offered to settle the claim or resolve the issue.
• Outcome amount (if requested)
  Some versions ask for the final judgment (or comparable “result” figure) so the tool can compare the offer to the outcome.
• Who made the offer (if the tool distinguishes “offeree” vs “offeror”)
  This can matter because the tool’s “more favorable / less favorable” framing and any cost-shifting logic depends on which side is benefiting in the comparison.

Tip: If the analyzer includes toggles such as selecting whether you’re analyzing from the offeror or offeree perspective, set them intentionally so the output matches the direction you’re evaluating.

3) Ensure the Massachusetts rule used is from ch. 231, § 59 (default/general logic)

Massachusetts’s offer mechanism is described in Mass. Gen. Laws ch. 231, § 59. The statute’s text includes:

“A party may make an offer in writing to settle a claim or to resolve an issue …”
Source: https://malegislature.gov/Laws/GeneralLaws/PartIII/TitleII/Chapter231/Section59

Because your brief did not find a claim-type-specific sub-rule, the analyzer should use a general/default period for timing rather than switching logic based on claim category.

4) Run the calculation

1. Click Analyze (or the equivalent button in the tool).
2. Review what the analyzer computes, typically including:

   • A timing window / relevant period determination
   • A comparison of the offer amount vs. outcome/judgment amount
   • A result summary such as “more favorable” or “less favorable” (and possibly a conditional cost-impact-style summary)

Guidance: If the interface offers something like “default period” vs “custom period,” keep it on the default for US-MA unless the UI clearly indicates a different Massachusetts sub-rule that you can justify with your case facts.

5) Interpret the output in a way that matches § 59

When you interpret DocketMath’s results, map them back to what the analyzer is doing computationally:

• Layer A: Timing compliance (default/general period)
  Check whether the analyzer’s “timing window” determination lines up with the Massachusetts § 59 default period logic.
• Layer B: Economic comparison (offer vs outcome)
  Check whether the judgment/outcome amount falls in a range that makes the offer more favorable for the party perspective selected in the tool.

Reminder / gentle disclaimer: Offer-of-judgment calculations can be sensitive to procedural details and to exactly how the tool defines “outcome amount.” Use the analyzer to understand scenarios and compare results—not as a substitute for legal judgment or advice.

Also watch for a common measurement issue:

• The analyzer can only be as accurate as your inputs. If it asks for a “result” figure, make sure your Outcome amount is the same type of number the tool expects (e.g., total award vs principal-only, or similar distinctions the UI may define).

Common pitfalls

Below are frequent issues that can make results from an offer-of-judgment calculation misleading—usually because the jurisdiction, dates, or input definitions don’t match what the tool expects.

• missing a required input
• using a stale rate or rule
• ignoring calendar or holiday adjustments
• skipping documentation of assumptions

1) Using the wrong jurisdiction code

• Symptom: The analyzer applies the wrong timing rules.
• Fix: Verify US-MA is selected before entering dates and amounts.

2) Entering dates in the wrong fields

• Symptom: The calculated timing window shifts and flips the conclusion.
• Checklist:

  • Offer date should be the date the offer was made in writing
  • Outcome/judgment date should match the “anchor” date the tool specifically requests

3) Expecting a claim-type-specific period when none is identified

Your brief indicates no claim-type-specific sub-rule was found for this Massachusetts setup. That means the analyzer should use the general/default period.

• Symptom: Output changes when you select a claim type you didn’t mean to test.
• Fix:

  • If a claim-type selection exists, confirm whether it truly changes timing-period logic.
  • If uncertain, rely on the tool’s default period option for ch. 231, § 59.

4) Mixing conventions for “offer amount” and “outcome amount”

• Symptom: The tool shows the offer as favorable (or unfavorable) but your understanding disagrees.
• Fix:

  • Ensure Offer amount and Outcome amount are on the same basis the analyzer is using.
  • If the tool distinguishes components (such as principal vs total), be consistent with those definitions.

5) Treating the tool output as legal advice

• Symptom: You treat the calculator as a guarantee of entitlement.
• Fix: Treat DocketMath as a computational aid and scenario comparison tool. Final application depends on case-specific procedural facts and how a court interprets the offer and outcome.

Try it

Use this quick test to confirm your DocketMath inputs and directionality (without assuming any real case outcome).

Open the Offer Of Judgment Analyzer calculator and follow the steps above: Run the calculator.

Capture the source for each input so another team member can verify the same result quickly.

Quick scenario test (sanity checks)

1. Select a reasonable offer date.
2. Select an outcome/judgment date after the offer.
3. Enter:

   • Offer amount: e.g., $10,000
4. Run two comparisons by changing only the outcome amount:

   • Run A (outcome above offer): Outcome amount = $15,000
   • Run B (outcome below offer): Outcome amount = $7,500
5. Compare results:

   • You’d expect the tool to label the offer differently depending on whether the outcome is above vs below the offer, given the same timing inputs.
   • If both runs produce the same “more favorable” direction, revisit which field the analyzer treats as “Outcome amount” and whether your numbers match the tool’s definition.

Rule-awareness check (default/general period)

After running each scenario:

• Look for any panel/summary such as assumptions or rule summary
• Confirm the analyzer is using the Massachusetts § 59 general/default period (not a claim-specific override)

This is especially important because your brief indicates no claim-type-specific sub-rule was located—so the default timing logic should remain stable across claim-type options unless the tool explicitly says otherwise.

Related reading

• Offer of Judgment Analyzer Guide for Alabama
• Offer of Judgment Analyzer Guide for Arizona
• Offer of Judgment Analyzer Guide for Colorado