Abstract background illustration for How to run Offer Of Judgment Analyzer in DocketMath for Missouri

How to run Offer Of Judgment Analyzer in DocketMath for Missouri

7 min read

Published June 4, 2026 • By DocketMath Team

Under review

missing_or_unverified_packet

Step-by-step

This guide shows you how to run Offer Of Judgment Analyzer in DocketMath for Missouri (US-MO) using jurisdiction-aware rules—specifically the timing deadline in Mo. Sup. Ct. R. 77.04.

General/default timing rule (no claim-type-specific sub-rule found): The jurisdiction data provided did not surface any claim-type-specific variation. For Missouri, treat “up to ten days before the trial begins” as the governing timing cutoff for typical analyzer use.

1) Open the Missouri Offer Of Judgment Analyzer

  1. Go to the primary CTA: /tools/offer-of-judgment-analyzer
  2. In DocketMath, set the jurisdiction to Missouri (US-MO) (if a jurisdiction selector is shown).
  3. Start a new calculation (or use the analyzer form if it opens directly).

2) Enter the inputs the analyzer requires

DocketMath’s Offer Of Judgment Analyzer generally needs inputs in a few categories. Enter values as plain numbers where applicable (for example, 50000), not currency-formatted text.

Use this checklist so your calculation has what it needs:

  • Offer amount (the dollar amount you offered to allow judgment)
  • Actual recovery / judgment amount (the amount the court awarded)
  • Timing inputs
    • Offer served date
    • Trial begins date
  • Costs / accrued costs (only if DocketMath asks for costs in your run)
  • Offer party context (set it correctly if DocketMath asks which side made the offer)
  • Any additional “effect” you specified (if the form supports non-monetary effects or detailed offer terms)

If DocketMath includes a rule confirmation or jurisdiction logic panel, review it before relying on the result—especially the part that checks the timing window.

3) Apply Missouri’s timing rule (Mo. Sup. Ct. R. 77.04)

Missouri’s rule centers on the deadline for serving the offer:

  • A defending party may serve an offer “at any time up to ten days before the trial begins”.
  • The offer may be for “the money or property or to the effect specified” in the offer, with costs then accrued.

In the DocketMath workflow, the most important practical step is to model the dates so the offer falls within that 10-day-before-trial window.

How to enter the dates in the analyzer:

  • Enter your trial begins date (the date you want to use as “trial begins” for modeling purposes).
  • Enter your offer served date.
  • Ensure the offer served date is 10 days or fewer before the trial begins date.

Example (date modeling):

  • Trial begins: June 20, 2026
  • Offer served: June 10, 2026 → within the window
  • Offer served: June 9, 2026 → within the window
  • Offer served: June 11, 2026 → not within the “up to ten days before” window (based on the modeled dates)

Warning: The rule language is “up to ten days before the trial begins.” Your outcome depends on what dates you enter and how DocketMath counts day boundaries. Double-check the trial start date you’re using (from your scheduling order or docket entry) and confirm the analyzer’s date logic if results seem counterintuitive.

4) Calculate and review the outputs

After you complete the inputs, click Analyze (or the equivalent button).

Review the outputs in two layers:

A) Eligibility / rule fit (timing)

Look for a section that indicates whether the offer is treated as within the Missouri timing window under Mo. Sup. Ct. R. 77.04.

  • If the analyzer says it’s outside the window, update:
    • the offer served date,
    • the trial begins date, or
    • any related date assumptions the form asks for.

B) Financial and cost-effect comparison

The analyzer’s core “offer vs. outcome” math typically compares:

  • the offer amount you modeled, versus
  • the judgment/recovery amount the court awarded,

and then applies whatever cost-shifting or threshold logic the DocketMath calculator is designed to implement.

Use this to interpret results:

  • If the modeled judgment is more favorable to the side that did better than the offer, the analyzer may show the offer as less beneficial (or the opposite, depending on the tool’s design and your entered context).
  • If the amounts are close, the output may show a narrower difference.

5) Iterate with “what-if” scenarios

DocketMath is most useful when you test variations. For Missouri, timing is especially sensitive—so vary dates and amounts deliberately.

Try scenarios like:

  • Scenario A: Same offer amount; offer served 10 days before trial
  • Scenario B: Same offer amount; offer served 8 days before trial
  • Scenario C: Lower offer amount; still within the timing window
  • Scenario D: Higher offer amount; still within the timing window

Then compare:

  • whether eligibility flips (inside vs. outside the window),
  • how the calculated effect changes when the offer amount changes.

6) Export or document your calculation

If DocketMath provides an export/share/download feature:

  • Save a snapshot of each scenario.
  • Record the inputs used (offer amount, judgment amount, and both dates), since small date changes can alter the analyzer’s timing determination.

Also consider noting:

  • your assumed trial begins date,
  • the offer served date you entered,
  • and whether costs were included and how (based on what the tool asks for).

Common pitfalls

  • Entering the wrong dates for “trial begins”

    • Missouri’s timing requirement is tied to “up to ten days before the trial begins.”
    • A frequent mistake is using an imprecise trial date (or a different docket date than what the analyzer expects).
  • Forgetting that the rule text is framed for a “defending party” offer

    • The rule language says: a party defending against a claim may serve the offer.
    • If DocketMath asks which side made the offer, make sure it matches your situation so the analyzer doesn’t apply the wrong directionality.
  • Not capturing the offer’s “effect” when available

    • The rule covers offers for “money or property or to the effect specified.”
    • If your offer included something beyond a single dollar figure and the DocketMath form supports it, enter it rather than relying only on the numeric amount.
  • Including costs inconsistently

    • The rule references “with costs then accrued.”
    • If you model costs, keep your cost assumptions consistent across scenarios (and consistent with what the tool expects).
  • Assuming claim-type-specific timing rules exist in this dataset

    • The provided jurisdiction data did not reveal any claim-type-specific sub-rule.
    • Unless you confirm an applicable exception elsewhere, treat the ten-day-before-trial window as the default for analyzer runs.

Even when the math looks reasonable, the result can be “rule-wrong” if your offer served date or trial begins date doesn’t match Mo. Sup. Ct. R. 77.04’s timing requirement.

Try it

Use this quick practice run to confirm your DocketMath setup for US-MO.

Quick practice checklist

  • Set jurisdiction to Missouri (US-MO)
  • Enter an offer amount (example: 25000)
  • Enter a judgment/recovery amount (example: 30000)
  • Enter timing:
    • Offer served date = 10 days before the trial begins date
    • Trial begins date = your assumed trial start date
  • Include costs only if you have a cost number that fits the analyzer’s cost fields

What to watch for in the results

  • The analyzer should indicate the offer is within the “up to ten days before the trial begins” window.
  • The financial section should reflect the relationship between:
    • the offer amount, and
    • the judgment amount.

Validate with a second scenario

Change only one variable:

  • Keep the offer served date the same, but shift the trial begins date by a couple of days (or vice versa).
  • Confirm the analyzer behaves as expected around the 10-day boundary.

This helps you learn how DocketMath counts dates so your later runs are more reliable.

Related reading