Your first e-tender: the DSC checklist that prevents rejected bids

Every tender season we get the same panicked call: "the portal says my certificate is invalid and the bid closes at 3 PM." Here's the checklist that keeps you off that phone call.

Two weeks before the bid

• Buy the combo, not sign-only. GeM, CPPP, IREPS and the state portals all require a signing certificate + encryption certificate pair. The encryption cert is what locks your bid until opening; without it the portal won't accept your submission.
• Match the entity. Bidding as a company? The DSC must be an organization certificate naming your authorized signatory — not the director's personal individual DSC.
• Check validity covers the tender lifecycle. Your certificate must be valid at bid opening, not just submission. A cert expiring next month is a disqualification waiting to happen.

One week before

1. Install token drivers and confirm both certificates show in the token manager.
2. Register your DSC on the specific portal. Each portal (GeM, CPPP, state) has its own DSC enrolment step — registration on one doesn't carry to another.
3. Run the portal's signing test utility if it has one (most do, buried in Help).

On bid day

• Use the browser the portal actually supports (several still want specific Java/utility versions — check their FAQ).
• Keep the token PIN handy; three wrong attempts can lock the token.
• Submit hours early. Portal load spikes at deadlines and signing timeouts are common at 2:55 PM.

The combo certificate with a 2-year validity covers most contractors through multiple tender cycles. If you bid across many portals, do the registration step on each portal the week you receive the token — not the week of your first bid.