Avoiding Vendor-Written Tender Specifications

A directorate in a line ministry needed an agent for parliamentary assurance drafts. A well-known integrator offered to 'help with the scope, free of charge'. The Word file that arrived had useful process maps and one fatal sentence: the platform must natively support AcmeFlow orchestration and AcmeGuard rails. Only one bidder could say yes without a subcontractor who did not exist. Three firms complained. The file collected a vigilance query. The assurance season arrived with the old Word macros still in use.

This is an opinion, not a charge sheet. Departments are short of people who can write agent specifications. Vendors have those people. Using their diagrams is not a crime. Pasting their product names, thresholds and exclusive interfaces into a competitive instrument is how a fair market dies, and how a CVC-style review later asks questions the file cannot answer. The Central Vigilance Commission has, for years, treated tailored specifications, restrictive eligibility and post-tender alterations as integrity risks. Integrity Pacts exist for the same family of problems. You do not need a new AI doctrine. You need buyer language.

Not legal advice. GFR, your procurement manual, GeM terms, and the CVC circulars that apply to your organisation still govern. Read them on cvc.gov.in and doe.gov.in. This article is the rewrite habit.

What vendor ink looks like on the page

Product names used as requirements. Benchmarks that only one lab publishes. Staffing patterns that match one firm's bench. Data-centre form factors that match one appliance. 'Must have been deployed in three Central ministries' when only one firm has a logo slide that says so. A security annexure that demands a particular SIEM brand. A language row that cites a vendor's own Indic scorecard.

Less obvious: a workflow that assumes the vendor's tool taxonomy; an SLA that is only measurable in their console; an exit clause that returns data in their unique archive format; a training curriculum that is a product course.

The test is simple. Cover the logos. Can two competent firms bid without asking the author for a decoder ring? If not, you have a single-source specification with a bid opening date.

Rewrite the left column before the bid is published. The right column is what an evaluator can mark without blessing a brand.

Vendor sentence	Buyer sentence	Why the rewrite is fairer
Must support AcmeFlow natively	Must orchestrate named tools with an allow-list, logs and a human approval gate	Any stack that can produce the artefacts can bid
Must score ≥ X on VendorBench-Indic	Must meet the department's held-out set attached as Annex L	The buyer owns the pass mark
Eight engineers onsite	Named outcomes, on-call windows, skills, not headcount theatre	Agent platforms are not staff-augmentation SI projects
Compatible only with Brand SIEM	Emit immutable logs to the department SIEM over a stated protocol	Your SOC is not a brand-renewal vehicle

A clean way to use vendor help

You may accept a briefing, a reference architecture, and a list of failure modes. You may run a paid discovery. You record who sent what, on which date, and you put the documents in the file as vendor material, not as the draft RFP.

You then rewrite. The rewrite is the department's work product. A second officer who did not attend the briefing reads it for brand residue. If a phrase can only be satisfied by the briefing vendor, it goes or it becomes a scored preference with a justification.

If the market is genuinely one firm, that is a PAC or a single-tender problem under the rule that actually applies — in GFR 2017, single tender and the PAC live under Rule 166, not under a workshop. Do not launder a PAC through a multi-bid RFP.

Provenance is the defence

When a complaint arrives, the file should show: the problem statement written by the department; the list of vendor inputs; the rewrite; the officers who certified that no exclusive brand remains without a recorded reason. That packet is boring. Boring is what survives a vigilance query.

Unsolicited proposals are a cousin of this problem. Many organisations have a process for them. Do not invent a single Department of Expenditure format that does not exist. Do not secretly turn the unsolicited text into the RFP. Record it. Rewrite it. See the companion piece in this cluster.

• Keep a provenance register: date, sender, artefact, what was reused as an idea, what was discarded.
• Ban product names in mandatory rows unless a PAC file exists.
• Publish enough of the specification that a non-incumbent can bid.
• If you used a paid discovery vendor, say so, and say they are not barred or are barred — pick one, in writing.

GeM does not wash the spec

Putting a tailored ATC on GeM does not make it fair. A custom bid with exclusive clauses is still exclusive. Category templates change; read the live form on gem.gov.in. The integrity question is the same on CPPP and on GeM: could a competent non-author bid?

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.

We do not have the skill to write this.

Then buy the writing as a small, competed professional service, or borrow a sister department's buyer-language annexure and adapt it. Lack of skill is not a licence to hand the pen to a bidder. It is a reason to start earlier.

Everyone does this.

Everyone also answers vigilance queries. The file that shows a rewrite and a provenance register is the file that ends the query. The file that is a vendor PDF with a government letterhead is the file that does not.

The vendor is DPIIT recognised, so bias is not an issue.

DPIIT recognition is an eligibility fact. It is not a waiver of fair specification. A recognised firm can still author an exclusive spec. The rewrite duty does not care about the certificate.

If we rewrite, we will specify something the market cannot deliver.

That is a market-sounding problem, which you solve with a pre-bid, a corrigendum, or a scoped pilot — not by accepting the first vendor's product sheet as the law of the tender.

The second-officer test before you publish

Hand the draft specification to an officer who did not attend any vendor briefing and who will not sit on the evaluation committee. Give them forty minutes and one question: can two firms you have never met bid this without phoning the author? If they circle three product-shaped nouns, you are not done. If they circle an experience cut that only one logo can meet, you are not done. If they say it reads like a data sheet, you are not done.

That officer's marked copy goes in the file next to the provenance register. It is cheaper than a CVC query and faster than a corrigendum after the pre-bid. Departments skip this test because they are late. Being late with an exclusive spec is how you become later.

A three-week rewrite that leaves a clean file

Start this before the bid calendar is announced. A rewrite after the pre-bid looks like you were caught.

1. Week 1: collect vendor inputs in a folder labelled vendor material. Write the department problem in one page with no product names.
2. Week 2: draft functional rows: outcomes, data classes, isolation, language tests, audit trail, exit. A second officer red-pens brand residue.
3. Week 3: legal and vigilance (or the officer who plays that role) read for exclusive eligibility. Publish. Register provenance behind the note.

How this shows up in the file

Three sentences belong in the note. One: the specification is the department's, rewritten from functional need. Two: vendor material received on listed dates is on file and was not adopted as mandatory text except where recorded. Three: no product name remains in a mandatory row without a PAC or equivalent justification.

If you cannot sign those sentences, you are not ready to publish.

This article is informational field guidance for Indian public institutions, not legal, procurement, security-accreditation or engineering advice. Confirm against the current Gazette, GFR, GeM term, CVC instruction, CERT-In direction, DPDP text, departmental manual and your counsel before you file it.

How to put this in the RFP, not the preamble

A P2 Procurement who searches “vendor bias tender specification” is usually drafting or scoring a bid. “Avoiding Vendor-Written Tender Specifications” belongs in eligibility, the evaluation matrix, or a numbered annexure. If it only lives in the covering note, L1 will ignore it.

Letting a vendor draft the specification is how a competitive tender becomes a single-source buy with extra stationery. Rewrite in buyer language and keep the provenance in the file. 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 “Avoiding Vendor-Written Tender Specifications” 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. “vendor bias tender specification” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.