How subcontractors use permit data to find real projects

A building permit is a public record of authorized work at an address, with the parties named on it. Used carefully, Austin’s issued permit records are the earliest public signal that a project exists. Used carelessly, they mislead: the same project appears under many permit numbers, values repeat or contradict each other, and a permit never says whether any scope is still open. This guide is the method PermitScope runs on Austin records every cycle, with real examples from the current one (Sep 23 to Oct 22, 2026). Every example links to the city record so you can check it yourself.

Step 1. Turn permits into projects

A real project usually files several permits: a building permit plus electrical, plumbing, and mechanical companions, sometimes phased building permits as well. Counting permit rows counts paperwork, not projects. Group records by site address and scope first. This cycle, 3,896 active Austin permit records group into 3,064 projects; 832 records were duplicates of a project already counted, and 517 projects carry more than one permit.

The extreme case this cycle is 6433 Champion Grandview Way Bldg 1: sixteen permit records (four building permits, each with electrical, plumbing, and mechanical companions) that are one project at one site (city record). A lead list that sells rows would offer you that project sixteen times.

Step 2. Read the lead class before anything else

What you can do with a project depends on who the record names. PermitScope sorts every project into one of three classes:

Class A, GC-led (875 projects this cycle). A general contractor or builder of record is named. That is the party who typically engages subcontractors, and the first call on the project.

Class B, trade-led, no GC of record (1,946 projects). No GC is named, but trade contractors or an applicant are. At 8709 Honeysuckle Trl, a second-story addition and remodel with two bathrooms in the recorded scope, the record names a mechanical contractor, an electrical contractor, and a plumbing contractor, and no GC (city record). Work the named parties and the project type; do not invent a GC the record does not name.

Class C, watchlist (243 projects). No party is named at all, like the commercial wall permit at 1500 W Parmer Ln (city record). There is nobody on the record to contact. These are watch items: note the site and scope, and check back as companion permits file.

Step 3. Read the scope text, not the work-type field

The work-type field is a filing category, and it can disagree with the work itself. At 4810 Gonzales St the record is filed as a Remodel, while its own scope text describes new construction of a multifamily club and amenity building, phase 1, at a stated value of $10,428,571 (city record). The scope paragraph is the direct evidence: what is being built, how big, and in what configuration. Quote it, check it, and treat the category field as a rough label only.

Put the method to work

The PermitScope digest cuts this same intelligence to your trade, your ZIP codes, and the project types and values you actually want. Join the launch waitlist and your preferences are saved for the first edition.

Join the waitlist

Delivery has not started yet. Your first two weekly digests are free when it begins, no card required, and joining the waitlist does not start a subscription.

Step 4. Separate what is stated from what is inferred

A permit states the work it authorizes. It does not list the trades that work usually involves. When a scope describes an interior remodel and addition, framing, drywall, and painting are a reasonable inference; they are not in the record, and PermitScope labels them as inference on every project. The same discipline applies to pools: at 6525 Ed Bluestein Blvd the record documents construction of a 2,773 sq ft commercial swimming pool by Cody Pools, Inc. (city record). Pool plaster, tile, and coping work around that pool is inference from the documented scope. Our Austin pool permit tracker lists every pool project this cycle with that line drawn the same way. Inferred trades tell you where to look; only the documented scope tells you what is actually being built.

Step 5. Treat every valuation with suspicion

Permit values are the dirtiest numbers in the dataset. Three rules keep them honest:

Most projects state no usable value. Only 148 of this cycle’s 3,064 projects state a job valuation of $500 or more. Austin records also carry $1 placeholder values. A missing or placeholder value says nothing about project size; never print it as a dollar figure and never size a project by it.

Values repeat across a site’s records. The city prints the whole project’s stated value on each component record. At 7401 Loyola Ln, a new sports facility, six records at the site carry the same $140,000,000 stated value (city record). Add them together and one $140,000,000 project becomes a fictional $840,000,000 one. Count the site once, at the stated value, once.

Fields can contradict each other on the same permit. At 1801 S 1st St, the building permit states $300,000 in its total job valuation field and $1,200,000 in its remodel valuation field (city record). Print both, flag the conflict, and use valuation for rough sizing only, never as a quote input.

Step 6. Remember what a permit never tells you

A permit does not say whether any scope of work is unfilled, who else is pricing the work, when trade packages will be let, or whether the named GC self-performs your trade. It carries no contact details beyond the names on the record, and it grants no exclusivity to anyone who reads it. Any service that presents a permit as an open contract is claiming something the record does not contain. The permit’s job is narrower and still valuable: it proves a real project exists, at a real address, with named parties, earlier than almost any other public signal.

Step 7. Work a weekly list like a route, not a pile

The method, compressed into a weekly routine:

Filter to your segment and the ZIP codes you actually serve. Start with Class A projects in your trade lens, newest first, while the project is at its earliest documented stage. Read the scope quote on each one, not just the category. Check the stated value only for rough sizing, and check it against the conflict and placeholder rules above. Open the city record link and verify the project before you act on it. Shortlist the handful that fit, contact the named party about that specific project and scope, and log the outcome. Hold Class B projects where a party you already work with is named, and park Class C on a watchlist instead of spending calls on it. Repeat next week; permit flow is a stream, not an event.

That routine is exactly what the PermitScope digest automates: the deduplication, the classes, the scope reading, and the valuation hygiene, cut to your trade and ZIP codes. Our weekly Austin brief shows the same engine running over the whole city.

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. 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.

PermitScope · Austin, Texas, our first live market. Data: City of Austin Open Data, public records as published. Permit data is public record information; it is not a guarantee of available work, and projects are never exclusive to any subscriber.