--- title: GeM incident management: raising, appeals and suspension · TrackTender description: How GeM incident management works for sellers: what triggers an incident, show-cause timelines, rectification, suspension periods, and your one appeal. canonical: https://tracktender.com/blog/gem-incident-management-suspension/ source: https://tracktender.com/blog/gem-incident-management-suspension/ --- # GeM incident management: raising, appeals and suspension > How GeM incident management works for sellers: what triggers an incident, show-cause timelines, rectification, suspension periods, and your one appeal. - [Blog](/blog/) / - GeM incident management: raising, appeals and suspension After you win - GeM - Incidents - After you win # GeM incident management: raising, appeals and suspension How GeM incident management works for sellers: what triggers an incident, show-cause timelines, rectification, suspension periods, and your one appeal. KSKetul Shah13 July 2026 · 9 min read Copied The short version A GeM incident is a recorded deviation from the platform's terms — raised against a bid, a contract or a catalogue — by the buyer, the seller, GeM Admin or the system itself. In this guide - [Who raises incidents, and what triggers them](#who-raises-incidents-and-what-triggers-them) - [The timeline: 7 days to resolve, 5 to respond, 10 before the system acts](#the-timeline-7-days-to-resolve-5-to-respond-10-before-the-system-acts) - [Rectification: a second chance, but only with buyer consent](#rectification-a-second-chance-but-only-with-buyer-consent) - [What suspension actually costs — the day-counts](#what-suspension-actually-costs--the-day-counts) - [Suspension vs debarment: different animals](#suspension-vs-debarment-different-animals) - [The appeal: one shot, ten days, no pause](#the-appeal-one-shot-ten-days-no-pause) - [How to never need any of this](#how-to-never-need-any-of-this) - [Frequently asked questions](#faq) Key takeaways - A GeM incident is a recorded deviation from the platform's terms — raised against a bid, a contract or a catalogue — by the buyer, the seller, GeM Admin or the system itself. - Post-contract, the two parties get 7 calendar days to resolve it between themselves. If it's escalated, a show-cause notice lands on your dashboard: respond within 5 calendar days, and if you've said nothing by day 10 the system acts against you automatically. - You can offer to rectify the deviation within 5 calendar days of the show-cause notice, but it only pauses the incident if the buyer consents — buyer silence for 5 days counts as no consent. - Suspension runs by severity: 30 days for a mild deviation, 45 for serious, 60 for severe, 365 for grave — longer for repeat deviations, up to 2 years with Chief Marketplace Officer approval. A strong fulfilment record can cut the period to as little as 30% of the standard. - You get exactly one appeal, within 10 calendar days of suspension, and only on material evidence that wasn't available earlier. The suspension stays in force while the appeal runs. 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. StageWindow Resolution between buyer and seller before escalation7 days from incident creation Your response to the show-cause notice (SCN)5 days (warning if silent) System acts automatically if SCN still unanswered10 days after SCN issue Reply to a “further clarification” from GeM Admin5 days Auto-closure if the raising party never escalates37 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: Severity1st & 2nd deviation3rd & subsequentRepeat window Mild30 days45 dayswithin 90 days Serious45 days60 dayswithin 120 days Severe60 days90 dayswithin 180 days Grave365 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. Most incidents start with a bad bid Non-delivery incidents usually trace back to accepting an order you couldn't fulfil on the timeline offered. TrackTender's AI parses tender PDFs — EMD, deadline, quantity extracted — and sends matched tenders to Telegram or WhatsApp for your states and categories, so you commit with the facts in front of you. [Get matched tenders →](/subscribe/) First month ₹30 (about ₹1/day), then ₹300/month. Cancel anytime. ## 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](/blog/how-to-sell-on-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](/blog/government-tender-payment-rules-msme-45-day/). 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](/blog/why-tenders-get-rejected-bid-disqualification/) 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. ## Frequently asked questions What is an incident on GeM? Any action at variance from GeM's terms and conditions of procurement is a 'deviation', and an incident is the formal record of one. Incidents can be raised against a bid number, a contract number or a catalogue, by the buyer, the seller or service provider, GeM Admin, or the GeM system itself based on platform data. How many days do I get to respond to a GeM show-cause notice? Under the incident management policy effective 21 July 2025, you should respond or report corrective action on the IM dashboard within 5 calendar days of the SCN. If there's no response in 5 days the system issues a warning, and if you still haven't responded 10 days after issue, the system automatically takes action against you. Can I fix the problem instead of being suspended? Sometimes. Within 5 calendar days of receiving the show-cause notice you can express willingness to rectify the deviation on the IM dashboard. The buyer then has 5 calendar days to consent; silence counts as refusal. If the buyer consents, the incident is marked 'Corrective Action Initiated' — but if you fail to deliver on the commitment, the buyer can re-escalate after 10 calendar days. How long does a GeM suspension last? It depends on severity. For a first or second deviation: 30 days (mild), 45 days (serious), 60 days (severe). Repeat deviations within the policy's lookback windows push those to 45, 60 and 90 days. A grave deviation with an unsatisfactory explanation draws 365 days, and suspension can run up to 2 years with Chief Marketplace Officer approval. What's the difference between suspension and debarment on GeM? Suspension (and temporary moratorium) is GeM's own administrative action under its incident policy — you can't bid or update catalogues for a fixed period, though you can complete transactions already finalised. Debarment is ordered by a buyer organisation or the Department of Expenditure under their own rules; GeM implements it on the platform, and a DoE debarment blocks you for all buyers on GeM for the full order period. Can I appeal a GeM suspension? Once, and only once per incident. The appeal must be filed within 10 calendar days of the suspension or temporary moratorium, and only on material evidence that wasn't available when the decision was taken. The suspension remains in effect during the appeal, and the appellate authority can decrease — or increase — the period. KS Written by Ketul Shah Ketul Shah is the founder of TrackTender and Anekant AI. He works with Indian SMEs that bid on government contracts and writes about GeM, e-procurement and how smaller suppliers can compete and win. [More about TrackTender →](/about/) Keep reading ## More from the blog - [13 July 2026GeM bid status: how to check your tender result (and read it)How to check GeM bid status from the seller dashboard, what each evaluation status means, how to see the published result with competitors' prices, and how to use it.](/blog/gem-bid-status-tender-results/) - [13 July 2026GeM product upload: catalogue listing and brand approval, explainedHow to upload products on GeM, why listings get rejected, how brand approval and its three-attempt limit work, and what the Q1–Q4 category quadrants mean.](/blog/gem-catalogue-upload-brand-approval/) - [09 June 2026BidAssist vs TrackTender: pricing, features and coverageA fact-checked BidAssist vs TrackTender comparison for Indian suppliers: what each does well, real pricing, and how to pick the right tender alert tool.](/blog/tracktender-vs-bidassist/) ## Stop reading about tenders. Start winning them. Pick your states and categories and get matching tenders on Telegram and WhatsApp. [Start tracking](/subscribe/)