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

Quick takeaways

• Wisconsin’s pre/post-offer split is driven by Wis. Stat. § 807.01, which governs settlement offers and the related fee-shifting framework in civil actions.
• DocketMath’s pre/post-offer damages calculator uses the same core mechanic Wisconsin contemplates: identify damages that accrued before the offer and those that accrued after the offer date.
• Based on the statute text provided (and your note that no claim-type-specific sub-rule was found), Wisconsin’s approach here is best treated as general/default, not claim-type-specific.
• If you want the split to be defensible, use clean timelines and consistent damage categories so you avoid double-counting or mixing accrual and payment dates.

Inputs you need

Before you run DocketMath’s pre/post-offer damages tool, gather the inputs that determine the two numbers you’re splitting.

A. Offer and timeline data

• Offer date: the date the settlement offer was made in writing (Wis. Stat. § 807.01)

  • DocketMath uses this as the pre cutoff.
• Damages start date: the earliest date you will treat as accruing (often claim accrual, incident-related start, or first provable damages period)
• Damages end date: the end of the damages calculation window (often trial end, verdict date, or the last date damages are calculated through)

B. Damages totals (by period)

Break your damages into at least these two buckets:

• Pre-offer damages: damages that accrued on or before the offer date
• Post-offer damages: damages that accrued after the offer date

In practice, you’ll usually compute this from either:

• a spreadsheet with line-item entries and dates, or
• a rate/time-based model (e.g., monthly wage loss) where DocketMath can allocate by date ranges.

C. A consistent definition of “accrued”

DocketMath works best when you choose one accrual method and apply it consistently across items, such as:

• date-of-service / date-of-injury for medical-like damages
• payment schedule or earned-date logic for wage-like damages (when appropriate)
• ongoing-loss allocation by day/week/month where losses accrue continuously

D. Quick completeness checklist

Use this checklist before calculating:

• I have the offer date for the written settlement offer (Wis. Stat. § 807.01)
• I have a damages accrual start date
• I have a damages calculation end date
• I have either line-item dates for each component or a time-allocation method with a clear rate/schedule
• I have totals (or enough input data) to produce pre and post damages totals

How the calculation works

DocketMath’s pre/post-offer damages split uses a timeline allocation approach: it separates damages into “before” and “after” using the offer date you provide. Wisconsin’s statute text you provided supplies the general settlement-offer framework—particularly that an offer is made in writing and must specify the amount (Wis. Stat. § 807.01).

And because the brief notes no claim-type-specific sub-rule was found in the provided text, the allocation here should be treated as general/default rather than creating special carve-outs by claim type.

Step 1: Confirm the statutory offer framework (Wis. Stat. § 807.01)

From the provided statute excerpt, Wisconsin requires:

• the offer be made in writing
• the offer specify the amount

This matters because the “offer date” you use for the split should correspond to the written settlement offer you are relying on under Wis. Stat. § 807.01.

Step 2: Set the pre vs. post boundary

Use the offer date as the cutoff:

• Pre-offer = damages accrued up to and including the offer date
• Post-offer = damages accrued after the offer date

DocketMath then applies this cutoff consistently to each dated damage component (or to each time-based segment).

Step 3: Allocate each damage component (how DocketMath does it)

Depending on how you enter the data, DocketMath typically does one of the following:

1. Line-item mode (date-stamped entries)

   • For items with a defined service/injury/accrual/payment/accrual date:

     • if item date ≤ offer date → place in pre-offer bucket
     • if item date > offer date → place in post-offer bucket

2. Time-allocation mode (rate-based entries)

   • For damages expressed as a rate (e.g., $/month, $/week) across a period:

     • DocketMath allocates the portion of the time window that overlaps the pre period vs. the post period.

Step 4: Validate the output totals

At minimum, you should be able to check:

• Pre-offer damages total
• Post-offer damages total
• a combined damages total (to confirm your inputs weren’t inadvertently omitted)

A practical validation table can look like:

Step 5: Use the split to structure the “before vs. after offer” story

In Wisconsin, Wis. Stat. § 807.01 is a settlement-offer mechanism, so the legal significance may depend on outcome/procedural elements beyond just the arithmetic. Still, the pre/post split is typically useful because it helps you quantify:

• how much damages exposure existed before the offer
• what additional damages accrued after the offer

DocketMath’s practical value is keeping the math tied to dates and allocation logic, which reduces “eyeballing” errors.

Common pitfalls

These are the mistakes that most often distort a Wisconsin pre/post-offer split when using a tool like DocketMath:

1. Using the wrong cutoff date

   • Filing date, hearing date, or other milestones are sometimes substituted for the actual written offer date.
   • Because Wis. Stat. § 807.01 requires the offer be made in writing, your cutoff should match the written offer date you’re using.

2. Double-counting ongoing damages

   • Example: wage loss entered both as a single “total wage loss” line and again as individual pay periods.
   • Result: post-offer damages can be inflated, shifting the split ratio.

3. Inconsistent accrual definitions

   • Example: medical items allocated by service date while wage loss is allocated by payment date.
   • Result: the model may still total correctly, but pre/post timing may be distorted.

4. Not segmenting time-based changes

   • If the damages rate changes (hours reduced, treatment frequency changes), you should generally:

     • enter separate segments, or
     • provide a schedule that DocketMath can allocate by date.
   • Using one uniform rate across all dates can misstate the pre vs. post portion.

5. Creating “claim-specific” splits without support

   • Since no claim-type-specific sub-rule was identified in the brief’s provided statute excerpt, treat this as general/default.
   • Don’t invent different pre/post periods per cause of action unless you have a grounded statutory or controlling authority basis.

6. Confusing the offer amount with damages

   • The settlement offer amount is not the same thing as damages accrued.
   • DocketMath’s job here is splitting damages into pre/post buckets—don’t input offer amounts as if they were accrued damages.

Sources and references

• Wis. Stat. § 807.01 (settlement offers; written offer specifying the amount)
  https://docs.legis.wisconsin.gov/statutes/statutes/807/01
  (Provided excerpt: “In civil actions, the party making an offer of settlement shall specify the amount of the offer, and the offer shall be made in writing...”)

• TODO: If you’re also modeling the fee-shifting consequences tied to § 807.01, confirm the specific subsections that govern the outcome thresholds and comparison mechanics relevant to your scenario (procedural requirements, effect of accepting/rejecting, and any timing rules).

Next steps

1. Click into DocketMath’s tool and start with the offer date (written offer) and your damages accrual timeline:

   • Primary CTA: /tools/pre-post-offer-damages
2. Enter your damages in the format that matches your data:

   • line items with dates, or
   • rate/time segments with start/end dates.
3. Review the pre/post totals and spot-check any “ongoing” categories (wage loss, continuing treatment) for rate changes or overlapping entries.
4. If the results will be used in briefs or exhibits, attach your allocation logic (how you defined accrual, and why the chosen dates are appropriate) so the split is auditable.

Related reading

• How to calculate pre/post-offer damages split in California — Full how-to guide with jurisdiction-specific rules
• [How to calculate pre/post-offer damages split in Florida