Worked example: Closing Cost in Arizona

Example inputs

Run this scenario in DocketMath using the Closing Cost calculator.

This worked example shows how DocketMath calculates closing cost in Arizona using jurisdiction-aware rules for the general criminal statute of limitations (SOL) period. It’s designed to help you understand how the tool arrives at a result—not to provide legal advice.

What jurisdiction-aware rule is used here (Arizona)

Arizona’s general SOL for criminal prosecutions is 2 years. The controlling statute cited in this example is:

• A.R.S. § 13-107(A) — generally sets the 2-year limitations period for offenses that do not fall under a different, claim-type-specific sub-rule.

Example scenario (inputs)

To keep the example concrete, let’s assume the following:

• Jurisdiction: Arizona (US-AZ)
• Offense/incident date: January 15, 2024
• Filing date (when the case is initiated): January 20, 2026
• Closing-cost calculator inputs (typical):

  • A time horizon component derived from the date gap between the incident and filing dates
  • General SOL period used: 2 years (from A.R.S. § 13-107(A))

In practice, DocketMath’s closing-cost calculator may also incorporate other cost or case-management assumptions depending on how the calculator is configured. This example focuses on the jurisdiction-aware timing component: whether the filing falls inside the SOL window and how that timing feeds into the closing-cost outcome.

Inputs checklist

Use this checklist to mirror the example inputs:

• Jurisdiction: **Arizona (US-AZ)
• Incident date: January 15, 2024
• Filing date: January 20, 2026
• Apply general SOL = 2 years under A.R.S. § 13-107(A) (no special claim-type sub-rule identified)

Example run

Below is a step-by-step walkthrough of how you would run the closing-cost workflow in DocketMath for this scenario.

Run the Closing Cost calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.

Step 1: Confirm the SOL rule

DocketMath applies the jurisdiction-aware rule for Arizona:

• General SOL period: 2 years
• Authority: **A.R.S. § 13-107(A)
• No claim-type-specific sub-rule identified: the general/default period is used.

So, the tool treats the SOL window as 2 years, measured from the offense/incident date.

Step 2: Compute the SOL deadline (date arithmetic)

• Incident date: Jan 15, 2024
• General SOL period: 2 years
• SOL deadline: Jan 15, 2026 (end of the 2-year window)

Now compare the filing date to that deadline:

• Filing date: Jan 20, 2026
• Deadline: Jan 15, 2026
• Result: filing occurs 5 days after the general 2-year SOL window ends

Step 3: Feed the timing result into the closing-cost calculation

DocketMath’s closing-cost calculator uses this jurisdiction-aware timing classification to determine the closing-cost outcome for the scenario you provide.

Because the filing date is outside the general SOL window (by 5 days), the tool’s logic will treat the case timing as beyond the general 2-year limitations period.

Directional takeaway for this run:

• Outside general SOL window → closing-cost result reflects the “late vs. deadline” SOL timing outcome

Example run summary (what the tool effectively “decides”)

Primary CTA

If you want to reproduce this using the calculator directly, start here:

• /tools/closing-cost

Sensitivity check

Real-world outputs can change when small date inputs change—especially around a deadline.

This section tests how the closing cost result changes when you shift only the filing date, while holding everything else constant (same Arizona rule, same incident date).

Sensitivity test setup

Fixed inputs:

• Jurisdiction: Arizona (US-AZ)
• Incident date: Jan 15, 2024
• SOL rule: 2 years under **A.R.S. § 13-107(A)

Variable input:

• Filing date changes by days relative to the Jan 15, 2026 deadline.

Test cases

What you should expect DocketMath to do

Because the tool is using the general/default SOL period of 2 years (and no claim-type-specific sub-rule is applied), the boundary is effectively determined by:

• Filing date on or before Jan 15, 2026 → inside the general SOL period
• Filing date after Jan 15, 2026 (even by 1 day) → outside the general SOL period

Quick “how to use this” guidance

When running the closing-cost calculator:

• Enter the actual incident/offense date you want the SOL clock to start from.
• Enter the actual case filing/initiating date you want measured against the SOL window.
• For scenario modeling, test at least:

  • the deadline
  • one day before
  • one day after

That approach helps you see whether the closing-cost outcome is stable or brittle around the SOL cutoff.

Related reading

• Average closing costs in Alabama — Rule summary with authoritative citations
• Average closing costs in Alaska — Rule summary with authoritative citations
• Average closing costs in Arkansas — Rule summary with authoritative citations