How Verification Works
What the Platform Decides
e-Nirikshak determines whether each bid is responsive to the published requirements — that is, whether the bidder has met what the tender asked for. Every determination is one of three outcomes: responsive, non-responsive, or needs review.
The platform does not award tenders and does not rank bidders by price. The award decision is taken by the competent authority under the General Financial Rules, outside this system.
Two Kinds of Check
Requirements are checked in one of two ways, and every finding records which was used.
| Method | Used for | How it decides |
|---|---|---|
| Deterministic rule | Measurable requirements: a turnover floor, a certificate valid on a date, an EMD amount, a material grade. | A plain comparison against the value stated in your documents. No language model is involved, the result is reproducible, and the same documents always produce the same finding. |
| Semantic match | Requirements calling for judgement: whether a datasheet satisfies a specification clause, or whether past supplies are comparable. | Relevant passages are retrieved from your own bundle and assessed by a language model, which must cite the specific passages it relied on. A finding that cites nothing, or cites something not in your documents, is rejected and sent to a human instead. |
Safeguards
- Your bid is sealed. It is encrypted on upload with a key held for that tender alone, and the key is released only when the tender closes. No officer, buyer or administrator can open any bundle before then.
- Your bid is never compared against another bidder's documents. Each bundle is indexed in its own namespace, and retrieval is confined to it.
- Nothing uncertain is decided automatically. A finding below the confidence threshold is routed to a compliance officer rather than applied.
- A human can override any finding. Overrides record the original verdict, the officer's identity and their written justification, and the engine's original finding is preserved.
- Every action is logged. The audit trail is append-only and hash-chained, so any alteration to it is detectable.
- You receive a receipt. On submission you are given a cryptographic hash of your bundle — your proof of exactly what you submitted.
What You Will Be Told
After the evaluation is finalised, you can see your own outcome and the reason recorded against each requirement, in plain language. You will not see other bidders' documents, outcomes or prices, and no other bidder will see yours.
Tender text, requirements and evidence are shown in the language of the source documents.