How Lumberyards Find and Prioritize New Construction Leads

Claim, evidence, and buyer action

Step 1

Build a discovery map your territory can operate

Use a local operating map to decide where your team will look for project signals. Permit portals can provide a repeatable public-record input; your team may use relationships for context, site observation for a verification step, plan rooms for selected project types, and counter conversations or referrals as optional inputs. Give each selected source a boundary, owner, review rhythm, and original URL or origin.

The Census Building Permits Survey offers multiple geographic levels [S1]. Local portals can use different fields and lifecycle labels, so your map should make those differences explicit.

Step 2

Read construction timing as a sequence, not a date

The Census Bureau describes new residential construction through authorization, authorized-but-not-started, started, under construction, and completed phases [S2]. Its June 2026 release reports permits, starts, and completions as separate measures [S3]. For sales, a permit is a reason to investigate, not a promise that a framing order is ready.

Require each record to carry both a public-record stage and a rep-verified timing note. “Issued” can prompt a closer look; “framing discussion confirmed for a stated window” is a better reason to schedule an action. Neither is a universal timing promise.

Census defines valuation as the estimated value of the residential structure shown on the permit, or an estimate accepted from the permit official when no value is listed [S2]. Keep it as directional context, not a takeoff, quote, or amount a yard can sell.

For field-level interpretation, use the companion guide Building Permit Data for Sales: What Lumberyard Teams Should Look For.

Step 3

Map the project to the person who can make the next decision

A record names a place and a public event. It rarely settles the relationship map. Build a contact hypothesis, then let the rep verify it. An owner or developer may control the project; a builder or GC may coordinate it; a framer may influence or place the lumber order; an estimator, superintendent, or purchaser may control scope or the commercial decision. The permit applicant can be an entry point without being the buyer.

Record the public name, the role you believe they hold, the evidence, and the question that would confirm or correct it. If the first conversation reveals a different buyer, update the map and preserve the original assumption as history. Relationships stay personal; operating knowledge stays with the company.

Step 4

Qualify with a consistent review frame

Qualification should make judgment consistent, not pretend a local sales decision can be reduced to a magic score. Use the same questions for every source, record where the answer came from, and label what remains unknown. High, medium, or low review labels are easier to explain than precise numbers whose inputs no one trusts.

Start with territory and structural-material relevance. Ask what the lifecycle signal means, whether the project is active, and when a conversation could be useful. Add account context and available rep time. The framework gives managers a way to explain why one project moved first without pretending certainty.

Step 5

Prioritize by fit, timing, context, and capacity

Prioritization decides which project receives attention first, which is watched, and which closes with a reason. Ask: can we serve it, is material relevant, what do we know about timing, is there a buyer path, does account context change the opening, and which rep can act well? Adjust the order as evidence changes while preserving the decision note.

Do not let apparent scale dominate. Census valuation is the estimated structure value on the permit, not material value [S2]. A local project with a clear buyer can deserve earlier review than a larger record with no workable lane. A known account can change the opening question; a distant start can stay visible without consuming today’s attention.

Step 6

Assign one owner, one next action, and one review date

Ownership turns a reviewed signal into work the team can manage. The action might be a call to verify who buys the framing package, a site visit to confirm stage, a warm introduction, a plan-room scope review, or a scheduled revisit. “Follow up” is not an action until the record says what the rep will do and when.

Separate relationship ownership from specialist help when needed, but keep one coordinator accountable. When work changes hands, preserve the reason, evidence, and date. A handoff that removes a name without adding another creates an unowned record.

Step 7

Install a daily, weekly, and monthly cadence

Daily review should happen before calls and visits. Reps review new records, overdue actions, changed stages, and urgent handoffs. Managers remove duplicates, resolve ownership questions, and make sure a project does not sit in a generic queue.

Weekly review asks which sources produced records worth investigating, which project types were repeatedly closed, where the public contact was not the buyer, and which owned actions are overdue. Monthly review can examine source maintenance, territory boundaries, builder context, repeat work, and the balance between immediate conversations and longer-term relationships. The cadence should change the system, not merely ask people to work harder.

Step 8

Measure whether the system creates useful decisions

Use definitions the team can apply each week. Establish a local baseline, document fields, and review definitions when the process changes. Do not import a universal target or turn activity counts into commercial claims.

The best result of a metric review is a better next decision. If duplicates rise, fix the merge rule. If a source produces names but little verification, change the source or question. If actions are repeatedly deferred, revisit territory, travel, or capacity. A number without an operating response is only a report.

Management failure modes

The habits that make a territory look covered

Failures usually come from collection without judgment or activity without ownership. Treat these as review questions, not blame. The goal is to make the next decision visible and supportable even when a public record is incomplete.

Where Radar fits: monitoring and first-pass prioritization

The framework above is the work a sales leader installs: discover signals, verify the project, decide, assign ownership, and review learning. LumberFlow Radar is designed for the front of that workflow. In its Private Beta, Radar monitors supported local building activity and brings it into a prioritized project queue for review [S6]. It handles monitoring and first-pass prioritization; the rep verifies the buyer, applies judgment, owns follow-up, and keeps the relationship.

See the related building permit leads workflow for product context. Radar remains a Private Beta activated by invitation in supported territories, and the queue is a place for rep review, not a substitute for verification and ownership.

Methodology and sources

This guide separates public-record definitions from local sales judgment. Census sources cover authorization, permit-issuing place, valuation, and construction phases [S1, S2, S3]. NRLA sources are attributed commentary [S4, S5]. Radar statements use the current first-party description [S6]. None establishes a universal threshold, buyer identity, order date, or commercial outcome.

Frequently asked questions