Inputs you need for Damages Allocation in Wisconsin
4 min read
Published April 15, 2026 • By DocketMath Team
Inputs you will need
Damages allocation in Wisconsin often turns on (1) the date the claim accrued (to help you measure what is likely within the statute of limitations), (2) which losses you’re allocating, and (3) how you want those losses mapped across parties and time periods.
DocketMath’s damages-allocation calculator is designed to make those inputs consistent, so you can compare scenarios (different accrual assumptions, different allocation bases, different party splits) without recalculating from scratch each time.
Because you’re working in Wisconsin, start with the governing limitations rule that applies generally:
- General statute of limitations (SOL): 6 years
- Statutory citation: Wis. Stat. § 939.74(1)
- Scope note (important): No claim-type-specific sub-rule was found in the provided jurisdiction data. So this workflow uses the general/default 6-year period as the baseline.
Note: This article uses DocketMath to organize inputs and calculations. It is not legal advice. Use it to structure your workflow and verify facts (especially dates, amounts, and allocation assumptions) with the record and applicable law.
To run the damages-allocation workflow with jurisdiction-aware rules, gather the inputs below.
Core inputs (worksheet-level)
- Choose the “as-of” date you want DocketMath to measure against (for example, a damages calculation cut-off date).
- If there are multiple loss events, list each date you intend to allocate.
- Examples of categories you might allocate:
- The method you want DocketMath to use to distribute damages (for instance, by time period, by event, or by weighted factors you define in the tool).
Wisconsin jurisdiction input (limitations constraint)
- Wisconsin default general SOL period: 6 years
- Apply that window relative to your accrual date(s) (or the earliest loss date you anchor to).
Optional but often useful inputs
- If you’re allocating shares, provide the party breakdown you want to test.
- If your approach allocates damages into time slices, specify your bucket boundaries (e.g., “inside SOL vs. outside SOL,” or by year).
- If you include recoveries, credits, or other offsets, enter them explicitly so they’re reflected in totals.
Where to find each input
Use the “where to find it” step to reduce guesswork and keep assumptions defensible.
Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.
1) Filing posture / “as-of” date
- If you’re doing scenario planning, pick the date you’re comfortable treating as the measurement endpoint.
2) Accrual date(s) / earliest loss date
3) Total claimed damages by category
4) Allocation basis
5) Wisconsin SOL constraint
- In DocketMath, this is where jurisdiction-aware logic matters. Set the tool to:
- US-WI, so it applies the Wisconsin default general period:
- 6 years under Wis. Stat. § 939.74(1)
- No claim-type-specific sub-rule assumed (based on the provided jurisdiction data)
Run it
You can run the jurisdiction-aware calculator directly from DocketMath:
- Primary CTA: **Open DocketMath Damages Allocation
When you run damages-allocation for Wisconsin (US-WI), the output you get will depend on two main levers:
- Your accrual date(s) (and the number of loss events)
- How you allocate losses across time and/or parties
Typical workflow
- Step 1: Enter your accrual date(s) and your as-of / cut-off date
- Step 2: Provide damages amounts by category
- Step 3: Set the allocation basis (time buckets, party shares, or weighted factors)
- Step 4: Ensure jurisdiction is US-WI so DocketMath applies the 6-year default general SOL period under Wis. Stat. § 939.74(1)
How the outputs change (practical examples)
- If your accrual date is later than expected, more of your damages may fall inside the 6-year window.
- If you list multiple accrual points, DocketMath can allocate losses across time buckets more precisely, which can shift totals between “within SOL” vs. “outside SOL” groupings.
- If you allocate by time period, your bucket definitions can materially change results even when total damages stay the same.
Warning: If your claimed “earliest loss date” is incorrect (for example, you use an incident date when the loss actually became identifiable later), your SOL-constrained damages totals can be materially overstated or understated. Treat the accrual date inputs as the most review-sensitive fields.
