Why first government bids get rejected

Most first bids never lose on price, because the price is never read. They get set aside on compliance first. Here is how that happens, drawn from a real federal RFP.

Brent Thompson · Datum Bid Co. · August 2026

When a contractor loses their first government tender, the notice usually arrives weeks later as one polite line. It rarely says why. Ask anyone who has sat on an evaluation panel and they will tell you the quiet part: before scoring even begins, a pile of bids gets set aside for failing a mandatory requirement. Those bidders spent evenings writing, priced the work sharp, and were out of the running before anyone read a word of it.

To make this concrete, I pulled apart a real solicitation: a Public Health Agency of Canada janitorial RFP for a laboratory site in Guelph, Ontario, which closed in February 2026. It is an ordinary, mid-sized services tender, about 76 pages with one amendment and two rounds of published questions. An ordinary package, and it contained every trap on this list.

1. The missing mandatory

Every tender hides shall-statements: a WSIB clearance certificate current at closing, insurance naming the buyer, a signed form, a declaration. Miss one and the bid is dead at opening. In the Guelph RFP, one criterion required a training strategy including proof of WHMIS training. Not a sentence saying staff are trained. The certificate, attached. A claim without its evidence fails a mandatory just as surely as silence does.

2. The buried gate

From the real RFP

The Guelph tender required attendance at a mandatory site visit. Reasonable enough. But the requirement did not live in the evaluation criteria where bidders look. It sat in the section titled "Communications," and it carried a second, easily-missed condition: confirm attendance with the contracting authority by 9:00 a.m. that same day, with representative names. The document is explicit about the consequence. Offers from non-attendees are declared non-compliant. A bidder who skimmed to the criteria table and priced the job carefully would have been eliminated by a paragraph they never read.

3. The amendment and Q&A trap

From the real RFP

Amendments and published answers legally reshape a tender, and they arrive after most bidders have stopped reading. In Guelph, two things happened. First, the amendment that extended the closing date contained a conflicting date in its own cover text, an obvious typo, but exactly the kind of thing you confirm in writing rather than guess about. Second, a published Q&A answer quietly hardened a requirement: a security registration form that the RFP text implied could be completed later was, per the answer, required with the bid. A bidder working from the original document alone would have submitted without it.

4. The listing that contradicts the document

From the real RFP

The CanadaBuys listing for the Guelph tender advertised selection by "highest combined rating of technical merit and price." The RFP itself said something different: lowest evaluated price among bids meeting all mandatory criteria. No point-rated criteria existed at all. The difference is not academic. Under combined rating you invest in polished technical prose; under lowest-compliant-price the technical section only needs to pass, and the contract is won or lost on the number. Bidders who trusted the portal metadata optimized for the wrong game. The document governs. Always the document.

5. The pricing-table kill clauses

Financial sections carry their own quiet disqualifiers. Three from the Guelph package: any blank price is treated as $0.00, and if you fail to confirm that when asked, the offer is declared non-compliant. The pricing annex separately declares that firm prices for all listed items are mandatory, and failure renders the bid non-responsive "without further consideration." And any indication that the offer is conditional on exchange-rate protection, boilerplate that rides along in many commercial terms, is an instant kill. Five pricing tables, every cell, no passengers from your standard terms and conditions.

6. The brochure problem

Evaluators score against published criteria and weights, with a checklist in front of them. A bid written like a marketing brochure makes them hunt for the answers. They do not hunt. They deduct. "Twenty years of experience" scores zero; a signed reference letter for the same scope of work scores. And most solicitations state plainly that only documents inside the package are evaluated. Links to your website, brochures on request, and reputation count for nothing.

What a compliant submission looks like

The fix is not talent. It is a system, applied without exceptions:

• A compliance matrix: every shall-statement quoted verbatim with its section number, tracked to the exact page of the response that satisfies it, with the evidence attached.
• The response structured in the buyer's order, under the buyer's headings, weighted the way they score.
• A cross-reference table up front that fills in the evaluator's checklist for them: requirement, where it is answered, what evidence is attached.
• Every amendment and Q&A folded in, with anything ambiguous confirmed in writing before the enquiry deadline.
• Submission at least 24 hours early, receipt archived, and a debrief requested after the result, win or lose.

None of this is glamorous. It is careful reading, done completely, every time. That is the entire reason a compliance failure is the most fixable way to lose a contract, and the reason I put my fee behind it in writing.