Change Requests After Go-Live: Budget for Them

The acceptance certificate was signed in January. In February the scheme notification changed the income ceiling. In March a district split. In April MCC froze the public launch of the fix. In May the vendor said the changes were out of scope. In June the department paid from a training head because nobody had written a change-request envelope. The auditor asked why. Nobody had a schedule. Everyone had a story.

Agentic systems are more sensitive to circulars than a static website. The clerk you bought is a pile of templates, retrieval corpora and rules. Those objects will move. If your bid priced only go-live, you priced a photograph.

This guide is for procurement officers and programme SIs. It is dated 17 August 2026. It is not legal advice. Read GFR or your state finance rules before you write a variation. The method is to expect change, price the unit, and log the act.

Name the changes you already know

Circular change: fees, income ceilings, checklists, deemed-approval clocks. These are not hypothetical. Pull two years of notifications for the workflow and count them.

Master change: village codes, facility IDs, organisation maps after a reorganisation. Legacy quality is not a one-time clean.

Language change: a second register, a corrected refusal line after a complaint, a GIGW fix.

Calendar change: MCC freezes, festival rushes, a cabinet date that moves. Clocks should stop, not pretend.

Legal change: DPDP operational dates, a new UIDAI circular, a court stay on a scheme. The agent must be able to refuse a now-unlawful step.

Put the change in the right envelope.

Event	Envelope	Fail if
Security patch, restart, still no egress	AMC	Vendor invoices a CR to keep deny-outbound
New income ceiling in a gazette	CR — rule and template change	Vendor says 'the model will adapt'
Add a district cohort	CR — scale packet	Thirty logins with no deputies, billed as AMC
MCC pause	Clock stop; maybe CR if remobilising	Liquidated damages on a freeze
Officer wants auto-deny after all	Not a CR — a refused change	A variation that repeals the human gate

Price a unit, not a mood

Write units a committee can count: a template change, a circular ingest with hash, a master-map version, a language pack, a connector purpose-tag change, a cohort dry run. Publish rates. Cap the envelope. Name the competent authority who can approve a draw. Log every draw against the register the governance body already keeps.

Do not hide the envelope as 'comprehensive AI transformation for three years'. Vague value is how you fail a vigilance question and how a vendor pads. Boring rates survive.

On GeM or a state portal, make sure the bid document actually contains the schedule. A side letter is how the next officer finds a surprise. If GFR or your state rules need a variation process above a threshold, write that threshold on the same page.

Two envelopes after the same acceptance

Objections you will hear — and what to do with them

Finance will cut anything called contingency

Then do not call it contingency. Call it a priced schedule of known change types with a cap. Attach the two-year circular count. Finance can dislike a number they can see.

The SI should absorb changes; that is agile

Agile without a unit price is either charity or a later claim. You will not like which one it was when the invoice arrives.

We will use the next budget cycle

Circulars do not wait for your cycle. MCC does not wait. A ninety-day envelope is the bridge. The CIO priority note in this batch is where the next cycle lives.

Unlimited CRs keep us safe

Unlimited CRs keep you unpriced. Cap, log, refuse the change that deletes the human gate.

A four-week playbook before you float the bid

1. Week 1: count two years of circulars, reorganisations and language complaints on this workflow.
2. Week 2: draft unit rates and a cap. Separate AMC. Name the approver.
3. Week 3: write refused changes — auto-deny, public APIs, silent merges, MCC-beating launches.
4. Week 4: put the schedule in the bid, not in a side WhatsApp. Walk it past finance before vendors see it.

File note you can paste

Subject: Change-request envelope for the agentic workflow after go-live.

The bid / contract shall include a priced schedule of change units (templates, circular ingests, master-map versions, language packs, cohort dry runs) with a cap and a named competent authority. AMC shall not be used to smuggle workflow changes or to relax deny-outbound. MCC-affected milestones shall stop the clock. Changes that remove the human gate, send personal data to public APIs, or silent-merge registers are refused. Draws will be logged against the agent register. This note does not authorise a slush fund.

This note is an internal aid. It is not legal or procurement advice.

Prcept AI will sell you a clerk you can change on a rate card. We will not pretend go-live is the end. If a cheaper bid has a zero envelope, ask them who pays for February. If the answer is 'goodwill', you have met the expensive vendor.

How to log a draw so audit is bored

Each draw against the envelope gets a one-page note. Unit type. Rate. Quantity. Circular or master that forced the change. Approver. Hash of the new template or map. Statement that the human gate and deny-outbound did not move. Bored auditors are the goal. A draw that also 'improves the model' without a unit is how goodwill becomes a second contract.

Refuse bundled draws. 'Twenty small fixes' is how a write path appears in item fourteen. One change, one purpose, one hash. If the vendor says that is inefficient, they are asking to hide work. Hidden work is how AMC and CR collapse into an argument.

At ninety days, publish used units versus cap to finance. If you are at eighty percent because the gazette moved, ask for a variation with the same rate card. If you are at eighty percent because the SI is re-selling go-live tickets, stop the draws. The envelope is a control, not a buffet.

This article is informational field guidance for Indian public institutions, not legal, procurement, GFR-interpretation or finance advice. Confirm against the live GFR or state finance rules, GeM terms, CVC expectations, MCC instructions, and counsel before you file it.

How to sequence this in a state, not a slide

“Change Requests After Go-Live: Budget for Them” is a department problem. A P2 Procurement should name the legacy system, the officer who owns the file, and the citizen charter clock before buying “change request government IT”.

Go-live is not the end of spend. Scheme circulars move, village codes split, MCC freezes clocks, and officers find the third edge case. Budget a change-request envelope or you will raid the next head and call it AMC. Do not invent league tables of states. Read tenders and policies. Election Model Code of Conduct can freeze a rollout. NIC is a partner, not a villain. SDC readiness is GPU, power, ops and egress — not a logo.

• Audit the legacy store first.
• Keep mutation and money as officer actions.
• Map SLAs to the citizen charter.
• Budget change requests after go-live.

Close this loop before the next CAB

Put “Change Requests After Go-Live: Budget for Them” 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. “change request government IT” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.

What must be true before you file this

If “Change Requests After Go-Live: Budget for Them” is only a heading, it will not survive a file inspection. A P2 Procurement should be able to attach one artefact that proves “change request government IT”: a log export, a clause, a scored row, a dated notice, or a refusal rule.

Write three dated sentences: what was decided, who owns it, and when it will be re-checked. Unsigned sentences are souvenirs. Dated sentences are controls.

• Name the owner of “change request government IT” inside the institution.
• Attach one artefact a stranger can open next year.
• Revisit when the model, the notice, or the SI changes.
• Do not treat a vendor slide as evidence.