How to run Damages Allocation in DocketMath for Alaska
5 min read
Published April 15, 2026 • By DocketMath Team
Step-by-step
Run this scenario in DocketMath using the Damages Allocation calculator.
This guide walks you through running Damages Allocation in DocketMath for Alaska (US-AK). The key jurisdiction-aware detail for this setup is Alaska’s general statute of limitations: 2 years under Alaska Statutes § 12.10.010(b)(2).
Note: For Alaska, this workflow uses the general/default 2-year period from AS § 12.10.010(b)(2). No claim-type-specific sub-rule was found for this workflow, so run the calculator using the general period rather than a specialized one.
1) Start the Damages Allocation tool
- Open the calculator directly: /tools/damages-allocation
- Confirm you’re in the correct jurisdiction context:
- Jurisdiction: **Alaska (US-AK)
2) Enter core case dates (the calculator’s “time logic”)
Most damages allocation calculators depend on the window of time over which damages are considered. In DocketMath, you’ll typically provide:
- Incident date (or the start point for the alleged harm)
- Filing/claim date (often the date the claim is brought, or the relevant notice is provided)
Then DocketMath uses Alaska’s general SOL period:
- 2 years per **Alaska Statutes § 12.10.010(b)(2)
Because this is the general/default rule, the tool should compute an eligibility window (commonly: damages that fall within the relevant 2-year timeframe).
3) Provide the damages components to allocate
Next, enter the amounts you want DocketMath to allocate. Depending on the calculator configuration, typical inputs include:
- Total claimed damages
- Component amounts (for example, categories you want separated and allocated)
- Optional breakdowns (such as time-phased amounts) if your workflow uses them
How outputs change:
- If you input a larger total, the allocation results scale proportionally.
- If you specify different category amounts, DocketMath re-balances the allocation shares across those categories.
- If you include time-phased components, changing your incident date and filing/claim date shifts which portions fall within the 2-year SOL window.
4) Run the allocation
Click Calculate (or the tool’s equivalent action). After the run, review:
- The allocated damages totals by category/component
- Any time-window adjustments tied to the 2-year period under **AS § 12.10.010(b)(2)
- A summary of how the tool treated the SOL window—this is especially important because you are using the general/default period
5) Verify the SOL window is the “general 2-year default”
Before you export or reuse results, double-check that DocketMath is using:
- Alaska Statutes § 12.10.010(b)(2): 2 years
If your matter involves a special statutory scheme and you intended a different limitations rule, this tool setup may not match that scenario. For this Alaska workflow, no claim-type-specific sub-rule was found, so the tool uses the general 2-year default.
Disclaimer: This walkthrough is about using DocketMath’s inputs and logic. It is not legal advice, and it may not reflect every nuance of a particular case.
6) Use the results for your workflow outputs
When you’re satisfied the inputs align with your intended assumptions, collect:
- Allocation totals by component
- Any SOL-trimmed amounts (if the tool applies a time cutoff)
- Notes you want to carry into your document workflow (for example, “Alaska general SOL: 2 years”)
If DocketMath provides export options, save the results for later comparison after you revise inputs.
Common pitfalls
These are the mistakes that most often distort allocation results in a jurisdiction-aware run.
- Even if the rest of your inputs are perfect, the computed window won’t match Alaska’s 2-year standard.
- This workflow uses the general/default 2-year period. If you assume a different period, your damages-trim outcome can be wrong.
- DocketMath typically expects the date that starts the relevant limitations evaluation (often filing or bringing of the claim). If you enter a different date, the SOL window changes.
- If the tool allocates proportionally, mismatched totals can cause unexpected category shares.
- If the tool supports time-phased inputs, failing to provide or correctly align them can lead to overstated amounts inside the SOL window.
- For this Alaska setup, no claim-type-specific sub-rule was found, so the tool uses the general 2-year default under AS § 12.10.010(b)(2).
Pitfall reminder: If your fact pattern includes a specialized limitations statute, relying on the general 2-year default could materially change which damages are counted. The DocketMath run will still be internally consistent—it just may not match the rule you intended to apply.
Try it
Ready to run the calculator for Alaska? Start here:
- Open /tools/damages-allocation
- Set Jurisdiction: US-AK
- Enter:
- Incident date (start of alleged harm)
- Filing/claim date (end of the evaluation window)
- Your damages inputs (total and/or component amounts)
Then confirm the run reflects:
- Alaska general SOL = 2 years under **Alaska Statutes § 12.10.010(b)(2)
Quick checklist for your first run:
If you change only one variable, iterate like this:
- Keep damages amounts fixed
- Adjust filing/claim date by 30–90 days
- Re-run and observe how any SOL-trim (if applied) changes the allocation totals
Single-variable testing helps you see what drives your results before you finalize downstream use.
