How to Find Government Projects Before They Become RFPs
If your firm sells services to local government, you already know the problem: by the time an RFP appears on a bid board, the project has been in motion for months. The city engineer has a preferred firm in mind. The budget was approved two quarters ago. The feasibility study was discussed at a committee meeting nobody outside city hall attended.
The opportunity was never hidden. It was published in public documents that most firms never read.
7,881 published pre-solicitation signals (budget approvals, anticipated RFPs, contract expirations, and rebid recommendations) — the signals that appear before formal bid postings.
Recent pre-solicitation signals:
- City of Mendota Heights · Dakota, MN — Budget Allocation (Jun 1, 2026): City of Mendota Heights has allocated $80,000 in its 2026 budget for improvements to the Fire Station Parking Lot. This project is expected to proceed in 2026. [source]
- City of Portage · Columbia, WI — Rfp Anticipated (Jun 1, 2026): The City of Portage plans to upgrade parking areas at Silver Lake Beach and Park within the next two years, with potential funding from the city budget. [source]
- City of Mendota Heights · Dakota, MN — Rfp Anticipated (Jun 2, 2026): The City of Mendota Heights is moving forward with planning for a new combined police station/city hall, with a revised budget estimate of $33. 5 million. [source]
Live proof refreshed June 1, 2026
The Problem With Waiting for RFPs
Formal solicitations are the last step in a process that starts with planning, moves through budgeting and funding, and only reaches procurement after the scope is defined and the money is committed. Firms that wait for the RFP are competing at maximum disadvantage:
- The selection committee already has an incumbent or preferred firm in mind
- You have no relationship with the project manager or city engineer
- Every competitor in your market received the same notification at the same time
- You are estimating a project you had no hand in shaping
Where Government Projects Actually Start
Local government projects leave public traces long before a formal solicitation exists. The key sources are:
- City council and board meeting agendas — staff memos recommending feasibility studies, project authorizations, and consultant selections
- Committee meeting packets — public works committees, finance committees, and planning commissions discuss projects in detail before they reach the full board
- Capital improvement plans (CIPs) — multi-year spending plans that identify specific projects, timelines, and funding sources. Read more about CIP signals
- Annual budgets — line items for design services, construction, equipment replacement, and facility improvements
- Meeting minutes — discussions about aging infrastructure, regulatory compliance deadlines, and facility condition assessments
- Grant and funding applications — state revolving fund applications, USDA grants, and bonding resolutions that unlock project spending
These documents are public. They are posted on government websites, agenda portals, and meeting archives. The challenge is that they are scattered across hundreds of individual government body websites in formats that range from well-structured HTML to scanned PDFs.
What to Look for in Public Documents
Not every agenda item is an opportunity. The signals that matter for business development are forward-looking and specific:
- Authorization of studies — feasibility studies, needs assessments, and condition evaluations are the earliest indicator that procurement will follow
- Budget approvals — when a governing body votes to allocate money for a specific project, the procurement clock starts
- Funding resolutions — bond issuances, grant awards, and intergovernmental funding agreements that commit dollars to projects
- Contract expiration dates — existing service agreements that will need renewal or rebid within 6-12 months
- Staff recommendations — memos from city administrators, public works directors, and facilities managers recommending specific projects or vendor selections
The Manual Approach (and Why It Does Not Scale)
Some firms assign a BD person to check a handful of government websites weekly. This works for a few bodies but breaks down quickly:
- A single state may have hundreds of cities, counties, school districts, and special districts
- Agenda systems vary — CivicPlus, Granicus, self-hosted WordPress, and custom portals all work differently
- Documents are posted on inconsistent schedules — some bodies post packets a week early, others post the day before
- Finding the signal in a 200-page meeting packet requires reading, not just scanning titles
The information is there. The problem is volume, format variation, and the time it takes to read and classify what you find.
How Vendor Radar Automates This
Vendor Radar runs nightly scraping cycles across government websites in Minnesota, Montana, North Dakota, South Dakota, and Wisconsin. Each document passes through a multi-stage extraction pipeline that identifies forward-looking signals, classifies them by service category and signal type, and links every signal back to its original source document.
Instead of checking dozens of websites manually, you get matched signals delivered to your dashboard and email digest — filtered to the service categories and geographic areas you care about.
What This Approach Does Not Do
Monitoring public documents is not a substitute for relationship-building. Early signals give you the starting point for a conversation, not a guaranteed win. You still need to:
- Reach out to project managers and city engineers
- Demonstrate relevant experience and local knowledge
- Prepare responsive proposals when the formal solicitation arrives
The advantage is timing. Knowing about a project six months before the RFP gives you time to do all of that — instead of scrambling to respond in two weeks.