BHU Issues 17-Point Vigilance Code for Tenders and Purchases

By Harsh Mehra7 min read
Procurement files and a laptop on an institutional office desk
Illustrative image: Procurement records and bid documents sit ready for review in an institutional office.

VARANASI: Banaras Hindu University has circulated a 17-point preventive-vigilance code intended to make purchases and construction tenders easier to audit from the first estimate to the final award. The guidelines focus on records, competition and reasons: officers must preserve the documentary trail, examine single-bid situations carefully and disclose conflicts that could compromise an evaluation.

The instructions require departments to retain note sheets, approvals, technical specifications, cost estimates, publication records, bids and both technical and financial evaluations. When only one bid is received, the file must show whether the tender was adequately advertised, whether bidders had enough time and why proceeding with a single offer was justified. Tender cancellation, re-tendering and extensions must also be supported by written reasons.

Procurement failures rarely begin with one dramatic signature. They often grow from a vague specification, a short response window, a missing comparison or a decision recorded only in conversation. A complete file forces the institution to show how each stage led to the next. It also protects an honest officer who can demonstrate that a decision followed the rules and was not improvised later.

Universities buy everything from laboratory equipment and books to civil works, software and hospital supplies. The market is diverse, and a rule suitable for routine stationery may not fit a specialised scientific instrument available from one manufacturer. That is why a single bid is not automatically improper. The relevant questions are whether competition was genuinely possible, whether the specification was neutral and whether the price was tested.

For vendors, consistent documentation can reduce uncertainty and make complaints easier to assess. For students and taxpayers, it offers a clearer route to ask how public money was used. The code will matter only if tender notices, corrigenda and award summaries are published in searchable form and if departments use the same naming and retention standards. A file that exists but cannot be located is not meaningful transparency.

BHU should accompany the circular with training for staff who draft specifications and evaluate bids. Periodic sample audits can identify recurring weaknesses before they become allegations. The university can also publish anonymised observations—late approvals, incomplete conflict declarations or unsupported extensions—so departments learn from patterns without waiting for a scandal.

Companies bidding for BHU work should read the tender and corrigenda together, submit clarifications through the official channel and preserve portal acknowledgements. Staff members who have a personal or financial link to a bidder should recuse themselves in writing. The public should judge the new system through later awards and audit outcomes, not through the language of the circular alone.

This report is based on a Live Hindustan account published on 26 August 2026. Dalimss News independently rewrote, checked and contextualised the available information. Where a claim, allegation or opinion is attributed to a person or institution, it remains their statement; no on-scene reporting or independent interview is claimed.

Sources and reporting

This report is based on a Live Hindustan account published on 26 August 2026. Dalimss News independently rewrote, checked and contextualised the available information. Where a claim, allegation or opinion is attributed to a person or institution, it remains their statement; no on-scene reporting or independent interview is claimed.

Related Stories