Public Records Fee Calculator Guide for Arizona
7 min read
Published March 22, 2026 • By DocketMath Team
What this calculator does
DocketMath’s Public Records Fee Calculator for Arizona (US-AZ) helps you estimate the fees tied to a public records request by translating your request details into a consistent fee calculation output.
Because public records fee rules can depend on what’s being requested and how the agency handles the request (for example, search, review, duplication, and transmission), calculators are most useful when you enter details that match the way the public body will actually process your request.
This guide walks you through:
- Which inputs to enter into the DocketMath calculator
- How changes to your inputs affect the estimated output
- A fully worked example you can mirror with your own request
- Common scenarios Arizona requesters run into (without turning the discussion into legal advice)
Note: This guide focuses on fee-estimation workflow and Arizona’s general statute of limitations context. It does not claim that any particular fee rule applies to every record type, agency, or request method.
When to use it
Use DocketMath’s Public Records Fee Calculator when you want to estimate your costs before you submit or while you’re refining a request.
Good times to use the calculator include:
- You’re assembling a request and you want to narrow the scope (for example, “all emails from January 10–20” instead of “all emails”).
- You’re requesting electronically stored information and you want to understand how changing delivery format can alter duplication/transmission assumptions.
- You’re preparing for back-and-forth with an agency (clarifying time ranges, narrowing custodians, or requesting a subset).
- You’re comparing a broad request vs. a targeted request to reduce estimated fees.
Statute of limitations context (separate from fees)
Some users bundle fee questions with timing questions—especially when they’re trying to decide how long they have to take action after a denial or delay. Arizona’s general statute of limitations is:
- 2 years for the general/default category
- Referenced in general terms via A.R.S. § 13-107(A) (Arizona criminal statute of limitations framework)
The general/default rule is what your timeline questions should start with when no claim-type-specific sub-rule is identified.
Warning: Fee estimation and deadline calculation are different problems. Even when timing matters, using A.R.S. § 13-107(A) as the basis for a “2-year” deadline does not automatically determine whether a specific pathway applies to your situation. This guide does not provide legal advice.
Step-by-step example
Below is a practical walkthrough using the DocketMath public-records-fee calculator pattern. Even if your exact agency’s fee worksheet differs, the steps show you how to enter inputs and interpret changes.
Example request (Arizona)
You want records from a city office:
- Time range: January 10–January 20 (11 calendar days)
- Record type: Emails (you specify subject keywords)
- Custodians: 2 staff members
- Estimated pages/emails: ~150 emails total (assume ~600 pages after attachments/formatting)
- Delivery: Electronic download (e.g., spreadsheet/CSV export or PDF batches)
- Copy/duplication assumption: You’ll likely receive a mix of PDFs and exports
Step 1: Enter your scope inputs
In the DocketMath calculator:
- Set Time range to 11 days
- Set Number of custodians to 2
- Set Estimated records volume to 150 emails
- Set Estimated duplication/page count to 600 pages (or the closest approximation you can support)
Step 2: Enter retrieval/handling assumptions
Next, capture the operational part of the request:
- Choose an assumption for search/review effort that matches how narrow or broad your request is.
- If you include keywords and specific subject lines, your “effort factor” is usually lower than a “search everything” request.
- If you can predict that attachments will be involved, include that in your page count estimate.
Step 3: Enter delivery/format
Finally, set delivery:
- Electronic delivery generally reduces traditional “paper copies,” but it may still involve formatting/export work.
- If you know the agency will scan or print, your duplication/pages estimate should reflect that.
Step 4: Read the calculator output
When you submit the inputs, you’ll get a numeric output—typically an estimated total fee and sometimes a breakdown (for example, search vs. review vs. duplication).
Use the output strategically:
- If the total looks too high, reduce variables you control:
- Narrow the time range
- Reduce custodians
- Replace “all emails” with keyword-limited phrasing
- Ask for a smaller subset first
Step 5: Adjust one variable at a time
To make the calculator useful for decision-making, change only one input per iteration. Example:
- Reduce time range from 11 days → 5 days
- Keep all other estimates constant
- Compare the new total vs. the old total
This makes it clear which lever is most effective for lowering estimated costs in your scenario.
Common scenarios
Arizona public records requesters often face predictable patterns. Below are common scenarios and how to apply the calculator effectively—without assuming one fee rule automatically fits all requests.
Scenario A: Broad request with many custodians
Problem pattern: “All emails from every employee” across months.
Calculator approach:
- Enter a higher number of custodians
- Use a longer time range
- Inflate estimated volume only when you have a basis (otherwise, you may over-budget)
What to do next:
- Use the calculator output to decide whether you should narrow the scope first.
- A targeted request often reduces total effort assumptions dramatically.
Scenario B: Short time window but high attachment volume
Problem pattern: A short period (e.g., 3 days), but lots of attachments.
Calculator approach:
- Set time range short
- Keep custodians moderate
- Increase estimated duplication/pages to reflect attachments
Result you’ll likely see:
- The duplication component rises even when the date range is small.
Scenario C: Electronic records but complex formatting
Problem pattern: You want data in a format requiring export or reformatting (e.g., logs spread across multiple files).
Calculator approach:
- Set delivery format to electronic
- Adjust the retrieval/review effort assumption upward if the request requires significant consolidation
Practical takeaway:
- Even “digital” doesn’t always mean “no processing.” Your estimate should mirror the agency’s workload.
Scenario D: Denial, delay, or non-response timing questions
Fee calculators don’t solve timing. If your question is “How long do I have after an agency action?”, you may need Arizona’s general limitations framework:
- 2-year general/default period referenced through A.R.S. § 13-107(A) (general framework)
- No claim-type-specific sub-rule was identified in the provided jurisdiction data, so the general/default period is the clear starting point.
Pitfall: People sometimes try to combine fee disputes with deadline calculations using the same assumptions. Fees are about access costs; limitations are about timelines. Treat them separately in your workflow.
Tips for accuracy
Better inputs lead to better estimates. Use these checklist-style tips before you finalize numbers in the DocketMath calculator.
Accuracy checklist
- Confirm the date range precisely (use the actual start and end dates you’re requesting)
- Count custodians intentionally
- If “multiple departments” are involved, estimate realistically rather than using a vague number
- Estimate volume using a defensible method
- Example: “I reviewed 20 emails and averaged 4 pages each → 150 emails ≈ 600 pages”
- Reflect attachments in duplication/page count when applicable
- Choose delivery/format that matches your request wording
- If you ask for “PDFs,” the duplication assumption may differ from “CSV export”
- Run “what-if” iterations
- Test: reduce time range, reduce custodians, or narrow keywords
Use a “scope-reduction loop”
If the first estimate is too high:
- Narrow your time range (e.g., halve the days)
- Reduce custodians (target specific roles)
- Add keywords/filters
- Recalculate and compare totals
This loop often finds a cost-effective scope without abandoning the request.
Keep limitations context straight
If you’re also tracking deadlines for potential legal action, anchor timeline thinking to the general rule you have:
- General/default limitation period: 2 years
- Reference point: A.R.S. § 13-107(A)
Remember: the limitations citation is part of the Arizona timeline framework; it doesn’t automatically validate which fee rule an agency must apply.
Related reading
- Public Records Fee Calculator Guide for Alabama — Complete guide
- Public Records Fee Calculator Guide for California — Complete guide
- Public Records Fee Calculator Guide for Colorado — Complete guide
