How to calculate pre/post-offer damages split in Minnesota

Quick takeaways

• Minnesota’s pre/post-offer damages split for Rule 68 offers (Minn. R. Civ. P. 68.01–68.05) is primarily driven by the offer service date.
• The modeling goal is typically:

  • Pre-offer damages = damages that accrue before the Rule 68 offer is served
  • Post-offer damages = damages that accrue on or after the offer’s effective start (i.e., the service date)
• Minnesota’s Rule 68 framework also includes cost-shifting: after judgment, the court compares the final judgment to the offer under the “not more favorable” test. That cost consequence uses costs/disbursements incurred after the offer, but it’s separate from how you calculate the damages split.
• Your split method should follow the default approach for this guide: use the offer service date as the boundary, because the brief request notes no claim-type-specific sub-rule was identified.

Inputs you need

To calculate a Minnesota pre/post-offer damages split in DocketMath, gather these inputs first.

Required

• Rule 68 offer service date (Minn. R. Civ. P. 68.01–68.05 framework)

  • Use the service date as the split boundary.
• Pre-offer damages accrual method

  • Examples:

    • a fixed amount “as of” a date
    • a daily/monthly rate × time accrued up to (but not including) service
    • an accounting schedule with dates
• Post-offer damages accrual method

  • Typically similar logic, but beginning at the service date.
• Any damages components with different timing

  • Examples:

    • unpaid wages vs. statutory interest
    • medical expenses incurred on specific dates
    • future damages you model as accruing over time

Needed for the Rule 68 comparison (cost-shifting context)

Even if you’re focused on the split, Rule 68 uses an offer vs. final judgment comparison to decide whether the offeree may face costs/disbursements incurred after the offer:

• Offer amount (or “the effect” stated in the offer)
• Final judgment amount (or total judgment that matters under your workflow)
• Who the offeree is

  • So you know which side is subject to the “not more favorable” cost consequence.

DocketMath setup (practical modeling choices)

• Define your split boundary precisely

  • Default for this guide:

    • Pre-offer = accrual before offer service date
    • Post-offer = accrual on/after offer service date
• Use a component-level approach (recommended)

  • Put each damages type in its own row/line item so each can apply the correct date range.

How the calculation works

In DocketMath, treat this as two layers that should not be mixed:

1. Accrual timing layer (how you split pre vs. post)
2. Rule 68 outcome layer (how you interpret cost-shifting risk after judgment)

1) Build the damages split using Minnesota’s Rule 68 timeline

Minnesota’s Rule 68 is governed by Minn. R. Civ. P. 68.01–68.05. Under the Rule 68 mechanism, the offer is “served,” and the consequences turn on what happens after judgment.

For the split itself, the practical boundary for this guide is the offer service date—because you’re allocating damages based on when they accrue, not based on how the court ultimately rules.

Step A: Define the date ranges in your model

Use these ranges consistently:

• Pre-offer range: from your damages inception/accrual start through day before the offer service date
• Post-offer range: from the offer service date through your judgment date or your modeling cutoff (whichever controls your output)

Step B: Allocate each damages component by its own dates

In DocketMath, structure your inputs so each component can “look up” whether its accrual date(s) fall in the pre or post window.

A practical component table usually looks like:

Then compute:

• Pre-offer damages = sum of all component values attributable to the pre-offer range
• Post-offer damages = sum of all component values attributable to the post-offer range
• Total damages = Pre + Post (use this as a validation check)

Minnesota “default period” note (no claim-type-specific sub-rule found)

The brief that informed this guide indicates no claim-type-specific sub-rule was found. So this calculator’s default should be:

• Keep the boundary tied to the offer service date for all damages components,
• unless you have controlling authority in a specific situation that says otherwise.

2) Apply Minnesota Rule 68’s “not more favorable” comparison (cost-shifting context)

After you compute the split, you can separately evaluate the Rule 68 outcome.

Minnesota’s Rule 68 allows either party to serve an offer. The revisor’s rule page includes general language stating that:

• “Either party may serve upon an adverse party an offer to allow judgment to be entered for the sum, or to the effect, specified in the offer.”
• And then the consequence:

  • If “the judgment finally entered is not more favorable to the offeree than the offer,” then “the offeree must pay the offeror’s costs and disbursements incurred after … [the offer].”

This is governed by Minn. R. Civ. P. 68.01–68.05. See:

• https://www.revisor.mn.gov/court_rules/cp/id/68/

Key workflow distinction:

• Your pre/post split answers: how much damages accrued before vs. after the offer service date?
• Rule 68’s cost rule answers: whether the offeree has an adverse cost consequence based on the offer vs. final judgment, for costs/disbursements incurred after the offer.

Practical tip for your DocketMath workflow

Even if the tool primarily outputs the split, add (or track) a parallel “Rule 68 evaluation” section:

• Offer amount/effect vs. final judgment amount
• Flag whether the result is consistent with “not more favorable” (for cost-shifting risk)

Gentle disclaimer: This guide is for modeling. It’s not legal advice. If you need certainty about how a particular damages item accrues under Minnesota law, consider reviewing the underlying authority and/or consulting a qualified attorney.

Common pitfalls

• Using the wrong date boundary

  • Mistake: splitting by filing date, receipt date, or offer “expiration.”
  • Fix: anchor the split to the offer service date under Minn. R. Civ. P. 68.01–68.05 (default boundary for this guide).

• Mixing cost-shifting into the damages split

  • Mistake: treating the “not more favorable” test as a way to decide which damages are “pre” or “post.”
  • Fix: the “not more favorable” test impacts costs/disbursements incurred after the offer—not the date-based damages allocation.

• Double-counting time-based components (especially interest)

  • Mistake: modeling interest as both:

    • part of “damages” and again as a separate “interest” line item
  • Fix: decide whether interest is included in principal damages or represented separately, then allocate exactly once.

• Assuming claim-type-specific split rules exist

  • Your brief notes no claim-type-specific sub-rule was found.
  • Fix: don’t create special boundaries by claim label. Use the default offer-service-date boundary unless a specific authority says otherwise.

• Failing the total validation

  • Mistake: Pre + Post ≠ Total
  • Fix: check for:

    • overlaps (same date allocated twice)
    • gaps (a date range excluded from both buckets)
    • missing components

Sources and references

• Minn. R. Civ. P. 68.01–68.05 (Minnesota Rules of Civil Procedure, Rule 68)
  https://www.revisor.mn.gov/court_rules/cp/id/68/
  (Revisor page includes the general authorization for service of an offer and the consequence if “the judgment finally entered is not more favorable to the offeree than the offer,” including costs/disbursements incurred after the offer.)

Next steps

1. Open the calculator here: /tools/pre-post-offer-damages
2. Enter the Rule 68 offer service date and confirm it’s used as the split boundary (pre = before; post = on/after).
3. Add each damages component in DocketMath (e.g., principal, interest, dated expenses).
4. For each component, provide either:

   • accrual dates/intervals, or
   • an accrual formula (rate × time) tied to the correct pre/post date windows.
5. Run the model and verify:

   • **Pre-offer