How to run Settlement Allocator in DocketMath for Wisconsin

Step-by-step

This guide walks you through running Settlement Allocator in DocketMath for Wisconsin (US-WI). The tool is designed to apply jurisdiction-aware rules, including Wisconsin’s general publication period under Wis. Stat. § 803.08 (used as the default when no claim-type-specific rule is available).

1) Open Settlement Allocator in DocketMath

1. Go to the primary CTA: Settlement Allocator.
2. If the UI includes a jurisdiction selector, confirm you have selected Wisconsin (US-WI).

2) Provide the settlement and case timeline inputs

To allocate a settlement amount across the covered period, Settlement Allocator generally needs timeline anchors and totals. Enter the values that match your case record and your organization’s workflow.

Common inputs include:

• Settlement date (the date the settlement is settled/allocated in your workflow)
• Key event date (often the “trigger” date used to start the allocation window—such as filing/occurrence/another trigger your process uses)
• End date (only if your DocketMath form asks for an end date beyond the settlement date)
• Total settlement amount
• Split inputs, if enabled in the form (for example, category shares or claimant-level amounts—depending on how the worksheet is configured)

If DocketMath includes optional advanced fields, leave them blank until you confirm they are intended to override Wisconsin’s default period logic.

3) Ensure the Wisconsin ruleset is active

Before calculating, verify the tool is using the Wisconsin ruleset and that the governing period is tied to Wis. Stat. § 803.08.

What to look for in the UI output:

• A displayed “period” or allocation window (start/end dates)
• A label or citation referencing the governing period as the Wisconsin general/default period
• A computed date range that aligns with how DocketMath explains the statute-based period

Wis. Stat. § 803.08 is the controlling reference for the default period used here. You can review the statute here:

• https://docs.legis.wisconsin.gov/statutes/statutes/803/08

4) Run the calculation

1. Click Calculate (or the equivalent action in the calculator).
2. Review:

   • The computed allocation window (start/end dates)
   • Any “effective period” or proration window the tool shows
   • The resulting allocation totals (and any breakdown, if the form provides one)

5) Review results and adjust inputs

Settlement allocation results can change immediately when you adjust timeline inputs, especially the inputs that define the allocation window.

Try small, controlled changes:

• Move the key event/trigger date forward or backward and observe how the allocated amounts shift.
• Change the settlement date and confirm the tool recomputes the covered period accordingly.

If the output seems off, check:

• Dates are entered in the correct format
• Wisconsin (US-WI) is still selected
• Any “override” or “advanced” fields are not unintentionally enabled

Practical reminder: Settlement allocation outputs are sensitive to date inputs. A one-day change can shift the computed statute-based window when the rule uses a statute reference like Wis. Stat. § 803.08.

6) Export or document the output

After you confirm the results look consistent, save them for your work record.

Common options include:

• Export (PDF/CSV) if available
• Copyable summary output for notes or a spreadsheet

Keeping your inputs and outputs together helps if you later need to audit why a particular allocation changed.

Common pitfalls

These are the most frequent issues when running Settlement Allocator in Wisconsin (US-WI).

1) Expecting a claim-type-specific limitation period

Because no claim-type-specific sub-rule was found in the Wisconsin jurisdiction data you provided, DocketMath uses the general/default period from Wis. Stat. § 803.08.

• Symptom: Your output period doesn’t match what you expected for a specific claim category.
• Fix: Confirm you didn’t enter claim-type-specific assumptions in unrelated fields. Stick to the tool’s default-period logic.

2) Reversing start and end dates

Allocation windows often rely on a correct start → end timeline. If dates are reversed, you may see:

• A shorter effective period
• Zero or negative duration effects (depending on how the tool handles it)
• Allocation results that don’t match expectations

Quick check: Does the computed allocation window show a start date earlier than the end date?

3) Choosing the wrong trigger date for the case workflow

Even with the correct statute-based period, allocation can be wrong if the trigger date doesn’t match what your workflow intends.

Common mix-ups:

• Filing date vs. occurrence date
• Notice date vs. settlement date
• Administrative date vs. court action date

Tip: Use the same trigger-date definition consistently across runs so you can compare results apples-to-apples.

4) Totals that don’t reconcile with split inputs

If the calculator expects split inputs to sum to a total, mismatches can produce confusing output.

Before you calculate, verify:

• Total settlement amount matches the sum of split inputs (when splits are enabled)
• Currency formatting is consistent (e.g., no stray commas or truncated values)
• Dates are reasonable for the record timeline

5) Not verifying the jurisdiction label and period reference in the result

Some tools remember prior selections. Always confirm:

• The jurisdiction shown near the calculator output is Wisconsin (US-WI)
• The period reference shown in the computed explanation is tied to Wis. Stat. § 803.08

Try it

You can sanity-check your Wisconsin run quickly using a controlled method.

A) Baseline run (control)

1. Open Settlement Allocator.
2. Select Wisconsin (US-WI).
3. Enter:

   • Total settlement amount
   • A start trigger/key event date
   • Settlement date
4. Click Calculate.
5. Record:

   • The computed allocation window (start/end dates)
   • The total allocation output

B) One-variable change test

Change only one input—for example, move the start trigger date by +30 days—then re-run.

• If the allocation window end date (or proration) changes: the tool is reacting as expected.
• If the output doesn’t change: check for an override field, an unchanged end-date input, or a fixed window behavior based on the current settings.

C) Confirm the statute period reference

At least once, verify that the output is explicitly connected to the Wisconsin default/general period logic tied to Wis. Stat. § 803.08.

Related reading

• How to calculate Settlement Allocator in Ohio — Full how-to guide with jurisdiction-specific rules
• How to calculate Settlement Allocator in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Settlement Allocator in Philippines — Worked example with real statute citations