Common Damages Allocation mistakes in Wyoming

The top mistakes

When people use DocketMath’s damages-allocation calculator for Wyoming (US-WY) filings, the most common errors usually come from mixing up: (1) what Wyoming’s timing rules require, (2) what “damages allocation” means for your inputs, and (3) how to document the numbers so they hold up to basic review.

Below are the top mistakes we see when preparing damages allocations in Wyoming.

1) Using the wrong statute of limitations window (SOL)

Wyoming’s default/general SOL is 4 years for covered civil claims. The general period referenced for this brief is Wyo. Stat. § 1-3-105(a)(iv)(C), which provides a four-year statute of limitations under the enumerated general rule.

A common error is assuming a different deadline applies to a particular claim type—especially when your damages categories suggest a specialized theory (like property loss, personal injury, or contract-related amounts).

2) Allocating “total damages” without breaking out components correctly

Another frequent failure is treating damages as a single undifferentiated bucket when your allocation requires component fields.

With DocketMath, you typically provide inputs that represent distinct damages components (for example: economic vs. non-economic, or different loss categories depending on the calculator’s structure). If you enter the same combined total into multiple fields, the output can effectively double count.

What goes wrong in practice

• You receive a total that is inflated because one figure appears twice.
• Allocation shares/percentages (if used) no longer reflect the underlying amounts.
• Later, you can’t reconcile the math to what’s stated in your narrative or exhibits.

3) Using inconsistent units or time windows for damage calculations

Wyoming matters often require damages to reflect a defined period (for example, a start date to an end date). A common error is mixing time spans across components, such as:

• calculating one component for 12 months
• calculating another component for 13 months
• setting the calculator’s time span but plugging in component values derived from a different span

Result: the overall output may still total correctly, but the components won’t match the timeline you say supports the damages.

4) Rounding too early (and then rounding again)

Rounding errors are surprisingly common—especially when you:

• round each component to the nearest dollar,
• compute allocation shares,
• round shares to whole percentages,
• convert back to dollars.

DocketMath-friendly approach: keep more precision in intermediate steps and only round for final presentation (e.g., for a filing exhibit or table).

5) Forgetting to align allocation numbers with the narrative theory

Even when the math is internally consistent, an allocation can be “wrong” in a practical review sense if the numbers don’t track the story in the filing. Examples include:

• economic losses described as wage-related, but entered as general “other”
• damages characterized as “past,” but calculated using a “future” assumption window
• mitigation described in the narrative, but not reflected in reduced amounts

This is less a computational issue and more an evidence alignment issue—something DocketMath outputs can help expose if you compare inputs to your stated basis.

6) Not linking the SOL timing to when the claim actually accrued

People often add the SOL deadline to the calendar without checking accrual assumptions. While accrual details depend on the specific facts, a procedural error can occur when your damages period calculation conflicts with your stated timeline for when the claim began.

If your damages window extends beyond what your filing supports, you can end up with an internally inconsistent packet—even if the calculator’s arithmetic is correct.

How to avoid them

You can reduce these errors quickly by treating DocketMath as a structured workflow—not just a math engine.

Use a written checklist for inputs, document each source, and run a quick sensitivity check before finalizing the result. When two runs differ, compare inputs line by line and re-run with one variable changed at a time.

1) Lock the Wyoming SOL rule up front (default 4 years)

Before finalizing damages allocations, set your baseline timeline expectation to Wyoming’s general/default 4-year period:

• Rule: **Wyo. Stat. § 1-3-105(a)(iv)(C)
• Period: 4 years
• Use this as default: unless you identify a specific different rule for a particular claim type.

Practical tip: keep a one-line note in your working file, such as:
“Wyoming general SOL applied: 4 years under Wyo. Stat. § 1-3-105(a)(iv)(C).”

Then ensure your damages timeline doesn’t silently contradict that framing.

2) Use DocketMath to validate totals and component consistency

Start from this worksheet-style principle:

• Total damages = sum of the components you entered
• Each component should map to a category you can explain

If your allocation table totals don’t match your computed sum from the inputs, stop and correct the inputs before trusting the outputs.

If you’re building your allocation now, open DocketMath damages allocation calculator and cross-check:

• component totals
• any shares/percentages used by the calculator
• the overall total

Gentle reminder: DocketMath helps with structure and arithmetic, but it doesn’t replace legal analysis of accrual, limitations, or evidentiary support.

3) Standardize dates and time windows before entering amounts

Create a quick checklist for your damages period:

This prevents the “12 months vs. 13 months” mismatch that leads to subtle errors.

4) Delay rounding until the end

Keep internal precision for calculations, then round only for final display.

A practical workflow:

• Keep calculator inputs with full cents (or at least 2 decimals).
• Round in a final formatting step for the filing table (if needed).

If you must round inputs, do it consistently across components so the allocation doesn’t drift.

5) Reconcile output numbers to your narrative and exhibits

After using DocketMath, do a reconciliation pass:

This catches category drift and “double count” issues before they become avoidable filing problems.

6) Don’t use the calculator to paper over missing factual grounding

A perfectly computed allocation can still be challenged if the underlying timeline, categories, or documentation don’t align with what you claim.

If a component depends on assumptions, keep those assumptions explicit in your working notes and ensure they match the evidence you plan to cite.

Disclaimer: This article is for general informational purposes and not legal advice. For questions about limitations periods, accrual, or admissibility, consult a qualified Wyoming attorney.

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