Bidder Conferences
Procurement technique · See it on the map
Guide only — The technique is holding the conference.
A meeting where every prospective vendor asks questions before proposals are due, so everyone hears the same answers.
When to use it
When you are asking more than one vendor to bid on the same substantial piece of work and the requirements are complex enough that vendors will have real questions — a construction bid, a multi-vendor RFP for a significant system. It only earns its cost when there is enough at stake, and enough vendors, to make fairness worth formalising.
When to avoid it
For a small engagement — one or two vendors, a modest budget, straightforward requirements — a bidder conference is disproportionate: it costs everyone's time to formalise a conversation that a phone call would settle. Answer questions directly instead, and document the answer if more than one vendor is in play.
Steps
What it produces
- A written question-and-answer record distributed identically to every bidder
Common pitfalls
- Answering a question by phone or email to one bidder afterward without sending the same answer to everyone else — a single side conversation defeats the entire point of holding the conference.
- Treating verbal answers given in the room as final without writing them down, so bidders leave with different memories of what was said.
- Running one for a purchase small enough that the formality outweighs any benefit.
Worked example
A city library district puts a new HVAC system out to bid among five contractors. At the mandatory pre-bid conference, one contractor asks whether asbestos abatement is included in scope. The facilities manager answers in the room and later emails the same answer, verbatim, to all five contractors — not just the one who asked — so every bid is priced against the same understanding of scope.
Source
- PMBOK-6 §12.2.2
Where it comes from: this technique is named by the PMBOK Guide, 6th edition.