Three hours into a BOQ that shouldn't take three hours
A junior estimator on their first NHAI project is given the SOR PDF and told to "check the rates." Three hours later they have found seven different entries that could apply to WBM sub-base, don't know whether the Delhi state PWD rates or the central MoRTH rates apply to a project on NH-48, and have marked the BOQ item at a composite rate that includes bituminous primer coat. The item doesn't need primer coat.
The engineer who assigned the task meant a 30-minute check. The confusion is not the estimator's fault. The MoRTH schedule of rates structure is not self-explanatory, and nobody explains it systematically to people who need to use it.
This piece covers what the SOR is, how the rate structure works, when central versus state SOR applies, and the two distinct ways contractors should use it.
What the MoRTH Schedule of Rates is
The Ministry of Road Transport and Highways publishes a Schedule of Rates for road and bridge works. It is not a price list. It is a set of unit rates derived from a standard analysis of material, labour, plant, and contractor overhead costs, adjusted periodically to reflect input price movements.
The current document is known informally as the MoRTH SOR. Its predecessor was the Standard Data Book (SDB), which some older contract documents still reference. When a client BOQ or a tender document refers to the "SDB rate" or the "Ministry rate," they mean the same document series.
MoRTH revises the SOR periodically. The base rate analysis uses input prices at a reference point in time. By the time a specific contract is executed, those prices may have moved significantly. That gap is addressed through Clause 70 price escalation, which adjusts the contract price using WPI and CPI-IW indices. The SOR rate is the starting point, not the end point.
How the rate structure works
The MoRTH SOR organises items by road layer and work type:
- - Part I: Earthwork, sub-grade preparation
- Part II: Granular sub-base and base courses
- Part III: Bituminous works
- Part IV: Cement concrete works
- Part V: Bridge and structure works
- Part VI: Traffic safety features, drainage, miscellaneous
Each item has a unique code. The code structure is hierarchical: the first digits identify the chapter, sub-digits identify the item type. WBM base course is in Part II. Dense Bituminous Macadam (DBM) is in Part III.
Within each item, the SOR shows:
- Basic rate: the unit rate derived from cost analysis
- Analysis of rate: the material, labour, and plant breakdown behind the rate
- Assumptions: the specification standard the rate is based on (MoRTH Chapter reference, IRC code)
The rate analysis section is what most estimators skip. It is also the most useful part. The assumptions embedded in the rate analysis tell you whether the rate applies to your site conditions. If the SOR DBM rate assumes stone aggregate from a quarry 20 km away and your quarry is 80 km away, the rate does not apply to your project. You need a rate deviation, and the rate analysis gives you the basis for calculating it.
Central SOR versus state SOR: when to use which
NHAI and NHIDCL projects (National Highways, Bharatmala packages) use the central MoRTH SOR. State PWD projects use the relevant state SOR. Hybrid projects where a state highway is upgraded to NH status and transferred to NHAI during project preparation sometimes reference both.
State SORs vary significantly from the central SOR. Maharashtra PWD rates for bituminous work can differ from the central rate by 8 to 15 percent. Rajasthan PWD rates for earthwork differ from MoRTH because the state factor analysis uses different labour productivity assumptions.
The contract document specifies which schedule applies. Read the Special Conditions of Contract (SCC). If the SCC is silent and the project is on a National Highway, use the central MoRTH SOR. If you are in a state highway project with central funding, read the Concession Agreement: it will specify the applicable schedule.
Mixing central and state SOR in a single BOQ is a common rate analysis error. It produces inconsistencies that NHAI's IE will flag during measurement or that the client's technical audit team will find during contract administration. Fix it in rate analysis, not after the BOQ is submitted.
Two ways contractors should use the SOR
Use 1: Rate analysis for your own BOQ pricing
- When you price a tender, your rates should be grounded in a rate analysis that shows:
- Material cost (sourced from your supplier quotes, not from SOR assumptions)
- Labour cost (market rate, not SOR assumption)
- Plant cost (your owned or hired plant, amortised)
- Contractor overhead and profit (your actual overhead recovery rate)
The SOR rate is a benchmark, not your rate. Submitting a rate that matches the SOR exactly signals one of two things: either you calculated it independently and arrived at the same number, or you copied the SOR without doing your own analysis. In a competitive bid, the second option usually means you are either over-priced (if material costs have risen since SOR revision) or leaving margin on the table (if you have better plant or procurement than the SOR assumes).
Your rate analysis workbook should show your derivation. The SOR provides the structure: it tells you which cost heads to model and what specification the work requires. The numbers come from your own procurement and plant records.
Use 2: Checking the client's BOQ rates
When you receive a BOQ from NHAI or a state authority, the client's rates are typically derived from the SOR. Checking whether the authority's estimated rates are reasonable before bidding protects you from pricing errors and from winning contracts that have been under-estimated at the client's end.
Significantly under-estimated client rates are a red flag, not an opportunity. A tender where every item is priced at 70 percent of your own rate analysis suggests either the client used an outdated SOR revision, applied the wrong state SOR, or made a measurement error. Winning that contract at or near the client estimate creates a cost recovery problem from day one.
The rate analysis section of the SOR is the fastest way to identify where client rates diverge from your expectations. If the client's DBM rate is 12 percent below your analysis, check whether their rate includes stone aggregate haulage at the assumed distance. Often it doesn't.
Where the SOR doesn't help
The SOR covers standard road items under standard site conditions. It does not cover:
- - Non-standard materials (geosynthetics, polymer-modified bitumen)
- Items unique to a specific project's SCC
- Rates for work in difficult terrain where productivity assumptions differ significantly from SOR norms
- Utility shifting, which is often a provisional sum item outside the SOR framework
For non-SOR items, contractors must prepare an independent rate analysis from first principles and submit it as part of the bid. NHAI's technical evaluation team will review these. An unsupported rate for a non-SOR item is a quality evaluation risk.
Reading tender BOQs against the SOR
CivilBolt's Tender Intelligence module maps BOQ items to the relevant SOR chapter and flags items where the tendered rate deviates significantly from the current SOR benchmark. The analysis helps you identify items where your rate analysis should dig deeper before the submission deadline, rather than discovering the discrepancy during contract administration.
The SOR is published. The SOR analysis is available. Most contractors don't use it systematically because the PDF is 600 pages and the rate structure is not obvious on first read. That gap is the competitive edge available to estimating teams willing to build the cross-reference once and maintain it across projects.
When was the last time your estimating team updated their SOR cross-reference workbook?