An RFP Template Departments Can Actually Reuse

A directorate rewrote its AI RFP from a blank page for the third year running because the last two documents had become unreadable novels: manpower annexures, SCADA leftover SLAs, a 22-language claim, and a security paragraph that said best practices. Each rewrite missed a different clause. Each pre-bid rediscovered the same silences. The officers were diligent. They lacked a skeleton that was allowed to be short.

This is a reusable skeleton for a department that wants an agent, not a 200-page custom MIS. It is not a downloadable statutory form. It will not click into GeM by itself. Category templates change; read gem.gov.in and your CPPP pack. It is the chapter list you copy, then delete from. A short marked document beats a long unmarked one.

Not legal advice. Your counsel, finance, CISO and DPO still own the words that bind you.

The spine — ten chapters, then stop

If you need an eleventh chapter, write why. Most eleventh chapters are inherited manpower or a vendor PDF.

Copy this contents page. Each chapter must contain something an evaluator can fail.

Chapter	Must contain	Delete if
1. Object and outcomes	Named workflows, what success looks like in officer time and error	You only have a slogan ('AI transformation')
2. Data and roles	Fiduciary/processor, classes, training ban, location	No personal data and you can swear it
3. Languages	Year-one rows, scripts, code-mix, eval set	English-only and you mean it
4. Architecture and isolation	On-prem / air-gap / hosted, Schedule A, load path	You are honestly buying hosted FAQ
5. Security and audit	RBAC, logs, keys, CERT-In clock, trail fields	Never — even hosted needs this slice
6. Human gates	Who may approve, under what DFPR or local delegation	The agent never proposes an action
7. Commercial shape	AMC / subscription / hybrid, units, exit	You have not decided the object — stop and decide
8. Delivery clocks	Predecessors: media, capacity, SIEM, DPA	You prefer a ceremony date to a clock
9. Evaluation	Mandatory fails, scored rows, demo sheet, references	You intend to mark by applause
10. Integrity and provenance	No exclusive brands, register of vendor inputs	Never

How to reuse without rotting

Keep a department master that is empty of product names and of last year's dates. For each buy, fork it. Fill the language table from this year's tickets. Fill Schedule A from this year's CISO. Fill the commercial shape from this year's architecture note.

Do not reuse manpower minima, brand rows, or a 22-language tick. Those are how skeletons become corpses.

Version the master. A later CAG or internal audit should see which skeleton you started from and what you changed.

GeM and CPPP are wrappers, not the skeleton

The skeleton is the ATC, the scope of work, the annexures. The portal is how you publish and receive. Do not let a category's default SLA — written for a different object — silently override chapter 7. If it will, write the override or change category.

This is not a 'download the RFP' file in the sense of a single Word document that you upload unchanged. Anyone selling you that is selling last year's novel.

• One page of definitions that defer to DPDP for statutory terms.
• Annex S security, Annex L languages, Annex A egress, Annex C commercial.
• A consolidated reading copy after every corrigendum.
• A delete-if rule on every inherited paragraph.

What not to copy from the last SI RFP

Eight onsite engineers. Biometric attendance. Java CVs. 99.99 percent uptime with no definition of the transaction. Source-code deposit of a foundation model you will never compile. A requirement to 'provide AI' as a man-month. Those clauses fight the object. They also select the wrong bidders.

Also leave out last year's ceremony date, last year's GPU brand, and last year's '22 official languages' tick. Those three travel from file to file like a virus. The skeleton exists so you can see them when they try to re-enter. A master that still contains them is not a master. It is last year's novel with a new cover.

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.

Our legal cell wants the 90-page familiar document.

Give them the ten chapters plus the organisation's standard GCC. Familiar liability clauses can live. Familiar manpower novels should not. Show them the teardown in this cluster.

A short RFP will look unserious.

A short marked RFP looks like an adult. Length is not seriousness. Failable rows are.

We need flexibility to add chapters later.

You can corrigendum. You should not publish a hollow spine. Empty chapters are silences. Silences become fights.

One template cannot fit a campus and a ministry.

The spine can. The fills cannot. That is why you fork. A campus hostel agent and a parliamentary-assurance agent share isolation and data chapters; they do not share the outcome sentences.

A worked fork so the skeleton is not abstract

Suppose the department is buying a grievance-drafting agent for one directorate. Chapter 1 names three outcomes: first draft in the officer's noting style, no invented circulars, reject path used. Chapter 2 names the fiduciary as the directorate, the processor as the vendor, and a training ban that includes traces. Chapter 3 names Hindi Devanagari and Hindi–English code-mix, not twenty-two languages. Chapter 4 says on-prem, Schedule A empty, hashed load path. Chapter 5 pastes Annex S. Chapter 6 stops citizen SMS and any register change for a named under-secretary. Chapter 7 is appliance plus AMC, no heartbeat. Chapter 8 lists media SOP and SIEM landing as department predecessors. Chapter 9 attaches the demo sheet and the reference questions. Chapter 10 records the three vendor PDFs received in March and states they were not pasted.

That fork is ten pages if you are generous, four if you are strict. It can be marked. A 90-page SI novel with the word agent in the title cannot. When the next buy is a campus hostel desk, you change chapters 1, 3 and 6 and leave the rest. That is reuse. Copy-pasting last year's GPU brand is not.

Stand up the master in fifteen days

Do this once at department level, then fork per buy. Do not do it inside a live bid panic.

1. Days 1–5: paste the ten chapters. Delete what you will never mark. Add your GCC.
2. Days 6–10: CISO, DPO, procurement, a user officer. Each owns one annex.
3. Days 11–13: strip product names. Add the delete-if rules.
4. Days 14–15: competent authority notes that this is the master. The next buy starts here, not from a blank page.

How this shows up in the file

The master lives with a version number and an owner. Each buy's fork records the version it came from. That is the reusable template, not a PDF on a consultant's laptop.

If someone asks for a 'download', give them the contents table and this article. Then sit with them to fill chapter 1. Unfilled chapter 1 is how templates become novels again.

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 “government AI RFP template download” is usually drafting or scoring a bid. “An RFP Template Departments Can Actually Reuse” belongs in eligibility, the evaluation matrix, or a numbered annexure. If it only lives in the covering note, L1 will ignore it.

Reuse a skeleton, not last year's SI novel. Object, data, languages, isolation, security, commercial shape, eval, exit. Delete any chapter you will not mark. 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 “An RFP Template Departments Can Actually Reuse” 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. “government AI RFP template download” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.