Statute of Limitations for Institutional Liability for Abuse in Arizona

5 min read

Published March 22, 2026 • By DocketMath Team

Overview

In Arizona, claims tied to abuse that involve an institution (for example, allegations against an entity operating a facility or program) often trigger questions about the statute of limitations (SOL)—the deadline to file a lawsuit after the abuse occurred.

This article focuses on the general/default SOL applicable to “institutional liability for abuse” in Arizona when no claim-type-specific SOL rule is identified. Per the jurisdiction data provided for this topic, the default limitations period is 2 years, and the general SOL statute is:

  • A.R.S. § 13-107(A) (general rule referenced in the provided jurisdiction data)

Note: This is a reference guide, not legal advice. Laws can turn on the exact cause of action and procedural posture (civil vs. criminal theories, named parties, and the specific facts alleged). If you are building a filing timeline, treat this as a starting point and confirm it against the specific claim you intend to bring.

For practical planning, you generally want two things:

  1. The starting date (often tied to when the injury accrued or was discovered, depending on the claim structure).
  2. The deadline date (starting date + SOL period, plus any exceptions or tolling).

DocketMath’s statute-of-limitations calculator helps you model those timelines quickly.

Limitation period

Default rule: 2 years (general SOL)

For purposes of this topic, the applicable default limitations period is:

  • 2 years

The provided jurisdiction data also states that no claim-type-specific sub-rule was found. That means the 2-year period is the general/default period, not a specialized period for a particular category of abuse-related claim.

In other words, if the case you’re evaluating doesn’t match a more specific SOL rule, you would typically apply the general 2-year SOL as the baseline.

How the calculator output changes with different inputs

DocketMath’s SOL calculator is designed to reflect the basic math behind limitations timelines. The key inputs you’ll provide (directly or via guided fields) typically affect the result in these ways:

  • Alleged date of abuse (or accrual/discovery date, depending on what you enter):
    • Earlier dates push the deadline earlier.
    • Later dates push the deadline later.
  • Tolling dates (if you model them):
    • Tolling generally pauses the running of the clock.
    • Starting the clock later extends the deadline.
  • Choice of “event date” to use as the start:
    • If you use a first injury date vs. a later discovery date, the computed deadline will shift accordingly.

Because the SOL “starting point” can vary depending on the theory and facts, be consistent with what date you enter into the calculator. If your team documents “event date” and “discovery date” separately, run two scenarios so you can compare outcomes.

Quick baseline timeline example (math model)

Assume you use a single event date as the clock start:

  • Event date: January 15, 2021
  • Default SOL period: 2 years
  • Baseline filing deadline: January 15, 2023

If you later determine a different event/discovery date should be used (or you add tolling), DocketMath will update the deadline accordingly.

Key exceptions

Arizona SOL deadlines can be affected by exceptions such as tolling or other doctrines that can pause, delay, or otherwise alter when the limitations clock starts or ends. At the drafting level, those exceptions typically fall into two categories:

  1. Tolling/pauses
    The clock may stop running for a period due to defined circumstances.
  2. Different accrual triggers
    The “clock start date” may depend on when a claim is considered to have accrued or when a qualifying discovery occurred.

Because this page is intentionally grounded in the provided jurisdiction data (which specifies no claim-type-specific sub-rule was found), this section focuses on how exceptions typically function, rather than claiming a particular exception applies automatically to every abuse-institution scenario.

Practical checklist for spotting exception issues

Use this checklist to determine whether you should model an exception in DocketMath (and document it):

Warning: Exceptions often depend on the specific legal theory and the exact facts alleged. Modeling a tolling period in a calculator without a defensible legal basis can create a misleading “safe deadline.” Use the calculator to structure scenarios, then validate the exception applicability with the claim’s legal elements and governing rules.

Statute citation

The jurisdiction data provided for this topic lists the following general/default statute and period:

Keep in mind the structure of limitations citations:

  • The statute tells you the rule.
  • The facts determine how the rule applies (especially on the clock start date and whether any exceptions/tolling doctrines apply).

Use the calculator

DocketMath’s statute-of-limitations calculator is the fastest way to translate the Arizona 2-year default into a usable deadline.

Suggested inputs (how to model timelines)

When you run the calculator, consider entering:

  • Clock start date (pick the date that your analysis uses for accrual/discovery/event)
  • SOL duration (use 2 years for the default rule)
  • Any tolling periods (if you are modeling a paused clock and you have specific dates)

How outputs work

The calculator will compute:

  • Baseline deadline: start date + 2 years
  • Adjusted deadline (if tolling/discovery inputs are used): baseline deadline shifted by the modeled changes

What to do with multiple scenarios

If you have more than one plausible starting date (for example, “date of first abuse” vs. “date reported/discovered”), run both:

  • Scenario A: start at earlier date
  • Scenario B: start at later date

This gives your team a practical range for deadline planning and helps identify whether timeline risk exists.

To generate your deadline now, use the DocketMath tool here: /tools/statute-of-limitations.

Related reading