BOQ budget control: tie every purchase request to the approved BOQ

BOQ budget control: tie every purchase request to the approved BOQ

Published By

Umar Shariff
Construction/Contracting
Nov 21, 2026

In short: BOQ budget control means no purchase request can leave site unless it points to a line of the approved BOQ and asks for no more than that line has left. A Saudi contractor gets there with a gate: the estimator's budget is loaded, the technical office breaks each BOQ line into the materials it will consume, cost control approves, and the BOQ and budget are locked. Hierarchical cost codes are reused across projects, and a request can only pick an approved line with requested ≤ planned − already requested. Quantity gaps, such as 1,000 m budgeted against a 1,200 m take-off, surface before execution, and any role that can bypass the budget is audited. Below: the gate, the cost codes, the request rule, the approval chain, a gap example and a free BOQ budget control sheet.

Procurement had already ordered 1,000 metres of cable tray for the second tower, exactly what the budget said. In month seven a site engineer sent a request for 200 metres more. Nobody had made a mistake in the field: the technical office's take-off from the shop drawings had said 1,200 metres since month two. The budget had been loaded from the tender estimate and never compared with it. The 200 metres were bought anyway, the cost hit a line with nothing left on it, and the project margin dropped in a report nobody read until the quarter closed.

The money did not leak at the supplier. It leaked in the gap between the budget, the BOQ and the purchase request, three documents that had never been tied together.

Why does margin leak when purchase requests are not tied to the BOQ?

When the BOQ lives in Excel and requests live in email, these things happen on every site:

  • Requests for items the BOQ never had. A site buys a "better" product nobody priced.
  • Requests above the BOQ quantity. Each request looks small; together they pass the line.
  • The budget and the take-off disagree, and nobody finds out until the last order.
  • Different codes on every project, so nobody can compare concrete cost across jobs.
  • Edits nobody can see. A budget line cut or raised quietly, with no record of who did it.
  • Finance sees the order after the fact. By the time a PO reaches finance, the line is already over.

None of this is fraud. It is what happens when the three documents are separate and the check is a person's memory.

What is the contract to budget to BOQ gate?

The contractor's rule is that the system starts at contract signature, and nothing is bought until the gate is closed:

The BOQ budget control gate in five steps: contract signed, estimator's budget loaded, technical office breaks each BOQ line into materials and quantities, cost control approves, then the BOQ and budget are locked
The gate: nothing is bought until the BOQ and budget are approved and locked
  1. Contract. The project opens with its contract value and BOQ.
  2. Estimator's budget. The estimator's Excel budget is loaded line by line. One contractor's upload had more than 20,000 lines.
  3. Technical office analysis. The technical office breaks each BOQ line into the materials and quantities it will really consume, from drawings and shop drawings.
  4. Cost control approval. Cost control checks the analysis against the budget and approves the final BOQ.
  5. Lock. Approval locks the BOQ and the budget. A separate role can unlock a line for a controlled correction, and every unlock is logged.

From here on, every purchase request draws from the approved BOQ. For the basics of how a BOQ is built, see our guide to BOQ in civil engineering.

How should construction cost codes be structured?

Give the whole company one set of cost codes and reuse it on every project. The contractor uses a hierarchy: a trade at the top and the element below it.

A hierarchical cost code tree reused across projects: 01 concrete with 01-01 columns and 01-03 footings, 04 blockwork with 04-01 block walls; the specification such as 35 or 50 MPa sits on the BOQ line, not in the code
One cost code tree for every project
  • 01 Concrete: 01-01 columns, 01-03 footings.
  • 04 Blockwork: 04-01 block walls.

The code stays the same from project to project; the specification changes on the BOQ line. Columns are 01-01 whether the mix is 35 MPa on one job or 50 MPa on the next. That is how you compare the cost of columns across five projects. As the contractor's team put it, "the whole company works on this code."

Each BOQ line is then built up from five cost types: materials, labour, subcontractor, tools and other (tests, curing and similar). A request draws on the cost type it belongs to, so a materials request cannot quietly use the labour allowance.

What is the purchase request rule?

One rule does most of the work:

A request can only pick an approved BOQ line, and requested quantity ≤ planned quantity − quantity already requested on that line.

The purchase request rule on one BOQ line: planned 100, already requested 60, so 40 is available; a new request for 50 is blocked and a request for 40 or less passes
Requested must be within planned minus already requested
Line 01-01, columns concreteQuantity (m³)
Planned on the approved BOQ100
Already requested (not rejected)60
Available to request40
New request for 50blocked: 10 over
Attempt to cut planned to 40rejected: below the 60 already requested

Three more rules close the loopholes:

  • No items outside the BOQ. If the site needs something the BOQ does not have, that is a variation or a budget addition, decided by the people who own those, not a purchase request.
  • A line with requests cannot be deleted, and its planned quantity cannot drop below what is already requested.
  • Below is fine, above is not. A request may be smaller than the line; it can never be larger.

One BOQ line can still have several purchase orders. On one tower, 20,000 m² of porcelain was split into 15,000 m² from the manufacturer and 5,000 m² from a distributor. Both orders draw from the same line, and the rule counts both.

Who touches a purchase request, and in what order?

The rule stops the obvious overrun. The approval chain stops the rest:

