Benchmarking in Procurement

Benchmarking in procurement is the systematic comparison of quoted prices, rates, or costs against established reference points to determine whether the government is getting fair value. In Indian government procurement, the primary benchmarks are the published Schedule of Rates, the government's own estimated cost for the tender, and historical award prices for similar procurements. Benchmarking is used by both the TEC during evaluation and by bidders when preparing their pricing strategy.

What is Benchmarking in government procurement?

Benchmarking serves different purposes at different stages of the procurement cycle. Before a tender is issued, the procuring entity uses benchmarks to prepare its cost estimate. For construction works, the benchmark is usually the CPWD Delhi Schedule of Rates or the relevant state Schedule of Rates, updated by a location factor and current material price indices. For goods, the benchmark may be GeM catalog prices, DGS&D rate contract prices, or recent purchase data from similar departments. The estimate prepared using these benchmarks becomes the government's internal yardstick for the tender.

During tender preparation, the eligibility criteria for turnover and experience are often set as a percentage of this benchmark estimate. A typical requirement is that average annual turnover must be at least 100 to 150 percent of the estimated cost, and at least one completed similar project must be worth 80 percent of the estimated cost.

During financial evaluation, the TEC compares the L1 bid against the benchmark estimate to assess price reasonableness. If L1 is significantly above the estimate, it triggers a detailed comparison of individual item rates against the Schedule of Rates to understand where the bid diverged from the benchmark and whether there is a valid market reason.

For PSUs, benchmarking is also done at the item level. If a bidder quotes a rate for a specific material or service that is far above the Schedule of Rates or recently published market indices, the TEC may flag it as an inflated rate and seek justification or adjust the analysis.

External benchmarks used in Indian procurement include the CPWD Delhi Schedule of Rates updated every two to three years, state PWD Schedule of Rates updated annually, MoRTH Standard Data Book rates for highway items, indices published by the Office of the Economic Adviser for material prices, and GeM catalog prices for standard products.

Why it matters for bidders

Bidders use benchmarking in their own pricing preparation, comparing their rate analysis against the Schedule of Rates to check whether their cost estimates are in line with published norms. A rate significantly above the SoR for a standard item is a risk: if the TEC flags it for scrutiny, the bidder will need to justify it with market documentation. A rate significantly below the SoR may win the bid but is worth questioning internally, since SoR rates are generally considered conservative and beating them substantially may indicate the bidder has missed a cost element.

Competitive benchmarking from past tender comparative statements is equally valuable. Firms that track L1 prices across tenders for the same category build a dataset of actual market prices that is more current and location-specific than the SoR. This data is the most reliable input for pricing the next similar tender.

Example

A contractor preparing a bid for road resurfacing work in Maharashtra uses three benchmarks. First, the MoRTH SoR rates for bituminous macadam and dense graded bituminous macadam. Second, the IOC-published price for bitumen (the dominant cost driver for road work) to check whether the SoR bitumen price is current. Third, the L1 prices from the last three road resurfacing tenders in the same district, obtained from past comparative statements sourced via RTI applications. Finding that actual award prices have been running 8 to 12 percent above the SoR due to increased bitumen prices, the contractor adjusts its rates accordingly rather than anchoring solely to the SoR.