Tolling the statute of limitations in Arizona

Tolling the statute of limitations in Arizona

6 min read

Published April 7, 2026 • Updated April 23, 2026 • By DocketMath Team

Article claim inventory in progress

Trust release 4

This page has legal or numeric text that still needs claim-level inventory before we can treat it as verified.

Direct answer

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

In Arizona, the general criminal statute of limitations is 2 years under A.R.S. § 13-107(A) (this is the default/general rule for the purposes of this guide). DocketMath’s statute-of-limitations calculator can help you model how that 2-year clock runs and how selected tolling inputs may affect the computed end date using jurisdiction-aware rules for US-AZ.

Note: This is an educational walkthrough about how to compute dates with DocketMath and how “tolling” is modeled in timelines. It’s not legal advice, and it doesn’t replace review of the specific charging theory and case facts.

What you need to know

Arizona’s baseline SOL (no claim-type-specific override found)

For this tutorial, the default/general limitations period is: 2 years. That starting point comes from:

  • General SOL Period (default): 2 years
  • General Statute: **A.R.S. § 13-107(A)

No claim-type-specific sub-rule was identified in the provided dataset, so this guide treats A.R.S. § 13-107(A) as the baseline limitations window.

“Tolling” changes the calculated expiration date

“Tolling” generally means the limitations clock is paused, interrupted, or treated differently for timing purposes during a relevant period. Practically, that typically affects the computed last permissible filing date (the end of the limitations window), not the original event/trigger date.

A useful timeline mindset:

  • Trigger/accrual date (when the clock starts, depending on the modeled scenario)
  • Baseline period (2 years)
  • Tolling event(s) (a doctrine-specific pause/interruption window)
  • New computed expiration/end date based on the baseline plus/minus tolling effects

Inputs matter more than the label “tolling”

Two scenarios can both involve “tolling,” but produce different results because DocketMath will respond to your inputs, such as:

  • The exact trigger date you enter
  • The start and end dates of the tolling window (if applicable)
  • How the selected tolling option is modeled (e.g., pause vs. interruption)

So, your result is only as good as the dates and options you select.

Step-by-step

Below is a practical workflow for using DocketMath to calculate Arizona SOL timing with tolling.

1) Identify your jurisdiction and open the calculator

  • Open DocketMath’s calculator here: /tools/statute-of-limitations
  • Confirm jurisdiction selection: **US-AZ (Arizona)

This tells DocketMath to apply Arizona’s baseline SOL rule (starting from A.R.S. § 13-107(A)).

2) Enter the trigger date (the clock start)

Decide what date best matches your scenario and the tool’s expected input. Commonly, it’s the event date (for example, the offense date in a criminal timing model).

Tip: If your tolling depends on something that happens after the trigger, the trigger date usually has the biggest impact on the computed end date.

3) Ensure the baseline SOL is the Arizona general rule

For this guide’s scope, the baseline is:

  • 2 years under **A.R.S. § 13-107(A)

If you’re dealing with a special rule not covered by your dataset, the tool may require additional selections or may not fully reflect an override. In that case, cross-check the tool’s selections against the governing theory for your situation.

4) Enter tolling event details (and the window, if any)

Use DocketMath’s tolling inputs to apply the tolling doctrine you’re modeling. The output should change based on:

  • Whether you apply a tolling event at all
  • The tolling start date
  • The tolling end date (if the tool uses a window rather than a single date)

How the end date shifts depends on whether the tool models tolling as a pause or interruption for the selected option.

5) Review the computed expiration / last filing date

DocketMath will generate an end date based on:

  • Trigger date
  • Baseline period (2 years)
  • Selected tolling adjustments

Make sure the output aligns with the timeline summary shown in the tool (if it provides one).

6) Run a “no tolling” comparison

Before trusting the tolling-adjusted date, run at least two scenarios:

  • Scenario A: baseline only (no tolling selected)
  • Scenario B: baseline plus tolling (with your best date estimates)

The difference between the two outputs shows the practical effect of your tolling inputs.

Key statutes and citations

Default limitations period used in this walkthrough

  • A.R.S. § 13-107(A)General SOL: 2 years

As noted in the brief for this guide, no claim-type-specific sub-rule was found in the provided dataset. Therefore, A.R.S. § 13-107(A) is used as the default/general period.

How to document your calculation choices

When you record your inputs and outputs (for internal notes, timelines, or case management), link each key number to its basis:

  • “Baseline SOL = 2 years under A.R.S. § 13-107(A)
  • “Trigger date entered = [date]”
  • “Tolling applied = [event], dates = [start–end]”

Caution: Many timing mistakes come from an incorrect trigger date or mis-specified tolling window boundaries. Even a one-day difference can shift the computed deadline.

Common pitfalls

  • Using the wrong baseline period

    • If you forget the general rule and assume a different SOL, everything will shift.
    • For this guide: baseline is 2 years under A.R.S. § 13-107(A).
  • Swapping tolling start and end dates

    • If the tolling end date is earlier than the start date (even accidentally), results can be wrong or confusing.
  • Selecting tolling that doesn’t cover the period you’re measuring

    • Tolling typically affects the limitations clock only during the relevant timeframe.
    • Make sure the tolling window you enter matches the facts you’re modeling.
  • Assuming every tolling doctrine “pauses time”

    • Some doctrines function as a pause, others as an interruption, and the tool’s modeling approach matters.
    • Let the tool’s option choices control the method used in the computation.
  • Skipping the no-tolling baseline run

    • Without Scenario A (no tolling), it’s harder to detect whether a tolling selection is producing an unintended result.
  • Not recording why each date was chosen

    • Even if the math is correct, undocumented assumptions are hard to verify later.

Run the numbers

Use this checklist to structure your DocketMath inputs and interpret the output.

Suggested workflow

What output changes when tolling is applied?

In models where tolling behaves like a pause, the end date often moves by approximately the amount of time attributed to the tolled period.

For example (conceptually):

  • Baseline expiration = trigger date + 2 years
  • Adjusted expiration = baseline expiration + (added/credited time based on the tolled window)

To quantify precisely with your selected inputs:

  • Run the tool twice (with and without tolling)
  • Note the difference between the computed end dates

Reminder: Treat the tool’s date as a calculation based on your inputs and the tool’s modeled assumptions—not a definitive legal conclusion. Validate the assumptions embedded in your selections against your scenario.

Related reading