Worked example: Damages Allocation in Alaska
6 min read
Published April 15, 2026 • By DocketMath Team
Example inputs
Run this scenario in DocketMath using the Damages Allocation calculator.
Below is a jurisdiction-aware worked example of damages allocation in Alaska (US-AK) using DocketMath with the default, damages-related limitations logic available in the calculator at /tools/damages-allocation.
Because your scenario does not have a claim-type-specific sub-rule identified in the provided jurisdiction data, this example applies the general/default SOL period:
- General SOL period: 2 years
- General statute citation: Alaska Statutes § 12.10.010(b)(2) (2-year limitation for certain actions not otherwise specified)
Note (important): This walkthrough uses the general/default 2-year SOL logic because no claim-type-specific damages sub-rule was found in the provided data. If your facts fit a different statute or exception, the allocation outcome can change.
Hypothetical fact pattern (used to drive the calculator)
Assume a plaintiff seeks damages for a single dispute with multiple time slices of alleged harm. You want to allocate total claimed damages between:
- amounts likely treated as timely (within the applicable lookback window), and
- amounts likely treated as untimely (outside the lookback window).
Inputs for the DocketMath damages-allocation calculator
Use the following numbers to model the allocation:
| Input | Example value | What it represents |
|---|---|---|
| Claim date (filing/trigger date) | 2026-04-15 | The date from which the calculator measures the lookback window |
| Alleged harm start date | 2024-01-01 | Start of the damages timeline you’re trying to allocate |
| Alleged harm end date | 2026-03-01 | End of the damages timeline you’re trying to allocate |
| Total claimed damages | $120,000 | Aggregate damages the plaintiff alleges across the whole timeline |
| Allocation method | Even allocation by time | Damages distributed proportionally across the days in the harm window |
| Uncertain “known amount” portion | $0 | Set to zero if you do not have separate evidence distinguishing damages segments |
Why these inputs?
DocketMath needs timeline facts translated into an allocation output. A simple, transparent method is proportional allocation by time (days-based): each day carries equal weight, so earlier vs. later days affect the timely/untimely split.
This is a modeling choice—not a factual conclusion. The goal is to quantify the impact of the 2-year default SOL lookback on an otherwise “lumped” damages figure.
Example run
Run the Damages Allocation calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.
Step 1: Determine the lookback window (Alaska default SOL)
With a 2-year general SOL under AS § 12.10.010(b)(2), the calculator uses a lookback period measured back from the 2026-04-15 claim date.
- Lookback window end: 2026-04-15
- Lookback window start: 2024-04-15
Timeline to allocate:
- Alleged harm from 2024-01-01 to 2026-03-01
Split the harm period into:
- Timely segment: 2024-04-15 → 2026-03-01
- Untimely segment: 2024-01-01 → 2024-04-14
Step 2: Compute day counts (days-based allocation)
Approximate day counts for clarity:
- Untimely days:
2024-01-01 → 2024-04-14 ≈ 105 days - Timely days:
2024-04-15 → 2026-03-01 ≈ 685 days - Total days: 790 days
Step 3: Allocate total claimed damages proportionally
Total claimed damages = $120,000.
Under even-by-time allocation:
- Timely damages ≈ (685 / 790) × 120,000
≈ 0.8671 × 120,000
≈ $104,053 - Untimely damages ≈ (105 / 790) × 120,000
≈ 0.1329 × 120,000
≈ $15,947
Example output (what In DocketMath, this appears as)
Run the DocketMath calculator at /tools/damages-allocation using the inputs above.
Illustrative results:
| Output category | Amount | How to interpret it |
|---|---|---|
| Timely damages (within 2-year default lookback) | $104,053 | The portion of the timeline inside the 2-year window under AS § 12.10.010(b)(2) |
| Untimely damages (outside 2-year window) | $15,947 | The portion of the timeline before 2024-04-15 |
| Total allocated damages | $120,000 | Should match the input total |
| Practical modeling note | “Allocation is model-based” | Even-by-time assumes each day contributes equally to damages |
Warning: Time-based allocation is a proxy. If actual damages occur in discrete events (e.g., only certain months reflect reimbursable costs), an even-by-time approach can misstate the real split.
Step 4: Turn the outputs into actionable case work (non-legal advice)
Use the split to organize evidence gathering and analysis:
- For the $15,947 (untimely) portion, identify which parts of the timeline fall before 2024-04-15.
- For the $104,053 (timely) portion, collect documentation supporting the damages that fall inside the lookback window.
- Treat the allocation as a scenario-planning estimate; confirm how the underlying damages theory ties to the dates.
Sensitivity check
This section stress-tests the math model inputs to show how outputs change, while keeping the same underlying Alaska default 2-year SOL rule (AS § 12.10.010(b)(2)).
To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.
Sensitivity #1: Shift the claim date by 30 days
Keep the harm window the same (2024-01-01 → 2026-03-01), but change the claim date:
- Original claim date: 2026-04-15
- Shifted claim date: 2026-03-16 (30 days earlier)
- New lookback start: 2024-03-16
Expected direction of change:
- Timely allocation decreases
- Untimely allocation increases
Reason: moving the lookback window earlier typically sweeps more of the harm timeline into the untimely bucket—especially because the split boundary (the SOL cut-off) sits relatively early in the harm range.
Sensitivity #2: Use a “front-loaded” damages pattern instead of even-by-time
If losses are not evenly distributed (common when damages spike around key events), try a different allocation method in DocketMath that weights earlier dates more heavily.
Expected direction of change:
- Untimely allocation increases if earlier periods receive more weight
- Timely allocation decreases correspondingly
Sensitivity #3: Narrow the harm window end date
Suppose evidence shows the last actionable harm date was earlier than 2026-03-01, for example 2026-01-15.
Expected direction of change:
- Total days in the harm window shrink.
- The fraction of days landing after 2024-04-15 may shrink too, changing the allocation mix.
A shortened timeline close to the SOL boundary can swing results more than expected.
Summary table: qualitative output movement
| Change you test | Likely impact on timely damages | Likely impact on untimely damages |
|---|---|---|
| Claim date moves earlier | Down | Up |
| Damages are front-loaded | Down | Up |
| Harm window end moves earlier | Mixed (often down) | Mixed (often up) |
Note: DocketMath is best used for quantification and scenario planning. The ultimate legal effect of any SOL bar depends on how the facts map to the statute and any recognized exceptions. This example applies only the general 2-year default under AS § 12.10.010(b)(2) as provided.