How to find commercial construction projects before they go to bid

To find commercial construction projects before they go to bid, monitor the signals that precede bidding: development applications, planning-board approvals, and building-permit filings. A permit above your value threshold with no general contractor attached is a funded project whose work is still winnable.

Every contractor, subcontractor, and building-product supplier knows the frustrating version of this timeline: a project you would have been perfect for surfaces on a bid board, already scoped, already crowded, sometimes already wired for a competitor. The information that would have let you get there early existed for weeks — in public records — but nobody on your team saw it in time.

This post walks the commercial project lifecycle signal by signal, shows where each signal is published, and then looks at what it takes to watch those sources continuously instead of assigning someone a Friday portal-checking rotation.

The lifecycle, as a chain of public signals

A commercial project emits public evidence at almost every stage. In rough order:

• Land and planning activity — parcel transfers, rezoning requests, development applications, and site-plan reviews on planning-board agendas. The earliest, noisiest signals: many die here, but the ones that advance are months ahead of any bid.
• Permit filed — a building permit is submitted with a property address, permit type, applicant, and usually a declared value. This is the first signal that is specific, valued, and dated.
• Permit approved / issued — the project is real in the way that matters: someone paid fees and intends to build.
• Bidding — for public work, a solicitation appears on a procurement portal; for private work, the GC quietly assembles subs. By now, everyone watching the bid board knows.
• Award and construction start — contracts sign, inspections begin. For anyone selling into the project, this is late.

Why contractor status is the field that matters

Value tells you whether a project is worth your time. Stage tells you how urgent it is. But contractor statustells you whether it is winnable. Many jurisdictions let owners and developers file early permits before a general contractor is selected, or record the contractor as pending — so “contractor: open” on a commercial permit is a direct signal that the award hasn't happened.

That turns a vague ambition (“find projects early”) into a precise, monitorable specification:

Where the signals are published

• County and city permit portals — the primary source for filings, approvals, values, and applicants. Every jurisdiction runs its own portal with its own fields and formats.
• Planning and zoning agendas — development applications and approvals, usually published as meeting agendas and minutes. Earlier than permits, less structured.
• Procurement portals — bid solicitations, addenda, and awards for public work, published per agency.
• Local business and trade press — announcements that corroborate and sometimes precede the records.

None of these is hard to read once. The problem is reading all of them, every day, without missing the one filing that mattered.

The manual approach, and where it breaks

The standard manual workflow — bookmark five portals, check them weekly, paste anything interesting into a spreadsheet — fails in predictable ways. Coverage stops at however many portals one person can stand to check. A weekly cadence means a signal can be six days old before you see it. The same project gets logged twice under two name spellings, or missed entirely because it appeared on the portal you skipped. And the spreadsheet records what something looked like the day it was pasted, with no memory of what changed since.

Continuous monitoring inverts each failure: sources are checked on a cadence; every record is deduplicated by content so unchanged pages cost nothing; raw payloads are kept as evidence; records resolve to one canonical project entity (permit number and parcel first, name and alias second); every field change is versioned; and changes that match your specification become scored events — permit approved, bid opened, contractor identified — rather than another row to skim.

Scoring: making the queue read itself

Once monitoring is continuous, the bottleneck moves from finding signals to ranking them. A practical opportunity score weighs the project's value against your threshold, its stage (approved and bidding stages score higher than planning), and above all whether the contractor slot is still open. The point isn't precision to the decimal — it's that an $8.7M warehouse at bidding with an open GC slot should never sort below a $600k renovation that was awarded last month.

How Ballast automates this

This signal chain is the flagship use case Ballast was built around. You describe the specification in a guided setup — entities (projects, permits, properties, companies), signals (permit filed, approved, bid opened, contractor identified), coverage, and a value floor — and Ballast generates the formal monitoring spec, checks approved sources on cadence, resolves records into a project graph with evidence and confidence on every field, and delivers scored events to your dashboard, your CRM-bound webhooks, or the REST API. Every new account includes a synthetic Central Florida construction feed so you can see the full loop before connecting real coverage.

The teams that win commercial work aren't reading more bid boards. They're hearing the permit signal first — and calling while the contractor field is still open.