How to interpret Damages Allocation results in Wisconsin

What each output means

Run this scenario in DocketMath using the Damages Allocation calculator.

DocketMath’s Damages Allocation calculator helps you translate a damages figure into an allocation profile you can use when you’re preparing case materials or sanity-checking assumptions. In Wisconsin, the calculator output typically comes in two practical layers:

1. An allocation breakdown — how the total damages are partitioned across categories or time periods (based on the inputs you provided).
2. A Wisconsin timing filter — a rule-driven step that can mark portions of the damages as included or excluded depending on whether their associated dates fall within the general statute of limitations (SOL) window.

Wisconsin SOL anchor used by the tool: the calculator connects the timing filter to Wisconsin’s general/default SOL period for this interpretation guidance. General SOL period: 6 years (see Wis. Stat. § 939.74(1)).
Source: https://codes.findlaw.com/wi/crimes-ch-938-to-951/wi-st-939-74/

What “Included” vs. “Excluded” usually signifies in Wisconsin

When interpreting the outputs, focus on the totals and the timing flags:

• Total damages allocated
  This is the sum of the allocation buckets produced by the calculator. If some buckets are flagged as outside the SOL window, the allocated included total may be lower than your raw total input.

• Included amounts (within the timing window)
  These are the portions the tool treats as falling inside the governing timing filter (for this Wisconsin guidance, the 6-year general rule).

• Excluded amounts (outside the timing window)
  These are the portions the tool treats as outside the SOL window under the tool’s Wisconsin-default approach.

• Timing cutoff date / lookback window
  DocketMath uses your case dates (such as the date anchor you provided—often an event/accrual/range start, depending on the worksheet) to compute a lookback period. Buckets that are tied to underlying dates older than the window are flagged as excluded.

“No claim-type-specific sub-rule found” (what that means for you)

This guide uses the general/default 6-year SOL because no claim-type-specific sub-rule was found for this interpretation guidance.

So, even if your worksheet includes multiple time windows or category lines, the calculator’s timing filter is treated as governed by the general 6-year period unless a claim-type-specific rule is explicitly provided by the tool or your workflow.

Practical takeaway: your Wisconsin outcome will usually rise or fall based on how your inputs map damages to dates, not on changing the dollar amount alone.

How to map the outputs to Wisconsin timing rules

Wisconsin’s general SOL period is 6 years under Wis. Stat. § 939.74(1). In practical terms for interpreting DocketMath:

• If a damages bucket’s associated underlying date is within the last 6 years (measured from the relevant date anchor you provided), it is typically included.
• If it’s older than 6 years, it is typically excluded under this general/default Wisconsin interpretation.

Because the calculator is applying the 6-year general/default rule here, your key interpretive job is to confirm that your date anchor(s) and the bucket/date mapping you used reflect the timeline you intend to analyze.

For the calculator itself, use: /tools/damages-allocation.

Gentle disclaimer: This is guidance on interpreting a tool’s outputs using a general/default SOL period; it’s not legal advice.

What changes the result most

Small input changes can flip whether specific allocation buckets are marked included or excluded. In Wisconsin (using Wis. Stat. § 939.74(1) as the general/default SOL), the largest drivers are usually timing-related:

• The date anchor you selected (the “starting point” for the lookback window)
• How much damages is tied to earlier time periods
• How damages is distributed across categories/time buckets
• Whether the worksheet/toggle applies time filtering (if available in your workflow)

Most sensitive levers (what to check first)

Threshold behavior: the “cutoff test” effect

In many worksheets, DocketMath’s results behave like a cutoff test:

• Within 6 years → included
• More than 6 years old → excluded

So, a common pitfall is assuming that changing the total damages number will change the timing results. Often, timing inclusion is driven far more by:

• the date anchor, and
• how your data ties damages to underlying bucket dates.

A quick interpretation move

When you see a surprised excluded amount, don’t just look at the dollars. Instead:

1. Identify the bucket(s) flagged as excluded.
2. Check the underlying date connected to those buckets.
3. Compare that date to the tool’s computed 6-year cutoff (based on your anchor).

That usually tells you exactly why the result changed.

Gentle disclaimer: tool behavior can vary depending on how the worksheet is configured; verify your configuration against the output detail view.

Next steps

To make the DocketMath Damages Allocation results usable in Wisconsin-focused materials, follow this sequence:

• Open the calculator results detail view (from /tools/damages-allocation) and check:

  • which buckets are marked included
  • which buckets are marked excluded
  • the cutoff date / lookback window computed by the tool

• Verify your date anchor against your case timeline:

  • confirm the event/accrual/range start dates you entered
  • confirm your timeline is consistent with a 6-year general rule under **Wis. Stat. § 939.74(1)

• Reconcile totals:

  • compare raw total you entered vs. the included allocated total
  • list the buckets that reduced the included total
  • check whether those buckets appear to cross the 6-year boundary

• Create a concise output snapshot for internal review:

  • included total: $___
  • excluded total: $___
  • number of buckets excluded: ___
  • cutoff date (date): ___

• Document the governing assumption (so readers don’t assume a different SOL rule):

  • state that the interpretation uses Wisconsin’s general/default 6-year SOL period under Wis. Stat. § 939.74(1)
  • note that no claim-type-specific sub-rule was found for this interpretation guidance, so the general/default period is applied

Related reading

• Damages Allocation Guide for Alabama — Comparative Fault Rules
• Damages Allocation Guide for Alaska — Comparative Fault Rules
• Damages Allocation Guide for American Samoa — Comparative Fault Rules