Direct answer
What should a lumberyard look for in building permit data?
Building permit data is a local project signal, not a buyer record. Start with the issuing jurisdiction, permit ID, type, work description, dates, status, location, and named participants. Then check each field’s definition, timing, completeness, and source update note. Use valuation only as directional scale context. A rep still verifies scope, buyer, and next action.
The record is a starting point, not the sales decision
A permit record looks precise because it has an ID, an address, and a status. Ask what this jurisdiction publishes, what the row means locally, and what a rep can verify before reaching out.
Owners, GMs, and sales leaders need a shared interpretation before they ask a rep to work a list. Keep the source, local labels, unknowns, and one next question visible. This guide is a field dictionary, not a promise that a record will become an order.
Start with the source
Name the jurisdiction, source URL, retrieval date, and local data dictionary.
Separate roles
Treat owners, applicants, contractors, and likely buyers as different questions.
Verify before acting
Use the record to choose a respectful next conversation, not to skip judgment.
Start with the jurisdiction, not a universal spreadsheet
The Census Bureau defines a permit-issuing place as a single municipality, a county, or a combination of municipalities. It defines authorization as a local jurisdiction approving construction by issuing a building or zoning permit [S1]. That framing matters: the public record is created and described locally, even when a federal program later aggregates selected residential statistics.
Austin and Chicago show why local reading comes first. Austin publishes applied and issued dates, status, expiration and completion dates, valuation, units, applicant and contractor fields, and a master permit number. Its page identifies the dataset as BLDS-compliant and warns that the data are informational and may differ from official department data [S3].
Chicago publishes a different shape: application-start date, issue date, status, milestone, work type, description, parcel index numbers, and contractor information. Its page says the dataset is updated daily and excludes permits voided or revoked after issuance [S4]. That is Chicago context, not a default elsewhere. Capture each source’s definitions and exclusions.
Read lifecycle timing as a sequence, not one date
Census groups new residential construction into authorization, authorized-but-not-started, started, under construction, and completed phases [S1]. A local portal may show only part of that sequence. Austin exposes applied, issued, status, expiry, and completion fields; Chicago exposes application-start and issue dates with status and milestone fields [S3, S4].
For sales review, a stage prompts a better question. A filed record can justify checking scope and territory; an issued record can prompt confirmation of the buyer and what remains open. A completed or expired record may deserve a disposition. None is a universal start date, order date, or buyer signal.
| Stage in the record | Record question | Sales use | Limitation |
|---|---|---|---|
| Application or filed | Has the jurisdiction received an application, and when did its process begin? | Use the record to decide whether scope and territory deserve an early review. | Some local datasets expose only issued permits, so an earlier signal may not be visible. |
| Review, milestone, or correction | What review milestone or condition does this jurisdiction publish? | Check whether the public status changes the next verification question. | A local milestone label is not a universal construction phase or start date. |
| Approved or issued | When did the authority record approval or issue, and is the permit active? | Confirm scope, likely timing, and the person who can explain the next material decision. | Issuance records permission; it does not prove that work has started or that material remains unpurchased. |
| Inspection, construction, or milestone updates | Does the source publish inspections, milestones, or status dates? | Use a changed record as a reason to verify current stage and scope. | A portal may expose only a current snapshot rather than the full history. |
| Completed, expired, cancelled, or voided | What disposition did the jurisdiction record, and on what date? | Close, watch, or investigate follow-on work with a written reason. | The status vocabulary and the meaning of a final record remain local. |
Field, sales question, and limitation: the working dictionary
A field earns a place in a sales workflow when the team can state what it means, what question it changes, and what it cannot prove. Keep the raw local value beside any normalized label; label missing data unknown.
| Field | Sales question | Key limitation |
|---|---|---|
| Issuing jurisdiction and source URL | Which authority defines this record, and where can the rep re-open it? | A field label has no portable meaning without the jurisdiction and its documentation. |
| Permit or project ID | Which record should the team reference and de-duplicate? | An ID identifies a record; it does not describe scope, timing, or the buyer. |
| Permit type, class, or subtype | What kind of work does this authority say it covers? | Types and codes are local. A category that sounds structural may include a different scope elsewhere. |
| Work description | What work does the record say is authorized or proposed? | Descriptions can be brief, coded, or incomplete; they are not a material list or takeoff. |
| Application or applied date | When did the jurisdiction record the application or plan-review start? | The field may be absent, may describe a particular review event, or may not reflect field activity. |
| Issue, approval, or milestone date | When did this authority record permission or a process milestone? | A date in the portal may lag the event or use a local definition that differs from another portal. |
| Status, milestone, and status date | What does this jurisdiction say is true now, and when was it last changed? | Status names are not standardized. Read the local data dictionary before sorting or filtering. |
| Address, parcel, or coordinates | Where is the work, and does it sit in the yard’s service boundary? | Addresses can omit units or use lot and parcel conventions; coordinates may be generated or absent. |
| Owner | Who is associated with the property or development? | An owner may hire a builder and may not control the material decision. An entity name may require verification. |
| Applicant | Who submitted the application or appears as the applicant organization? | The applicant can be an owner, agent, architect, or contractor. The role does not settle who buys. |
| Contractor and trade | Which firm or trade does the authority associate with the work? | Contractor fields may be missing, partial, or separate from license records and purchasing contacts. |
| Valuation | What directional scale context did the permit source report? | Census defines this as estimated structure value, not permit fees or a lumber amount. It can be missing or marked NVR. |
| Square footage and units | Does the source provide project area or housing-unit context? | The measure may describe only a portion of the work, use a local definition, or be absent. |
| Expiration and completion dates | What closing or expiry event did this authority record? | The field helps with disposition, but it does not reconstruct all purchasing or construction activity. |
| Source update or first-seen note | When did the team retrieve or first see this record, and when did the source update it? | A retrieval date is not proof of when the underlying event happened. |
Valuation is directional project context
Census defines valuation as the estimated value of the residential structure shown on the permit. If no value is listed, the Census FAQ says it may accept an estimate from the reporting permit official; it also says not to report permit fees as construction value. When a municipality does not require a value, the FAQ uses NVR, meaning “no value required” [S2].
For a lumberyard, valuation is a scale clue, not a material amount. It does not tell you the package, specification, supplier, purchase timing, or relevant share of the work. A higher number can prompt a scope question, never replace one. Keep the published value, unit, source date, and caveat together.
Participant versus buyer: keep the distinction visible
A permit can name several participants without naming the person who will choose or place a lumber order. Austin’s dataset publishes separate applicant and contractor fields alongside property and project fields [S3]. Those columns describe the record; they do not settle the commercial relationship.
A participant is not automatically the buyer. An owner may hire a builder; an applicant may be an owner, agent, architect, or contractor; a contractor may delegate purchasing. Treat “likely material buyer” as a rep hypothesis with evidence and a verification question, never as a copied permit field.
Owner or developer
Property or development party named by the record.
Buyer question: Who controls the project and who can identify the material decision-maker?
Applicant or agent
Party that submitted the application or is listed as the applicant organization.
Buyer question: Is this person the builder, an agent, an architect, or only the filing contact?
Contractor or trade
Firm or trade associated with the permitted work when the jurisdiction publishes it.
Buyer question: Does this firm buy the relevant package, recommend a supplier, or hand purchasing to someone else?
Likely material buyer
A rep’s working hypothesis about who controls or places the material order.
Buyer question: What conversation or source can confirm the buyer path before outreach is treated as informed?
Missing, changing, and duplicate data need an operating response
Data quality is a set of questions about source, field, date, and intended use. Austin warns that reports can differ as its database is updated; Chicago documents daily updates and an exclusion rule [S3, S4]. Record those facts instead of treating every row as equally current or complete.
Multiple permit types can belong to one project. A parent or master ID, parcel, address, description, and participant names help test whether a row is new work or another record already under review. Preserve each authority’s ID and source history when grouping records for one conversation.
Missing values
Label the field unknown, preserve the source URL, and choose a verification question. Do not treat a blank as proof that the project has no relevant work.
Stale or changing rows
Store retrieval and source-update notes, then check the local documentation before deciding how often to revisit a record.
Multiple permits for one project
Keep the authority and permit ID, then test address, parcel, parent or master ID, description, and participant fields before creating a second outreach record.
Different codes and labels
Keep the local raw value beside any normalized label. Link the local dictionary so a manager can audit the interpretation.
Responsible use of public project information
Public availability is not verified contact permission or a complete relationship record. Keep the source URL, retrieval date, local terms, and reason for review. Confirm that the person is connected to the project, identify yourself, use a permitted channel, and honor no-contact requests. Ask your legal or compliance adviser about rules for your territory and channel; this guide is not legal advice.
Do not infer household circumstances or personal intent from an address. Minimize copied contact data, restrict access, and correct stale details under company policy. With no buyer confirmation, the respectful next step may be a verification question, watch status, or close reason.
Common permit-data misinterpretations
“A permit equals a project that will build.”
A permit records an authorization or local process event. Review status, scope, expiration, and current evidence before treating it as active sales work.
“The newest status is the best trigger.”
The newest row may be a completion, expiry, correction, or administrative update. Read the local definition and ask what changed.
“The applicant is the buyer.”
The applicant is a participant. Map the owner, builder, contractor, estimator, purchaser, or other person who can confirm material responsibility.
“Valuation is the lumber amount.”
Census’s estimate is structure context. It is not a takeoff, a quote, or the amount a yard will sell.
“The same filter works in every city.”
Keep local raw values and dictionaries. A type, status, date, or parcel field can have a different meaning or be absent elsewhere.
“A blank field means no opportunity.”
A blank means the source did not provide a value that you can use. Record the unknown and decide whether verification is worth the time.
Where Radar fits: monitoring and first-pass prioritization
The field guide above is the interpretation and judgment a sales team still owns. Radar handles monitoring and first-pass prioritization; the rep verifies the buyer, applies judgment, owns follow-up, and keeps the relationship. In its Private Beta, Radar is for supported local building activity and a prioritized project queue for review [S5].
See the related building permit leads workflow for product context. For the broader operating system, return to How Lumberyards Find and Prioritize New Construction Leads. The field guide answers what the record means; the operating guide covers prioritization, ownership, cadence, and measurement.
Methodology and sources
This guide starts with the permit-data dossier, then limits factual claims to directly reviewed Census, municipal, and first-party sources. Census supplies definitions and the valuation caveat; Austin and Chicago show different fields, dates, status notes, and exclusions. Product language follows the current Radar boundary and registry rule. Sales judgments are labeled as local operating choices.
S1 · Defines authorization, the permit-issuing place, building or zoning permits, and the five phases used in New Residential Construction statistics.
U.S. Census Bureau: Building Permits Survey DefinitionsSource date: Current definitions page; accessed August 16, 2026
Limitation: These are federal statistical definitions. They do not define every local permit status or establish a project-specific buying date.
S2 · Defines permit valuation as the estimated value of the residential structure, excludes permit fees, and explains the NVR notation when no value is required.
U.S. Census Bureau: Building Permits Survey Definition FAQsSource date: Last revised November 30, 2022; accessed August 16, 2026
Limitation: The FAQ addresses Census reporting. Local valuation fields may use different rules or may be absent.
S3 · Shows one local schema with permit type, class, work class, description, applied and issued dates, current status, expiration and completion dates, valuation, units, location, and separate applicant and contractor fields. The dataset identifies itself as BLDS-compliant.
City of Austin Open Data: Issued Construction PermitsSource date: Dataset updated August 16, 2026; accessed August 16, 2026
Limitation: Austin’s field names and data practices are a local example. Its own disclaimer says the data are informational and may differ from official department data.
S4 · Shows a different local schema with permit status, milestone, application-start date, issue date, work type, work description, parcel index numbers, and contractor information. The portal states that this dataset is updated daily and excludes permits voided or revoked after issuance.
City of Chicago Data Portal: Building PermitsSource date: Dataset updated August 15, 2026; metadata updated May 29, 2026; accessed August 16, 2026
Limitation: Chicago’s update frequency and exclusions cannot be generalized to another jurisdiction.
S5 · First-party product source for Radar’s Private Beta, supported local activity monitoring, prioritized project queue, and rep review boundary.
LumberFlow RadarSource date: Current product page; reviewed August 16, 2026
Limitation: Product copy describes current behavior. It is not evidence of outcomes, jurisdiction coverage, or data quality.
Written and reviewed by Alex Wu, Founder & Supply Chain Technologist.
Published . Last updated . Editorial standards
Frequently asked questions
What does building permit data tell a lumberyard sales team?
It can identify a local record, project description, stage, location, and public participants when the jurisdiction publishes those fields. It is a reason to investigate, not proof of a material order or a specific buyer.
What is the difference between an applicant and a contractor?
The applicant is the party shown as submitting the application. A contractor is the firm or trade associated with the work when the source publishes it. One person or company can fill both roles, but the record may also separate them. Verify the buyer path.
Does permit valuation equal the lumber package value?
No. Census defines permit valuation as an estimated value of the residential structure and says not to report permit fees as construction value. Keep it as directional context, not a material amount, quote, or sales expectation.
Why do permit fields differ by city?
Permit-issuing places publish their own records and field conventions. Compare the local data dictionary before mapping a type, status, date, or participant field into a shared sales workflow.
How does Radar fit with permit-data review?
Radar handles monitoring and first-pass prioritization for supported local building activity in a Private Beta. The rep verifies the buyer, applies judgment, owns follow-up, and keeps the relationship.
Make permit review easier to explain
See how Radar’s supported-local project queue can fit the review, verification, and ownership process your sales team already needs to run.