Permit Pulse guide
City Permit Feed Validation Checklist
A checklist for deciding whether a city permit source is good enough for a Permit Pulse market brief.
Source access
Confirm the feed is official/open, stable enough to revisit, and not dependent on login-gated portal scraping. Save the source link, source owner, last checked date, and any rate or export limits before creating a public URL.
Field coverage
Require at least permit ID, issued date, permit type, description, and one useful signal field such as ZIP, contractor, parcel area, or address area. If the page cannot explain which source fields drive the buyer decision, it is not ready for indexing.
Classification quality
Sample at least 25 target-trade records and review ambiguous descriptions, missing dates, duplicate permits, and confidence mix. A market page should disclose limitations and avoid hiding low-quality rows behind polished copy.
Publish decision
Publish a city/trade brief only when the source supports a useful weekly decision and internal links can connect it to real city, topic, and guide context. Otherwise keep it unpublished, list it in the roadmap, and send visitors to request validation.
Frequently asked questions
Is permit data the same as a lead list?
No. Permit data is a public activity signal. Permit Pulse should not claim guaranteed leads or enrich private contact data.
When should a new market page be published?
Only after the official/open source is verified and the available fields support a useful city/trade decision.
Need a weekly brief for your market?
Use the request form to name the city, trade, and decision you need. New pages stay off the sitemap until the source and fields are validated.