How to run Offer Of Judgment Analyzer in DocketMath for Michigan

Step-by-step

Run this scenario in DocketMath using the Offer Of Judgment Analyzer calculator.

Below is a practical walkthrough for running Offer Of Judgment Analyzer in DocketMath for Michigan (US-MI). This guide focuses on how to set the tool up so the results align with Michigan’s offer-of-judgment framework under MCL § 600.2922.

Note (timing anchor): Michigan’s offer-of-judgment acceptance is governed by the “time provided by court rule.” MCL § 600.2922 provides that an offer is “deemed accepted if the opposing party fails to accept it within the time provided by court rule.” In other words, the statute gives the concept, but the exact number of days comes from the applicable court rule—so if DocketMath exposes timing inputs, confirm the deadline setting you use matches your procedural posture and court.

1) Open the Michigan Offer Of Judgment Analyzer

1. Go to the tool page: /tools/offer-of-judgment-analyzer
2. Confirm Michigan (US-MI) is selected (via a jurisdiction selector, if available).
3. Click Start or use the tool’s main input panel.

2) Enter the core offer details

In most offer analyzers, the key “math” inputs are the offer amount, relevant dates, and what you want the tool to compare that offer against. In DocketMath, enter:

• Offer amount (the dollar amount you offered)
• Offer date (or the date the tool uses as the timeline anchor)
• Which party you’re analyzing (the tool may label roles like “Offeror” vs. “Offeree”—match the option to who made the offer)
• Expected judgment amount (the amount you expect the case could end at, so the analyzer can compare offer vs. outcome)

If DocketMath includes a “results basis” or similar choice (for example, compare to verdict vs. compare to judgment), select the option that matches how you expect the case to conclude.

3) Configure timing to reflect Michigan’s “deemed accepted” concept

MCL § 600.2922 sets the central logic: the offer is deemed accepted if the opposing party does not accept within the court-rule timeframe.

In DocketMath, do the following:

• Find any field for acceptance deadline days, response window, or timing rules
• If DocketMath offers a Michigan-specific default, use it only if it matches the timing you want to model
• If the tool prompts you to enter timing explicitly, enter the deadline that applies under the relevant Michigan court rule for your case

Because your request is Michigan-specific, the tool should reflect the statutory concept—but the deadline calculation still depends on the rule timing you input (if applicable). Treat timing as a rule setting, not as something automatically supplied by the statute.

4) Add cost/fee inputs (if the tool supports them)

Many offer-of-judgment calculators model financial consequences beyond the headline comparison by including optional items such as:

• Interest
• Costs
• Attorney fees (depending on the tool’s scope)

If DocketMath includes optional fields for these:

• Enter values intentionally if you want those elements reflected in the “total impact”
• If you leave them blank, confirm what the tool assumes (for example, zero vs. default values) by checking the output legend or assumptions panel

5) Review jurisdiction-aware rules that change the output

For Michigan, the biggest jurisdiction-aware effect is the alignment with MCL § 600.2922’s deemed-acceptance concept: if the opposing party fails to accept within the court-rule timeframe, the legal effect is treated as acceptance.

In practice, you should expect outputs to change when you adjust:

• Offer amount vs. projected judgment (changes whether the tool flags a “favorable” difference based on the modeled outcome)
• Response window / acceptance timing (changes whether the tool treats the acceptance as timely/untimely in its modeled scenario)
• Costs/fees inputs (changes the total delta even when the core offer-vs-judgment comparison is stable)

A quick sanity check:

• If you increase the offer amount while keeping the projected judgment and timing constant, the tool’s numeric comparison should shift consistently (i.e., reflect that the offer is closer to or more favorable relative to the anticipated judgment, according to the tool’s logic).

6) Run the analysis and export or save

1. Click Calculate.
2. Review the summary output:

   • Offer vs. judgment comparison
   • Any messaging related to timely acceptance / deemed acceptance
   • Total financial impact (especially if costs/fees/interest are modeled)
3. If available, use Save or Download to keep a record of the run.

To understand cause-and-effect, re-run the tool by changing one variable at a time (e.g., offer amount first, then timing). This makes it easier to interpret why the output changed.

Michigan rule anchor (what the analyzer is reflecting)

Michigan’s offer-of-judgment baseline is captured in MCL § 600.2922:

• A party may make an offer of judgment in any civil action.
• The offer is deemed accepted if the opposing party does not accept within the time provided by court rule.

Source: https://legislature.mi.gov/doc.aspx?mcl-600-2922

Common pitfalls

Below are the most frequent mistakes when running an offer-of-judgment analyzer in Michigan. Use this as a quick pre-flight checklist before relying on results.

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

Quick checklist (tick when correct)

Specific Michigan pitfalls to watch

• Assuming MCL § 600.2922 provides the deadline: It does not supply a specific number of days. It defers to “the time provided by court rule.”
• Mixing up timeline fields: If DocketMath includes both offer date and acceptance deadline, verify which input the tool uses to calculate timing.
• Over-interpreting results without checking assumptions: Optional fee/cost/interest inputs can swing the “total impact” even if the underlying offer-vs-judgment comparison doesn’t change much.

Try it

You can run the Offer Of Judgment Analyzer in DocketMath here: /tools/offer-of-judgment-analyzer

If you want a fast way to validate the tool logic in Michigan, try a simple three-run mini-test:

1. Baseline run

   • Set an offer amount
   • Set a projected judgment amount
   • Use the tool’s default timing or your case’s known response window

2. Offer change run

   • Increase the offer amount by a meaningful increment (e.g., +$10,000)
   • Keep projected judgment and timing constant

3. Timing change run

   • Adjust the response window / acceptance deadline by a small amount (e.g., +1 day)
   • Keep financial values constant

What you should observe:

• Changing the offer amount should shift the offer-to-judgment comparison and likely the delta.
• Changing timing should affect any messaging or logic tied to timely acceptance / deemed acceptance, consistent with MCL § 600.2922’s “court-rule timeframe” concept.

To keep your results usable for internal review, store the output from each run (or screenshot the summary) and label each scenario clearly (e.g., Baseline, Higher offer, Later deadline).

Related reading

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