Statute of Limitations for State Tort Claims Act — Filing Deadline in Arizona

7 min read

Published March 22, 2026 • By DocketMath Team

This article is for informational purposes only and does not constitute legal advice. Laws change frequently — verify all citations with current official sources.

Overview

Run this scenario in DocketMath using the Statute Of Limitations calculator.

Arizona’s deadline for bringing certain tort-related claims against the state is driven by the state’s general statute of limitations and any specific procedural requirements that apply to the type of claim. For most routine tort filing questions, the practical starting point is the general 2-year limitation period.

Per your jurisdiction data, there is no claim-type-specific sub-rule identified for this summary. That means the guidance below treats the period as the general/default rule rather than a specialized exception for a particular tort category.

Note: This page focuses on the timing (the “when to file” question). It does not cover every possible prerequisite to suing the state, which can include notice or administrative steps depending on the claim facts.

If you’re working with a deadline, DocketMath’s statute-of-limitations calculator can help you translate a known event date (like the date of injury or alleged wrongdoing) into a filing deadline you can calendar. For the tool, use: /tools/statute-of-limitations.

Limitation period

General rule (default)

General SOL period: 2 years
Default length: 2 years from the relevant triggering date
No claim-type-specific sub-rule identified in the provided jurisdiction data for tort claims under the State Tort Claims Act context—so the 2-year rule is treated as the general/default period here.

What the “triggering date” usually is

For timing tools, you typically need to choose the date that starts the clock. Common triggering dates in tort litigation include:

the date of the injury, or
the date the harm occurred, or
the date of the wrongful act that caused the injury.

Because tort statutes can be sensitive to the precise fact pattern, DocketMath is designed so you can plug in the date most consistent with your case timeline and then see the resulting deadline.

Practical filing calendar workflow

Use this workflow to reduce deadline risk:

☐ Identify the most defensible “start date” (injury date vs. wrongful-act date)
☐ Enter that date into DocketMath
☐ Confirm the output calendar date
☐ Add a buffer for gathering documents and drafting filings (many teams use 30–60 days as an internal buffer, even when the statute allows less)
☐ Re-check the date if new facts shift the triggering event

Pitfall: People often enter the date they first noticed harm instead of the date the harm occurred. If the statute starts on the earlier event date, filing “on time” by the later date can still be late.

Key exceptions

Arizona’s statutes and related doctrines can affect when the countdown begins, pauses, or—rarely—extends. While your brief specifies a general/default 2-year period, exceptions can still matter in practice. Below are the main categories you should evaluate when calculating a deadline.

1) When the clock starts vs. when the harm is discovered

Some claims involve a discovery concept—meaning the operative date may not be the first moment you become aware of every consequence. Your case may require careful alignment of:

the date harm occurred, and
the date it became reasonably knowable (depending on the claim theory and applicable doctrine).

DocketMath can’t decide legal doctrine on your behalf, but it can show how the deadline changes when you select different plausible trigger dates.

2) Tolling (pauses) for specific statutory reasons

Tolling can extend deadlines. Common tolling frameworks in civil law may include events like:

certain disability conditions,
legally recognized delays,
or other circumstances that prevent a claim from being brought within the normal time window.

Because tolling depends heavily on facts and the specific statutory framework, treat it as a separate checklist item rather than something you assume automatically.

3) Procedural prerequisites (deadline traps)

Even if the “limitations period” is 2 years, some claims require extra steps (for example, notice procedures) before a lawsuit is filed. Missing those steps can create dismissal risk that looks like a time-bar.

This is why your timeline review should cover two tracks:

☐ Statute of limitations date (calendar filing deadline)
☐ Any prerequisite deadlines that must be satisfied before filing

Warning: A lawsuit might be filed before the SOL expires, but still fail if a required prerequisite step was missed or performed late. Track both timelines.

4) Multiple events (last-injury vs. continuing harm)

Where harm occurs across multiple dates (for example, repeated conduct or a worsening injury), the “start date” can become contested. DocketMath helps by showing how different start dates affect the end date.

Consider maintaining a short table of candidate trigger dates before you calculate:

☐ Date A: first injury-related event
☐ Date B: last event in the sequence
☐ Date C: date symptoms worsened or were formally diagnosed

Then calculate each and compare.

Statute citation

The general Arizona statute of limitations referenced for this summary is:

A.R.S. § 13-107(A) — provides a 2-year general limitation period for relevant offenses and supplies the general/default 2-year period used here for tort timing questions based on your jurisdiction data.

Your jurisdiction brief indicates:

General SOL Period: 2 years
General Statute: **A.R.S. § 13-107(A)
No claim-type-specific sub-rule was found, so this page applies the general/default period.

If you want the raw statutory language for context, you can cross-check your internal matter file against the statute text.

Use the calculator

DocketMath’s statute-of-limitations calculator helps you convert dates into a filing deadline with fewer calendar errors.

Inputs to enter in DocketMath

Jurisdiction: US-AZ (Arizona)
Statute framework: the general/default 2-year period used in this summary
Triggering date: select the date that starts the clock in your fact timeline (commonly injury date or wrongful-act date)

Output to interpret

After you enter your triggering date, DocketMath generates:

the end date of the limitations period (the last day you typically can file based on the SOL calendar)

How the output changes

To see sensitivity to the triggering date, run multiple scenarios:

Scenario	Triggering date entered	Resulting deadline behavior
Early start	Earlier injury/wrongful-act date	Deadline moves earlier
Later start	Later worsening/last-event date	Deadline moves later
Administrative delay	Date you completed prerequisites	SOL deadline still depends on the statute trigger; prerequisite deadlines may be separate

Even when the rule is “2 years,” the deadline can shift significantly depending on the date you choose as the start.

Suggested use checklist

☐ Run 2–3 plausible start-date scenarios
☐ Pick the scenario that best matches your strongest factual record
☐ Calendar filings using your chosen deadline plus a buffer
☐ Re-validate if new dates emerge (e.g., new documentation showing earlier injury)

For direct access to the tool, use this primary CTA: /tools/statute-of-limitations.

Sources and references

Start with the primary authority for Arizona and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

A.R.S. § 12-541