Permits Are Not Projects: What Austin’s Permit Records Actually Show
If you have ever bought a permit list, or pulled one yourself, you have seen the headline number: thousands of permits issued. It feels like thousands of jobs. It is not. A permit is a filing. A project is a site where work will actually happen, and one project routinely carries several filings. Treating the two as the same number is the most common, and most expensive, mistake in permit-based lead research.
We know because we made the correction ourselves. When PermitScope built its Austin dataset from the city’s issued construction permits, we fetched 4,690 records. After removing inactive, expired, and administrative filings, 3,896 active qualifying permits remained. Grouped by site address, those 3,896 permits became 3,064 distinct projects. In other words, raw qualifying permit counts in Austin run about 27 percent higher than the distinct projects they represent.
Why the gap exists
A single kitchen and bath remodel can generate a building permit, an electrical permit, a plumbing permit, and a mechanical permit, all at the same address, all for one job with one budget and one decision maker. Count permits and you count that job four times. Count projects and you count it once, with every trade that the job will actually need attached to it.
The gap also runs the other way. Some filings in a raw export are not work at all: expired permits, withdrawn applications, and administrative records inflate the file without representing a single hour of construction. In our Austin pull, 794 of 4,690 records, about 17 percent, were excluded on exactly those grounds before any counting began.
Who is actually named on a project
A permit record names parties in different roles, and the roles matter. Of Austin’s 3,064 current projects, 875 name a general contractor of record. The rest are led by a trade contractor or an applicant with no GC named. An applicant is whoever filed the paperwork. It might be the GC, a specialty contractor, an architect, or the property owner. Any lead source that presents applicants as contractors is selling you names it has not verified, and any count of “GC-led projects” that does not distinguish the roles is a guess.
What the trade picture really looks like
Once permits are grouped into projects and each project’s scope is read, the trade counts change shape. In the current Austin dataset, the largest documented trade groups are excavation (1,177 projects), drywall (978), painting (963), concrete work (900), framing (859), and roofing (852). One project normally appears in several of these groups, because one job needs several trades. Where a trade is inferred from a project’s documented scope rather than named on a permit of its own, we label it as inferred. Inference is useful for finding work early. It is not the same as a filed trade permit, and an honest report says which is which.
Stated values need a skeptic’s eye
Austin permit records include stated project values, and some of them are placeholders. A value of one dollar in the record is a data-entry convention, not a one dollar job. When records for the same project state conflicting values, the honest presentation is to show them side by side, not to add them into a bigger, wronger number. If a lead list quotes you a market’s total value, ask how placeholders and conflicts were handled. The answer tells you whether the list was built or merely exported.
How to judge a permit lead before you chase it
- Dedupe by site. If a source cannot tell you how many distinct projects its permits represent, its counts are inflated.
- Check the status. Only active filings represent upcoming work.
- Read the parties by role. Contractor of record, trade contractor, and applicant are three different things.
- Read the scope text. The job is described in the record itself; a category label alone will mislead you.
- Verify against the record. Every project claim should trace back to a public permit record you can open yourself.
This is the standard PermitScope applies to its own published figures, including the corrections note on our first Austin brief, where our earliest trade table proved materially wrong for 15 of 18 trades and we republished it with the corrected counts and the method stated. Permit data is public. Getting it right is the work.
Want projects matched to your trade and service area? Join the PermitScope waitlist. Your first two weekly digests will be free when delivery launches.
Sources and method
City of Austin, Issued Construction Permits (official open data). PermitScope analysis, October 2026: 4,690 records fetched, 794 excluded as inactive, expired, or administrative, 3,896 qualifying permits deduplicated by site address into 3,064 projects. Trade counts from documented scope evidence; inferred trades are labeled as inferred wherever PermitScope publishes them.
Permit intelligence for specialty subcontractors. Now serving Austin, Texas, Chicago, Illinois, New Orleans, Louisiana, Seattle, Washington, and Baton Rouge, Louisiana, with more markets in preparation.
Data: City of Austin, Issued Construction Permits (official open data). PermitScope reads the records; the city does not endorse this service, and subscribers receive no advance or privileged access to them.
A permit is evidence that a project exists. It is not a guarantee of available work, an unfilled contract, or an invitation to contact anyone. Projects are never exclusive to any subscriber. Verify scope and timing with the named party before acting. Status: PermitScope is in pre-launch. Registration is a launch waitlist; digest delivery has not started yet, and no paid subscriptions are being accepted yet.