How public procurement works on e-GP
One continuous, tamper-evident workflow from a procurement plan to the final payment — with cryptographic integrity (sealed bids, HSM-quorum opening, signed decisions) and open data at every step. Each stage below links to where you can see it in action.
- 1
Firms register online (PAN/VAT, licences, bank details), reviewed and approved by PPMO before they can bid.
🔒 PAN/VAT & bank details encrypted at rest
- 2
Procurement Planning
खरिद योजनाProcuring EntityMaster & Annual Procurement Plans → packages → lots, with budget linkage and approval workflow.
🔒 Budget/plan gate before any tender publishes
- 3
Standard Bidding Documents (SQ / NCB / ICB / PQ / EoI / RFP), BoQ with CPV codes, single/double envelope, addenda.
🔒 Approval workflow + tamper-evident audit
- 4
Bid Submission
बोलपत्र पेशBiddersBidders submit sealed bids before the deadline and receive a cryptographic receipt.
🔒 Envelope-encrypted to the entity's key — unreadable until opening
- 5
Bid Opening
बोलपत्र खोल्नेOpening CommitteeAt the scheduled time a committee opens technical envelopes; financial envelopes stay sealed.
🔒 HSM M-of-N quorum unseal + digitally-signed minutes
- 6
Evaluation
मूल्याङ्कनEvaluation CommitteeTechnical scoring & compliance, then financial evaluation (lowest-cost or QCBS), with full audit of decisions.
🔒 No financial view until technical passes (segregation)
- 7
Contract Award
ठेक्का सम्झौताAward AuthorityThe winning bid is approved and the award published to the public portal.
🔒 HSM-signed award letter + FMIS encumbrance
- 8
Contract Management
सम्झौता व्यवस्थापनProcuring Entity · ContractorMilestones, variation orders, and geo-tagged field progress monitoring through to completion.
🔒 Verified milestones gate payment
- 9
Payment
भुक्तानीContractor · FinanceContractor invoices verified milestones; payments are certified and disbursed via Treasury/FMIS.
🔒 Signed payment certificate; no over-payment
- 10
Every process is published as OCDS open data; oversight reviews a live red-flag console.
🔒 Open Contracting Data Standard 1.1
Every step is recorded in a hash-chained audit log
Tamper-evident from plan to payment, and published as OCDS open data for public oversight.
