Buyer-Side GeM Guide for Department Staff

The new section officer had buyer rights, a login, and a secretary who had said 'just do it on GeM' in a review. Nobody had said which instrument. Direct purchase of a catalogue item that was not the work. A custom bid whose ATC was pasted from a desktop-supply tender. A PAC conversation that cited the wrong GFR rule. Three weeks later finance asked for the reasonableness note.

Buyer-side GeM is not seller-side GeM inverted. The seller is trying to stay responsive. The buyer is trying to stay legal, auditable and able to receive the thing the department actually needs. For agentic software that last part is the hard one, because the catalogue language was not written for an on-prem agent that must not train on a citizen corpus.

This guide is for department staff — DDOs, section officers, university store-purchase clerks — who will press the buttons. It is not a substitute for the live GeM buyer FAQs or the GFR compilation on doe.gov.in. It is the sequence we wish every first AI purchase had used.

Start from the need, not from the button you were shown

Write four sentences before you open the portal. What work will the agent do. Where will it run. Which data classes it will touch. Who is the competent authority for this value. If you cannot write those sentences, you are not ready to choose Direct Purchase, L1, bid or PAC-on-GeM.

GFR 2017 Rule 149 is the Central rule that points buyers at GeM when the goods or services are available on GeM, subject to the conditions in the live compilation. It is not a command to crush a novel on-prem agent into the nearest catalogue row. If the category is a bad fit, the work is to choose the right GeM instrument or to record why a different route is being used — not to pretend a laptop category is an agent platform.

States and autonomous bodies may have adopted GFR language, or they may have their own stores codes. Confirm which book you are under before you tell a vice-chancellor that 'GeM is mandatory' as if it were a statute of general application.

Pick the instrument on purpose

Direct purchase of a listed item is for when the catalogue item is the work. An agent platform with deployment, integration and a no-training clause is rarely that item. Buying the wrong SKU because it is fast is how you spend a year arguing about what was ordered.

A bid — including a custom bid — is the honest path when specifications matter. That is where you write on-prem, air-gap, Indian legal entity, no training on department data, and the evaluation table. It is slower than a click. It is faster than an incident.

PAC buying, when someone in the room says only one firm can do this, is not GFR Rule 161. In GFR 2017 the Proprietary Article Certificate lives with Single Tender Enquiry under Rule 166. On GeM, PAC still carries extra diligence on price reasonableness, commonly read with Rule 149. Do not let a vendor draft the certificate you will sign.

The button is not the legal basis. The note that chose the button is the legal basis.

Instrument	When department staff should consider it	What the file must still show
Catalogue / direct, within the live threshold	The listed item is actually the deliverable	Need, competent authority, and why this SKU matches the work
Comparison / L1 among listed items	Several catalogue items genuinely compete	The comparison extract and that specifications were not bent to a favourite SKU
Bid / custom bid	Specifications, SLAs or deployment decide the work	ATC, evaluation table, responsiveness, reasonableness if competition is thin
PAC on GeM	Only after a Rule 166-style proprietary case is honestly made	PAC signed by the department, finance concurrence as required, extra rate diligence
Outside GeM	When the live GFR / departmental rule actually allows it	The written reason, not a verbal 'category does not fit' after the fact

Writing an ATC that an agent can be marked against

Do not paste a hardware ATC. Spare-part depots, OEM authorisations for servers you are not buying, and 'three similar works of 80 per cent of estimated value' copied from a civil tender will either lock you to an incumbent SI or lock out every honest startup the secretary said they wanted.

Write rows a stranger can fail. Where does inference run. Are prompts, embeddings and traces stored only on named systems. Is training on department data contractually forbidden. What happens on exit. Who owns fine-tunes. What evidence is due in the technical packet, not in a post-award workshop.

If you want MSE or startup participation, say which documents you will honour, and do not simultaneously demand five prior Central Government work orders of the same shape. You can prefer experience. You cannot pretend you also prefer first-timers.

• Deployment: SaaS / departmental rack / SDC / air-gapped — pick one primary, allow an alternate only if you will mark it.
• Data: no training on customer data; deletion and export on exit; log retention that can meet CERT-In-style clocks if they apply to you.
• Identity: the legal entity you will pay, and whether consortium is allowed.
• Evaluation: document marks versus price, and whether any demo carries marks.
• Service: response times you can measure, not '24x7 world-class support'.

During the bid, and after someone is unhappy

Answer pre-bid queries in writing on the portal so every seller sees the same amendment. A telephone clarification to one founder is how award challenges start.

Open technically first when the bid says you will. Do not peek at prices while you are still deciding responsiveness. GeM’s workflow is there to protect you from yourself.

If an incident is raised, read the buyer incident pages on gem.gov.in. Some steps cannot be 'mutually closed' by the department once GeM admin is in the matter. Do not promise the seller a closure the policy does not give you.

The conversation finance will actually have

Finance is not trying to kill AI. Finance is trying to see sanction, competent authority, the instrument, the rate, and the clause that says the department is not buying a never-ending cloud subscription by accident.

Bring them a one-page note: need, instrument, estimated value, why GeM, why this category or custom bid, how preference rules will be applied, and how you will test price reasonableness if only one packet is responsive.

If the vendor is offering a 'pilot at rupee one' that becomes a three-year platform, say so. Hidden years are how GeM transactions turn into audit paras.

What officers say when the portal feels like the policy

These are the shortcuts we hear in stores sections. They create the March audit para.

If it is on GeM we are automatically covered.

GeM is a marketplace and a process. Coverage still depends on the instrument, the ATC, competent authority and reasonableness. A wrong SKU on a valid portal is still a wrong purchase.

Custom bids take too long; the secretary wants a demo this month.

Then run a time-boxed paid discovery under a lawful small instrument, with no personal data, or tell the secretary the truth about the larger ATC. A rushed custom bid with a hardware paste will take longer than a careful one.

The vendor can write the ATC. They know the product.

They may supply facts. The department owns the specification. A vendor-written ATC that only one firm can meet is how you buy a challenge and a vigilance question in the same envelope.

Incidents are the seller’s problem.

Buyer-side deviations — cancelling after acceptance without grounds, refusing a conforming delivery — sit on the buyer incident pages. Read them before you act in anger.

Four weeks to a defensible first AI purchase on GeM

This assumes you already have competent-authority interest, not a vague wish.

1. Week 1: write the four sentences — work, runtime, data classes, authority. Decide instrument. If someone says PAC, open Rule 166, not 161.
2. Week 2: draft an ATC with fail-able rows. Circulate to the DPO / CISO for the data sentences and to finance for the value and preference sentences.
3. Week 3: publish, answer pre-bid on the portal only, refuse private clarifications. Prepare the responsiveness sheet.
4. Week 4: evaluate as published, write the reasonableness note if needed, award, and store the portal extract off GeM. Brief the receiving officer on what was actually bought.

What goes in the departmental file

Keep a paper or e-office part that does not depend on anyone’s GeM session: need note, instrument choice, ATC and corrigenda, pre-bid answers, packets, comparative statement, preference arithmetic, reasonableness note, sanction, award extract, and the contract print.

If an incident or representation arrives, file it with the dated reply. The next officer should be able to continue the purchase without calling you on a holiday.

This is a field guide for Indian departmental staff, not legal or procurement advice. GFR 2017 is a Department of Expenditure instrument for the Central Government and bodies that adopt it. Confirm Rule 149 conditions, GeM buyer terms and your stores code on the live sites before you indent.