Damages Allocation rule lens: Wisconsin

The rule in plain language

Wisconsin generally uses a 6-year statute of limitations for many criminal “damages” theories asserted through criminal proceedings. The baseline rule is in Wis. Stat. § 939.74(1), which generally requires that prosecutions be commenced within 6 years of the crime.

What this means for a damages allocation lens

When DocketMath is used to allocate damages across time (for example, by using start/end dates), you typically want to anchor your timeline to the outer SOL boundary created by Wisconsin’s general rule—unless your matter has a specific, claim-type-specific (or theory-specific) limitation period that overrides the general rule.

General/default only (no special carve-out found here)

For this Wisconsin lens, this write-up uses the general/default SOL period from Wis. Stat. § 939.74(1). Per the briefing note, no claim-type-specific sub-rule was found in this content to override the general period.

Practically, that means:

• Your calculations should assume a 6-year window from the relevant triggering date you’re using (often the date of offense/event, depending on your workflow).
• If your use case involves a different limitation rule (for example, a special statute or a different legal theory that has its own limitation period), you’ll need to adjust the input window accordingly.

Why it matters for calculations

Damages allocation often depends on what period of time counts. Even when the underlying liability theory differs, many allocation models share a common computational reality: the final damages figure can change significantly when you adjust the start and end dates that are allowed.

Here are the main ways Wisconsin’s 6-year general SOL (per Wis. Stat. § 939.74(1)) tends to affect a damages allocation run in DocketMath.

1) It defines the outer boundary of the “allowable” timeline

If DocketMath allocates damages over months/years, the SOL period typically acts like a cutoff for which intervals are included.

A common workflow is:

• Choose a trigger date (the date your model treats as the starting point—often the offense/event date).
• Compute a latest allowable cutoff = trigger date + 6 years (general/default).
• Allocate damages only to the time segments that fall within that boundary.

2) It can change totals when your data spans more than 6 years

If your dataset includes activity outside the SOL window, allocations can shift in at least two ways:

• Some intervals may be excluded, reducing total damages.
• Remaining intervals may be reweighted, especially if your model prorates by time (or uses time-based scaling, weighting, or discounting).

Illustrative (non-case-specific) examples:

3) It improves reporting defensibility and auditability

If you’re generating exhibits, settlement ranges, or scenario comparisons, the SOL window usually becomes a key assumption. Referencing Wis. Stat. § 939.74(1) (6-year general rule) gives you a clear basis to:

• identify the governing rule used in the model,
• document the date arithmetic (trigger date + 6 years),
• and explain which intervals were included vs excluded.

4) It interacts with allocation methodology

Different allocation approaches handle dates differently. Some segment by:

• incident date → receipt date,
• service period → claim period,
• continuous harm → a cutoff date.

Even so, when a SOL boundary is applied, it generally truncates the included period—so the most important input is the trigger date you use to represent the start of the SOL clock.

Use the calculator

You can run the Wisconsin damages allocation lens in DocketMath here:

• Primary CTA: /tools/damages-allocation

Run the Damages Allocation calculation in DocketMath, then save the output so it can be audited later: Open the calculator.

Step-by-step: what to input for the Wisconsin lens

While the exact fields may vary depending on your DocketMath setup, you’ll typically provide inputs in these categories:

1. Date anchors

• Trigger date (the event/offense date your workflow uses as the SOL starting point)
• Optional end date (if you’re modeling “through a certain point” rather than only applying the SOL cutoff)

1. SOL rule selection

• Use Wisconsin general SOL (6 years) based on **Wis. Stat. § 939.74(1)
• This write-up assumes general/default only (no claim-type-specific override detected for the lens)

1. Allocation inputs

• Damage amounts by period (or a single total you want prorated)
• Any multipliers or weights included in your allocation method (severity weights, apportionment factors, etc.)

How outputs change when you adjust inputs

Expect the results to move in a predictable way when you change the date inputs:

• Move the trigger date forward by 1 year: the SOL cutoff also moves forward by ~1 year, potentially adding intervals previously excluded.
• Data spans more than 6 years: expanding the underlying dataset beyond the cutoff typically won’t increase included damages because the SOL boundary truncates the timeline.
• Data already falls within 6 years: SOL selection usually won’t change totals; it mainly affects how clearly the model documents its assumptions and timeline logic.

Quick pre-flight checklist (keep your run consistent)

Before you click calculate, validate the following against Wis. Stat. § 939.74(1):

If you want to cross-check your timeline logic quickly, start with the damages allocation calculator (often the fastest path to confirm how date changes affect results):

• /tools/damages-allocation

Sources and references

Start with the primary authority for Wisconsin and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

• Primary authority reference

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