How to run Damages Allocation in DocketMath for Wyoming

6 min read

Published April 15, 2026 • By DocketMath Team

This article is for informational purposes only and does not constitute legal advice. Laws change frequently — verify all citations with current official sources.

Step-by-step

Run this scenario in DocketMath using the Damages Allocation calculator.

This guide walks you through running Damages Allocation in DocketMath for Wyoming (US-WY). The walkthrough assumes you’ll use DocketMath’s jurisdiction-aware setup and that your matter is governed by the general Wyoming statute of limitations (not a claim-specific one).

1) Start at the correct tool

Open DocketMath’s calculator here: /tools/damages-allocation
Confirm you’re in the Damages Allocation workflow (calculator name: damages-allocation).

2) Select Wyoming jurisdiction (US-WY)

Look for the jurisdiction selector and choose:

Jurisdiction: **US-WY (Wyoming)

DocketMath uses this selection to apply Wyoming-specific configuration, including limitations logic that is relevant to the allocation workflow.

3) Understand the Wyoming limitations assumption used in this calculator run

Wyoming’s general statute of limitations for many civil actions is 4 years under:

Wyo. Stat. § 1-3-105(a)(iv)(C)
(General SOL Period: 4 years)

Important: No claim-type-specific sub-rule was found for this workflow. That means this calculator run should treat the SOL basis as the general/default period, not a specialized rule for a particular claim category:

Default assumption for this workflow: 4 years under **Wyo. Stat. § 1-3-105(a)(iv)(C)

Note (read this carefully): If your matter involves a claim category with a different limitations rule, the “general/default SOL” assumption can misstate eligibility timing. The results below reflect the general/default SOL assumption described above.

4) Enter damages inputs in DocketMath

In the Damages Allocation interface, you’ll typically enter values that feed the allocation math. Use a worksheet-like approach so it’s easy to verify later:

Total damages amount: the full claimed pool to allocate
Damages categories: if DocketMath prompts for multiple buckets (for example, economic vs. non-economic, or other tool-defined buckets)
Allocation weights or percentages: if the tool asks you to allocate by ratio
Date fields relevant to limitation timing logic (if included in the workflow)

If the tool asks for dates, use the fields consistently, such as:

Key event/accrual date(s) (for example, when damages accrued or when the relevant conduct occurred)
Filing/measurement date (the date you’re measuring against the SOL window)

5) Configure timeline inputs for the 4-year window

When the interface includes timing fields, set them so the calculation can determine whether damages relate to periods inside vs. outside the 4-year general SOL.

A common pattern in Damages Allocation runs is:

Determine whether portions of damages relate to periods within the 4 years prior to the relevant filing/measurement date
Allocate between eligible vs. ineligible portions according to the tool’s allocation logic

Practical tip: Use consistent date meaning across all date fields. Even if the interface is forgiving, inconsistent inputs can materially skew outputs.

6) Review outputs and how they change

After you run the calculation, you should see outputs that typically include:

Allocated amounts per category/bucket
Eligible vs. non-eligible portions (where SOL timing is applied)
Totals reflecting the allocation results

How inputs affect outputs (what to watch):

Move the filing/measurement date forward → generally more damages may fall within the 4-year window → the eligible portion may increase
Move the key event/accrual date earlier → generally more damages may fall outside the 4-year window → the eligible portion may decrease
Change allocation weights/percentages → category totals shift even if eligibility stays the same

7) Export or capture results for review

Once the results look correct for your intended scenario:

Copy the key totals into your case notes
Save any screenshots/exports if DocketMath provides them
Record the inputs used—especially the SOL-relevant dates and category assumptions

This helps you rerun quickly if you later adjust dates, buckets, or weightings.

Common pitfalls

These issues most often cause confusing results in Wyoming runs—especially where a general/default SOL is used.

Using claim-specific limitations assumptions without updating the workflow assumption
- This workflow uses the general 4-year period from Wyo. Stat. § 1-3-105(a)(iv)(C).
- Since no claim-type-specific sub-rule was found for this calculator run, you shouldn’t assume the output covers every Wyoming claim category.
Entering inconsistent dates across fields
- For example, one field may represent “accrual,” while another represents “notice” or “filing,” but the tool may expect both to align with a specific measurement framework.
- Keep date meanings consistent with how the tool labels them.
Running Wyoming (US-WY) but leaving non-WY timing assumptions
- Confirm the jurisdiction selector is set to US-WY before running.
- Then verify that your date inputs match the Wyoming scenario you’re trying to model.
Changing allocation amounts without accounting for eligibility timing
- If DocketMath separates “eligible vs. non-eligible,” changes can appear to behave “unexpectedly” if you’re focusing only on category weighting rather than the SOL-based eligibility split.
Forgetting the SOL assumption is specifically a “default” for this workflow
- Even though the calculator uses 4 years under Wyo. Stat. § 1-3-105(a)(iv)(C), it may not be correct for every Wyoming claim type.
- Treat the calculator output as a structured estimate under the workflow’s default assumptions, not a substitute for claim-specific analysis.

Gentle caution: Don’t assume that because the tool applies 4 years (under Wyo. Stat. § 1-3-105(a)(iv)(C)) the result is automatically correct for every Wyoming claim type. This guide reflects the general/default period and the available sub-rule coverage for this workflow.

Try it

If you want a quick, hands-on run, use this micro-checklist:

Go to /tools/damages-allocation
Set **Jurisdiction = US-WY (Wyoming)
Confirm the SOL logic uses the general/default 4-year period under **Wyo. Stat. § 1-3-105(a)(iv)(C)
Enter:
- Total damages
- Category allocations (amounts, weights, or percentages—whichever the calculator requests)
- SOL-relevant dates (key event/accrual and measurement/filing date)
Run the calculation
Compare outputs after changing one input at a time, such as:
- Move the measurement date by 30 days to see how the eligible portion shifts
- Adjust one category weight by 5% to see how category totals change

A good practice is to record “before vs. after” totals so you can tell whether changes are driven mainly by eligibility timing or by allocation weighting.