GeM incident management: raising, appeals and suspension

An incident on GeM is the platform’s formal record of a deviation — anything you did (or failed to do) that varies from GeM’s terms and conditions of procurement. It can be raised against a bid, a contract or a catalogue, and it’s the mechanism through which a delivery dispute turns into a suspension that locks you out of bidding for 30, 60 or 365 days.

GeM runs on self-declaration, so it polices behaviour hard on the back end. The current Incident Management Policy (effective 21 July 2025) spells out exactly who can raise an incident, what the timelines are, and what a suspension costs. Most sellers never read it until they’re already inside a show-cause window. Read it now instead — here’s the whole machinery, with the day-counts that matter.

Who raises incidents, and what triggers them

Five parties can raise an incident: the buyer, the seller or service provider (yes, you can raise one against a buyer), GeM Admin, a verifying agency appointed by GeM — and the GeM system itself, which auto-raises incidents from platform data. Nobody has to complain for some deviations to be caught.

The common triggers on the seller side:

• Non-delivery or incomplete delivery. The classic. You accepted the order and didn’t ship, or shipped short or late. (The policy notes these incidents close once the CRAC — the consignee’s receipt and acceptance certificate — is generated, so delivery genuinely completed is your way out.)
• Quality rejection. Supplying goods of inferior or substandard quality against the contract, or delivering fake, counterfeit or refurbished products — the latter is treated far more harshly.
• Wrong catalogue claims. Listing products with specifications, certifications or OEM status you can’t back up. Catalogue incidents are pre-contract incidents, and there’s no rectification option on those — the offending offering gets removed and action follows.
• Service-contract failures. Non-compliance on service contracts, not honouring warranty obligations, delaying wages or statutory payments (PF, ESI) for staff deployed at the buyer’s site.
• Not producing documents — certificates, test reports — when asked during inspection or assessment.

Deviations are graded into four severity levels: mild (impacts other stakeholders), serious (potential to adversely impact the market ecosystem), severe (adversely affects the procurement process or breach of contract), and grave (damages the credibility of the platform itself). The severity grade drives everything that follows, and GeM Admin has discretion to assign a level where a deviation isn’t already listed.

The timeline: 7 days to resolve, 5 to respond, 10 before the system acts

For post-contract incidents, the sequence runs like this. Every number below is calendar days, from the policy itself.

Stage	Window
Resolution between buyer and seller before escalation	7 days from incident creation
Your response to the show-cause notice (SCN)	5 days (warning if silent)
System acts automatically if SCN still unanswered	10 days after SCN issue
Reply to a “further clarification” from GeM Admin	5 days
Auto-closure if the raising party never escalates	37 days from creation

Stage one: resolution. Once an incident is raised, the party it’s raised against gets a resolution period of 7 calendar days to rectify the deviation and report it through the IM module. Fix it here and the reporter can close the incident — no further action, no mark. This window is the cheapest exit you will ever get. Use it.

Stage two: escalation and show-cause. If nothing’s resolved, the reporter escalates to GeM Admin and a show-cause notice lands on your dashboard. You’re expected to respond, or report corrective action, within 5 calendar days. Miss that and the system issues a warning. If you still haven’t clicked “respond to SCN” 10 days after issue, the system takes action against you automatically — no human review of your side, because you never gave one.

Stage three: clarification and decision. GeM Admin may seek further clarification after your response; you get 5 calendar days to answer. Then GeM decides on facts and merits. One procedural point: everything happens on the IM dashboard. Emails don’t count as responses, and you’re not supposed to reveal identifying details (names, phone numbers) in dashboard comments.

If the raising party never escalates at all, the system closes the incident 37 days after creation.

Rectification: a second chance, but only with buyer consent

The policy gives sellers a real rectification path after escalation, and it’s worth understanding precisely because the windows are short.

Within 5 calendar days of receiving the SCN, you can express willingness to rectify the deviation, on the IM dashboard itself. The buyer then has 5 calendar days to consent. No response from the buyer in that window is treated as no consent, and GeM proceeds under the policy. If the buyer does consent, the incident is marked “Corrective Action Initiated”, you fix the problem, and both sides confirm the rectification with documents. The buyer can then close it through mutual resolution — though any liquidated damages remain the buyer’s call under the contract.

