Common Damages Allocation mistakes in Alaska
6 min read
Published April 15, 2026 • By DocketMath Team
The top mistakes
Run this scenario in DocketMath using the Damages Allocation calculator.
When people use DocketMath to prepare damages allocation work in Alaska (US-AK), the errors usually come from a few repeatable patterns. Below are the most common mistakes we see—and what they look like once you run /tools/damages-allocation.
Practical note: This is general guidance about common allocation mistakes, not legal advice.
1) Using the wrong statute of limitations for the damages work
A frequent failure is pairing a damages-allocation spreadsheet with an incorrect timing rule. In Alaska, the general/default statute of limitations is 2 years.
- General SOL period: 2 years
- Cited rule: Alaska Statutes § 12.10.010(b)(2) (general/default period)
Clear jurisdiction note (important): No claim-type-specific sub-rule was found in the provided Alaska jurisdiction data. That means you should apply the 2-year general/default period when you don’t have a more specific accrual/timing rule for a particular claim type.
Why this breaks allocations: If the underlying damages window is wrong, the “time-sliced” or “period-based” damages inputs in /tools/damages-allocation can silently include months (or exclude months) that should have been handled differently.
2) Misallocating damages across categories (lumping vs. separating)
Another common error is collapsing different damages components into one bucket, then treating the output as if it were a single undifferentiated number.
Typical examples:
- Mixing economic and non-economic components
- Combining past and future periods into one line
- Treating reimbursements/credits as if they were the same as “paid damages”
In DocketMath terms: If the calculator expects separate fields (common in damages allocation workflows), lumping inputs forces one allocation approach across items that should be split. The output may look internally consistent—but it can be categorically wrong.
3) Off-by-one date ranges (accrual start/end confusion)
Even when people use the correct 2-year timing rule from AS § 12.10.010(b)(2), they often build the range incorrectly in their inputs.
Common patterns:
- Starting on the wrong day (e.g., event date vs. notice date vs. filing date)
- Ending the range on the wrong boundary (e.g., including the day of filing)
- Using “365 days” as a substitute for an actual date-to-date span
What changes in the DocketMath output: Because damages are often modeled monthly/weekly/by-pay-period, a small date-range change can move substantial sums between blocks. That’s how “minor” input edits create major allocation shifts.
4) Neglecting jurisdiction alignment (US-AK rules applied to non-AK records)
If the underlying facts involve multi-state conduct, teams sometimes compute damages using Alaska assumptions while the evidence dates or payment streams follow other conventions.
You’ll see this when:
- Payment records are organized in a different cadence (e.g., weekly vs. biweekly formats)
- The document set follows different allocation conventions
- People copy-paste a template from another state and only change the title
Why it’s costly: /tools/damages-allocation can only allocate what you provide. If the structure of your inputs doesn’t match the allocation model’s expectations, the calculation will still produce numbers—just for the wrong underlying story.
5) Feeding the calculator “net numbers” without describing offsets
A subtle but recurring error: entering net amounts (after deductions, insurance, or reimbursements) while the allocation logic expects gross amounts plus separate offset fields.
Result: double-counting (or double-deducting) and allocation shifts that can’t be reconciled later.
6) Missing the “what the calculator did” step
Teams sometimes run /tools/damages-allocation and report only totals—without retaining:
- The limitation period used
- The period start/end dates used in the model
- The category splits entered
- Any offsets/credits applied
- Any input formatting assumptions
Later, if the damages narrative is challenged, you can’t show whether the calculation matched your evidence and your chosen Alaska timing window.
Warning (gentle but real): If you can’t reproduce /tools/damages-allocation using the same inputs and date window, the calculation becomes hard to verify—even if the totals look reasonable.
How to avoid them
Use a checklist workflow before you finalize your /tools/damages-allocation run. The goal is to keep your numbers tied to Alaska’s 2-year default limitations period and to your actual evidence structure.
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.
Step 1: Lock the timing rule you’re actually using (Alaska default = 2 years)
Before you enter anything into /tools/damages-allocation, decide whether you are using Alaska’s general/default limitations period.
- Use Alaska Statutes § 12.10.010(b)(2) as your default when you do not have a claim-type-specific rule.
- Apply 2 years to determine which damage time blocks belong in the allocation.
Then document that choice (even in a short note in your working file) so the calculation is traceable.
Step 2: Separate categories in your input data
Prepare your damages inputs so DocketMath can treat components differently. A simple structure that reduces allocation errors usually looks like:
- Past economic damages (by month or pay period)
- Past non-economic damages (if applicable)
- Future damages (if applicable—often handled separately)
- Offsets/credits (insurance payments, reimbursements, third-party payments)
- Any workflow-specific adjustments (only if your template supports them)
If your documents only provide one combined figure, plan a reconciliation step before the allocation is treated as reliable.
Step 3: Use date-to-date thinking (and keep an audit trail)
When selecting the date range for the 2-year window:
- Start with the specific accrual/event date you’re using for the model
- End with the filing/measurement boundary you’re using
- Record the exact start and end dates you input
After running /tools/damages-allocation, save the outputs with those dates attached. This makes off-by-one errors much easier to spot.
Step 4: Feed gross numbers plus explicit offsets (not “mystery netting”)
For calculator reliability:
- Enter gross amounts where possible
- Enter offsets separately in their own fields
- Avoid mixing “already netted” figures into the gross fields
This prevents allocation drift that can’t be explained from the final totals alone.
Step 5: Cross-check totals against sanity ranges before relying on them
After you compute with /tools/damages-allocation:
- Verify that totals scale with your date range
- Confirm that category totals add up to the expected grand total
- Check whether any component looks unusually large or small compared to adjacent periods
As a quick test: if adjusting the date range by one month changes results by a surprising amount, re-check the range boundaries first.
Step 6: Use the tool the right way—then document the inputs
When you run /tools/damages-allocation, keep a short record of:
- The limitation period used (2 years under AS § 12.10.010(b)(2), as applicable)
- The date window used in the model (start/end)
- The category splits entered
- The offsets/credits applied
That’s not legal advice—it’s calculation hygiene, and it’s often the difference between numbers you can defend and totals you can’t.