Two-Envelope Bidding for AI: A Walkthrough

The e-procurement clock hit 15:00. Technical covers opened. Someone in the second row already had a printout of commercial totals because a bidder had mailed the complete set to the indentor the night before. The chair pretended not to see the printout. Marks that afternoon were kind to the cheap stack. Two-envelope had been a folder structure, not a discipline.

Two-bid or two-envelope practice — technical and financial sealed separately, technical opened first, financial opened only for the qualified — is ordinary Indian hygiene. GFR states it for high-value plant and machinery in the goods chapter and, in the consulting chapter, as the ordinary way to receive proposals (technical first). QCBS, where your manual allows it, usually sits on that sequence. The sequence does not by itself score isolation or refuse a brochure. It only stops price from writing the technical minutes if you let it.

This walkthrough is for the officer who will actually run the sittings for an agent-platform bid. It is not a portal manual. Screens on GeM and CPPP change; the duty not to contaminate the technical sitting does not.

What two-envelope is not

It is not QCBS. You can open technical first and still award L1 among responsive bids. QCBS adds a published quality score and a formula. Do not tell the committee they are doing QCBS because there were two PDFs.

It is not a substitute for a fail-able specification. Two envelopes around a four-row brochure still produce a cheap brochure. It is not a reason to hide the matrix. Publish the technical test with the bid. Secrecy is for the sealed financials and the sealed hold-out items, not for the rules of the exam.

The sequence, in language a minute-taker can use

Publish: what goes in envelope one (technical, compliance, artefacts, presentations if any), what goes in envelope two (prices only), the portal equivalent of those envelopes, the qualification threshold or responsiveness test, and who may attend which opening.

Receive both before the deadline. Late financials do not get a private second chance. If the portal splits the packets, trust the portal clock, not a courier story, unless your rules say otherwise. Open technical. Record who is present. Collect devices if you must. Do not open, preview, or sanity check financial files. Evaluate against the published matrix. Sign the technical minutes, including fails and dissents.

Notify qualified bidders of the financial opening. Open prices. Apply L1 or the QCBS formula you published. Stop if someone produces a number that was not in the sealed packet.

Contamination events and what the chair should do.

Event	Why it breaks two-envelope	Chair's move
Bidder mails a combined PDF before opening	Price is in the technical room	File it unread into a sealed commercial cover; minute the attempt
Member asks for a ballpark to plan the budget	Marks will chase the ballpark	Refuse. Budget was supposed to exist already
GeM/CPPP preview shows a rate	Portal misuse	Stop the sitting; write to the admin; do not pretend you un-saw it
Technical marks revised after prices known	The classic integrity failure	Do not. If a genuine arithmetic error exists, legal and vigilance, not a quiet edit
Unqualified bidder's price accidentally opened	Now everyone knows a number that should not count	Minute it; do not use it; take counsel before continuing

Ways AI bids specially mess this up

Technical presentations that include total cost of ownership slides. Ban price from the technical presentation. If they show it, stop the slide. Token calculators in the technical annexure that only work if you assume a volume, which is a price. Move calculators to the financial envelope; keep the unit definition in technical.

PoC vendors who already quoted informally. Those quotes must not sit in the evaluation folder. The estimate file is a different folio. QCBS formulas that someone tweaks after seeing that quality marks did not save the isolated bidder. The formula was published. Tweaking it is a new bid.

Minutes that a later officer can defend

Technical minutes name each published row, the artefact seen, the band, and dissent. They do not say committee after detailed deliberations awarded 36 marks. Financial minutes name the packet hashes or portal print, the arithmetic, and the formula. They do not reopen technical stories.

If a representation arrives, you should be able to hand over those two minutes and the published matrix without writing a novel.

1. Publish packet contents, threshold and formula.
2. Open technical only; police price talk.
3. Mark artefacts; sign; then open finance.
4. Apply the published method. Stop if contaminated.
5. Keep the two minutes on separate folios.

Objections you will hear — and what to do with them

These are the lines that stall the file. Answer them in the room, then put the answer in the note. A spoken answer without paper will be forgotten by the next officer.

