Bid Participation Checklist for First-Timers

At 11.20 p.m. in a Kothrud apartment the founder still thought the bid was about the product. The GeM clock in the other tab said 15:00 the next day. The technical PDF was beautiful. The Udyam certificate on the shared drive had expired in March. The Class-3 DSC was in a drawer in the founder's parents' house in Nashik. Nobody had opened the Additional Terms and Conditions past page two.

First government bids are not usually lost because the agent is weak. They are lost because a document the buyer treats as a gate was treated as paperwork. A cancelled cheque in the wrong name. A PAN that does not match the seller legal entity. An EMD exemption claimed without the current DPIIT letter attached. A technical compliance matrix that says 'yes' against a clause the stack cannot meet on day one.

This is the checklist we walk with first-time sellers the week before they touch upload. It is written for Indian GovTech founders, not for a consumer app launch. It is not legal advice. It is the boring sequence that keeps a good platform from being marked non-responsive at 15:01.

Treat the clock as part of the specification

GeM and CPPP do not care that your PDF is better. They care that the packet arrived inside the window, signed by the person the portal believes is authorised, in the formats the bid named. A first-timer who starts the upload at 14:40 on a closing day is bidding against the portal, not against the incumbent.

Write the calendar backwards from the closing minute. Subtract two working days for DSC driver fights, GeM OTP delays, and the bank's holiday calendar if a bid security instrument is required. Subtract one more day if any certificate must come from a chartered accountant. Do not plan to obtain a fresh Udyam print, a board resolution and a bank guarantee on the same morning.

If the bid allows a pre-bid query, use it for the one clause that would make you non-responsive, not for a product demo. Queries become part of the file. A sloppy question that reveals you have not read the ATC is worse than silence.

Close the legal entity pack before you polish slides

The buyer is buying from a legal person. The portal will reject a packet where the seller name, PAN, GSTIN, cancelled cheque and DSC identity do not tell one story. That story must match the incorporation documents, not the brand on the website.

If you are an LLP, do not upload a private-limited board resolution template you found on a blog. If two founders can bind the firm, say so in a current authority letter. If only one can, that one must be available on closing day. A DSC sitting with a travelling co-founder is a bid you have already lost.

DPIIT recognition and Udyam registration are useful only when they are current, in the same legal name, and actually invited by this bid. They are not architecture certificates. They do not prove on-prem deployment. They sometimes ease EMD, prior turnover or prior experience if the bid text and the live GeM / GFR path allow it. Attach the certificates. Do not attach a tweet about Startup India.

If the left column is pretty and the right column is missing, the committee never reaches the product.

Packet	What first-timers usually upload	What the file actually needs
Identity of the bidder	Brand deck and a website URL	COI / LLP agreement, PAN, GSTIN, cancelled cheque in the same legal name
Authority to bid	A WhatsApp 'you handle GeM'	Board / designated-partner resolution or authority letter matching the DSC holder
MSE / startup claim	A screenshot of the Startup India dashboard	Current Udyam and / or DPIIT certificate, plus the bid clause that grants the relief
Bid security	A sentence saying startups are exempt	The exemption documents named in this RFE, or the instrument the bid actually asked for
Integrity / declarations	Skipped because 'standard'	Signed integrity pact, non-blacklisting, Make in India / local-content affidavit if the bid seeks them
Technical matrix	A glossy architecture PDF	Clause-by-clause compliance against the ATC, with evidence or an honest partial

Read the ATC like a map of traps, not a brochure

The bid document is not a conversation. It is a marking scheme. First-timers skim scope and price and miss the three lines that will fail them: a mandatory on-prem proof, a named certification that is not STQC-by-default, a prior-work format that demands a government work order rather than a private LOI, or a consortium rule that forbids what you were about to try.

Print the ATC. Highlight every 'must', 'shall' and 'documentary evidence'. For each highlight, write one of three words in the margin: have, can-get-by-closing, or cannot. Anything in the third column is either a pre-bid question or a no-bid. A 'yes' typed against a cannot is how first-timers create a later incident.

Watch for cloned eligibility from a hardware tender: OEM authorisation, spare-part warehouses, three similar works of 80 per cent value. Some of those rows can be challenged in pre-bid if they have no relation to an agent platform. Some cannot. Do not invent a relaxation the bid does not give you.

• Closing date, opening date, and whether the technical opening is public on the portal.
• Whether EMD / bid-security exemption is offered to Udyam MSE, DPIIT startups, or both — and which documents are named.
• Whether consortium is allowed, and whether joint and several liability is written.
• Whether the buyer wants a GeM catalogue item, a custom bid, or a service-level contract.
• Whether deployment is SaaS, NIC/SDC, or air-gapped — and what evidence they want in the technical packet, not after award.
• Whether a reverse auction will follow, and whether you can live with that price path.

The night-before-upload drill

