Inputs you need for Damages Allocation in Alaska

Inputs you will need

Run this scenario in DocketMath using the Damages Allocation calculator.

To run DocketMath → damages-allocation for an Alaska (US-AK) matter, you’ll want to collect the same core inputs each time. The goal is to support a damages allocation workflow that’s internally consistent and ready for Alaska timing checks (especially around whether portions may fall outside the relevant SOL window).

Because you asked for jurisdiction-aware rules, Alaska’s general statute of limitations (SOL) period is the key timing parameter to plan around. Under the default/general period in Alaska Statutes § 12.10.010(b)(2), the general SOL period is 2 years. Your brief did not identify a claim-type-specific sub-rule, so this content treats the 2-year period as the default baseline for timing logic (not a tailored rule for a specific cause of action).

Collect these inputs before you open /tools/damages-allocation:

• If you have multiple events, plan to use:

Where to find each input

Use this as a practical “where to look” checklist so you can avoid rework.

Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.

Timing inputs

• Filing date / suit commencement date

  • Look at your court docket entry showing when the complaint was filed (or the matter commenced in court).

• Accrual/occurrence dates

  • Look to documents that anchor when harm occurred or became measurable, such as:

    • incident report
    • contract breach date
    • service interruption date
    • treatment records start date
  • If you have multiple events:

    • Use the earliest date for conservative timing analysis (i.e., to understand the most timing risk).
    • Use the latest date only if you’re intentionally segmenting damages by event timing.

Damages totals by category

• Economic damages

  • Look at:

    • billing statements / medical bills
    • pay stubs / payroll records
    • invoices and receipts
    • accounting summaries
  • If you’re modeling lost wages, ensure the period you calculate matches your damages theory and the dates you’re inputting.

• Non-economic damages

  • Look at the medical documentation and case notes that support how the injury affected the person.
  • Keep your own internal mapping consistent with your litigation posture (e.g., what events you attribute to which impacts).

Liability allocation inputs

• Percentage allocations

  • Look at:

    • your discovery position
    • expert report assumptions (if you have them)
    • settlement posture / mediation allocation logic
    • internal comparative responsibility assumptions
  • Make sure your percentages are consistent with how your DocketMath workflow expects totals to be handled.

Attribution mapping

• Category-to-party routing

  • Look to your causation theory in the case file:

    • Which party conduct you believe is responsible for each damages category
  • Organize this mapping by damages category so DocketMath can route category totals to the correct party share(s).

Run it

Once you’ve gathered the inputs, run DocketMath’s damages-allocation tool at /tools/damages-allocation.

Enter the inputs in DocketMath and run the Damages Allocation calculation to generate a clean breakdown: Run the calculator.

If an assumption is uncertain, document it alongside the calculation so the result can be re-run later.

Step-by-step workflow

1. Enter timing inputs

   • Add:

     • Filing date
     • Accrual/occurrence date(s) (earliest and/or latest, depending on your segmentation approach)

2. Enter damages totals

   • Input each damages category total you want allocated.

3. Enter allocation shares

   • Add party percentage shares according to your chosen approach.

4. Map categories to parties

   • Specify which damages category flows to which party share(s).

5. **Apply Alaska timing check (default/general SOL)

   • DocketMath uses Alaska’s general SOL period of 2 years based on Alaska Statutes § 12.10.010(b)(2) as the default timeframe.
   • Since no claim-type-specific sub-rule was found in your brief, treat this logic as default/general, not tailored to a specific claim category.

Disclaimer (gentle): Timing flags or outputs from an allocation tool do not automatically decide legal viability of every damages theory. SOL determinations can involve more nuance than a checklist-based input model, so confirm with qualified legal guidance for the specific facts.

How outputs typically change when inputs change

• Earlier accrual date

  • Damages tied to earlier events are more likely to land near or outside the 2-year default window used for timing checks.
• Earlier filing date

  • Generally increases SOL risk; later filing dates typically reduce it.
• Different percentage shares

  • The numeric allocation output shifts immediately because category totals are routed through the shares you enter.
• Segmenting damages by event dates

  • If you provide multiple accrual/occurrence dates and separate routing by category/event, outputs can differ by segment—especially where timing-related flags are part of your workflow.

What the Alaska SOL input means (plain terms)

Alaska’s general statute of limitations is 2 years for the default period referenced by Alaska Statutes § 12.10.010(b)(2). Because your brief did not identify a claim-type-specific sub-rule, the practical approach here is to treat the 2-year general baseline as the default parameter for timing-related checks in DocketMath.

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