Why Damages Allocation results differ in Alaska

The top 5 reasons results differ

Run this scenario in DocketMath using the Damages Allocation calculator.

If you run DocketMath’s Damages Allocation calculator for the same underlying dispute in Alaska (US-AK) but see different allocation outcomes, the differences almost always come from how the calculator’s inputs map to Alaska’s timing rules—plus a few common data issues. Here are the top 5 causes that most frequently change results.

1) The statute of limitations window is applied differently (or not at all)

In Alaska, the general/default statute of limitations is 2 years under Alaska Statutes § 12.10.010(b)(2). DocketMath uses this general period when there’s no claim-type-specific sub-rule provided.

Important: The brief you’re using indicates no claim-type-specific sub-rule was found, so the correct approach is to default to the general 2-year period. If your workflow (or your data) assumes a different claim-type rule, results can diverge quickly.

Why it changes outputs: if your “eligible damages” period shifts (because your assumed SOL start/end boundaries shift), the calculator may allocate more or less damages into the covered window.

2) You used different date inputs (event date vs. notice date vs. filing date)

Damages allocation is highly sensitive to which dates you enter. Common date choices include:

• date of the underlying conduct (event date)
• date damage onset began
• date notice was given (if you tracked it)
• date suit was filed (or the last relevant measurement date)

Even a single-day change can affect whether damages fall inside the 2-year eligibility window.

3) You entered “loss categories” that don’t align with the breakdown model

DocketMath’s allocation depends on the structure of your damages inputs. For example, splitting amounts into categories (medical, lost earnings, property, etc.) can change how the calculator distributes totals over time.

If one run groups amounts broadly while another run uses more granular categories, the proportional allocation can differ because the calculator is distributing based on the inputs you provided.

4) Partial documentation changes the proportional weighting

When supporting amounts are entered unevenly (for example, one category is provided as monthly figures while another is a single lump sum), the weighting across time periods can shift.

Result: two users can enter the same overall damages total but different category distributions, leading to different allocated totals per time window.

5) One run includes periods you meant to exclude

Differences often come from time-range exclusions or inclusions, such as:

• gaps where damages did not occur
• mitigation periods you marked as “non-loss”
• periods overlapping with other coverage/settlements

If one run includes those periods and another excludes them, you’ll see changes even when everything else looks similar.

Quick reference: what tends to mismatch

How to isolate the variable

To identify which input caused the difference, run controlled comparisons inside DocketMath (without changing multiple things at once). This is especially important because Alaska’s 2-year general SOL rule can magnify small date shifts.

• 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.

Step-by-step isolation checklist

1. Freeze non-date inputs

   • Keep totals, category splits, and any inclusion/exclusion selections the same.
2. Run Version A

   • Use your original date inputs and category inputs.
3. Run Version B, changing only one variable

   • Swap the start date basis (event date vs. damage onset).
   • OR swap the end date basis (filing date vs. last measurement date).
   • Keep categories identical to avoid confounding.
4. Confirm the calculator is defaulting to the general/default 2-year SOL under Alaska Statutes § 12.10.010(b)(2) (since no claim-type-specific sub-rule was found in your materials).
5. If you have multiple alleged conduct periods, run them separately instead of aggregating—otherwise small boundaries can blend together and appear as “mysterious variance.”

Use a “diff” log to make the cause obvious

Record the exact boundaries used:

• Version A SOL window: ___ to ___
• Version B SOL window: ___ to ___
• Observed change in eligible damages: +___ / -___

If the SOL boundaries don’t change but outputs still differ, the cause is more likely category structure or weighting (reasons #3–#4). If the boundaries do change, it’s usually the SOL/date mapping (reasons #1–#2).

Next steps

A practical, low-guesswork workflow:

1. Verify your SOL basis in your DocketMath workflow:

   • defaulting to 2 years under Alaska Statutes § 12.10.010(b)(2) when no claim-type-specific sub-rule is available.
2. Standardize your date definitions:

   • choose one consistent meaning for the start (damage onset or event date, depending on your mapping)
   • choose one consistent meaning for the end (filing date or last measurement date)
3. Normalize categories:

   • either always use categorized entries or always use a consistent lump-sum method.
4. Run a three-pass test:

   • Pass 1: change dates only
   • Pass 2: change categories only
   • Pass 3: change exclusions only
5. If results still diverge after Pass 3, compare:

   • whether your category sums reconcile to the same totals
   • whether your excluded/non-loss periods match exactly

If you’re trying the calculator right now, start here: /tools/damages-allocation.

Gentle note: This is diagnostic guidance, not legal advice. If you’re unsure which date basis or limitation period should apply to your specific claim, consider confirming with a qualified professional.

Related reading

• Damages Allocation Guide for Alabama — Comparative Fault Rules
• Damages Allocation Guide for American Samoa — Comparative Fault Rules
• Damages Allocation Guide for Arizona — Comparative Fault Rules