GeM Contract Amendment: What's Possible

The contract said on-prem, one directorate, six months. In month two the seller's engineer mentioned that the hosted fallback would be easier until hardware arrived. Someone on the buyer side said fine on a call. Nobody amended the GeM contract. CRAC season became an argument about what had been bought.

GeM contracts can be varied. They cannot be rewritten by chat. This guide separates variations that procurement officers routinely process from changes that need a new bid. Screens change; read the live buyer manual on gem.gov.in. This is not legal advice.

The object stays the object

A contract is a public promise to buy a described article at a described rate under described terms. GeM stores that promise as structured fields. An amendment that updates a date, a consignee address, or a quantity within a sanctioned ceiling is usually still that promise. An amendment that swaps an air-gapped install for a foreign API is a different promise.

GFR contract-management practice, and every finance wing you will meet, will ask two questions: is the variation within the original scope, and is the new value within the sanction. If either answer is no, stop clicking and write a new estimate.

Usually variation versus usually new buy

Change	Typically	Watch
Delivery date slipped because the site was not ready	Extension	Write whose delay; do not hide seller default
Extra user licences of the same listed article	Quantity variation if the bid allows	Financial power and splitting
Additional consignee of the same department	Possible consignee edit	Same article, same rate
Swap hosted SaaS for the on-prem SKU, or reverse	New article	New bid or a documented deviation with eyes open
Add a new workflow that processes a new personal-data class	Often new scope	DPDP and security, not only money
Price increase because the seller's costs rose	Rarely a GeM right	Do not invent a variation clause

Competent-authority approval is not a courtesy copy. A variation that lifts value above the original sanction is a new financial decision. Process it like one. If the original bid went to a secretary, do not let a section officer extend it into a second year because the seller is already in the building. Presence on the VLAN is not a delegation of financial powers.

How the portal thinks

GeM's buyer help has, over the years, offered contract-edit and extension paths that depend on order type, status, and whether invoice or CRAC has begun. Because those paths are versioned, this article will not draw a click-path that will be wrong next quarter. The operational rule is: if the screen will not let you change a field, that is information. Do not route around it with an offline side letter that contradicts the portal.

Side letters are how incidents are born. The incident FAQs already treat post-contract deviations as raiseable facts. A buyer who agreed on WhatsApp and then raised an incident on the original SLA is not being unfair. They are being consistent with the only contract GeM will show an auditor.

Three amendments, only two of which should exist

Security and data changes are almost never amendments

Moving inference from the state data centre to a vendor cloud, even an India region, is a change of means. Adding a new class of personal data to the agent's tools is a change of processing. Turning on training because the model 'needs examples' is a change of purpose. None of those belong in a date-extension screen. They belong in a CISO note, a DPDP role map, and often a new buy.

If the seller proposes a temporary hosted fallback until hardware arrives, treat it as a new article with a start and a stop, or refuse it. A temporary fallback that is still on in month five is the production system. CRAC against the original on-prem tests would then certify a lie. DDOs should not be asked to certify a lie.

Quantity increases need a value check against the original sanction and against the no-splitting rule. Ten extra licences of the same listed article can be honest. Ten extra licences plus a new bureau plus a new workflow is a programme. Programmes get estimates. They do not get a quiet edit because the seller is already on the VLAN.

Keep an amendment log on the file: date, field changed, old value, new value, competent-authority page, portal screenshot. When the incident arrives — and one will, someday — the log is how you show that the contract the portal shows is the contract you meant. Chat exports are not that log.

Playbook before anyone clicks Amend

1. Write the change in one sentence. If the article name changes, stop.
2. Check the live GTC and buyer manual for that contract type.
3. Check financial power against the new total, not the delta only.
4. Check the no-splitting rule if you are about to create a sibling order instead.
5. Get competent-authority approval on paper, then click.
6. Tell the seller that portal fields beat chat.
7. If the change is architectural, involve the CISO, not only procurement.

Service contracts with auto-renew language are a special trap. GeM and the ATC, not a seller email, decide whether a year two exists. If the original bid was six months, year two is a new demand unless the bid wrote an option. Do not 'amend' your way into a standing order that was never competed. That is PAC-by-habit with extra steps.

Objections that lead to bad clicks

The year will lapse if we re-bid. Then extend time on the original object, or seek a proper sanction for a new estimate. Lapse does not authorise a new product.

The seller is already inside the network. That is a reason to be stricter, not looser.

GeM has no field for this, so we will issue an office order. An office order that contradicts the GeM contract is a future incident. Change the portal or change the buy.

File note for a lawful variation

Contract [GeM number] is proposed for variation as follows: [time / quantity / consignee]. The article, rate and security schedule are unchanged. New total value [ ], within sanction [ ]. Live GeM GTC/manual checked on [date]. This is not a change of architecture. Seller chat is not relied upon.

Prcept AI will not ask you to amend an on-prem contract into a hosted fallback. If the site is late, extend time. If the programme grew, write a new bid. Demand the same from whoever is on the other side.

How a buyer or seller should act on this

Treat “GeM Contract Amendment: What's Possible” as an operating problem, not a thought piece. A P2 Procurement who searches “GeM contract amendment” is usually one bid, one CRAC, or one rejection away from a cash event. The file that wins is the one with dates, document names and a named officer — not a paragraph that restates GeM’s homepage.

Some GeM fields can be varied with competent-authority approval. Architecture, category and the article itself usually cannot. Write a new buy when the object changes. That is why this guide ends in artefacts: screenshots of the live portal term, the clause you invoked, and the date you last checked it. GeM, GFR notes and state portals move. A citation without a date is folklore.

Confirm the live GeM FAQ, the current revenue policy and the bid text before you copy any number from a blog — including this one. If the portal and this article disagree, the portal wins. Put the printout in the file.

• Write the purpose of the buy in one sentence a DDO will sign.
• Name the route: catalogue, custom bid, bid, RA, CPPP, or state portal.
• Attach the exemption or preference documents you will actually upload (Udyam, DPIIT, MII, OEM).
• Record who can accept the consignee receipt and who raises the bill.
• Do not invent a category, a PAC, or a price-reasonableness story after L1 is public.

Close this loop before the next CAB

Put “GeM Contract Amendment: What's Possible” 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. “GeM contract amendment” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.