We've watched clients wait twelve weeks for a 2,500-square-foot house plan to clear review in jurisdictions where the published time frame said thirty days. When the plan examiner finally calls, it's one line item—something that could have been flagged in week one. The project sits. Costs creep. The GC starts asking if we should pull the application and re-file somewhere else.
That pattern just got harder to ignore in Arizona.
Senate Bill 1566 took effect this month, requiring municipalities and counties to set and publish time frames for issuing licenses or building permits for single-family home construction
. And if the jurisdiction crosses the line from slow to deliberately obstructive?
The Attorney General's Office can now impose a $5,000 penalty
What SB 1566 actually does
Municipalities and counties must now establish set time frames for issuing licenses or building permits for home construction
. That's not new in spirit—most Arizona AHJs already publish review timelines. What's new is the enforcement mechanism.
If a municipality or county is found to be intentionally obstructing the approval of licenses or creating delays out of malice, it faces a $5,000 penalty enforced by the Attorney General's Office
. The key word: malice.
"Malice is a very high standard. It has to be intentional," said the bill's sponsor, Senate President Warren Petersen, during a House committee hearing in March
Petersen clarified: "This doesn't happen a lot, but we do hear about anecdotes where people are intentionally delaying projects, there's no reason—there's nothing that's being waited on"
We're not talking about understaffed plan-review teams working through a backlog. We're talking about cases where the delay serves no code-enforcement purpose.
Who this helps (and who it doesn't)
SB 1566 won't speed up a legitimately complex review. If your project triggers floodplain overlay, wildfire interface provisions, and a use permit, the timeline reflects real work. The bill targets something narrower: AHJs that sit on complete applications without issuing corrections, approvals, or denials—and do so for reasons unrelated to code compliance.
Supporters argued that "time is money" and delays add costs and uncertainty, disincentivizing investment in homes
. That's the builder angle. For jurisdictions, the risk is reputational. A $5,000 fine isn't going to bankrupt a city, but an Attorney General finding of malice in permit administration is the kind of thing that gets covered in the local paper.
Several Arizona municipalities opposed the bill, and most Democrats in the House and Senate voted against it
Rep. Quantá Crews (D-Phoenix), who previously worked in the County Assessor's Office, said delays were usually justified: "I have had projects that for properties have taken me months, and not because I was stalling anything. I just wanted to make sure that it was done correctly"
That's fair. The bill isn't designed to punish thoroughness. It's designed to punish the opposite—cases where a project sits because someone at the jurisdiction level decided it should.
What this means if you're submitting in Arizona
First: know your jurisdiction's published time frames. Most post them on their development-services page or in their municipal code. If a plan sits past that window with no deficiency notice and no approval, document it.
Second: understand that "malice" is a high bar. The AG isn't going to investigate every late permit. You'll need evidence that the delay was intentional and not tied to legitimate code review. That might mean:
- Multiple resubmissions for the same minor issue that could have been consolidated
- Extended silence after a complete application with no deficiency letter
- Verbal confirmation from staff that the application is "fine" but still no issuance
Third: this doesn't replace good project coordination. SB 1566 gives you a remedy after the fact. It doesn't give you leverage during review. If your drawings are incomplete, your setbacks are wrong, or your energy calc is missing, the jurisdiction has every right to reject the submittal—and the clock resets.
We always tell clients: the best way to avoid delay is to submit clean. That means coordinated sheets, a complete application checklist, and a pre-submittal meeting if the jurisdiction offers one. SB 1566 won't fix a bad application. It might fix a jurisdiction that's sitting on a good one for no defensible reason.
The bigger picture: Arizona's permit environment
Arizona operates under a home-rule framework. Each city and county adopts the International Codes independently, with local amendments.
Pima County adopted the 2024 codes effective January 2026, while Phoenix generally follows the 2018 codes with local amendments
. That patchwork makes statewide permit reform tricky—what works in Scottsdale doesn't necessarily translate to Yuma.
SB 1566 doesn't touch that structure. It doesn't standardize review timelines or impose a universal permitting process. It simply says: if you publish a time frame, and you blow past it for reasons unrelated to code enforcement, there's now a consequence.
For more on navigating Arizona's jurisdiction-by-jurisdiction code landscape, see our Arizona locations guide.
What we're watching
This bill passed, but enforcement depends on the AG's willingness to investigate complaints. Will the office take up cases? Will $5,000 be enough of a deterrent to change behavior at the AHJ level? We don't know yet.
What we do know: Arizona builders now have a tool they didn't have six months ago. Whether it gets used—and whether it works—will become clear over the next permit cycle.
If you're working on single-family projects in Arizona and run into a delay that feels less like thoroughness and more like obstruction, document everything. SB 1566 won't apply retroactively to permits issued before it took effect, but it's live now. And the first test case is going to set the tone.
For help navigating Arizona permit processes or coordinating submittals across jurisdictions, reach out. We draft for all fifty states, but we live in Phoenix—and we know which AHJs move fast and which ones don't.