How to Find Construction Projects Before the RFP
A construction project is public long before its RFP is issued. It surfaces first as a bond or levy, then a capital plan, board minutes, an architect selection, and permits — each a public record. By the time the RFP posts, the decisions that mattered most are usually already made.
The public trail a construction project leaves before the RFP
Every publicly funded construction project, and most large privately funded ones, leaves a record long before a vendor ever sees a request for proposal. The record runs in a fairly consistent order, and each stage is visible to anyone who knows where to look.
It starts with financing. A school district, municipality, or hospital system that wants to fund new construction usually needs a bond or a levy. A bond is debt, typically approved by voters or by a governing board, repaid over years out of future tax revenue, and it is the standard mechanism for a single large capital project like a new building or a major renovation. A levy is an ongoing tax rate directed at a purpose; depending on the state and the entity, it may fund smaller capital work or operating costs rather than one large project. Either way, the vote or the board action is public, and it is the earliest reliable signal that a project is coming.
Financing approval feeds a capital plan — a multi-year list of facility projects a board adopts, usually ranked by priority and tied to available funding. Capital plans are typically presented at public meetings and often published as board packets or budget documents. From there, the project moves through board minutes: the recurring public record of what a school board, city council, or hospital board discussed and voted on, including project scope changes, site selection, and budget updates that never make it into a press release.
Next comes architect selection, frequently run as a qualifications-based process with its own public notice, followed by design: schematic design, then design development, where the project's scope and systems get defined in enough detail to estimate cost. Permits get filed with the local building or planning department once design is far enough along, and those filings are public records in nearly every jurisdiction. Procurement, the formal purchasing process which may include prequalification or a bidders list before a single RFP goes out, is usually the last stage before the RFP itself.
Bond or levy, capital plan, board minutes, architect selection, design, permits, procurement, RFP. Every stage before the last one is a public record. Most sales and business development teams start watching at the second-to-last stage or the last one.
Why the influence window closes before the RFP is issued
By the time an RFP is posted, the scope is written, the budget is set, and in many cases the specification already reflects input from whoever was in the room during design. A vendor who first sees the project at RFP stage is competing on price against firms that helped shape what is being asked for — sometimes literally, when a specialty contractor or supplier consulted with the architect during design development.
What "too late" looks like in practice: a bidders list that was already forming during procurement and closed before an unfamiliar name asked to be added; a spec written around a competitor's product or approach because that competitor was in the design conversation; a relationship with the facilities director or business manager that a competitor built over the eighteen months the project moved through capital planning and design, while the RFP-stage vendor is meeting them for the first time. None of that is unfair. It is simply what happens when the only stage you are watching is the last one.
A method for tracking projects at each stage
The practical problem is not that this information is hidden. It is that it is scattered across dozens of sources: county election results, individual district and municipal websites, meeting agenda systems, architect selection notices, building department permit databases, and procurement portals. Each source describes the same project differently at each stage, which makes it easy to lose track of a project as it moves.
A workable method has four parts. First, define the territory as a set of organizations to watch, not a list of open opportunities: school districts, municipalities, health systems, and any other entity type relevant to what is sold, inside a defined geography. Second, assign a record type to each stage: ballot measures and bond results, capital improvement plans and budget documents, board meeting agendas and minutes, architect and engineer selection notices, building permit filings, and procurement or bid postings. Third, set a cadence for checking each source, since board minutes and permit filings post on different schedules than ballot results. Fourth, and hardest by hand, match records to the same underlying project as it moves. A project referred to as "New Elementary Wing" in a capital plan may appear as "District Facility Expansion Phase 2" in board minutes and under a formal project number in the permit filing, with nothing linking them automatically.
Common mistakes that keep vendors out until it's too late
- Watching only the procurement portal or RFP feed. That is the last stage, not the first, and it is where every competitor is already looking.
- Treating board minutes as too dry to read. They are long and often poorly indexed, which is exactly why they are underused — and exactly why the scope and budget changes buried in them are worth finding early.
- Skipping architect selection. The architect shapes the spec during design, and a relationship built during selection is worth more than one built after the RFP is out.
- Losing the project across name changes. Without a way to match records to the same project, a team can be watching a district closely and still miss that "the wing addition" from the capital plan is the same project as the permit filed six months later under a different name.
- Waiting for a call from a general contractor or architect. That call is a relationship outcome, not a discovery method — it depends on already being known to the people who make it, which is exactly the position a vendor tracking projects late has not earned.
Diagnostic questions worth asking about your own pipeline
- Of the projects your team bid on in the last year, how many were first identified at the RFP stage versus earlier?
- Can anyone on the team name the school districts or municipalities in the territory with an active or recently passed bond, without looking it up?
- When a project is lost, is the stated reason ever "we were competing against a firm that helped write the spec"?
- Is there a defined cadence for checking board minutes and capital plans for the organizations in the territory, or does discovery depend on one person's habits?
Tracking bonds, capital plans, board minutes, architect selections, and permits by hand does not scale much past a handful of accounts a week, which is why most teams give up and default to watching the RFP feed. The Sales Intelligence Platform does this continuously: it watches the public record across a defined territory, matches each record to the right project as it moves through stages and changes names, and joins that to what the company already knows about the organization and the people involved, so a rep sees a project the week it enters a capital plan rather than the week it posts an RFP.