How to run Offer Of Judgment Analyzer in DocketMath for Mississippi

7 min read

Published June 4, 2026 • By DocketMath Team

Under review

missing_or_unverified_packet

This article is for informational purposes only and does not constitute legal advice. Laws change frequently — verify all citations with current official sources.

Step-by-step

To run DocketMath’s Offer Of Judgment Analyzer for Mississippi (US-MS), you’ll enter inputs that map to Miss. R. Civ. P. 68, then interpret the results using the rule’s timing requirement (“more than fifteen days before the trial begins”) and its cost-shifting mechanics. This guide is for educational purposes and isn’t legal advice.

Start by opening the calculator here: Offer Of Judgment Analyzer.

Rule anchor (Mississippi): The governing language is Miss. R. Civ. P. 68. The timing trigger is the general/default period: “more than fifteen days before the trial begins.” No claim-type-specific sub-rule was identified, so you should not assume different deadlines by claim type unless you find additional governing text in your materials.

1) Choose Mississippi as the jurisdiction context

Go to /tools/offer-of-judgment-analyzer
Set the jurisdiction (or profile) to:
- US-MS (Mississippi)

If the tool shows more than one Mississippi profile, use the one labeled for Miss. R. Civ. P. 68 / Mississippi civil procedure (names vary by UI).

2) Enter the offer economics (amount and “judgment” comparison)

Add the core monetary inputs the analyzer asks for. The labels may vary slightly, but you’re generally matching these concepts from Rule 68:

Offer amount: the dollar amount offered under Rule 68.
Expected final judgment (or outcome) amount: what you anticipate the court could award (or the benchmark amount you want to compare against the offer).
Costs then accrued / cost inputs (if the tool prompts for them): Rule 68 refers to “costs then accrued.” Enter costs using whatever breakdown the tool requests (for example, “costs accrued at time of service” or “cost totals”).

Tip: If the calculator first asks you to compare offer vs. expected judgment, complete that comparison first. Then fill in cost inputs, since the largest risk/benefit in many offer-of-judgment analyses comes from the cost consequence, not just the base damages number.

3) Set the timing input using Mississippi’s default “15+ days” rule

Mississippi’s Rule 68 timing is explicitly:

An offer may be served “at any time more than fifteen days before the trial begins.”
(Source: Miss. R. Civ. P. 68, https://courts.ms.gov/rules/msrulesofcourt/rules_of_civil_procedure.pdf)

In the DocketMath interface, you’ll typically choose between:

Trial start date + offer service date, or
a single field like “days between service and trial”

How to enter it correctly:

Make sure the tool reflects strictly more than 15 days.
If the tool uses day-difference math, that generally means you want 16+ days between:
- Offer service date and
- Trial begins date

Common mistake to avoid: entering exactly 15 days. The rule says “more than fifteen days,” so scenarios at 15 days often fail compliance checks.

4) Confirm who is serving the offer (role matters)

Rule 68 is framed around:

“a party defending against a claim” serving an offer to the adverse party

So in the analyzer:

Select the correct role if it asks whether you’re modeling the defending party (offeror) versus the adverse party (recipient).

Why it matters: Many offer-of-judgment calculators assume the defendant’s offer triggers consequences differently than an offer placed in the opposite direction. If you invert the roles, the tool’s cost-shift direction can effectively flip.

5) Run the analyzer and interpret the outputs in layers

After you click calculate / run / analyze, review the results using three checkpoints:

Timing compliance indicator
- Look for a pass/fail or warning tied to “more than fifteen days before the trial begins.”
Offer vs. expected judgment impact
- The analyzer should compare your offer amount to the expected final judgment/outcome amount you entered.
Cost-shift computation
- Rule 68’s practical effect is driven by costs (“costs then accrued”).
- The tool should show how the cost numbers change depending on where the final judgment lands relative to the offer.

Practical takeaway: Don’t treat the tool as only a “damages comparison” engine. In most cases, the cost math will move the result materially.

6) Save your scenario and run “what-if” tests

DocketMath is most useful when you test alternatives. Try at least two scenarios:

Scenario A (more aggressive offer):
- Increase the offer amount
- Optionally keep costs the same (to isolate the offer effect)
Scenario B (more conservative offer):
- Lower the offer amount
- Keep timing the same to see how much leverage you lose

Then adjust timing:

Move from 15 days to 16 days before trial and re-run to see whether the timing compliance flips.
If you move earlier (e.g., 25+ days), confirm the tool clearly marks timing as compliant.

Mississippi rule anchor you’ll see reflected in outputs

Based on Miss. R. Civ. P. 68, your model should reflect:

Timing: offer served “more than fifteen days before the trial begins”
Costs: the tool should reference or reflect “costs then accrued”
Outcome consequence: the cost consequence is triggered based on how the final judgment aligns with the offer

Common pitfalls

Missing the “more than 15 days” requirement
- The rule uses the wording “more than fifteen days”.
- If you enter 15 exactly, you may trigger a noncompliance warning (or worse, a misleading risk profile).
Using filing date instead of service date
- Rule 68’s trigger is about the offer being served.
- If the tool asks for an offer service date, use that—not the date you filed the offer in court.
Choosing the wrong offer role (defendant vs. adverse party)
- Rule 68 is framed for “a party defending against a claim.”
- If the analyzer has an “offeror/recipient” selector, set it to match your scenario. Inverting roles can flip the implied cost-risk direction.
Leaving “costs” blank when the tool expects them
- Rule 68 explicitly references “costs then accrued.”
- If DocketMath allows you to omit costs and still runs, it may use defaults that can understate or overstate the effect. Fill in costs where possible.
Assuming claim-type-specific deadlines
- For this Mississippi Rule 68 timing rule, the guidance above is the general/default period: more than 15 days before trial begins.
- No claim-type-specific sub-rule was identified in the provided jurisdiction rule excerpt, so don’t search for different deadlines unless your additional source materials point to them.

Big “silent error” to watch: entering a trial start date that doesn’t match your actual scheduled trial. Even with the correct offer service date, the timing compliance indicator depends on both dates.

Try it

Use this quick, self-check method to validate your setup in DocketMath for US-MS.

Quick test checklist (aim for “pass”)

Jurisdiction set to US-MS
Offer service date is 16+ days before the trial begins date
- (because the rule says “more than fifteen days”)
Offer amount and expected final judgment/outcome are filled in
Costs inputs are populated (especially any fields labeled as “costs then accrued,” “costs accrued,” or similar)
Offeror/recipient role matches the defending party framing in Miss. R. Civ. P. 68

Example scenario to sanity-check

Try numbers you can verify quickly:

Trial begins: October 15, 2026
Offer service: September 28, 2026
- That should generally compute to 17 days between dates in day-difference logic (confirm using the tool’s own calculation)
Offer amount: $25,000
Expected final judgment: $30,000
Costs inputs: enter realistic estimates for both sides using the tool’s fields

What to look for in the output

When you run the analyzer, confirm:

Timing compliance recognizes the offer as served more than 15 days before trial.
Offer vs. judgment indicates the final amount is above/below the offer according to your inputs.
Cost-shift direction changes in a way that aligns with the Rule 68 “cost consequence” concept (i.e., the result should not ignore the costs you entered).

Then adjust one variable at a time (offer amount, costs, or timing) and ensure the output responds as you’d expect.