Worked example: Damages Allocation in Wisconsin

6 min read

Published April 15, 2026 • By DocketMath Team

Example inputs

This worked example shows how DocketMath’s damages-allocation calculator can help you map claimed amounts into categories when you’re dealing with Wisconsin time limits for bringing certain actions. The focus here is on allocation of damages inputs alongside a jurisdiction-aware default lookback for when claims may be time-barred.

Wisconsin time-limit assumption used in this example

Wisconsin’s general statute of limitations for certain criminal-related limitations and analogous time-bar frameworks is set by:

  • Wis. Stat. § 939.74(1)6 years (general/default period)

Per the jurisdiction data provided, no claim-type-specific sub-rule was found. That means this example uses only the general/default period (6 years) as the calculator’s jurisdiction-aware rule for all damage buckets.

Note: This example demonstrates a general/default lookback using Wis. Stat. § 939.74(1). If your fact pattern involves a different governing limitation rule (for a specific claim type or cause of action), the allocation math may need different configuration.

Scenario for the calculator (dates and amounts)

Assume the following:

  • Incident date (start of window): 2017-05-10
  • Filing date (end of window): 2023-09-01
  • Total claimed damages: $150,000

Also assume you have already broken your claimed damages into three buckets (you can enter these as separate line items in DocketMath):

Damage bucketWhat it represents (practical example)Claimed amount
Economic damagesOut-of-pocket loss, quantifiable costs$90,000
Non-economic damagesPain, suffering, inconvenience (modeled amount)$45,000
Statutory/other damagesAny additional category you track as “other”$15,000
Total$150,000

Finally, suppose you can associate each bucket with a distribution by date relative to the incident and filing timeline. For this example, use these distribution assumptions:

  • Within 6-year window:
    • Economic: 60% ($54,000)
    • Non-economic: 30% ($13,500)
    • Statutory/other: 50% ($7,500)
  • Outside 6-year window: the remainder for each bucket

Gentle disclaimer: This is an example with modeling assumptions about “when” damages occurred. Real-world timing disputes often require more granular evidence than a single percentage split.

Example run

To run this in DocketMath, use the tool at /tools/damages-allocation:

  • Open: /tools/damages-allocation
  • Jurisdiction selected: US-WI
  • Use the calculator’s Wisconsin default lookback:
    • General limitation period: 6 years under Wis. Stat. § 939.74(1)
    • No claim-type-specific sub-rule is applied in this example (because none was identified in the provided jurisdiction data)

Step-by-step: how the allocation happens in this example

The key mechanism is straightforward:

  1. DocketMath uses the 6-year default window for Wisconsin (Wis. Stat. § 939.74(1)).
  2. It then allocates each damage bucket into:
    • Within limitation window (generally treated as “timely” under the calculator’s default rule)
    • Outside limitation window (generally treated as “time-barred” under the calculator’s default rule)

Using the distribution assumptions above:

Economic damages ($90,000 total)

  • Within window (60%): $90,000 × 0.60 = $54,000
  • Outside window (40%): $90,000 × 0.40 = $36,000

Non-economic damages ($45,000 total)

  • Within window (30%): $45,000 × 0.30 = $13,500
  • Outside window (70%): $45,000 × 0.70 = $31,500

Statutory/other damages ($15,000 total)

  • Within window (50%): $15,000 × 0.50 = $7,500
  • Outside window (50%): $15,000 × 0.50 = $7,500

Output totals you should expect

Now sum by allocation category:

Allocation categoryEconomicNon-economicStatutory/otherTotal
Within 6-year window$54,000$13,500$7,500$75,000
Outside 6-year window$36,000$31,500$7,500$75,000
Grand total$90,000$45,000$15,000$150,000

DocketMath’s damages allocation results should therefore show:

  • Timely portion (within window): $75,000
  • Time-barred portion (outside window): $75,000

If your tool output labels these slightly differently (for example, “allocated within limitation” vs. “allocated outside limitation”), use the underlying split described above.

Warning: The output depends heavily on your time distribution inputs (e.g., “60% within the window”). If your bucket timing is estimated, rerun the calculator with revised percentages.

Sensitivity check

Stress-test the allocation using two variations: (1) changing the timing distribution by bucket, and (2) moving the filing date.

Variation A: Different timing distribution by bucket

Keep the same overall dates, but change the assumed within-window percentages:

  • Economic within window: 50% (instead of 60%)
  • Non-economic within window: 40% (instead of 30%)
  • Statutory/other within window: 50% (same as before)

Recompute:

Economic ($90,000)

  • Within: $90,000 × 0.50 = $45,000
  • Outside: $90,000 × 0.50 = $45,000

Non-economic ($45,000)

  • Within: $45,000 × 0.40 = $18,000
  • Outside: $45,000 × 0.60 = $27,000

Statutory/other ($15,000)

  • Within: $15,000 × 0.50 = $7,500
  • Outside: $15,000 × 0.50 = $7,500

Totals:

  • Within window: $45,000 + $18,000 + $7,500 = $70,500
  • Outside window: $45,000 + $27,000 + $7,500 = $79,500

Impact compared to the original run:

  • Timely portion: $75,000 → $70,500 (down $4,500)
  • Time-barred portion: $75,000 → $79,500 (up $4,500)

This illustrates that even with the same jurisdiction rule (6 years under Wis. Stat. § 939.74(1)), the allocation can swing materially based on the assumed “when” for each bucket.

Variation B: Filing date changes (lookback shifts)

Hold the distributions constant, but move the filing date.

  • If the filing moves later by 12 months, a larger portion of events may fall inside the same 6-year window.
  • If the filing moves earlier by 12 months, more events may fall outside the window.

Because this example uses only the general/default period and no claim-type-specific sub-rule was identified, the filing-date sensitivity generally applies uniformly to the buckets within the calculator’s logic.

Pitfall: Don’t assume a bucket (like non-economic) is always “later” or “earlier.” If your assumed non-economic timing clusters near the edge of the window, even a small shift in dates can change the split noticeably.

Quick checklist before relying on outputs

  • Jurisdiction is set to US-WI
  • The calculator is using 6 years under Wis. Stat. § 939.74(1) as the general/default period
  • Each bucket’s within+outside percentages sum to 100%
  • You ran at least one sensitivity pass (like Variations A and B)
  • You confirmed whether any claim type in the real matter could require a different limitation rule than the general/default assumption

Related reading