How a Project Actually Gets Bid and Won
14 min read
Picture yourself as an estimator at a mid-size general contractor. Word gets around that a hospitality developer is planning to convert an old downtown office building into a boutique hotel, real money, and exactly the kind of job your firm wants on its resume. But wanting the job doesn't get you in the room. Before anyone talks about price, the developer's team needs to know your firm can actually pull this off. That screening usually happens through a Request for Qualifications (RFQ), a request for your firm's past project experience, financial standing, and safety record, with no pricing involved yet. Out of a dozen firms that respond, the developer shortlists four, including yours. Only then does the real solicitation land: a Request for Proposal (RFP), asking for a full proposal: your proposed team, your approach to keeping the public and neighboring businesses safe during construction, and, finally, a price. Not every project works this way. A city building a new fire station is far more likely to skip qualifications-weighing entirely and issue an Invitation for Bid (IFB) instead, a stricter, price-only process common on public work, where the contract has to legally go to the lowest bidder who meets the requirements, full stop, no matter how good another firm's team is. Some public agencies narrow the field even further, accepting bids only from firms already on an approved prequalified bidders list, screened in advance for financial capacity and safety record, so the agency never has to evaluate a bid from a firm that couldn't actually perform the work. Which document lands on your desk changes everything about how you respond: an RFP rewards a firm that sells its qualifications well; an IFB rewards a firm that prices the job exactly right and follows every procedural rule to the letter.
Quick check: 1 of 5
A public IFB, above almost anything else, has one hard rule. What is it?
Say your firm makes the RFP shortlist. Before you can put a number on paper, someone has to walk the actual building, which is exactly what happens at the pre-bid meeting. A dozen contractors tour the site together, and one of them asks about a suspicious pipe running through the ceiling of the old boiler room. The answer changes everything: asbestos abatement will be handled separately by the owner, not included in the contractor's scope. That single answer could swing every bidder's number by tens of thousands of dollars, exactly why it's worth confirming on site rather than guessing at from drawings alone. Sometimes an answer at the pre-bid meeting, or a mistake the architect catches afterward, is significant enough that it can't just live in one bidder's memory. That's when the architect issues an addendum: a formal, numbered correction sent to every single bidder, so nobody ends up pricing a different project than everyone else. Missing an addendum is one of the most common, entirely avoidable ways an estimator blows a bid: the number comes in based on outdated information, and there's no fixing it once the bid is submitted. Back at the office, the real work of pricing begins with a quantity takeoff, measuring the exact quantities of everything the job needs, straight off the drawings: cubic yards of concrete, linear feet of new partition wall, number of replacement windows. It's tedious, it's exacting, and it's the foundation every other number in the bid gets built on. Get the takeoff wrong and every price built on top of it is wrong too, no matter how accurate the unit costs are.
Quick check: 2 of 5
Why does an estimator attend the pre-bid meeting in person instead of just working from the drawings?
Here's a common assumption worth correcting early: that the lowest number submitted always wins the job. On a public IFB, that's essentially true by law. But on the RFP your firm is chasing for this hotel, it isn't: the developer is explicitly weighing qualifications and approach alongside price, which means a well-qualified firm with a slightly higher number can genuinely beat a cheaper, less-convincing proposal. Knowing which kind of process you're actually in changes how much energy goes into the number versus the story around it. Before your firm's bid can even be submitted, it typically needs to include a bid bond, a guarantee, backed by a bonding company, that if your firm wins, it will actually sign the contract and provide the required follow-on bonds. It sounds like a formality until a firm bids on several large projects in the same month without checking its total bonding capacity, and then can't actually get bonded to sign the one job it wins. Bonding capacity is a real, finite resource, not a rubber stamp. Once subcontractor quotes start coming in, such as electrical, drywall, or plumbing, they rarely line up as cleanly as they should. One drywall quote excludes fire-taping, another excludes material delivery; compared as raw totals, the incomplete quote just looks like the cheaper one. Bid leveling is the unglamorous but essential fix: adjusting every quote so they all reflect the same actual scope before anyone compares numbers. Skip this step, and the "savings" from picking an artificially low number tends to reappear later as a change order, once the missing scope turns out to be required after all.
Quick check: 3 of 5
Two drywall subcontractors quote the same job, but one number is $8,000 lower. What should an estimator check before assuming it's the better deal?
Your firm wins the hotel project. This is where a lot of newcomers assume the hard part is over; it isn't. The number that won the job was built from estimated subcontractor costs, some of them quoted under real time pressure before the bid was even due. Buyout is the process, right after award, of turning those estimates into actual, signed subcontracts, and the gap between the two, in either direction, often decides whether the project makes the profit margin it was bid at. A project manager who rushes buyout and accepts the first quote for a specialty scope like custom millwork, without re-shopping it competitively, can watch that gap eat into the job's margin before a single wall gets built. Every one of those negotiations gets measured against one document: the scope of work, the written, specific description of exactly what's included in the contract price, and just as importantly, what isn't. Almost every payment dispute on a project eventually comes back to this same question: was it actually in scope, or not? A scope of work that says "replace kitchen flooring" doesn't cover the hallway next to it, whatever the owner assumed when they read it. And sometimes, before any of this even happens, the numbers simply don't work: the total bid comes in well over what the developer can actually spend. That's when value engineering comes in: a systematic look for a cheaper material, system, or method that still delivers what the owner actually needs. Swap a custom stone lobby facade for a manufactured stone veneer that looks nearly identical at a fraction of the cost, and the budget gap closes without the owner ever feeling like they got a lesser hotel, as long as whoever's doing the value engineering resists the temptation to cut something the owner will actually notice later, like insulation quality that shows up as a higher utility bill for years afterward.
Quick check: 4 of 5
A subcontractor's buyout price for a specialty scope comes in $30,000 over what was carried in the original winning bid. What does that actually mean for the project?
Zoom back out, and the whole funnel looks like this, in order: qualifications get screened first (RFQ, sometimes prequalification), then the real ask goes out (RFP or IFB), then contractors walk the site and get corrections in writing (pre-bid meeting, addendum), then the number gets built from the ground up (quantity takeoff, bid bond, submitted bid), then competing quotes get made comparable before anyone picks a winner (bid leveling), and even after the contract is signed, the real financial outcome isn't settled until buyout locks in what the subcontractors actually cost, measured against a scope of work precise enough to prevent an argument later. This entire process is the daily world of an Estimator and a Senior Estimator, who build and review these numbers for a living, often supported by a Bid Coordinator who manages the logistics of actually getting a submission out the door on time, and a Preconstruction Manager, who runs the qualification and proposal side of the funnel before a single number gets finalized. A Cost Engineer often picks up right where this lesson leaves off, tracking cost performance once the project is actually underway. If any part of this sounded like something you'd want to do for a living, the Preconstruction & Estimating interview guide walks through exactly how these interviews go, including the fact that some firms will actually hand you a real takeoff exercise to complete on the spot, and the Certified Professional Estimator (CPE) exam guide is a concrete next step if you want a credential that signals you already know this material. If you remember one thing from all of this, make it this: almost every mistake in this lesson is really the same mistake wearing a different hat: someone moving fast and skipping a step that exists specifically to catch the thing they just missed. Skip the pre-bid meeting, miss a site condition. Skip leveling the quotes, miss a scope gap. Rush buyout, miss the number that protects the margin. None of these steps are bureaucracy for their own sake; they're what turns a guess into a number you can actually stand behind.
Quick check: 5 of 5
What's the common thread connecting most of the bidding mistakes in this lesson?
Explore next