Why Closing Cost results differ in Arizona
4 min read
Published April 15, 2026 • By DocketMath Team
The top 5 reasons results differ
Run this scenario in DocketMath using the Closing Cost calculator.
If you’re running the DocketMath “closing-cost” calculator for Arizona (US-AZ) and your outputs don’t match what you expected, the differences usually come from inputs and jurisdiction-aware rule handling—not from the tool “changing.” Even small shifts in dates or assumptions can move results.
Below are the top 5 causes we see when people compare results across scenarios in Arizona.
Confusing the default SOL window with a claim-specific window
- Arizona’s general rule for criminal statute of limitations (SOL) is 2 years under A.R.S. § 13-107(A).
- Your brief indicates no claim-type-specific sub-rule was found, so the tool (and your scenario) should treat this as the default period.
- If another workflow used a different period (or a claim-specific override), the closing cost results can diverge even with the same fee inputs.
**Date boundary effects (exact day matters)
- SOL calculations depend on the start and end dates you enter (for example, an event date vs. a filing or milestone date).
- A one-day shift can move a scenario from “within 2 years” to “outside 2 years,” which can change how the scenario is classified—and that can impact the closing cost output.
Jurisdiction mismatch in cross-state scenarios
- DocketMath applies jurisdiction-aware rules.
- If you accidentally use dates or assumptions that were prepared under another state’s workflow, but then run them under US-AZ, the outputs may not align with your expectations.
Mismatched assumptions about which cost components are included
- “Closing cost” models depend on which cost buckets/components you include as inputs.
- If one run includes fewer components (or a different fee schedule basis) while the other run includes more, the totals can differ even when SOL timing is identical.
Premature or delayed “effective” milestone date entry
- Many real-world workflows hinge on a key operational milestone (often acting like an “effective” date), such as a notice date, service date, or similar trigger.
- Entering the wrong milestone date changes the SOL timeline, and depending on your DocketMath setup, that can alter the scenario outcome used by the calculator.
Pitfall: Comparing two screenshots from two runs isn’t the same as comparing the same model. If one run uses the Arizona default 2-year SOL under A.R.S. § 13-107(A) and another run uses a different SOL basis, you’ll see differences even with identical cost inputs.
How to isolate the variable
Use this repeatable diagnostic approach to pinpoint what’s driving the mismatch.
- Freeze the jurisdiction and tool settings so both runs use the same rule set.
- Compare one input at a time (dates, rates, amounts) and re-run after each change.
- Review the breakdown to see which segment or assumption drives the difference.
Step-by-step checklist (repeatable)
Practical “single-variable reruns”
Do three targeted reruns and record each output:
| Rerun | What you change | What you keep fixed | What to look for |
|---|---|---|---|
| 1 | End date only | Everything else | Whether the result classification changes |
| 2 | Start date only | Everything else | Whether timing crosses the 2-year boundary |
| 3 | Fee component inputs only | Both SOL dates fixed | Whether totals change independently of timing |
This approach makes the cause obvious: the mismatch is either driven by SOL timing boundary inputs or by cost-component configuration.
Next steps
Standardize your date definitions
- Write down which real-world milestone maps to your “start date” and “end date.”
- If that mapping varies between runs, your comparisons won’t be apples-to-apples.
Use Arizona’s default SOL consistently
- Arizona’s general SOL is 2 years under A.R.S. § 13-107(A).
- Because no claim-type-specific sub-rule was found, avoid silently switching to other periods in your own process.
Document your DocketMath inputs before comparing
- Capture at minimum:
- jurisdiction (US-AZ)
- SOL start date
- SOL end date
- enabled cost components
Treat unexpected differences as a data-quality signal
- Most discrepancies come from input drift (dates or enabled buckets), not from a “rule conflict.”
Note (not legal advice): This is a diagnostic, informational explanation. If your situation depends on a specific claim type or a special procedural timeline, the default A.R.S. § 13-107(A) assumption may not fully match every real-world pathway.
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
