Pre/Post-Offer Damages Split Guide for Minnesota
8 min read
Published March 22, 2026 • By DocketMath Team
What this calculator does
Run this scenario in DocketMath using the Pre Post Offer Damages calculator.
DocketMath’s Pre/Post-Offer Damages Split calculator (Minnesota: US-MN) is designed to help you split damages into two time buckets:
- Pre-offer damages: losses that occurred before an offer of judgment (or similar procedural offer) became operative for timing purposes.
- Post-offer damages: losses that continued after the offer’s effective date.
You provide the key dates (and usually the total damages figure), and the tool outputs an allocated split you can use for drafting, case evaluation, or settlement discussions.
This guide focuses on the Minnesota timing rule that often drives these splits—the statute of limitations framework used to determine how far back damages may be considered.
Warning: This guide and the calculator output are for informational purposes and case-prep workflows. They don’t replace legal judgment about offer mechanics, effective dates, or whether a particular damages theory is recoverable.
The Minnesota time limit you’ll see used in the workflow
Minnesota uses a 3-year statute of limitations for certain civil claims, commonly tracked with:
- Minnesota Statutes § 628.26 — 3 years (including the noted exception framework referenced as exception V1 in your jurisdiction data)
When you’re preparing a pre/post split, this 3-year window can affect:
- how far back your pre-offer damages start, and
- whether some historical damages should be excluded from the “pre” bucket (because they fall outside the relevant limitations period).
You may also see the same 3-year period referenced in practical summaries of Minnesota gross misdemeanor-related limitations timelines, including:
(That public summary can be helpful as a cross-check, but your primary legal anchor remains Minn. Stat. § 628.26.)
When to use it
Use the DocketMath calculator when your case analysis depends on timing-based allocation—especially if your “damages” number blends losses from multiple periods.
Common triggers in Minnesota practice include:
- You have a damages total but need to separate:
- damages accrued before an offer was made (or became effective), versus
- damages accrued after.
- You’re comparing settlement exposure before vs. after an offer.
- You’re drafting a damages narrative that must reflect temporal causation (what happened when).
- You’re reconciling damages with a 3-year lookback window under Minn. Stat. § 628.26 to determine which damages are potentially recoverable in the pre-offer category.
Typical situations where a split matters
| Scenario | Why the pre/post split changes the number |
|---|---|
| Damages accrue daily (rent, storage, continuing service charges) | Post-offer bucket can be larger if losses continue after the effective date |
| One-time damages with a limited reporting lag | Pre/post allocation depends heavily on whether the “one time” event happened before or after the offer date |
| Mixed damages (some capped, some continuing) | The split requires consistent rules for what belongs in each time bucket |
| A damages “start date” is older than 3 years | Minn. Stat. § 628.26 (3-year period) can restrict what you include in pre-offer calculations |
Pitfall: A frequent error is using the offer date as a damages start date, or using “case filing date” instead of the offer’s effective date. Those dates often differ, and the split can shift materially.
Step-by-step example
Below is a practical walk-through you can mirror in DocketMath. The example illustrates how the inputs drive outputs and how the 3-year limitations window under Minn. Stat. § 628.26 can influence the pre-offer start.
Example facts (for illustration)
Assume:
- Offer effective date: March 1, 2024
- You’re evaluating damages from a known start date: February 1, 2021
- Damages accrue at a consistent daily rate (for simplicity): $100/day
- Total damages are therefore based on days between your selected start and end dates.
- You’re working with a claim that is constrained by the 3-year period under Minn. Stat. § 628.26.
Step 1: Identify your pre-offer and post-offer boundaries
- Pre-offer end date: the day before the offer effective date
- Pre-offer period ends February 29, 2024
- Post-offer start date: the offer effective date
- Post-offer period starts March 1, 2024
So far:
- Pre: Feb 1, 2021 → Feb 29, 2024
- Post: **Mar 1, 2024 → (your chosen end date)
Step 2: Apply the Minnesota 3-year window to the pre-offer period
Minnesota’s 3-year limitations timeline is anchored in:
- Minn. Stat. § 628.26 — 3 years
If you’re preparing damages with a limitations “lookback” constraint, your earliest allowable pre-offer date becomes:
- March 1, 2021 (three years before the offer effective date, in this example workflow)
That means your original pre-offer start (Feb 1, 2021) is outside the 3-year window, and you would adjust the pre bucket to start at March 1, 2021 instead.
Result of step 2:
- Adjusted pre-offer period: Mar 1, 2021 → Feb 29, 2024
Post-offer:
- stays Mar 1, 2024 → end date
Step 3: Choose an end date for calculation
Let’s pick an end date for the example:
- Damages end date: March 1, 2025
Now compute days (illustrative):
- Pre-offer: Mar 1, 2021 → Feb 29, 2024
- Post-offer: Mar 1, 2024 → Mar 1, 2025
With a $100/day rate, the calculator will multiply the number of days in each bucket by the daily amount.
Step 4: Run the DocketMath split
In DocketMath (pre-post-offer-damages tool), you’ll generally enter:
- Offer effective date: 03/01/2024
- Damages start date (and/or pre-offer start): 02/01/2021 (then apply limitations rule via the tool’s logic/workflow)
- Damages end date: 03/01/2025
- Rate or total damages inputs (depending on the tool interface)
- Any limitations period setting consistent with **Minn. Stat. § 628.26 (3 years)
Output you’re looking for:
- Pre-offer damages (adjusted to the 3-year lookback window)
- Post-offer damages (from the offer effective date forward)
- Totals and sanity checks (e.g., pre + post = total)
What changes when you alter an input?
| Change you make | Expected effect on the output |
|---|---|
| Offer date moves later (e.g., June 1, 2024) | Larger post-offer bucket; pre-offer lookback shifts |
| Damages start date moves older than 3 years | Pre-offer bucket truncates; post remains unchanged |
| End date moves later | Post-offer increases (pre unchanged) |
| Daily rate increases | Both buckets scale proportionally, assuming the same day counts |
Common scenarios
This section covers the most frequent “gotchas” that affect pre/post splits in Minnesota workflows.
1) Damages that begin long before the offer
If your damages start date is older than the 3-year window tied to Minn. Stat. § 628.26, you’ll often need to:
- truncate the pre-offer period to start at the limitations cutoff, and
- include the excluded time in neither bucket (depending on your damages theory and timing constraints).
Practical example:
- Offer effective date: 04/15/2024
- Original damages start: 01/01/2020
- Limitations lookback (3 years): earliest start becomes roughly 04/15/2021
2) One-time events vs. continuing losses
A pre/post split behaves differently depending on damage type:
- Continuing losses (e.g., ongoing service charges): daily/period allocation matters most.
- One-time loss (e.g., a single replacement cost): if the triggering event happened before the offer effective date, it belongs in pre-offer—even if the invoice arrives later.
Pitfall: Filing a bill or learning of a loss date is not the same as when the damages actually accrued. The split should track the accrual timing you’re using for the damages theory.
3) Multiple offers or changing offer effective dates
If there are multiple offers, you may need more than one split:
- Split #1 for Offer A’s effective date
- Split #2 for Offer B’s effective date
In that situation, be consistent about:
- which damages window you’re applying each time, and
- whether your pre-offer truncation uses the same limitations anchor (3-year window under Minn. Stat. § 628.26).
4) Partial limitations exclusions
Sometimes only part of your damages series is outside the 3-year lookback. That yields:
- Pre-offer = truncated portion only
- Post-offer = unaffected (still measured from offer effective date onward)
A common pattern:
- pre-offer includes month-by-month segments near the cutoff, while older months are excluded.
5) Leap years and day-count conventions
Because the split often runs by days, leap years matter. Ensure your workflow matches:
- how your tool counts days between dates, and
- whether you want inclusive vs. exclusive counting (especially for the offer effective date boundary).
For example:
- If pre ends on the day before the offer
