Methodology

How we count permits, tag trades, and rank contractors

Every public page is built from the same normalized database as the paid alerts. The window on this build is Aug 22, 2026 through Nov 19, 2026 (America/Phoenix).

Sources

We use each city’s official open-data API. We do not scrape hidden pages or buy a third-party permit file.

Austin, TX

  • Dataset: Issued Construction Permits (3syk-w9eu).
  • Update frequency: Daily.
  • History: 1921 (portal metadata says 1980–present) to present.
  • Permits in the current window: 14,715.

Chicago, IL

  • Dataset: Building Permits (ydr8-5enu).
  • Update frequency: Daily.
  • History: 2006 to present.
  • Permits in the current window: 8,534.

Mesa, AZ

  • Dataset: Building Permits (dzpk-hxfb).
  • Update frequency: Daily at 12:55 PM America/Phoenix.
  • History: 1987 to present.
  • Permits in the current window: 1,182.

Issue dates on all three feeds last topped out at the previous calendar day even when the dataset metadata had refreshed the same afternoon. Daily alerts should treat “yesterday’s issue date” as the latest complete day.

What we keep — and what we never publish

Stored and shown: city, permit id, issue date, street address, ZIP when the city publishes one, work description, permit type, work class, valuation, contractor business name, status, and a link back to the source row when one exists.

Never requested, stored, or printed: homeowner or owner names, applicant names, phone numbers, or email addresses. Chicago contact slots are kept only when the contact type is a contractor and is not an owner. Mesa applicant and contractor phone/email fields are not selected. Austin applicant fields and contractor personal names are not selected.

Public rankings further drop contractor values that look like a personal name (for example a bare first and last name with no company suffix or trade word).

Chicago’s feed has no site ZIP code. Mesa has no dedicated ZIP column. Valuation is the city’s declared figure, not our estimate; Austin trade permits are often $0, and a few Mesa rows carry very large figures that we do not “correct.”

How trades are tagged

A permit can carry more than one trade, so trade totals are not mutually exclusive and will not sum to the city total. Official work or permit types are preferred when a city publishes them (Chicago “Reroofing”, “Small-Scale Solar PV System”, “Fence or Trash Enclosure”; Mesa “Swimming Pool”, “Walls/Fences”; Austin “Mechanical Permit” for HVAC; building remodel types for remodel). Descriptions fill the gaps, with guards for known false positives: rooftop solar is solar, not roofing; “will not be solar panels” is ignored; “away from the back fence” is not fence work; electrical or plumbing permits with a “Remodel” work class are not remodel leads. Mesa pool descriptions that mention a temporary protective fence are not tagged as fence jobs.

Trends and rankings

“Last 30 days” is compared with the 30 days before that, ending at the exclusive window end. A change under 10% is called steady. Weekly charts use fixed seven-day buckets from the window start, not ISO weeks. Contractor rank is a count of issued, tagged permits in the window, then published valuation as a tie-break. It is not a recommendation.

Thin trades

If a city-trade pair has fewer than 30 tagged permits in 90 days, we still publish the real rows, but we do not sell it as a $39 standalone plan. Current thin pairs:

  • Austin fence: 13 in 90 days.
  • Chicago pool & spa: 15 in 90 days.
  • Mesa roofing: 1 in 90 days.
  • Mesa fence: 8 in 90 days.

Mesa roofing in particular is rare in that feed (a handful of permits per quarter).