GeM Incident Management: Handling a Complaint

The first GeM incident most AI founders see is not fraud. It is a late delivery on a small professional-services schedule, or a catalogue that promised on-prem and a consignee who thought they had bought a hosted login. The buyer clicks Incident. A clock starts that does not care about your sprint.

Incident Management on GeM is a published process with calendar days, severities and auto-action. This guide is for the seller who has to keep the company able to bid next month. It follows the public FAQs on gem.gov.in/userFaqs/incident and the policy GeM hosts in its manuals section. If those pages move, the pages win. This is not legal advice.

What an incident is, and what it is not

An incident records a deviation. It can be raised against a bid number, a contract number or a catalogue. Buyers, sellers, the system and GeM admin can raise one. For sellers, post-contract incidents are raised from the Incident tab on the dashboard with the New button. You respond on the incident detail page. That is the channel. WhatsApp to the buyer is not the channel.

A helpdesk ticket is also not a substitute. Tickets fix portal problems. Incidents decide whether you remain a seller in good standing. Mixing the two is how people miss an SCN sitting on a different tab.

Clocks from GeM's public incident FAQs (confirm live text)

Event	Published timing	What you do
Creation to bilateral resolution	7 calendar days	Respond, upload proof, try to close facts with the other party
Escalate to GeM	After first comment of the other party, or after 7 days, whichever earlier	If you raised it and it is unresolved, escalate on the portal
Show-cause notice response	10 calendar days	Answer every allegation with documents
Willingness to rectify after escalation (bid/contract)	10 calendar days if the raising party accepts	Offer a dated cure, then do it
Further clarification from GeM	5 calendar days	Reply on the incident page
Un-escalated incident auto-close	37 days from creation if not escalated	Do not rely on this if you are the raised-against party
Appeal	Within the window in IM policy clause 8; FAQ says no second appeal	Helpdesk path plus extra documents the policy lists

Severity is not a vibe

The IM policy defines four severities: Mild, Serious, Severe and Grave. Suspension length follows severity and can increase if deviations repeat inside a defined window. The FAQ does not invite you to negotiate the adjective on email. It invites you to read clause 3 of the policy.

Some reasons are already labelled. Bid or catalogue tinkering and bypassing system validation are described as Grave. Non-payment of transaction charges or AMC is described as a temporary moratorium until payment, for a period the FAQ states. Debarment incidents follow the debarment letter, not GeM's severity table, and need a letter signed at the seniority the FAQ specifies.

Do not invent a scoring formula for how GeM chooses severity. There isn't a public points engine you should role-play. There is a policy annex of reasons and a human-plus-system process. Stay inside that.

Two incidents that look similar and are not

The response pack that usually works

1. Open the incident the same day the mail arrives. Screenshot the reason code and the clock.
2. Write a factual timeline: order, delivery or go-live, PRC/CRAC or service acceptance, messages on GeM, messages off GeM.
3. Upload the contract, the SLA page, the delivery proof, and any buyer acceptance. PDFs, not a pitch deck.
4. If you can cure, say so in one paragraph with a date. Use the rectification / consent path the FAQ describes for bid and contract incidents.
5. If you cannot cure because the allegation is wrong, say so without adjectives. Quote the clause.
6. Assign one human to refresh the page daily until closure. SCN and clarification clocks are easy to miss.

Mutual resolution is a seller-initiated request on bid and contract incidents, not on catalogue incidents and not on incidents GeM admin created. Before action, the buyer can accept. After action, the primary buyer or HOD path applies, once to each, on the FAQ's terms. Use it when the facts are actually cured. Do not use it as a shrug.

Objections that make incidents worse

If we respond we admit guilt. Silence is treated as a fact pattern. The FAQ's auto-action sentence is the whole answer.

We will sue. You can still miss a 10-day SCN. Parallel legal strategy does not stop a marketplace clock.

The buyer is wrong so we will wait them out. Un-escalated incidents can auto-close after 37 days if the raiser does nothing. If you are the raised-against party, waiting is how SCN and auto-action find you.

We will change the catalogue after the incident. The FAQ says there is no rectify-the-deviation option on a catalogue incident in the same way. Fixing the listing later does not erase the reason already raised.

Roles inside the firm

Incidents die when everyone is cc'd and nobody owns the page. Name three roles before the first one arrives. The contract lead writes the timeline. The technical lead gathers delivery evidence. A director signs any SCN response that admits a miss or offers a cure. Sales may speak to the buyer about the work. Sales may not be the only person who has the GeM password.

Keep a standing evidence folder per contract: signed ATC, SLA page, kickoff minutes, go-live mail, acceptance test, CRAC screenshot, change requests, and every portal message. When an incident cites late delivery, you should be able to upload that folder in an hour. Building it after the SCN is how people invent dates.

Catalogue incidents need a different owner: whoever publishes listings. A product marketer who edits titles to chase search will eventually write a Grave reason. Give them a rule. If a field is blocked, they stop. If they want a new attribute, they petition a category. If a buyer asks for a special title that is not the article, they refuse in writing.

Appeals are scarce. The FAQ says there is no second appeal, and some debarment paths sit outside GeM's clause 8. Treat the first appeal as the last structured chance. Extra documents mean extra documents, not a longer adjective. If counsel is involved, they still file through the helpdesk path the policy names, unless they have chosen a court. Parallel heat on social media during an open SCN is how you look like a firm that cannot keep a clock.

Playbook for the week an incident lands

• Hour 1: log in, download the IM policy, assign an owner, notify the contract lead and the CFO if charges or suspension are in play.
• Day 1: portal response with timeline and evidence. No marketing language.
• Days 2–6: cure if you can; request consent to rectify if the FAQ path fits.
• Day 7: if you raised the incident and it is unresolved, decide whether to escalate. If you are raised-against, do not assume the buyer forgot.
• SCN day 0–10: treat as a board item. If GeM seeks clarification, the 5-day clock is shorter than your weekly meeting.
• After action: appeal once, on time, with the extra documents clause 8 wants. Or mutual-resolve through the HOD path if the buyer is willing.

File note for the contract folder

Incident [number] received on [date] under reason [code]. Owner: [name]. Portal response filed on [date] with [list of PDFs]. Cure offered / not offered because [fact]. SCN received / not received. We will not discuss this incident except on the GeM page and in this folder. Appeal deadline, if any: [date]. This note tracks process. It is not a legal opinion.

Prcept AI treats GeM incidents as operational clocks. On-prem delivery evidence and a written training ban make most service disputes factual. Keep your own evidence that clean, whoever you buy from.

How a buyer or seller should act on this

Treat “GeM Incident Management: Handling a Complaint” as an operating problem, not a thought piece. A P5 Founder who searches “GeM incident seller” 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.

A GeM incident is a clock, not a comment thread. Respond on the portal, inside the published calendar days, with documents. Silence becomes auto-action. 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 Incident Management: Handling a Complaint” 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 P5 Founder, not “the vendor.”

Revisit the item when the model, the GeM term, the region, or the SI changes. “GeM incident seller” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.