Purchase request approval chain in five steps: site engineer raises it against a budget line, technical office checks quantity against real site need, procurement gets two to three quotes from approved suppliers, cost control re-checks quantity price and total, procurement issues the PO and finance pays by payment milestones
Five people, five checks, one purchase order
  1. Site engineer raises the request against a budget line.
  2. Technical office checks the quantity against what the site really needs now.
  3. Procurement gets two or three quotes from suppliers approved for that project, after the consultant has approved the material submittal.
  4. Cost control re-checks quantity, price and total against the line.
  5. Procurement issues the PO, and finance pays according to the PO's payment milestones.

Two details make the chain stronger. Free-text payment terms ("50/50", "70/30", "advance") are replaced by mandatory payment milestones on the PO. And a supplier with no VAT number and no commercial registration on the vendor master cannot be paid. Our guide to how purchase orders work covers the PO itself.

How do quantity gaps surface before execution?

Go back to the cable tray. The budget said 1,000 m and the take-off said 1,200 m. The gate is where that is caught: when the technical office breaks the line into real quantities, the analysis sits next to the budget and the difference is visible in month two, not month seven.

A quantity gap on one line: budget 1,000 metres against a technical office take-off of 1,200 metres, a 200 metre or 20 percent gap to resolve before execution as a variation or a budget addition
Find the gap at the gate, not at the last order

Then decide what the gap is:

  • The client's scope grew. It is a variation: price it and get it approved.
  • The estimate was short. It is a budget addition, decided by top management, with a reason.
  • The take-off is wrong. The technical office corrects it before anyone orders.

Set a threshold so small differences do not swamp the review; flagging any line more than 5% apart is a reasonable start. What matters is that every gap has an owner and a decision before the first request, so the construction budget means what it says.

Why audit every budget-bypass role?

Every system has a way round its own controls: an UPDATE BOQ role, an administrator, a "budget override" setting for emergencies. That is normal. Leaving it unwatched is not. At one company, a user with a budget-bypass role cut a budget line and nobody noticed for a month.

  • List every role that can unlock, edit or bypass the BOQ and budget, and who holds it.
  • Log every change: line, old value, new value, who, when and why.
  • Read the log monthly in the cost control review, and ask about every change made by someone outside the approval chain.
  • Keep the bypass roles few, and take them back when a project closes.

How can you start in 30 days?

  • Week 1: agree the cost code tree with projects, the technical office and cost control. Map one live project's BOQ to it.
  • Week 2: run the gate on that project: load the budget, add the technical office's quantities, list the gaps, approve and lock.
  • Week 3: route every new purchase request through the rule and the approval chain. Record blocked requests and why.
  • Week 4: run the first monthly review: gaps closed, requests blocked, changes in the log. Then take the next project through the gate.

Download the free BOQ budget control sheet

The kit puts the gate and the rule into a workbook and a short guide:

  • Excel sheet: a Start here sheet; Settings with your authorised roles and gap threshold; a cost code tree; the BOQ budget with take-off against budget, the five-way build-up, requested, available and percent consumed; a purchase request log that checks each request against what is available and marks it OK or BLOCKED; a budget change log that flags changes by anyone outside the authorised roles; and a summary by cost code.
  • PDF guide: the gate, the cost code tree, the request rule, the approval chain, the gap decisions, the bypass-role audit, the 30-day start and a blank purchase request form to print.

Where does HAL Contracting fit?

In HAL Contracting, procurement sets a budget per budget reference and activity and ties every BOQ item to its activity. Purchase requests, purchase orders, stock issues and invoices all count against the activity as committed cost. Project admins see only their own projects, pick the BOQ and see how much of each item is left to order. A request that would break the BOQ or the budget is blocked, and it is checked again at the purchase order. RFQs go to several vendors with a side-by-side comparison, budget changes go through an approval workflow, and budget against actual is reported per project and cost centre with a variance report. See HAL pricing for the plans.

Related reading: variation orders on the BOQ, material inspection requests and two-step site receipt and job costing: actual vs estimated cost.

Frequently asked questions

What is BOQ budget control?

BOQ budget control ties every purchase to a line of the approved bill of quantities and its budget. Requests can only pick approved lines, can never ask for more than the line has left, and are checked again before the purchase order is issued.

How do you tie a purchase request to the BOQ?

Give every request a BOQ line and cost code, and check it with one rule: requested quantity must be no more than the planned quantity minus what is already requested on that line. Items that are not on the BOQ go through a variation or a budget addition instead.

Who should approve the BOQ and budget before procurement starts?

The estimator prepares the budget, the technical office breaks each BOQ line into the materials and quantities it will consume, and cost control approves the final BOQ. Approval locks the BOQ and the budget, and only a separate, logged role can unlock a line.

How should construction cost codes be structured?

Use one hierarchy for the whole company, with a trade at the top and elements below it, such as 01 concrete with 01-01 columns and 01-03 footings. Reuse the codes on every project and keep the specification on the BOQ line, so costs can be compared across jobs.

What should you do when the take-off is larger than the budget?

Find it at the gate, before anyone orders. If the client's scope grew, raise a variation. If the estimate was short, top management decides a budget addition. If the take-off is wrong, the technical office corrects it.

Why audit roles that can bypass the budget?

Because every bypass role can change a budget without going through the approval chain. At one company a budget line was cut by such a user and nobody noticed for a month. List the roles, log every change and read the log each month.

Umar Shariff