Statute of Limitations for Written Contract in Alaska
6 min read
Published April 8, 2026 • By DocketMath Team
Overview
In Alaska, the statute of limitations (SOL) for a written contract claim is 2 years under Alaska Statutes § 12.10.010(b)(2).
This 2-year period is the default rule for written contracts. In the materials reviewed for this topic, no contract-type-specific sub-rule was found, so the general/default 2-year period is the starting point for most written-contract disputes in Alaska.
Note: A “written contract” claim typically involves an agreement memorialized in writing (signed paper agreement, contract document, or other written memorialization). This page focuses on SOL timing at a practical level, not on whether a particular agreement qualifies as written in every fact pattern.
Limitation period
The limitations period is 2 years. Alaska’s general limitations statute for this category is Alaska Statutes § 12.10.010(b)(2), which provides a two-year time limit under the statute’s general framework for qualifying actions—including many contract-related claims where this default scheme applies.
What this means for dates
To use the SOL effectively, you’ll want to identify the start date (often called the accrual date) and count forward 2 years.
A key practical point: the start date is not always the contract signature date. Many disputes turn on when the cause of action accrues, which commonly aligns with when a breach occurs (or when damages are discoverable/ascertainable in light of the claim). Accrual can depend on the contract’s terms and the nature of the breach—so treat the accrual date as the most important factual input for SOL timing.
Quick timeline example (illustrative)
- Contract breach occurs: January 10, 2025
- SOL length: 2 years
- Target filing window: typically until about January 10, 2027
This example is meant to show how the 2-year rule works in practice—it does not determine accrual in any specific case.
Practical checklist for SOL timing
Before using DocketMath, gather:
- The contract document and the relevant written terms
- The date of the alleged breach (or the date performance was due and not performed)
- The date you have reason to believe the claim accrued (often tied to breach and when damages were or could reasonably be identified)
- Any important dates for demands, negotiations, or partial performance (useful for timing context)
Key exceptions
Alaska’s 2-year default SOL for written contracts (via AS § 12.10.010(b)(2)) can be affected by doctrines that either delay the clock or prevent a defendant from relying on the SOL in that scenario.
Because these issues can depend heavily on facts and procedural posture, treat the following as a spotting guide, not a determination. There are several categories that commonly matter in SOL disputes:
1) Tolling (pausing or extending time)
Some circumstances can pause the limitations period. Tolling may depend on recognized legal or factual events recognized under Alaska law (or related procedural doctrines).
In practice, tolling questions often turn on things like:
- whether the plaintiff could reasonably bring the claim,
- whether the defendant’s conduct affected timing, and
- whether Alaska law recognizes tolling under those specific circumstances.
2) Accrual rules (when the clock starts)
Even when the SOL length is fixed at 2 years, the start date can shift. Contract claims frequently focus on when the breach occurred and when damages were (or could reasonably be) identified.
3) Multiple obligations / installment-type breaches
If the written contract calls for performance in installments or has multiple payment triggers, there can be multiple relevant breach dates. In those situations, the SOL may apply separately to each missed obligation (depending on the contract structure and the claim’s theory).
4) Filing and procedural timing
The SOL is a deadline to bring the action, but “bring” can interact with Alaska procedural timing (like filing and service concepts). Don’t wait until the last day—build buffer time so you’re not relying on last-minute procedural steps.
Warning: Missing the SOL deadline can be fatal to a claim, even when the underlying contract dispute may have merit. Consider aiming for filing well before the computed deadline.
Statute citation
Alaska Statutes § 12.10.010(b)(2) sets the general/default SOL period of 2 years for actions falling within the statute’s category framework, including many written contract enforcement scenarios.
Quick reference checklist:
- Jurisdiction: Alaska
- Claim type (scope here): written contract (general/default rule)
- SOL length: 2 years
- Statute: AS § 12.10.010(b)(2)
Use the calculator
Use DocketMath’s statute-of-limitations calculator to translate the 2-year rule into a specific deadline based on your timeline.
Primary CTA: /tools/statute-of-limitations
Inputs that typically affect the output
When you use DocketMath, you’ll generally provide:
- Start date / accrual date (the date you believe the clock starts)
- Jurisdiction: US-AK
- Time period category: written contract under Alaska’s general/default 2-year rule (tied to AS § 12.10.010(b)(2))
How outputs change when inputs change
- If your accrual date moves later (for example, you identify the breach date more precisely), the SOL deadline moves later accordingly.
- If your accrual date moves earlier, the SOL deadline moves earlier.
- The calculator generally applies the 2-year duration consistently; it can’t automatically determine whether tolling/exception doctrines apply without you providing the underlying facts (and without additional legal analysis).
Practical workflow
- Confirm the breach/payment due date under the contract.
- Choose a defensible accrual date for the written-contract cause of action.
- Run the calculation in DocketMath.
- Add a buffer before the deadline to account for filing and scheduling realities.
- If tolling/exception facts seem relevant, review them separately—then consider whether a deeper procedural/legal check is needed.
If your dispute involves multiple breaches (e.g., installments), run separate calculations for each relevant breach date so deadlines don’t get mixed together.
Gentle reminder: This is general information and planning support, not legal advice.
Related reading
- Choosing the right statute of limitations tool for Vermont — How to choose the right calculator
- Statute of limitations in Singapore: how to estimate the deadline — Full how-to guide with jurisdiction-specific rules
- Choosing the right statute of limitations tool for Connecticut — How to choose the right calculator