On GeM everything is visible anyway.

Check the live workflow for your bid type. If the portal cannot hide financials, write how you will still evaluate technical first — different officers, sequenced reports — or choose a channel that can. Do not use folklore about 2019 GeM as the file.

Two-envelope slows us down.

It adds a sitting. A representation after a contaminated sitting adds a year.

Our committee is senior enough not to be influenced by price.

Then they will not mind not seeing it. Seniority is not a Faraday cage.

We already know who is cheaper from the PoC.

Then you are already contaminated. Do not pretend the envelope will save a number that lives in the chair's memory. Extra care, or a different committee.

Run one clean two-envelope cycle

1. At float: publish packet map, matrix, threshold, formula if any.
2. At pre-bid: ban price talk; remind PoC vendors that old quotes are not in the room.
3. Technical week: no devices with commercial PDFs; signed minutes before any financial appointment is booked.
4. Financial week: open, apply, stop if a stray number appears.
5. After award: keep the two minutes and the hashes with the file for the audit cycle you actually face.

How this shows up in the file

Subject: Two-envelope procedure for the agent-platform bid.

Technical and financial packets will be received together and opened in sequence. Technical evaluation will use only the published matrix and artefacts. Financial packets will remain unopened until technical minutes are signed. QCBS, if used, is a separate, published formula, not a synonym for two PDFs. Any contamination event will stop the sitting pending advice. This note is not legal advice.

Rule 163 and Rule 187 are not the same sentence

In the goods chapter, GFR describes a two-bid system for high-value plant and machinery: technical and financial received together, technical opened first. In the consulting chapter, proposals are ordinarily asked for in two bids, with the technical proposal opened first (Rule 187 is the usual hook officers cite). Do not write a note that pretends one rule covers every software object. Name the chapter you are actually using.

Two-stage bidding is a different animal: you do not yet know the specification well enough to ask for a final price. Agent platforms sometimes look like that when the department cannot write workflow cards. The honest move is to write the cards or to buy a short, data-poor discovery. The dishonest move is to call a two-envelope NIT two-stage because the words both contain two.

Put the live rule number, the portal packet names, and the published matrix on the first folio of the evaluation file. A later officer should not have to guess whether they inherited QCBS, L1-after-filter, or a contaminated sitting. The walkthrough above is only as good as that folio.

This article is a field guide for Indian public buyers, not legal, procurement, financial or audit advice. Confirm every citation against the live GFR compilation on doe.gov.in, the relevant DoE procurement manual, GeM terms, CVC guidance and your own counsel before a sentence enters a tender file.

How to put this in the RFP, not the preamble

A P2 Procurement who searches “two envelope bidding process” is usually drafting or scoring a bid. “Two-Envelope Bidding for AI: A Walkthrough” belongs in eligibility, the evaluation matrix, or a numbered annexure. If it only lives in the covering note, L1 will ignore it.

Two-envelope is a sequence, not a quality miracle. Open technical first, sign the marks, then open price. If a laptop in the room already has the commercial PDF, you are running one envelope. QCBS weights are a choice you must publish before opening. Accuracy is a task plus a dataset, not a slogan. SLAs for agents must name tool-calls, human gates and log export — uptime alone is a hosting metric.

Do not let a vendor write the specification and then bid on it. Record unsolicited proposals. Pay for pilots that touch personal data. Write exit before you write go-live.

1. Move the control from the preamble into a scored or eligibility row.
2. Attach a one-page definition (accuracy, SLA, language, data handling).
3. Require an artefact in the technical bid, not a slide.
4. Extend the bid date if a corrigendum is material.
5. Minute the demo on your data, offline if you claimed air-gap.

Close this loop before the next CAB

Put “Two-Envelope Bidding for AI: A Walkthrough” on the next change-advisory or bid-opening agenda as a single line item with an owner. If it cannot earn a line item, it will not earn a control. The owner should be a P2 Procurement, not “the vendor.”

Revisit the item when the model, the GeM term, the region, or the SI changes. “two envelope bidding process” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.