By the evening before closing you should not be writing prose. You should be checking hashes, filenames, page counts and signatures. Government portals still punish a 20 MB PDF that should have been 8, a scanned stamp that is unreadable, and a spreadsheet saved as the wrong extension.

Name files the way the bid asked, not the way your design system prefers. If they want Annexure-B-turnover.pdf, give them that string. A committee member opening twenty packets will not hunt through 'final_v7_USE_THIS.pdf'.

Have a second person click every link in the packet on a machine that is not yours. First-timers fail because a figure is missing on page 14 of a scan they never reopened. That second person is not there to improve the writing. They are there to confirm the packet is complete.

1. Confirm the seller profile on GeM or the CPPP enrolment matches the legal name on every annexure.
2. Confirm the DSC is valid, the token driver works on the upload machine, and the authorised person is in the room.
3. Re-download Udyam, DPIIT, GST, PAN and bank proof the same day. Portals notice stale scans.
4. Tick the compliance matrix against the live ATC, not against last week's draft.
5. If a bid-security instrument is required, confirm the beneficiary name, validity and the bank's holiday calendar.
6. Upload a dummy packet 24 hours early if the portal allows replacement. Do not make the first upload the only upload.
7. Export the acknowledgement and the hashed file list into your own folder. The portal is not your archive.

When the honest move is not to bid

A first bid that you cannot perform is more expensive than a missed opportunity. If the ATC demands a named certificate you do not have and cannot obtain before opening, walk. If the deployment model is air-gapped and your only runtime phones a foreign licence host, walking is cheaper than an incident after award.

If the only way you 'comply' is a consortium the bid forbids, or a subcontractor who will not accept joint liability, you do not have a bid. You have a hope. Committees are not obliged to rescue hope.

Prcept AI will tell a founder to skip a notice when the notice is a hardware clone or a SaaS-only shape we cannot honestly meet. A no-bid memo in your own folder is a professional artefact. A non-responsive packet is a public one.

Lines first-timers use to skip a row

These are the sentences we hear in the war-room the night before closing. Answer them on paper. A spoken 'it will be fine' is not a control.

We are DPIIT recognised, so EMD and turnover do not apply.

Only if this bid says so, and only if the certificate is current and in the bidding entity’s name. Startup India describes relaxations that many Central bids implement. It is not a blanket repeal of every ATC. Read the clause. Attach the document the clause named.

The technical PDF is the bid. Annexures can follow if they shortlist us.

They will not shortlist a non-responsive packet. Government opening is not a startup accelerator office hours. What is not in the packet at opening is not in the evaluation, except where the bid itself allows clarification of an ambiguity — not creation of a missing mandatory paper.

Our systems integrator partner will 'cover' OEM and experience.

Only if the bid allows a consortium or named sub-contract, and only if the experience the ATC wants is allowed to come from that member. A side letter the buyer never sees does not amend the tender. If you need a partner, build the joint packet the bid described.

We can mark every compliance row yes and sort the gaps after award.

That is how first awards become incidents. A yes you cannot perform is a representation. GeM incident management and contractual termination sit on the other side of that representation. An honest partial, or a no-bid, is cheaper.

Seven nights before closing — a first-timer run

Start this the week you decide the notice is real. Do not start it the afternoon the portal starts warning you.

1. Night 7: print the ATC. Build the have / can-get / cannot list. Decide bid or no-bid. If consortium is required, call the partner that night, not after the slides are pretty.
2. Night 6: freeze the legal-entity pack. PAN, GST, cancelled cheque, authority letter, Udyam, DPIIT. Reconcile every string of the legal name.
3. Night 5: draft the compliance matrix against clause numbers, not against your brochure headings. Flag every evidence gap.
4. Night 4: write the technical narrative only for rows that need explanation. Keep it dull and evidenced. Stop adding adjectives.
5. Night 3: second-person review of the entire packet on a clean laptop. Fix scans, filenames, signatures.
6. Night 2: test DSC and portal login. Upload a replaceable draft if the portal allows. Confirm bid-security instrument status.
7. Night 1: no new prose. Confirm clocks, hashes, acknowledgements. Sleep. A tired founder at 14:50 is how packets miss the slot.

What goes in the file — founder folder and buyer note

Founders should keep a folder that a later investor, CA or investigating officer can open without you: the live bid PDF, the exact packet uploaded, the portal acknowledgement, the exemption certificates as downloaded that week, and a one-page memo stating which relaxations you claimed and why the bid allowed them.

If you are the departmental officer opening first-time packets, the file needs a different paragraph: the mandatory annexures you will actually enforce, the MSE / startup relief you will honour if documents are current, and the one sentence that says non-responsive means non-responsive. Do not invent a cure process the bid did not write.

This article is a field guide for Indian public buyers and GovTech founders, not legal, tax or procurement advice. GeM terms, GFR compilations, ATC text and bid-specific clauses change. Confirm against the live notice on gem.gov.in and your counsel before you act.