How to calculate pre/post-offer damages split in Michigan
7 min read
Published June 4, 2026 • By DocketMath Team
Quick takeaways
- Michigan’s pre/post-offer damages split uses Michigan Court Rule MCR 2.405 (offer of judgment) as the governing framework for determining outcomes that hinge on the date an offer is rejected.
- In DocketMath, the “pre/post-offer damages split” means you calculate how much of your damages accrued before the offer date vs. after the offer date, and then reflect MCR 2.405(D) consequences that follow rejection of the offer.
- Michigan defines an “offer” in MCR 2.405(A)(1) as a written offer to stipulate to entry of a judgment in a sum certain, and it is deemed to include all costs and interest then accrued—so your model needs accurate offer date and sum-certain offer amount handling.
- No claim-type-specific sub-rule was found to change the default split period. Treat this as the general/default period: anchor the split to the offer date, then apply the standard MCR 2.405(D) effects after rejection.
Note: This article explains how to structure a damages split using DocketMath and MCR 2.405. It’s not legal advice—use it as a calculation/workflow guide.
Inputs you need
Before you run the pre/post-offer damages calculator in DocketMath, gather the inputs below and make sure they all reference the same case timeline.
1) The offer details (MCR 2.405)
- Offer date
- The key anchor date for the pre/post split is when the offer became operative for your timeline (i.e., the offer’s operative date in the record).
- Offer amount (sum certain)
- Under MCR 2.405(A)(1), the “offer” must be a written notification to an adverse party willing to stipulate to entry of a judgment in a sum certain.
- That offer is also deemed to include all costs and interest then accrued. Practically, that means your model should be careful not to double-count costs/interest that the offer definition already treats as included up to the offer moment.
- Whether the offer was rejected
- You generally apply post-offer consequences only when the offer was rejected (because MCR 2.405(D) addresses consequences following rejection).
2) The damages outcomes you’re splitting
You’ll usually need:
- Total recoverable damages (or the components you use to compute it in your model)
- Damages that are time-dependent
- Examples often include damages that accrue over time (e.g., lost wages, wage-loss, certain ongoing losses), where an accrual rate or schedule is available.
- Damages that are not time-dependent
- Examples might include damages categories that don’t accrue day-by-day after a date.
- Accrual cutoff / final decision date for your time-based calculations
- This is the end date for your “post-offer” period in the model (for example, judgment entry date or another date your damages methodology uses consistently).
3) Jurisdiction-specific cost/interest modeling components
Because MCR 2.405(A)(1) deems the offer to include costs and interest then accrued, you need a consistent approach to:
- What “then accrued” costs/interest you treat as belonging to the pre-offer side
- What costs/interest you treat as belonging to the post-offer side
- How you incorporate MCR 2.405(D) consequences after rejection
Practical modeling note: DocketMath can help you keep damages-time allocations structured, but you still control whether you model costs/interest as separate line items or fold them into other amounts—just ensure it matches the definitions implied by MCR 2.405(A)(1) and the consequences in MCR 2.405(D).
4) Verification metadata
- Case caption / docket reference
- Links or identifiers for:
- the offer document (and its operative date)
- the rejection/acceptance outcome
- the judgment/verdict entry (or the date you use as the accrual end date)
How the calculation works
In DocketMath, the US-MI “pre/post-offer damages split” workflow is built around a timeline method:
- Identify the offer date (the split anchor).
- Allocate each damages component between:
- Pre-offer period (accrues up to the offer date)
- Post-offer period (accrues after the offer date up to your model’s accrual cutoff)
- Apply Michigan’s MCR 2.405(D) consequence framework when the offer is rejected, and ensure your cost/interest modeling stays consistent with MCR 2.405(A)(1).
Below is how to implement that structure in practice.
Step A — Validate your offer inputs against MCR 2.405(A)(1)
Start by checking the offer’s core legal characteristics from MCR 2.405(A)(1):
- Written notification
- Willingness to stipulate to entry of judgment in a sum certain
- Deemed to include all costs and interest then accrued
Practical impact in DocketMath:
If the “offer amount” you enter isn’t truly a sum certain, or if your model adds costs/interest on top of amounts that the rule deems “then accrued” and included, your pre/post split and any later comparison to judgment language can become inconsistent.
Step B — Split time-dependent damages at the offer date
For time-dependent damages, the core allocation rule is:
- Pre-offer damages = (accrual rate/schedule) × (time from accrual start to offer date)
- Post-offer damages = (accrual rate/schedule) × (time from offer date to accrual cutoff)
In DocketMath terms:
Enter your damages categories with their accrual logic, then ensure every category uses the same date anchors: the same offer date and the same accrual end/cutoff date.
Step C — Split non-time-dependent damages consistently
For damages that don’t accrue over time, use a consistent allocation method, for example:
- Assign the non-time-dependent amount based on the nature of the loss and when it was effectively incurred, or
- Use an agreed internal allocation across categories if multiple components behave differently.
Key point: the split must still respect the “pre vs. post” concept anchored to the offer date, even if the dollar amount doesn’t accrue continuously.
Step D — Apply MCR 2.405(D) after a rejected offer
MCR 2.405(D) is the section titled “Imposition of Costs Following Rejection of Offer.” Conceptually, this means:
- If the offer is rejected, Michigan’s rule triggers the cost consequences described by MCR 2.405(D).
- Your model should therefore reflect those consequences in a way that aligns with which portions of the outcome are treated as pre-offer vs. post-offer in your workflow.
Common timeline mistake to avoid:
Don’t anchor the “post-offer” period to “after filing,” “after summary disposition,” or “after trial.” For this framework, the anchor is the offer date, plus whether the offer was rejected.
Step E — Default period rule (no claim-type-specific sub-rule found)
Your brief indicates:
- No claim-type-specific sub-rule was found that would modify the relevant split period.
So, treat this as the general/default period:
- Split based on pre-offer vs. post-offer using the offer date
- Apply the standard consequences framework after rejection under MCR 2.405(D)
Step F — Interpret the outputs from DocketMath
DocketMath will produce (at minimum) two damages totals:
- Pre-offer damages
- Post-offer damages
Then, any cost/interest consequences you incorporate (consistent with MCR 2.405(A)(1) and MCR 2.405(D)) should be tied to the same timeline and the same offer outcome (rejected vs. not rejected).
Common pitfalls
Pitfall: Using the wrong “offer date”
- Fix: Use the operative offer date from the record—since the split anchor is the offer date, not the complaint date or trial date.
Pitfall: Entering a “sum-certain” mismatch
- Fix: Ensure your entered offer amount truly reflects a sum certain as required by MCR 2.405(A)(1).
- Also ensure your model doesn’t double-count costs/interest, because MCR 2.405(A)(1) deems costs and interest then accrued as included.
Pitfall: Misallocating time-dependent damages
- Example: using judgment entry as the cutoff for one category but using a different date for another.
- Fix: keep the offer date anchor and the accrual cutoff/end date consistent across all time-dependent categories.
Pitfall: Inventing special split windows for specific claim types
- Fix: since no claim-type-specific sub-rule was found, use the general/default period: split at the offer date, then apply MCR 2.405(D) consequences after rejection.
Pitfall: Treating MCR 2.405 as only about “damages”
- Fix: remember MCR 2.405(D) specifically addresses costs following rejection, and MCR 2.405(A)(1) addresses how the offer treats costs and interest then accrued.
Sources and references
- Michigan Court Rules, MCR 2.405 (Offer of judgment)
Source (official Michigan judiciary site): https://courts.michigan.gov/siteassets/rules-instructions-administrative-orders/michigan-court-rules/court-rules-book-ch-2-responsive-html5.zip/index.html
