Deadline Calculator Guide for Arizona

What this calculator does

DocketMath’s Deadline Calculator (Arizona) is designed to compute key time limits using Arizona’s criminal statutes of limitations framework—so you can focus on dates and deadlines instead of manual counting.

In Arizona, the baseline criminal statute of limitations is set by A.R.S. § 13-107(A), which provides a 2-year limitation period in the general case (with listed exceptions that can create longer periods for certain circumstances). Your calculator uses the following jurisdiction data:

Because this guide is meant to be practical and date-focused (not legal advice), think of the calculator as a structured way to run date math based on the limitation period you select.

If you want to run the numbers right away, open the tool here: /tools/deadline.

When to use it

You’ll get the most value from the DocketMath deadline calculator when you’re dealing with a known set of dates and you want to estimate the end of a limitation window.

Use it for situations like:

• You know the alleged offense date (or the date conduct ended) and you need to determine the latest filing window under the limitations period.
• You’re comparing:

  • an investigation timeline,
  • a charging date, and
  • the limitation cutoff date produced by the calculator.
• You need to understand how switching the selected period (2 years vs. 3 years) changes the cutoff.

Inputs you should gather before you calculate

To use the tool effectively, collect:

• Date of offense / conduct date
  The date the underlying conduct occurred (or the relevant date tied to your limitation rule selection).
• Which limitations period applies (2-year or 3-year)
  Select based on the exception category you’re working with (your calculator’s O2/P3 settings).
• (Optional) Filing/charging date to test
  If you have it, you can check whether it falls before or after the computed cutoff.

What the output can—and can’t—tell you

The calculator returns a computed deadline date based on the limitations period chosen. It does not replace the need to confirm:

• the exact statutory subsection that governs the offense category,
• whether an exception truly applies, and
• how Arizona’s limitation rules are applied to the specific procedural posture.

Step-by-step example

Below is a concrete walkthrough showing how DocketMath’s deadline math changes when the limitation period changes between A.R.S. § 13-107(A) (2 years) and the 3-year exception.

Scenario

• Alleged offense occurred: January 15, 2024
• You want the “deadline” date using Arizona’s statute of limitations approach:

  • Option 1: 2 years under **A.R.S. § 13-107(A)
  • Option 2: 3 years under A.R.S. § 13-107 (exception P3)

Step 1: Start in the tool

Open /tools/deadline and select Arizona (US-AZ).

Step 2: Enter the offense/conduct date

Enter:

• Offense date: January 15, 2024

Step 3: Select the limitations period

Choose one:

• 2-year mode tied to A.R.S. § 13-107(A) (general limitation period; your ruleset also references exception O2 under this 2-year umbrella), OR
• 3-year mode tied to A.R.S. § 13-107 (exception P3)

Step 4: Read the computed deadline

Now compare the results:

Step 5: (Optional) Test a charging date against the cutoff

If you also enter a charging date (for example, March 1, 2026), the tool can help you quickly see:

• March 1, 2026 is after the 2-year cutoff (Jan 15, 2026)
• March 1, 2026 is before the 3-year cutoff (Jan 15, 2027)

This comparison is useful when you’re trying to determine whether time has run past the relevant limitation window—without doing manual date conversions.

Common scenarios

Different fact patterns lead people to use the calculator in different ways. Here are several common scenarios you can model.

1) You have a single offense date and want the cutoff

Best fit for: Straightforward calculations.
Inputs:

• Offense date: known
• Choose 2-year (A.R.S. § 13-107(A)) or 3-year (exception P3) as applicable
• Optional: charging date

Output use: Decide whether a later event date occurs before or after the calculated cutoff.

2) You’re comparing two possible exception settings

Best fit for: When you’re unsure whether a 2-year or 3-year window is relevant under A.R.S. § 13-107.
Action:

• Run the tool twice:

  • once under 2-year mode tied to **A.R.S. § 13-107(A)
  • once under 3-year mode tied to A.R.S. § 13-107 (exception P3)

Why it helps: You’ll immediately see how the cutoff shifts by exactly 1 year in this ruleset.

3) The offense date is near a calendar transition

Best fit for: When accuracy depends on day-level math.
Examples:

• conduct begins on December 31
• conduct ends on January 1
• charging occurs on a leap-year-adjacent date

In these cases:

• enter the date exactly as you have it,
• run both the 2-year and 3-year modes if your exception selection is uncertain,
• and treat the cutoff as a day-level benchmark.

4) You’re reverse-checking: “When could they still file?”

Best fit for: You know the filing/charging date and want to estimate whether it could still be within the limitations window.
Action:

• Enter the offense date
• Compare the charging date to the computed deadline

If the charging date is after the computed cutoff, the calculation flags a potential timeliness issue. If it’s before, the calculator suggests the filing occurred within the selected limitations window.

Tips for accuracy

You’ll get better results from DocketMath when you treat it like a precision date tool rather than a rough estimator.

Confirm which date you should use

Before running the tool, clarify internally:

• Is the relevant date the date the offense occurred, or the date the conduct ended, or another event date tied to the limitations framework?
• If your record shows a date range, decide which exact date you are using for the calculator run.

Then, keep that choice consistent across all scenarios.

Always run the correct limitations period

Because Arizona’s baseline is 2 years under A.R.S. § 13-107(A), the calculator depends heavily on whether you select:

• 2-year mode under A.R.S. § 13-107(A), or
• 3-year mode under A.R.S. § 13-107 (exception P3)

A quick self-check list:

Don’t mix “computed deadline” with “event deadlines” that belong to other rules

Your statute of limitations cutoff is not the same as:

• internal agency deadlines,
• service deadlines,
• discovery deadlines,
• or court scheduling deadlines.

The DocketMath calculator focuses specifically on the limitations window used for deadline math based on the provided Arizona statute citations.

Use multiple runs to sanity-check results

If the calculator output seems surprising, try:

• running again with the same date but switching between 2-year and 3-year modes
• checking that the date format you entered is consistent (e.g., no accidental month/day swap)

Keep an audit trail of your inputs

For each run, record:

• offense date entered
• limitations period selected (2-year or 3-year)
• charging date (if used)

This lets you reproduce the result and explain the difference between two scenarios.

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-2101

Related reading

• Why deadlines results differ in Canada — Troubleshooting when results differ
• Worked example: deadlines in New York — Worked example with real statute citations
• Deadlines reference snapshot for New Hampshire — Rule summary with authoritative citations