Two catches. If you commit to rectify and then don’t deliver, the buyer can re-escalate after 10 calendar days, and now you’re facing the original incident with a broken promise attached. And there’s no rectification option at all for pre-contract (catalogue) incidents.

What suspension actually costs — the day-counts

If your explanation is found unsatisfactory, suspension follows, graded by severity and repetition:

Severity	1st & 2nd deviation	3rd & subsequent	Repeat window
Mild	30 days	45 days	within 90 days
Serious	45 days	60 days	within 120 days
Severe	60 days	90 days	within 180 days
Grave	365 days	—	—

Suspension can run up to 2 years with the approval of GeM’s Chief Marketplace Officer. Mild, serious and severe cases are typically handled through a “temporary moratorium”, which bites the same way in practice: you can’t participate in bids or RAs, your catalogues come down, you can’t add or update offerings, and your dashboard access is restricted. You can still complete transactions already finalised — deliveries and payments on existing orders continue. The suspension and your incident history are visible on the marketplace, and they hit your seller rating.

There’s a genuinely useful mitigation clause here. If you had at least 20 contracts in the past year and no more than two same-reason incidents in the last 30 days, your fulfilment rate buys the period down: 98%+ fulfilment cuts the suspension to 30% of the standard period, 95–98% to 40%, and 90–95% to 50% (subject to minimums of 10/15/20 days for mild/serious/severe). There’s a separate reduction — to 30% — where the complaining buyer itself owes you payment beyond timelines on more than two accepted contracts. Neither reduction applies to grave incidents or buyer-ordered debarments. Your track record is literally a discount on future punishment; protect it.

Suspension vs debarment: different animals

Suspension is GeM’s own administrative action under this policy. Debarment is a different track: a buyer organisation, ministry, state or the Department of Expenditure conducts its own proceedings under its own guidelines and issues a debarment order — signed at Joint Secretary/Additional Secretary level (GM and above for CPSEs). GeM then implements it on the platform, and on that SCN you can only contest clerical discrepancies in the entry, not the merits of the debarment itself. A Department of Expenditure debarment blocks you for all buyers on GeM, for the entire order period, and buyer organisations can name allied firms for action alongside the debarred one.

The appeal: one shot, ten days, no pause

The appeal provisions are tight, so treat them as a scalpel rather than a safety net:

• File within 10 calendar days of the suspension or temporary moratorium being imposed.
• One appeal per incident. There is no second appeal.
• Grounds must be additional material evidence that wasn’t available when the decision was taken — not a rehash of arguments already made.
• The suspension remains in effect during the appeal, whatever the outcome.
• The appellate authority can decrease the period — or increase it.
• No appeal on GeM at all for buyer-specific debarments; those you contest with the buyer organisation outside the platform.

The practical implication: the SCN response is your real defence, not the appeal. By appeal stage you need new evidence, you’re already suspended, and you have one attempt. Put your best, documented case in at the show-cause stage, inside the 5-day window.

How to never need any of this

Every suspension I’ve seen up close traces back to a decision made before the incident existed. The prevention list is short and boring:

• Accept orders like they’re commitments, because they are. Most non-delivery incidents are orders accepted on optimism. If the delivery window doesn’t work with your actual stock and logistics, don’t accept — a declined order costs you far less than a 30-day suspension. I went deeper on order discipline in the GeM seller playbook.
• Quote delivery windows you can miss by a week and still meet. Buffer is not weakness. The policy counts calendar days; so should your planning.
• Keep your catalogue honest. Every specification and certification you claim is a deviation waiting to be reported if it isn’t true. Catalogue incidents have no rectification path.
• Get the CRAC generated, always. It closes non-delivery incidents, it’s your proof of acceptance, and it’s the same document that starts your payment clock under the MSME 45-day payment rule. Chase it as hard as you chase the money.
• Watch your dashboard daily when anything is disputed. SCNs appear on the dashboard, and the clocks — 5 days, 10 days — run whether you’ve seen the notice or not.
• Respond to everything, in the window, with documents. Silence is the one strategy the policy punishes automatically.

The same discipline that keeps your bids from getting rejected keeps your account from getting suspended: read what you’re agreeing to, claim only what you can prove, and answer every notice in writing, on time. GeM’s incident machinery is strict, but it’s also predictable — and predictable systems reward the seller who knows the day-counts cold.