BOQ best practices for UAE projects

The Bill of Quantities is the spine of every UAE construction project. Tender pricing references it. IPC measurement quotes it. Variation orders extend it. Cost control reports against it. Subcontract awards flow from it.

When the BOQ is well-structured, every downstream module benefits. When it isn't, the same problems surface again and again at three weeks into the project — and they get more expensive every week after that.

These are the six rules that, in my experience running projects in Abu Dhabi, separate a BOQ that ages well from one that becomes a liability.

Rule 1: Lock the structure before you price

The BOQ structure — Bills, Sections, Sub-sections, Items — should be agreed and frozen before estimating starts. Restructuring a BOQ mid-tender is what causes the "version 3 has 1,247 items, version 4 has 1,251 — but who can map which is which?" problem.

A defensible structure looks like:

• Bill 1 — Substructure: earthworks, foundations, basement retaining
• Bill 2 — Superstructure: columns, slabs, walls, staircases
• Bill 3 — Finishes: floor, wall, ceiling, joinery
• Bill 4 — MEP: mechanical, electrical, plumbing
• Bill 5 — External works: landscaping, roads, boundary

Within each Bill, sub-sections drill down two levels max:

Bill 1 — Substructure
  1.1 Earthworks
    1.1.1 Excavation in soft soil
    1.1.2 Excavation in rock
  1.2 Foundations
    1.2.1 Mass concrete
    1.2.2 Reinforcement

Anything more granular is a measurement detail, not a structural one.

Rule 2: One unit per item, no exceptions

A BOQ item that mixes units — "Reinforcement steel (kg / m³)" — is a landmine. The estimator picks one to price; the QS measures the other; the consultant rejects the IPC. Pick the unit per BOQ industry standard (reinforcement: kg; concrete: m³; formwork: m²) and stick with it.

If a single physical item genuinely needs two units (very rare), split it into two BOQ items.

Rule 3: Rates are time-stamped, not eternal

A unit rate is valid as of a specific date. Steel rates in May 2026 are not the same as in May 2025; concrete prices float with cement manufacturer pricing rounds.

When a tender takes six months from invitation to award (not unusual in the UAE), rates that were defensible at submission may need revisiting at award. Build that expectation in: lock the BOQ rates, but track the basis date and the contingency you priced.

Rule 4: Provisional sums are dangerous defaults

It's tempting to throw provisional sums (P-sums) at items you can't fully scope at tender. The danger: a P-sum hides everything. Eventually those items get measured, priced, and added to the IPC — and the consultant has every right to reject the rate basis if the tender didn't capture it.

Better: itemize as much as possible. If you absolutely must use a P-sum, attach the assumed scope and rate basis as an annexure to the BOQ. When the actual scope is finalized, you have a defensible reference point.

Rule 5: Revisions are diffs, not replacements

Halfway through tendering, the consultant issues an addendum. Three items change quantity, two new items are added. The wrong response: re-issue the entire BOQ as "v2."

The right response: track the revision as a diff. Item 2.3.4 changed from 250 m³ to 280 m³. Item 4.1.7 added (15 nos). That's revision 2.

When IPCs reference the BOQ, they reference a specific revision. Disputes over which revision was current at the time of measurement get resolved by the diff, not by competing PDF copies.

Rule 6: Excel is a starting point, not a system

Every BOQ in the UAE starts as an Excel file. That's fine for tender exchange — Excel is the universal interchange format.

But the moment the project starts, that Excel needs to live inside a system that can:

• Track revisions as diffs (Rule 5)
• Tie measurements back to specific items (for IPCs)
• Track committed vs. paid vs. remaining quantities
• Flag when measured quantity exceeds BOQ + approved VOs

Excel can do none of these reliably. It can be made to look like it does, but the moment you have 50 active projects, the maintenance burden of doing this in Excel exceeds the cost of moving to a real system.

A worked example

Imagine a 4-tower residential project. The BOQ has 1,247 items across 5 Bills.

In month 6, the consultant issues an addendum:

• 12 items see quantity changes (mostly increases, due to design evolution)
• 4 new items added (fire-rated doors that weren't in the original spec)
• 1 item deleted (a floor finish substituted by another)

In Excel, this typically becomes "BOQ_v3_FINAL_REV2.xlsx" with cells highlighted in yellow. Six months later, when an IPC dispute arises, nobody is sure whether yellow meant "changed" or "to be reviewed."

In a system designed for BOQs, the addendum is a tracked revision. Item 2.3.4 went from 250 m³ to 280 m³ on 2025-11-15, attributable to addendum #4. The IPC dated 2025-12-01 references item 2.3.4 at its 2025-11-15 quantity. There is no ambiguity.

What this looks like in practice

The BOQ Importer in ORKSTRA was built around these six rules.

• It enforces single-unit items (Rule 2)
• It preserves Bill / Section / Sub-section structure (Rule 1)
• It tracks revisions as diffs (Rule 5)
• It exposes the basis date for rates (Rule 3)
• It flags P-sums for explicit handling (Rule 4)
• It feeds directly into IPC measurement and cost control (Rule 6)

The Excel doesn't disappear — you still receive it from consultants, you still send it to subcontractors. It just stops being the system of record.

That single shift is worth half the IPC cycle time on most projects we've seen. Get the BOQ right, and everything downstream gets easier.

— Eng. Amr Shoieb