Glossary term
Two-Envelope Bid System
TERM SUMMARY
A two-envelope bid system is a solicitation procedure in which a supplier submits two separately sealed components: one with the technical and administrative proposal, the other with the price.
- Why it matters
- A two-envelope bid system is a solicitation procedure in which a supplier submits two separately sealed components. One envelope holds the technical and administrative proposal.
- Category
- Canadian government procurement terminology
- Reference role
- This term page is designed to be linkable, crawlable, and easy to quote or summarize.
A two-envelope bid system is a solicitation procedure in which a supplier submits two separately sealed components. One envelope holds the technical and administrative proposal. The other holds the price or financial proposal. The two are kept apart so that the technical evaluation is not influenced by the price.
The technical submission is normally evaluated before the price submission is opened. This preserves the independence of the technical and financial evaluations. Related terms include the two-envelope approach, the two-envelope procedure and, in NATO documents, the double envelope system or "Sealed Bidding (Two Envelopes)." A two-submission procedure follows the same logic but may use electronic or other delivery methods rather than physical envelopes.
How the two envelopes are divided
The split is the same across the procedures documented here. Technical and administrative material goes in one component. Price goes in the other. Each component is evaluated on its own terms, and the evaluations happen in separate phases.
- Envelope one: the technical proposal, and in some solicitations the administrative documents.
- Envelope two: the price or financial proposal.
- Evaluation order: technical first, with the price component opened afterwards.
The NATO double envelope requirements
NATO Joint Force Training Centre (JFTC) states that formal bids must use a double envelope system. Its invitation for bid instructions require an outer package containing two separately sealed inner envelopes. Inner Envelope A holds the technical and administrative proposal, and Inner Envelope B holds the price proposal. Each inner envelope must be separately sealed and identified, including the bidder's name.
NATO notice material also uses the label "Sealed Bidding (Two Envelopes)" for the same procedure. Canadian suppliers pursuing NATO work will meet this wording in solicitation documents.
Use in Canadian federal procurement
The procedure appears in at least two documented Canadian contexts. The first is federally funded First Nations capital projects. Indigenous Services Canada guidance describes a two-envelope approach in which proponents submit one sealed envelope with the technical proposal and another with the financial proposal. The technical and financial proposals are evaluated in two separate phases.
That guidance lists several possible selection methods:
- combined technical-and-price ratings
- lowest price per point
- lowest price after the technical threshold is met
The second context is a CanadaBuys-hosted competitive procurement. A two-stage request for proposals on CanadaBuys uses a "two-envelope" procedure for Phase Two. Proponents submit the technical component in one envelope and the proposed price in a second.
What it means for a supplier bidding on Canadian public contracts
Follow the submission instructions exactly. Separate technical and financial material into the envelopes or submission components the solicitation specifies. Do not place price information in the technical submission where the solicitation separates the evaluations, because the cited procedures require the two components to be submitted separately.
Check how the solicitation will be evaluated. The method can differ from one solicitation to the next, from combined ratings to lowest price after a technical threshold. Where the instructions call for identification on each envelope, as in the NATO JFTC requirements, label each one as directed. Build your bid package so that the technical team and the pricing team can each complete their component without exposing the other's content.