BOQ vs WBS: How to Tie Site Measurements to Cost Control

Short answer: a Bill of Quantities (BOQ) tells you what will be paid for and at what rate; a Work Breakdown Structure (WBS) tells you where in the project that work sits and who is responsible for it. Cost control works when every BOQ line is mapped to a WBS work package, every site measurement is recorded against that pair, and every bill is raised only from recorded measurements. Without that link, you can see that the project is over budget, but not which part of the site is leaking money.

This guide explains the difference, shows how to connect the two, and gives a checklist you can use on your next project.

What a BOQ is (and what it isn't)

A BOQ is an itemised list of the work in a contract: item description, unit of measurement, quantity and rate. In India, measurement rules for building and civil works are set out in the Bureau of Indian Standards' IS 1200 series, published in separate parts by trade (earthwork, concrete, masonry and so on).¹ On many projects the BOQ is the commercial backbone: tenders are priced on it, and running account (RA) bills are paid against it.

What a BOQ is not is a map of the project. A single BOQ item such as "M25 concrete in footings" may cover footings in three different blocks, built in different months by different crews. If you only track at BOQ level, the quantity for the whole item looks fine until the last block, when it suddenly runs out.

What a WBS is (and why the 100% rule matters)

The Project Management Institute describes the WBS as a deliverable-oriented, hierarchical breakdown of the project's work.² Two ideas from the WBS standard matter most for cost control:

• The 100% rule. The WBS includes all of the work in scope and nothing outside it, and at every level the children add up to exactly the parent.²³ If the work isn't in the WBS, it has no home for its cost.
• Work packages. The lowest level of the WBS is the work package: a measurable piece of work that can be estimated, scheduled, assigned and controlled.²³

The WBS organises the site. It does not, on its own, tell you rates or what the client will pay.

BOQ vs WBS at a glance

	BOQ (Bill of Quantities)	WBS (Work Breakdown Structure)
Answers	What is being paid for, in what unit, at what rate	Where the work sits in the project and who owns it
Organised by	Trade / item (concrete, masonry, finishes)	Deliverables (block, floor, system, package)
Main users	Estimators, quantity surveyors, billing, client	Planners, project managers, site engineers
Changes when	Variations, extra or substituted items	Scope or sequencing changes
Alone, it shows	Total quantity and value per item	Structure of the work and responsibility
Alone, it misses	Location and timing of cost	Commercial value and rates

Neither is better. They are two views of the same work, and cost control depends on joining them.

Where cost actually leaks

Most budget overruns on site are not one big mistake. They are small gaps between three records that should agree:

1. Planned quantity (from the BOQ, split by WBS package).
2. Measured quantity (what was actually built and recorded on site).
3. Billed and paid quantity (what went into the RA bill).

Public-works practice in India builds discipline around the middle record. The CPWD Works Manual, for example, has dedicated sections on writing the measurement book, recording measurements, giving the contractor notice before measuring, test-checking of measurements by senior officers, and preparing bills from those records.⁴ It also treats extra, substituted and deviated items as a separate process with its own rate determination.⁴ Private firms don't have to copy government procedure, but the principle carries over: no bill without a recorded measurement, and no measurement without a home in the BOQ and the WBS.

How to tie site measurements to cost control: 7 steps

1. Build the WBS to the level you will actually measure

Break the project down by deliverable (block → floor → element) until each work package is something a site engineer can measure in one visit. If you would never measure "Block A superstructure" as a whole, it isn't a work package yet.

2. Split each BOQ line across WBS packages

Take each BOQ item and allocate its quantity to the work packages where it occurs. "M25 concrete in footings: 420 m³" becomes "Block A footings: 140 m³, Block B: 150 m³, Block C: 130 m³". The split must add back to the BOQ total: the 100% rule applied to quantities.

3. Give every pair a cost code

A cost code is the key that links a BOQ item to a WBS package (for example B-SUB-FTG / CON-M25). Budgets, purchase orders, measurements and bills all carry the same code. This is what lets you answer "how much have we spent on Block B footings?" in one query.

4. Record measurements against the code, with evidence

Each measurement entry should carry date, location, dimensions, computed quantity, who measured, who checked, and photos or drawings where useful. Measure on a regular cycle (weekly or per RA bill period), not only when a bill is due.

5. Compare three numbers every cycle

For each cost code, compare planned quantity, measured-to-date and billed-to-date. Flag any code where measured quantity is running ahead of physical progress, or where billed quantity is ahead of measured.

6. Handle variations as their own items

When work goes beyond the agreed quantity, or new items appear, record them as deviations or extra items with their own approval and rate, rather than quietly absorbing them into existing lines. That keeps the original budget readable.

7. Raise bills only from approved measurements

The RA bill should be generated from approved measurement entries, not typed separately. That one rule closes most of the gap between what was built and what was paid.

Cost-control checklist for your next project

• WBS covers 100% of scope; children add up to parents
• Every work package can be measured in one site visit
• Every BOQ line is split across work packages, and splits add back to the BOQ total
• One cost code per BOQ item × work package
• Purchase orders and GRNs carry the cost code
• Measurements recorded on a fixed cycle, with checker named
• Planned vs measured vs billed reviewed every cycle
• Deviations and extra items approved and coded separately
• Bills generated only from approved measurements
• Budget forecast updated when measured quantities move

Doing this in a spreadsheet vs one system

You can run this in spreadsheets, and many firms do. The problem is that the BOQ, the measurement sheets, the purchase records and the bills usually live in different files owned by different people. Every cycle someone reconciles them by hand, and errors creep in at the copy-paste.

Woxox Construction OS keeps these records together: WBS, BOQ, work packages and measurements, budgets and cost codes, requisitions, RFQs, purchase orders and GRNs, site records, RFIs, and quality and defects. Schedules carry a baseline and a forecast, so you can see how the plan has moved. Construction AI can suggest actions, but a person approves them. Accounting and GST invoicing sit in Woxox Finance on the same database, so a measurement, a purchase and a bill can all point to the same cost code.

The point is not the software. The point is that planned, measured and billed quantities stop living in three places.

Next step

If your BOQ, measurements and bills live in different files today, we can walk through how they would sit together on your own project. Talk to Woxox.

Sources

1. Bureau of Indian Standards, IS 1200 series, Method of Measurement of Building and Civil Engineering Works (published in parts). Copy via Government of India archive: archive.org.
2. Norman, E. S., et al. (2006), Practice Standard for Work Breakdown Structures overview, Project Management Institute.
3. "Work breakdown structure", Wikipedia (summarising the PMBOK Guide and MIL-STD-881).
4. Central Public Works Department, CPWD Works Manual 2012: Section 7 (Measurement Books), Section 9 (bills and payment), Section 24 (extra, substituted and deviated items).