PermitVector Resources
How Fresh Is Texas Permit Data? A Guide to Data Lag and What It Means for Your Pipeline
By Ken Besada · Updated June 10, 2026
Most Texas cities that publish permit data openly update their feeds daily, with a typical lag of zero to two days between permit issuance and availability in the public dataset. The practical implication: a contractor monitoring permit data every morning can realistically learn about a new permit within 24–48 hours of the municipality approving it. But not all cities behave the same, and several major markets — notably Dallas proper and Houston proper — do not publish open data at all. This guide explains what “data freshness” actually means for Texas permit intelligence, where the gaps are, and how to think about data quality when evaluating any permit data source.
What “Data Lag” Means in Practice
A permit is issued when the local building department approves the application. That approval is recorded in the municipality’s internal permitting system. “Data lag” is the time between that internal record being created and the permit appearing in the public-facing data feed that contractors and data services can access.
Three stages contribute to total lag:
| Stage | What Happens | Typical Duration |
|---|---|---|
| Internal processing | City staff reviews application, makes decision, records it in system | Hours to days (mostly same day) |
| Publication delay | System pushes approved records to public API or portal | 0–24 hours for Socrata/ArcGIS live feeds; up to weekly for manual CSV exports |
| Collection and delivery | Data service pulls the feed, processes, and delivers to subscribers | Hours, if the pull is automated and daily |
For cities running live Socrata or ArcGIS endpoints — which includes Austin, San Antonio, Fort Worth, and several others in the Texas open-data ecosystem — permit records can appear in the public feed within hours of approval. In practice, a daily pull at 3–4 AM CT captures the prior day’s permits reliably.
For cities publishing weekly or ad hoc CSV dumps, the effective lag can be 5–7 days on average, with occasional bursts when a large batch is published after a longer gap.
How Often Do Texas Cities Actually Update Their Feeds?
Publishing cadence varies by city and by the technology stack the permitting department uses. Here is a general characterization of the Texas markets PermitVector covers, based on observed behavior of the open-data endpoints:
| Market | Data Source Type | Observed Update Cadence |
|---|---|---|
| Austin | Socrata (data.austintexas.gov) | Daily; near real-time for most permit types |
| San Antonio | City open data portal | Daily to near-daily |
| Fort Worth | ArcGIS public feed | Daily |
| Arlington | City permitting portal | Daily to near-daily |
| Sugar Land | City CSV / portal | Near-daily |
| Pearland | City records | Daily to near-daily |
| San Marcos | City portal | Near-daily |
| Midland | City records | Near-daily |
| El Paso | Open data portal | Daily |
| Unincorporated Harris County | Harris County AEIS / open data | Daily |
“Near-daily” means that in practice, records may batch and publish every one to two days rather than continuously, but the effect on a morning subscriber is minimal — you are seeing permits within 48 hours of issuance in most cases.
Why Daily Beats Weekly
A contractor running a weekly permit review on Monday morning is making decisions based on data that may be 1–7 days old. In practice, the average record is 4 days old.
For new construction permits, that window matters. A general contractor awarding subcontracts is most accessible in the first 48–72 hours after a foundation or framing permit is issued. By day 4–7, some subcontractors have already been contacted, or the GC has moved on. Being the third roofer to send a postcard to a 5-day-old permit address is less effective than being the first.
For homeowner-facing trades with longer decision cycles — landscaping, pool, security — the timing advantage is narrower, but consistency still matters. A homeowner who hears from a contractor promptly perceives them as organized and attentive, which sets a tone for the relationship.
The practical value of daily data is not just speed on any single permit — it is the compound effect of consistently being the first contact across many permits over months.
Known Error Classes in Permit Data
No government data source is perfectly clean. Anyone selling Texas permit data — including PermitVector — should be transparent about the known error classes that exist:
Duplicate filings. When a permit application is amended, revised, or re-submitted, some city systems generate a new record rather than updating the original. This can cause the same project to appear twice (or more) in a feed. Good data processing flags and deduplicates these by matching on address, permit type, and approximate issue date.
Permit type miscodes. The permit type field is often entered by a permit clerk from a dropdown list. A project described as “addition” in the work description field might be classified as “remodel” by the clerk, or vice versa. Similarly, mechanical permits sometimes include work across multiple trade scopes. Trade classification algorithms have to account for this variation.
Stale owner information. Owner names in permit records reflect who owned the property at the time of filing. In active investor markets, properties may have been sold between permit filing and your outreach. County appraisal district records are more current for ownership information and are worth cross-referencing for high-value targets.
Address standardization errors. Free-text address fields in permit systems often include abbreviations, inconsistent street type formatting, and missing unit numbers. These create challenges for geocoding and duplicate detection. A robust data pipeline standardizes addresses against USPS or county appraisal district address files.
Missing fields. Not every jurisdiction publishes every field. Some cities redact owner names; some do not publish valuations; some permit types lack meaningful work descriptions. The richness of a permit record varies by city.
The Dallas and Houston-Proper Gap
This is the most significant honest gap in Texas permit data coverage for any service relying on public open-data feeds, and it deserves a direct explanation.
Dallas proper (the City of Dallas, not DFW suburbs) operates its permitting through a portal that requires user registration and login. The underlying data is not available via a public API endpoint. To access it programmatically, you would need to authenticate as a user, which enters legal gray area around terms of service for automated access.
Houston proper (the City of Houston) has a similar situation. Houston’s eSPAN permitting portal requires a registered account. The city does not publish an open-data feed comparable to Austin’s Socrata endpoint.
What this means: Data services that claim “Houston coverage” typically mean unincorporated Harris County — the areas outside Houston’s city limits that are governed by Harris County rather than the City of Houston. This is a substantial and active real estate market (Sugar Land, Katy, Cypress, Pearland, Humble, and other communities are partly or entirely in unincorporated Harris County), but it is not Houston proper. Similarly, “Dallas coverage” typically means suburban markets like Fort Worth, Arlington, Plano, or other Collin and Tarrant County markets — not the City of Dallas itself.
PermitVector covers unincorporated Harris County and Fort Worth / Arlington (Tarrant County). It does not cover Houston proper or Dallas proper, and says so plainly. See /data for current market coverage details.
When evaluating any permit data provider, ask specifically: “Does this include City of Houston permits issued through eSPAN, and City of Dallas permits from the Dallas ePlan portal?” If the answer is yes, ask how they access those systems.
How to Think About Data Quality When Evaluating Providers
A permit data service’s value is a function of freshness, accuracy, coverage, and classification quality together. Questions worth asking any provider:
Freshness questions:
- How often do you pull data from source systems?
- What is your typical lag between a permit being issued and appearing in your product?
- Do you pull on weekends and holidays, or only weekdays?
Accuracy questions:
- How do you handle duplicate permits?
- How do you handle permit type miscodes?
- What is your address standardization process?
Coverage questions:
- Which specific jurisdictions do you cover? (City vs. county matters.)
- Do you cover Dallas proper and Houston proper, and if so, how?
- How do you handle TDLR-licensed trade permits vs. municipal building permits?
Classification questions:
- How are permits assigned to trades?
- Is classification rule-based, ML-based, or manual?
- What is your error rate on trade classification, and how is it measured?
A provider who cannot answer these questions with specifics is either reselling someone else’s data or has not invested in data quality infrastructure.
PermitVector’s answers to these questions are documented at /methodology and /data.
What “Fresh” Data Actually Delivers
The value of fresh permit data is not abstract. Here is what it means in operational terms:
- 0-2 day lag on a daily pull means you learn about a new permit before most competitors even know the project exists.
- Daily delivery at 6 AM CT means you can act on that information the same morning it arrives — before your workday is consumed by other tasks.
- Consistent deduplication and classification means the permits you receive are already filtered to your trade, without requiring you to wade through irrelevant records.
The alternative — checking city portals manually, pulling weekly CSVs, or buying data from a broker who aggregates on a monthly cycle — introduces lag that compounds across hundreds of permits and multiple markets.
Getting Started
If you want to understand the specific data sources, collection methods, and quality standards behind PermitVector’s ten Texas markets, the methodology page is the primary reference. The data page lists current market coverage and known gaps.
For a comparison of how PermitVector’s data freshness and coverage compare to other Texas permit data sources, see Best Construction Permit Data Providers for Texas.
A 14-day trial is available at /leads if you want to see the actual daily output before committing.