Offer of Judgment Analyzer Guide for Michigan
8 min read
Published April 8, 2026 • By DocketMath Team
What this calculator does
Run this scenario in DocketMath using the Offer Of Judgment Analyzer calculator.
DocketMath’s Offer of Judgment Analyzer (Michigan) helps you estimate how an offer of judgment under Michigan law (MCL § 600.2922) might affect outcomes when the opposing party does not accept within the required timeframe.
At a high level, the tool models the offer’s financial components so you can see how your offer amount, the timing of acceptance (or the point at which acceptance is no longer timely), and the judgment figure you expect could interact.
Legal anchor (what the statute establishes):
Under MCL § 600.2922, a party may make an offer of judgment, and the offer is deemed accepted if the opposing party fails to accept it within the time provided by court rule.
Note: The statute provides the mechanism, but the acceptance deadline is set by court rule. This guide focuses on Michigan’s framework and shows you how to run the analysis with DocketMath; it does not replace rule text.
Inputs DocketMath typically needs (and what they change)
Use the calculator to enter the figures that control your risk/benefit estimate:
- Offer of judgment amount (the number you offered)
- Time-to-accept (or offer date / acceptance cutoff) (to model whether the offer was accepted or deemed accepted)
- Expected/known judgment amount (what you think the court will enter)
- Key fee/cost components you want included in the estimate (if your workflow tracks them)
Even without adding claim-type-specific logic, the tool’s purpose is straightforward: compare your offer to the likely result and show how the offer decision changes the total dollars at stake.
Michigan timing note (general/default rule)
The content brief indicates no claim-type-specific sub-rule was found. That means you should treat the guidance here as the general/default period—the same deadline applies unless a specific court rule or order changes it for your situation.
When to use it
Use DocketMath’s Offer of Judgment Analyzer when you’re deciding whether an offer is likely to be beneficial, or when you need to understand the financial impact after an offer is made.
Common moments include:
- Before filing the offer: you have a range of plausible judgments and want to pressure-test your offer amount.
- After the deadline passes: you want a quick way to estimate what the “deemed accepted” framework could mean for totals.
- During settlement discussions: you’re comparing settlement positions with a concrete, rule-based mechanism in mind.
- For case inventory and strategy: you’re tracking multiple cases with different offer amounts and expected outcomes.
Why timing matters under MCL § 600.2922
MCL § 600.2922 deems acceptance if the opposing party fails to accept within the time provided by court rule. That makes the acceptance window a major driver of whether the offer is treated as accepted.
Warning: Don’t rely on a “calendar intuition.” The offer’s effect hinges on the court-rule deadline, not only on the offer date or negotiation pace.
Quick checklist: does your case fit the tool?
Consider running the analysis if you can answer “yes” to most of these:
Step-by-step example
Below is a simplified walkthrough showing how DocketMath can help you reason through the economics of an offer.
Example facts (illustrative)
Assume you’re considering an offer in a Michigan civil action:
- Offer date: June 1, 2026
- Offer of judgment amount: $50,000
- Expected/known judgment amount: $65,000
- You also track estimated taxable costs and attorney fees as separate line items you may want included in your estimate.
Because MCL § 600.2922 turns on whether acceptance occurs within the court-rule period, the key timing input is whether the opponent accepted within the required window.
Note: The statute says the acceptance deadline is “provided by court rule.” This walkthrough shows the logic—you’ll align the actual deadline with the controlling rule for your posture.
Step 1: Enter the core amounts
- Open DocketMath’s Offer of Judgment Analyzer: /tools/offer-of-judgment-analyzer
- Input:
- Offer amount:
50000 - Expected judgment:
65000
What you should expect: when the expected judgment exceeds the offer, you’re usually modeling a scenario where the offer may not “lock in” a favorable result for the offeror. The calculator will still compute totals so you can see the dollar impact cleanly.
Step 2: Enter timing
- Input:
- Offer date:
2026-06-01 - Acceptance status or cutoff: model whether acceptance happened before the court-rule deadline.
Output behavior: DocketMath’s “deemed accepted” logic depends on the acceptance window. If you mark it as not accepted within the deadline, the calculator treats it as accepted by operation of MCL § 600.2922.
Step 3: Add costs/fees estimates (if you track them)
- If your workflow includes them, add:
- Estimated costs: e.g.,
2500 - Estimated attorney fees (if applicable in your tracking): e.g.,
12000
Why this matters: even if you focus on the judgment amount comparison, real settlement impact often turns on fee/cost components. The tool lets you include or exclude them based on what you want to model.
Step 4: Review the result comparison
- Look at outputs that compare:
- Offer amount vs. expected judgment
- Totals under the modeled acceptance scenario
- Net difference you’d “save” or “lose” relative to your expected judgment path
In this example:
- Offer: $50,000
- Expected judgment: $65,000
So the “offer vs. result” gap is $15,000. The calculator turns that into a more decision-ready summary, factoring in your timing selection and any included costs/fees.
Step 5: Run “what if” variations quickly
Most users get value from testing multiple offer amounts:
- Try $45,000, $50,000, $55,000, and $60,000
- Keep the expected judgment constant
- Keep timing constant
- Watch how totals shift
This is how the tool becomes a decision support instrument rather than a single-number calculator.
Common scenarios
Offer of judgment disputes and strategy discussions commonly fall into a few recognizable buckets. DocketMath’s analyzer is best suited for these because they map cleanly to “offer amount + acceptance timing + likely result.”
1) Pre-trial offers with disputed damages
If damages are contested (e.g., service issues, property loss, or business disputes), you may have a reasonable damages range.
How to use the tool:
- Enter a midpoint expected judgment and a high/low range across multiple runs.
- Evaluate offers at 25%, 50%, and 75% of the expected judgment.
Checklist:
2) Offers made near dispositive motion timing
When the case is entering a new phase, parties sometimes use offers to shift settlement posture.
Key advantage of running analysis:
- You model whether the offer was likely to be treated as accepted or not, based on your timing input.
Pitfall: A late or procedurally defective offer can trigger the wrong model assumptions. If you’re unsure about the exact procedural mechanics, verify the court rule and case management order before treating the output as decision-grade.
3) After discovery narrows the “expected judgment”
Once evidence comes in, your expected judgment estimate might move.
How to use the tool:
- Re-run the calculator when your damages estimate changes by more than your “margin of safety” (for example, a swing of $10,000 or 20%, depending on your case economics).
4) Post-judgment planning
If a judgment is already known, you can compare your offer to the entered number without guessing damages.
How to use the tool:
- Enter the actual judgment amount
- Focus on the offer amount difference and the modeled acceptance scenario
Tips for accuracy
To get outputs you can trust enough for real casework, focus on precision in a few places.
1) Match your timing to court-rule deadlines
MCL § 600.2922 says the offer is deemed accepted if the opposing party fails to accept it within the time provided by court rule.
- Treat the acceptance period as rule-driven, not negotiation-driven.
- Use the same time zone and date handling that your docket system uses.
Warning: This guide uses the statute’s mechanism, but the exact deadline must match the controlling Michigan court rule for the posture of your case. DocketMath’s analyzer helps you calculate outcomes given your timing inputs—you still need correct dates.
2) Separate “judgment” from “settlement vibes”
The tool needs a judgment amount (entered or expected), not just a settlement target.
Practical approach:
- If the judgment isn’t known, use a single best estimate plus scenario runs (low/high).
- Avoid mixing offers that include terms unrelated to the money judgment unless your process explicitly models them.
3) Be consistent with costs/fees assumptions
If you include costs and attorney fees in the estimate:
- Use the same methodology across runs
- Document your assumptions in your case notes
- Don’t mix “likely recoverable” in one run and “fully billed” in another unless the tool is configured for that
4) Run a sensitivity test (do 3-5 runs, not 1)
A reliable workflow is:
