Why Damages Allocation results differ in Wyoming

The top 5 reasons results differ

When you run DocketMath → damages-allocation in Wyoming (US-WY), you may see different allocation outcomes across runs, spreadsheets, or workflows—even when the underlying dollar amounts look the same. In Wyoming, these differences are usually driven by how the tool applies jurisdiction-aware rules and by whether your inputs align with those rules, especially around the default statute of limitations (SOL).

1) Date window mismatch (SOL-driven eligibility)

If one workflow uses a filing date and another uses a trigger date (or vice versa), the SOL window shifts—changing which damages fall inside the eligible period. With a 4-year limit, moving the start/end by weeks or a few months can shift an entire group of line items from “included” to “excluded,” changing the allocation split.

2) Trigger date interpretation (event vs. discovery vs. accrual)

Teams often use different definitions of “when damages start,” such as:

• incident/event date,
• accrual date,
• discovery-related date.

If your inputs represent different interpretations, DocketMath can’t know which one is intended. Even if the final numbers “should” match conceptually, the eligible time period may differ.

3) Damage period boundaries (cutoffs, partial years, inclusivity)

Even with the same SOL length, results can change based on how the model slices time, for example:

• calendar-year aggregation vs. daily proration,
• inclusive vs. exclusive cutoffs,
• mid-month start/end handling.

With Wyoming’s 4-year default, a one-day difference in boundary handling can move the “last eligible day” and shift allocation.

4) Category-level labeling (what counts as “damages”)

Allocation outcomes depend on which line items are treated as part of the damages base. Differences commonly come from mapping choices such as:

• labor vs. materials,
• direct vs. consequential,
• paid amounts vs. calculated damages.

If one workflow labels an item as “damages” and another labels it as “reimbursement/other,” DocketMath may allocate it differently.

5) Settlement/adjustment entries treated inconsistently

If one dataset includes (or nets out) offsets, reimbursements, or adjustments—while another omits them—the net damages basis can change. Because allocation is based on the categories included in the damage base, inconsistent treatment of adjustments can produce different allocation outcomes.

How to isolate the variable

Treat this like debugging: hold everything constant except one factor at a time, then identify where the tool “flips” inclusion/exclusion.

• Freeze the jurisdiction and tool settings so both runs use the same rule set.
• Compare one input at a time (dates, rates, amounts) and re-run after each change.
• Review the breakdown to see which segment or assumption drives the difference.

1) Lock the jurisdiction and confirm the SOL rule being used

Before comparing runs, confirm you’re using Wyoming’s default 4-year general SOL:

• Wyo. Stat. § 1-3-105(a)(iv)(C) → 4 years
• No claim-type-specific sub-rule found → general/default applies

Checklist:

2) Change only one input per attempt

Use DocketMath and modify just one variable between runs:

• Filing date (keeping trigger/accrual date fixed)
• Trigger/accrual date (keeping filing date fixed)
• Damage period start/end boundaries
• Category mapping for each line item (damages vs other)

3) Compare the eligibility boundary, not just the totals

When allocations differ, look for where line items cross the inclusion threshold:

• the first day included
• the last day included
• which categories become eligible vs. ineligible within the SOL window

4) Validate line-item categorization with a crosswalk

Make a simple crosswalk of how each workflow labels items:

Then rerun DocketMath after aligning labels.

Next steps

Start with the variables most likely to be impacted by Wyoming’s 4-year default SOL—date inputs and boundaries—because they most often change the eligible window.

Practical workflow:

1. Run a baseline in DocketMath: **/tools/damages-allocation
2. Change trigger/accrual date by a known increment (e.g., 15 or 30 days)
3. Change filing date by the same increment (while keeping the other date fixed)
4. Keep category labels identical; compare only eligibility-window effects
5. If differences remain, audit category mapping and any offsets/adjustments included in the damage base

Gentle caution: This isn’t legal advice. If your inputs use different “start date” concepts (event vs. accrual vs. discovery), a 4-year SOL window in Wyoming can slice the damages differently, leading to allocation differences even when the underlying invoices or amounts are similar.

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