How to run Damages Allocation in DocketMath for Wisconsin

Step-by-step

This guide walks you through running Damages Allocation in DocketMath for Wisconsin (US-WI) using jurisdiction-aware rules. The calculator you’ll use is damages-allocation via: /tools/damages-allocation.

Before you start, remember: Wisconsin has a “default” approach for contributory negligence that does not automatically bar recovery when the plaintiff’s negligence is not greater than the negligence of the person against whom recovery is sought. In DocketMath terms, that means the allocation logic should follow Wisconsin’s “not greater than” threshold rather than a “hard bar” model.

1) Open the tool

1. Go to: /tools/damages-allocation
2. Select Wisconsin (jurisdiction code US-WI) in the jurisdiction dropdown (or confirm it is preselected).

2) Gather the allocation inputs (what the tool needs)

Damages Allocation generally requires you to represent:

• Total damages (or damages categories that roll up to a total)
• Negligence percentages for each relevant party (e.g., Plaintiff and Defendant; add multiple defendants if your case model includes them)
• Any additional adjustment inputs your DocketMath session expects for the calculator configuration

Use this checklist before entering numbers:

Input checklist (copy for your workflow):

• Total damages amount (or category amounts)
• Plaintiff negligence (%)
• Defendant negligence (%)
• Additional party negligence (%) if applicable
• Confirm negligence percentages sum correctly (if the UI enforces a sum, follow the interface rule)

If the tool expects fractions instead of whole percentages, enter values in the required format and then re-check totals according to what the UI accepts.

3) Enter negligence and damages

In DocketMath:

1. Enter your damages first (so allocation outputs can display immediately).
2. Enter negligence % for the parties.
3. Add any additional defendants/plaintiffs if the interface provides multiple parties.

Quick sanity-check before you calculate:

• Your negligence inputs should match your underlying case assumptions.
• If the UI requires percentages to add to a certain total (often 100%), adjust until the UI is satisfied.

4) Apply Wisconsin’s contributory negligence allocation rule

Wisconsin’s governing standard for this tool run is Wis. Stat. § 895.045.

The statute provides (in relevant part) that contributory negligence does not bar recovery in an action to recover damages for negligence resulting in death or in injury to person or property if that negligence was not greater than the negligence of the person against whom recovery is sought.
Source: https://docs.legis.wisconsin.gov/statutes/statutes/895/iv/045

Key threshold concept for allocation:

• If Plaintiff negligence ≤ Defendant negligence, the plaintiff is not barred under the statute, and the tool should show an allocation-style result.
• If Plaintiff negligence > Defendant negligence, the statutory threshold is not satisfied, and the tool’s Wisconsin logic should reflect a bar/zero-recovery style outcome if the UI exposes that behavior.

5) Run the calculation

1. Click Calculate (or the tool’s equivalent action).
2. Review the output sections that show:

   • Allocated damages by party
   • The resulting recoverable amount (and any “barred/no-bar” indicator, if shown)
   • Any intermediate values DocketMath uses to compute the final allocation

If the output looks unexpected, revisit this:

• Did you enter plaintiff vs. defendant negligence into the correct fields?
• Did a small change push plaintiff negligence from equal to to greater than defendant negligence?

6) Interpret outputs in plain terms

When reading results, translate what you see back to Wis. Stat. § 895.045:

DocketMath outputs are only as accurate as the inputs. If you change inputs and the “bar/no-bar” behavior flips, that typically indicates you crossed the threshold described in Wis. Stat. § 895.045.

7) Iterate with “what-if” changes

Damages allocation is easier to understand through scenario testing. For example:

• Increase plaintiff negligence from 49% to 51% to observe the effect of crossing the threshold.
• Adjust defendant negligence to model disputes over causation or comparative fault.

A practical approach:

• Change one input at a time
• Re-run
• Compare what changes in:

  • Whether the statutory threshold is met
  • The recoverable amount
  • The allocated breakdown

8) Document the run for case work

Even if DocketMath provides a final number, capture the key inputs and outputs:

• Jurisdiction setting: Wisconsin (US-WI)
• Total damages used
• Entered negligence % values by party
• The recoverable amount and allocation breakdown shown by the tool

This helps you reproduce the reasoning internally without re-deriving assumptions.

Common pitfalls

1. Crossing the “not greater than” threshold without noticing

   • Wisconsin turns on whether plaintiff negligence is not greater than defendant negligence.
   • A shift from 50% / 50% to 51% plaintiff / 49% defendant can flip the statutory threshold.

2. Swapped party negligence entries

   • If the UI labels “Plaintiff” and “Defendant,” ensure the numbers match those labels.
   • Swapping can produce a result that “computes,” but doesn’t reflect the intended posture.

3. Forgetting to re-check totals after edits

   • If you update one percentage, the overall set may no longer align with what the UI expects.
   • Confirm you’re meeting any sum constraint the interface enforces (if applicable).

4. Assuming a claim-type-specific negligence rule

   • Based on the provided brief, no claim-type-specific sub-rule was identified.
   • Treat Wis. Stat. § 895.045 as the general/default baseline for this tool run.

If your case model includes multiple defendants, follow how DocketMath defines “defendant negligence.” Some interfaces treat “defendant negligence” as a combined figure; others require separate entries per party. Use the tool’s own breakdown to confirm what it’s treating as the “person against whom recovery is sought.”

Try it

Run a Wisconsin scenario in DocketMath now:

1. Open /tools/damages-allocation
2. Confirm the jurisdiction is Wisconsin (US-WI).
3. Enter:

   • A total damages figure
   • Plaintiff negligence %
   • Defendant negligence %
4. Click Calculate
5. Test a boundary case:

   • Scenario A: Plaintiff negligence = 50%, Defendant negligence = 50%
   • Scenario B: Plaintiff negligence = 51%, Defendant negligence = 49%
6. Compare results and connect the change to Wis. Stat. § 895.045 (the “not greater than” threshold).

If results look surprising:

• Verify which input field is plaintiff vs. defendant.
• Re-check the negligence values that determine whether plaintiff negligence is greater than defendant negligence.

Related reading

• How to calculate Damages Allocation in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Damages Allocation in Philippines — Worked example with real statute citations
• Inputs you need for Damages Allocation in Philippines — Input checklist with sourcing guidance