Offer of Judgment Analyzer Guide for Wisconsin

What this calculator does

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

DocketMath’s Offer of Judgment Analyzer (Wisconsin) helps you estimate the potential financial impact of an offer of judgment workflow under Wisconsin law—using the key dates and dollar amounts that usually drive the outcome.

At a high level, Wisconsin’s offer-of-judgment statute is Wis. Stat. § 807.01. It allows a party to serve an offer, and if the other side accepts, judgment is entered accordingly. If the other side does not accept, the statute can still shift costs and/or fees depending on how the final result compares to the offer.

This guide focuses on using the calculator to model typical outcomes so you can:

• compare an offer amount versus an expected recovery,
• estimate whether the offeror may be treated more favorably on cost/fee consequences,
• sanity-check the numbers before you commit them to a filing strategy.

When to use it

Use the DocketMath calculator when you’re working with an offer of judgment analysis under Wis. Stat. § 807.01 and you want to quantify how different assumptions may change the result.

Common moments to run the calculator include:

• Pre-filing evaluation: deciding whether an offer amount looks competitive compared with your estimated verdict or settlement range.
• Decision time after an offer is served: assessing whether pursuing the case could expose you to statutory fee/cost consequences.
• Settlement negotiations: showing a clear comparison between the offered figure and your projected recovery.
• Post-verdict comparison: understanding how the final “surpass / not surpass” concept in Wis. Stat. § 807.01(3) may affect attorney fees.

Core statutory anchors the tool is designed around

The calculator is built to reflect the structure of:

• Wis. Stat. § 807.01 (offer of judgment procedure and consequences)
• Wis. Stat. § 807.01(3) (fee-related outcome rule tied to whether the offeree surpasses the offer)
• Wis. Stat. § 814.04 (cost shifting mechanics associated with the broader costs framework)

If your matter doesn’t fit the statute’s structure (e.g., procedural posture or claim type mismatch), the numeric modeling may not match what actually happens in court.

Step-by-step example

Let’s walk through a realistic workflow using DocketMath’s Offer of Judgment Analyzer. You can start it right here: /tools/offer-of-judgment-analyzer.

Step 1: Identify the “offer amount” to model

Assume the offeror serves an offer of:

• Offer amount (principal): $50,000

In many cases, you’ll also have competing views about what amount will be reflected in the final judgment (especially when interest, costs, or statutory add-ons are in play). The calculator helps you model the key comparison numbers so you can see which way the economics lean.

Step 2: Enter your best estimate of the final judgment

Assume the offeree believes the case may end with a judgment of:

• Expected judgment (principal): $62,500

This matters because the fee consequence under Wis. Stat. § 807.01(3) is tied to whether the offeree surpasses the offer.

Step 3: Add attorney-fee assumptions (if your goal is an estimated fee shift)

Suppose you model:

• Attorney fees (estimated): $12,000
• Costs (estimated): $3,000

The calculator’s goal is not to guess fees for you; rather, it converts your inputs into an estimate of how the statutory mechanism might affect the economics.

Step 4: Decide what “surpass” means in your modeling

Under Wis. Stat. § 807.01, if the offeree accepts, judgment is entered accordingly.

Where the “surpass” point matters is in Wis. Stat. § 807.01(3): it establishes an exception connected to attorney-fee compensation when the offeree surpasses the offer. Practically, this means:

• if the offeree’s final recovery clears the offer amount, the offeree may avoid some attorney-fee consequences,
• if the offeree does not surpass the offer, the offeror may have a stronger argument for fee shifting under the statute.

Your modeling should therefore use a “comparison amount” consistent with how you expect the court to enter judgment in your case.

Step 5: Run the calculator and interpret outputs

Now you’ll compare:

When the expected judgment is higher than the offer, the tool should indicate that the offeree likely surpassed the offer amount for purposes of the Wis. Stat. § 807.01(3) exception logic—meaning your estimate of fee exposure may improve for the offeree relative to the “did not surpass” scenario.

Then repeat with an alternative projection to understand sensitivity:

• Scenario A: Expected judgment = $62,500 (surpass)
• Scenario B: Expected judgment = $45,000 (not surpass)

Step 6: Use the sensitivity to guide your decision tree

A quick comparison helps you decide what factual uncertainty matters most.

• If you think the case could land at $62,500, fee exposure may be lower for the offeree under the § 807.01(3) exception logic.
• If the more realistic range is closer to $45,000, the offeree is more likely not to surpass the offer, which can worsen fee exposure.

Common scenarios

Below are practical scenarios where offer-of-judgment analysis commonly turns on the same few variables. The calculator helps you model each one by switching the offer amount and the expected judgment range.

1) Offeree believes they’ll beat the offer

• Offer: $50,000
• Expected judgment: $60,000
• Result: likely “surpass” outcome → statutory fee exception logic under Wis. Stat. § 807.01(3) may be triggered (in your modeling)

2) Offeree expects a lower outcome than the offer

• Offer: $50,000
• Expected judgment: $48,000
• Result: not surpass → fee exposure may be more unfavorable for the offeree (per your estimate of the statutory effect)

3) Multiple offers over time

If there are multiple offers, run the calculator for each offer separately and compare:

• offer amount vs. likely final judgment date/value,
• which offer is the relevant one for your analysis window.

DocketMath’s modeling works best when each run represents one offer event with one consistent “expected judgment” number.

4) Cost-focused modeling under Wisconsin costs framework

Wisconsin includes a costs framework in Wis. Stat. § 814.04. The tool can be used to include:

• estimated costs and costs exposure assumptions,
• how those assumptions interact with offer-of-judgment cost/fee consequences under Wis. Stat. § 807.01.

5) Negotiation strategy and “walk-away” targets

You can use the calculator to define a target:

• “If we believe the case lands at or above $X, we’re in a better position; if below, the risk increases.”

This approach is especially useful when settlement leverage depends on a narrow numerical threshold.

Quick checklist (use before running)

Tips for accuracy

To get the most reliable output from DocketMath’s Offer of Judgment Analyzer, focus on consistency and the “comparison logic” that underlies Wis. Stat. § 807.01 and its attorney-fee exception in § 807.01(3).

1) Make your “expected judgment” comparable to the offer

The calculator can’t correct mismatched definitions. If your offer figure is “principal” but your expected judgment figure includes other components (or vice versa), your surpass calculation may flip.

Practical approach:

• use one consistent basis for both inputs (e.g., both as principal-only figures, unless you intend otherwise).

2) Model a range, not a single number

Even in straightforward cases, damage valuations drift. Try:

• expected judgment at -10%, 0%, and +10% around your best estimate
• expected judgment low/high bounds from your litigation valuation

Then you’ll see whether the statutory consequences change only if you clear the offer threshold.

3) Treat attorney-fee inputs as estimates, not promises

Your fee input is a modeling parameter. Use the best available:

• billing history to date,
• anticipated remaining work,
• complexity multiplier (if you have one)

4) Don’t ignore costs framework assumptions

If you include costs in your model, make sure the numbers reflect:

• the categories of costs you expect to be relevant,
• the costs you would realistically incur up to judgment.

That aligns better with Wis. Stat. § 814.04 and the costs mechanics that often show up in disputes.

5) Keep runs organized

If you run multiple scenarios, label them by:

• offer amount,
• expected judgment range

Related reading

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