Damages Allocation reference snapshot for Arizona

Rule or statute summary

Run this scenario in DocketMath using the Damages Allocation calculator.

For Arizona damages-allocation workflows, the key time-based reference point is the statute of limitations (SOL) default that your process can use when no claim-type-specific limitations period is identified.

In DocketMath, the “reference snapshot” approach means the tool uses a jurisdiction-aware default when it does not find a claim-specific SOL sub-rule in the provided rule set.

Arizona (US-AZ) default SOL used in this snapshot

• 2 years — general/default SOL period
• Statute referenced: **A.R.S. § 13-107(A)

Important limitation on what this snapshot does (and does not) cover

No claim-type-specific sub-rule was found for this snapshot. That means this page treats the 2-year default as the operative timing reference unless your matter-specific law setup (or your own jurisdiction research) indicates a different limitations period applies to the specific cause of action.

How SOL reference affects a damages allocation snapshot

SOL references typically drive your allocation in practical, “date-driven” ways, such as:

• Time-bar filtering: which portions of claimed damages fall within the limitations window versus outside it.
• Lookback/look-window behavior: the tool may allocate damages based on a cutoff date derived from the filing date and SOL length.
• Input sensitivity: the key inputs (especially dates) determine which dated damage entries qualify.

Citations

• A.R.S. § 13-107(A) — general SOL period of 2 years (as used by this Arizona snapshot)
  Source (jurisdiction reference): https://www.findlaw.com/state/arizona-law/arizona-criminal-statute-of-limitations-laws.html?utm_source=openai

Caution / verification check: A.R.S. § 13-107 appears within Arizona’s criminal code. If your damages allocation relates to a civil claim type, confirm that A.R.S. § 13-107(A) is actually the governing limitations statute for your cause of action. This snapshot follows the provided jurisdiction dataset and does not independently confirm claim-type applicability.

Use the calculator

Run a damages allocation reference in DocketMath here: /tools/damages-allocation

Run the Damages Allocation calculation in DocketMath, then save the output so it can be audited later: Open the calculator.

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

Step 1: Confirm the SOL default assumption

Because no claim-type-specific limitations sub-rule was identified, DocketMath applies this snapshot’s 2-year default SOL reference for US-AZ.

If your workflow includes a claim-type-specific override later, the cutoff logic may change—so document which SOL rule you used.

Step 2: Enter dates that anchor the time window

SOL-based allocation is typically driven by comparing:

• your filing date (or the “case initiation” date your workflow uses as the start point), and
• the event/accrual-related date(s) you attach to each damages amount.

Which input to change first: if you need to test timing sensitivity, change the filing date before other dates, because it often shifts the SOL “cutoff” used to decide what falls inside vs. outside the window.

Step 3: Provide damages tied to each date

A common pattern is to attach each damages line item to a specific event date:

Practical tip: The tool generally needs date + amount pairs. If you enter damages without an associated date, you may not get a reliable SOL-based inclusion/exclusion split.

Step 4: Interpret the output allocation clearly

When DocketMath returns an allocation split (for example, “within SOL” vs. “outside SOL”), your output notes should reflect:

• SOL length used: 2 years
• Statute referenced in this snapshot: **A.R.S. § 13-107(A)
• Why no alternative was used: no claim-type-specific sub-rule was found in the provided jurisdiction dataset

Quick scenario checks (how outputs change)

Use these as sanity checks while you adjust inputs:

• Move filing date forward by 1 year: earlier-dated damages may fall outside the 2-year window.
• Move event dates later: more damages may fall within the 2-year window.
• Add additional dated damage entries: totals in the “within SOL” bucket may increase because more entries qualify.

If you need to sanity-check other parts of your workflow before allocation, revisit the same tool entry point: /tools/damages-allocation.

Related reading

• Damages Allocation Guide for Alabama — Comparative Fault Rules
• Damages Allocation Guide for Alaska — Comparative Fault Rules
• Damages Allocation Guide for American Samoa — Comparative Fault Rules