Empanelment Bid: Common Disqualifiers

A Hyderabad firm spent six weeks on an architecture annexure for a Telangana-adjacent IT empanelment. The air-gap story was good. The portal upload failed the pre-qualification envelope because the EMD instrument named the old Pvt Ltd entity, the affidavit was signed by a director who had resigned in MCA, and the ISO PDF was a scan of a certificate that had expired on a Sunday. Technical never opened. The founder blamed 'the system'. The system had been literal.

Empanelment RFEs are designed to throw away incomplete packs so a small committee can mark a small set. Disqualifiers are therefore front-loaded, formal, and unromantic. This checklist is the unromantic list. It will not make a weak product strong. It will stop a strong product from dying as a PDF.

Formats differ — CPPP two-cover, GeM, a state portal, an email-to-the-cell vintage process. The sins repeat. Treat this as a pre-flight, then read the RFE's own disqualification clause, which always wins.

Not legal advice. A bounced bid can sometimes be saved if the RFE allows clarification on 'non-material' gaps. Do not plan on that mercy.

The disqualifiers that actually show up

Identity mismatches: legal name, PAN, GSTIN, CIN, Udyam, DPIIT, GeM seller ID, bank account name, and letterhead do not tell the same story. A space, a Pvt. vs Private, a dropped LLP, is enough.

Instrument failures: EMD missing, wrong amount, wrong validity, wrong beneficiary, drawn on a bank the RFE excluded, or an exemption claimed without the paper the RFE named (Udyam vs DPIIT vs NSIC).

Signature failures: DSC expired, token with a departed employee, affidavit on the wrong stamp value, unsigned integrity pact, board resolution that authorises a different RFE, Power of Attorney not notarised where asked.

Eligibility arithmetic: turnover below the line and no valid startup relaxation, experience citations that are work-in-progress, a consortium that the RFE forbade, a blacklisting affidavit that is silent on a real show-cause.

Document currency: ISO, CMMI, BIS, solvency, ITR acknowledgements, GST returns — expired or for the wrong entity in the group.

Portal theatre: late click, file larger than the cap, wrong cover (commercial in technical), password-protected PDF the committee cannot open, scanned pages too dark for a PAN.

A Thursday-before-close checklist

Item	Fail mode	Owner	Evidence to screenshot
Legal name chain	Letterhead ≠ PAN ≠ GST ≠ portal	COO / CS	MCA master data + GST portal
EMD / exemption	Wrong beneficiary; claimed DPIIT but attached Udyam only	Finance	Instrument + RFE clause + certificate
DSC + signatory	Director resigned; token with intern	Authorised signatory	MCA list + board resolution + DSC validity
Turnover / experience	CA certificate not in the RFE format; projects without completion proof	Bid lead + CA	Format page from RFE + CA letter
ISO / scored certs	Expired Sunday; wrong scope; group cert not naming bidder	Ops	Certificate + scope + end date
Blacklisting affidavit	Copied old year; silent on a real dispute	Founder	Affidavit dated this week
Covers and filenames	Price in technical PDF; 80 MB zip	Bid lead	Portal preview / hash list

Disqualifiers that look technical but are still formal

Some RFEs require an OEM authorisation if you are not the manufacturer of the 'product'. If you wrap weights, decide whether you are OEM of the runtime. A missing MAF is a PQ fail, not a debate about open source.

Some require a data-centre declaration or a MeitY-empaneled cloud. If you are on-prem only, say so in the form they provided. Leaving the cell blank because 'it does not apply' is how a script marks you non-responsive.

Some require a local office. A coworking invoice may or may not count. The RFE will say lease, electricity bill, or GST registration in the state. Attach what they named.

Over-claiming C-DAC, iDEX, or a ministry logo can become a misrepresentation finding, which is worse than a PQ bounce. If you cannot attach the letter, delete the sentence.

What a clarification can save — and cannot

Clarifications can usually fix a blurry scan, a missing page of a multi-page ITR, or a question about how two experience citations add up — if the RFE allows and if you answer in time in their table.

Clarifications rarely save a missing EMD, a late bid, a commercial figure in the technical cover, or an eligibility you never had. Do not use the clarification window to invent a certificate.

If you receive a clarification, answer only what they asked, with annexure numbers, and do not attach a new marketing deck. New decks create new questions.

After a bounce

Ask for the reason in writing. Many portals show 'non-responsive' without a noun. A noun is how you improve.

Do not litigate a blurry PAN as a conspiracy. Fix the factory. Put the checklist on the next bid.

If the bounce was wrong — they missed your DPIIT exemption — write a factual representation with the clause and the attachment hash. Stay polite. You may still lose the calendar. You may win the next list.

Objections you will hear — and what to do with them

These are the lines that stall the file. Answer them in the room, then put the answer in the note. A spoken answer without paper will be forgotten by the next officer.

Committees should look at substance.

They will, after you survive form. Form is the filter that protects their time. Respect it.

We were close; they should have called.

Some will. Many cannot, because the RFE says non-responsive is fatal. Build as if nobody will call.

A consultant promised the pack is 'standard'.

There is no standard pack. There is this RFE. Make the consultant tick this RFE's clause list.

ISO expired but recertification is booked.

Then either the RFE accepts a booking letter — rare — or you are expired. Do not tick valid.

The Thursday red-team

If close is Friday 15:00, red-team Thursday 11:00 with someone who did not write the pack.

1. Print the RFE eligibility and disqualification clauses. Tick each against a file in the zip.
2. Open every PDF. Confirm it is not passworded, not a zero-byte, and is the latest.
3. Check name chain: MCA, PAN, GST, Udyam, DPIIT, bank, portal.
4. Check EMD or exemption against the exact clause.
5. Check signatory against MCA and the board resolution.
6. Check covers: no price in technical.
7. Upload a dummy if the portal allows, or compute sizes. Then stop changing product prose.

How this shows up in the file

A one-line founder certificate: 'I have seen the Thursday checklist for RFE [name]. I know the legal name, the EMD story, and the signatory. I have not authorised a logo we cannot attach.' File it. It changes behaviour.

After submission, store the portal receipt, the hash of the zip, and the exact time. Arguments without hashes are folklore.

This article is informational field guidance for Indian public institutions and their vendors, not legal, tax, procurement or engineering advice. Confirm the live circular, RFE, GCC, GeM term, state G.O. and your counsel before you file anything. Incentives, ceilings and portal screens change.

How to run the route without confusing the letterhead

“Empanelment Bid: Common Disqualifiers” is a route problem. A P5 Startup/Vendor should know which legal person they are talking to — NIC, NICSI, a state IT corporation, iDEX, or a GeM buyer — and which paper that person can actually issue. Searching “empanelment disqualification” is not the same as being on a panel that can receive a work order.

Most empanelment deaths are clerical. The committee never debates your agent. They bounce the zip. Run this list before the portal clock hits zero. Empanelment letters are not purchase orders. DPIIT recognition is not a technical score. Reserved startup seats, if a notice writes them, are local to that notice. IndiaAI compute empanelment is not NICSI application-software empanelment.

Keep a warm evidence pack: CIN, GST, DPIIT, Udyam, financials, work-completion letters, architecture one-pager, DPA draft. Renewals are lost by people who treat the panel as a trophy.

• Screenshot the live RFE paragraph you are relying on, dated.
• Match the bidding entity name across every certificate.
• Do not mix iDEX, TDF, NICSI and GeM clocks on one tracker cell.
• Record the validity end date 90 days before it dies.

Close this loop before the next CAB

Put “Empanelment Bid: Common Disqualifiers” 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 Startup/Vendor, not “the vendor.”

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