They Already Know Who's Getting the Job
Every contractor in public work has had the thought. You read an RFP and something feels off. The specs are oddly specific. The timeline is unusually short. The required experience reads like a resume for one company in particular. You start wondering if this job was already decided before they published it. Sometimes you are right.
Before you price
This happens. Not always, but more than people say.
Some public contracts are wired. The owner knows who they want, for whatever reason, and the RFP is written to get there. It could be a longstanding relationship. It could be that the incumbent helped write the spec. It could be politics. It could be none of that, and you are just pattern-matching on a legitimately demanding set of requirements.
The problem is that from the outside, a legitimate RFP and a wired one can look almost identical. You cannot always know. What you can do is learn to read the signals.
Proprietary specs that match one vendor exactly
A public RFP is supposed to describe outcomes and performance requirements. When it describes a specific product by name, or lists technical requirements that only one manufacturer meets, that is a signal.
Sometimes this is innocent. The owner used that product before and trusts it. But sometimes an RFP calls for something so specific that you can look it up and find exactly one company that makes it.
If you see spec language that reads like it was copied from a brochure, it might have been. That does not automatically mean you cannot win. It does mean you need to look harder at whether a substitute will be accepted, and how serious the owner actually is about evaluation.
Experience requirements that fit one company's resume
Public RFPs often require relevant experience. Three similar projects completed in the past five years is reasonable. But when the experience requirement gets oddly specific, that specificity is worth noticing.
Five years of experience managing sewer rehabilitation contracts over two million dollars within fifty miles of the city limits is not describing general qualifications. It is describing someone.
If the requirements are written narrowly enough that only a handful of companies in your market could qualify, ask yourself who those companies are. If one of them is the incumbent or has a close relationship with the owner, that is relevant information for your bid decision.
The timeline is designed for someone who already knows the project
Aggressive timelines favor incumbents. The incumbent already knows the facility, the staff, the quirks, and the scope. A new contractor needs time to learn all of that. When a timeline is tight enough that success basically requires prior knowledge of the project, the timeline is a competitive moat.
Watch for bids with unusually short mobilization windows, compressed estimate periods, or start dates that assume you already have materials staged. None of these are automatic disqualifiers. They are worth naming when you are deciding how much time to put into the bid.
The award history tells you something
Before spending estimating time on a public bid, look up who won the last few contracts from this owner. Most public agencies post award notices, and some post bid tabs showing every bidder and their price.
If the same company has won this work for the last several cycles, that is not proof of anything. But it is context. A contractor who has won four consecutive awards from the same agency has a relationship, institutional knowledge, and probably a price advantage from not having to price unknowns.
This does not mean you cannot beat them. It means you should factor in what it will cost you to compete from zero when they are competing from a base of existing knowledge.
Addenda that appear right before the deadline
Addenda are normal. Owners issue them to answer questions, fix errors, and update requirements. But addenda that come out right before the bid deadline and significantly narrow the spec deserve attention.
An addendum issued two days before bids are due that adds a new requirement, changes the evaluation criteria, or removes an alternate that most bidders had priced is worth a second look. Sometimes these changes reflect legitimate feedback from the pre-bid meeting. Sometimes they reflect a late decision to make sure only one company qualifies.
If you see a last-minute addendum that seems to help a specific type of bidder, flag it and decide whether it changes your number or your decision to bid.
What to actually do about this
If you suspect an RFP is wired, you have a few options.
Send an RFI. Ask the specific question that would expose the requirement. Will substitutes be accepted for the proprietary spec in Section 3? What is the basis for the minimum experience requirement? A legitimate owner will answer straightforwardly. An owner who wants to discourage your bid will often make the answer complicated.
Check the award history. See who has been winning this work. If it is always the same contractor, decide whether the relationship or the price is the barrier, and whether you can compete on either.
Calculate what the bid actually costs you. If a competitive bid takes your estimator two days, and you are probably going to lose, is this where those two days should go? Sometimes bidding a long shot is worth it for practice, for getting on an approved vendor list, or for showing up on the owner's radar. Sometimes it is not.
You can also bid anyway, on purpose. A competitive bid that comes in close sends a signal to the owner that they are paying more than market. Even if you lose, you are in the conversation for the next cycle.
The honest version
Most RFPs are not wired. Most public owners are trying to run a fair process and buy the right thing. The ones that are wired are a small fraction.
But your time is real. Two days of estimating on a job you will not win is two days not spent on something you can. Learning to read the signals is not cynicism. It is bid management.
The goal is not to avoid all competition. It is to compete where competing makes sense.