Skip to main content
Plumb Intelligence
The data behind every answer

Anyone can show you a permit. We show you what it means.

Public data is the starting line, not the product. Plumb Intelligence fuses six layers of Arizona public records into one graph — permits linked to the licensed contractor who pulled them, refreshed daily, matched record by record with the confidence shown, and traceable to its source.

Latest permit issued Jul 25, 2026 · 1,441 issued across covered jurisdictions in the last 7 days

1M+
permits tracked
23
jurisdictions across 6 Arizona counties
1.76M
Maricopa County parcels joined
64K
AZ ROC licenses — statewide roster
The layers

Every source, its cadence, and its real coverage

Six public layers. Cadence is our refresh interval — the permit portals are pulled daily; the county and state layers on their own schedules.

City permit portals

New permits pulled directly from 20 Arizona city portals across 6 counties — lifecycle-classified (applied → issued → final), scored for lead quality, and clustered into projects.

1M+ permits
DAILY
Maricopa County Assessor

Parcels with owner of record, mailing address, property type, year built, living area, and assessed value — joined to permits by normalized APN.

1.76M parcels
WEEKLY
AZ ROC roster

The statewide contractor license roster — classifications, status, expirations, bonds — plus disciplinary actions and the unlicensed-violator list.

64K licenses
WEEKLY
Property sales

Recorded sales from Maricopa County recorder and affidavit records — price, date, and buyer where the record carries them. Powers sold-but-no-permit signals.

~910K sales
WEEKLY
Water supply (ADWR)

Arizona Dept. of Water Resources designations joined spatially to parcels — active management area, assured/adequate water supply, and provider.

parcel overlay
YEARLY
Neighborhood (Census ACS)

U.S. Census 5-year estimates joined on ZIP — income, ownership rate, and housing mix — for context around a permit, not guesses about it.

ZIP-level
YEARLY
The pipeline

Five stages, source to record

01
Ingest

Pull each source on its own schedule from city portals, county files, and the state registry.

02
Normalize

Standardize addresses, trades, APNs, and license formats into one schema.

03
Classify

Tag each permit by lifecycle stage — applied, issued, final.

04
Join

Match permit → parcel → owner and permit → ROC contractor.

05
Score

Attach a provenance stamp — and, where a match is fuzzy, its confidence — to every join.

The fusion

Joined — and honest about how far each join reaches

We never claim a link we can't back. These are the real join rates across the corpus today — coverage, not aspiration.

43%
Permit → ROC contractor

of all permits carry a contractor link — 67% of the ones that name a contractor. Each link shows ✓ Verified or ~ Likely with its confidence.

~89%
Permit → parcel & owner

reach a Maricopa County parcel, unlocking owner of record, mailing address, and property detail. Where none matches, we say so rather than guess.

~87%
Valuation coverage

reported or carefully imputed. Estimates always show a ~ and an EST. tag — never dressed up as a filed figure.

Coverage varies by city, and we show it. Some feeds publish permits without a contractor name at all — Queen Creek's, for example — so those permits can never be license-linked. That's a property of the source, not a defect we hide: each permit shows its own match state, and the claim-your-profile path lets contractors close gaps themselves.
The confidence model

How a match earns its label

Every contractor link carries a provenance tier — how the match was made, not just that it was. The tier maps to the badge you see on the record. Never a silent guess.

✓ VERIFIED
License-matched
The license number on the permit itself matched to the AZ ROC roster. No inference — the city record named the license.
~ LIKELY
High-confidence match
A strong name, DBA, or phone match to the roster — always shown with its confidence, never dressed up as verified.
SUGGESTED
Low-confidence candidate
A possible match worth a human look. Presented as a suggestion, never as fact.
UNCLAIMED
No contractor named
The permit names no contractor — common on owner-builder work and in feeds that omit the field. We say so instead of guessing.
Provenance

Every record shows its work.

Source, freshness, and match confidence travel with every record — permit, contractor, and owner. We say “ingested” when it's our pull time and “source updated” only when the upstream feed stamps it — because those are different promises.

Show your workEXAMPLE · PERMIT #MES-2026-04821
Permit record
City of Mesa · permit portal
INGESTED
today 7:02 AM
Contractor match
Fuzzy name + DBA · not license-verified
CONFIDENCE
~ LIKELY 82%
Parcel & owner
Maricopa County Assessor
INGESTED
this week
Valuation
two-state: reported vs. estimated
$14,800reported·~$44.2KEST.
Our pledge

Four rules we don't break

1

Coverage, not aspiration

The join rates on this page are the real ones, measured across the corpus — not a marketing ceiling.

2

Every number traces to a public record

Permits, parcels, licenses, sales — each field links back to the city, county, or state record it came from.

3

Estimates are labeled

An imputed dollar figure always carries a ~ and an EST. tag. It is never presented as a filed number.

4

Corrections are fast

Every contractor profile has a suggest-an-edit path, and fixes flow back into the record — contractors can close gaps themselves.

Get the Arizona Permit Pulse

A monthly read on Arizona construction — permit volume, the fastest-issuing cities, and which trades are heating up. Free, no spam, unsubscribe anytime.

See it on your own territory.

Free lookup, no signup — or start a 14-day trial and get the fused record for the permits in your zips.