+966 55 252 5261 info@ltsthink.com Alzahraa District, Jeddah Sun–Thu · 9–5
Follow:
Journal Technology

BOQ Management for Contractors: From Quantity Takeoff to Project Budget

Learn how BOQ management connects quantity takeoff, tender pricing, cost codes, procurement and project budgets into one controlled workflow for Saudi contractors.

TechnologyNov 19, 202610 min read
BOQ management on a Saudi construction site, with a quantity surveyor reviewing project drawings and measurements beside an active building project.

BOQ management is the process of controlling quantities, descriptions, rates and commercial assumptions from tender preparation through project execution. For Saudi contractors, it should do more than maintain a spreadsheet of quantities: it should connect the tender BOQ to the approved contract, project budget, procurement plan, site measurements and financial reporting.

The practical objective is simple: know what was priced, what was contracted, what has been executed, what has been purchased and what remains financially available. A connected contracting ERP system helps maintain that relationship instead of forcing commercial, procurement and site teams to reconcile separate files.

What BOQ management means in construction

A Bill of Quantities (BOQ) describes the work included in a construction contract, usually through item descriptions, units of measurement, quantities and rates. Depending on the contract and tender documents, it may also include specifications, measurement rules, provisional items and other commercial conditions.

For a general contractor, the BOQ is an important commercial reference. For an MEP contractor, it may organize electrical, mechanical, plumbing and specialist installation works. For infrastructure contractors, it can cover excavation, earthworks, utilities, roadworks and associated activities. Fit-out contractors may organize finishes, partitions, ceilings, joinery and specialist packages.

The structure differs by project, but the management requirement is consistent: each BOQ item needs a clear identity, a measurable scope and a traceable relationship with project costs.

Why spreadsheet-based BOQ management becomes difficult

Spreadsheets are useful during early estimation. They are flexible, familiar and practical when a small team is preparing a tender. Problems appear when the same BOQ moves between estimators, quantity surveyors, procurement officers, project managers, site engineers and finance teams.

Common problems include:

  • Different BOQ versions: Teams price or execute work against different revisions without realizing that the underlying quantities have changed.
  • Disconnected cost information: Tender rates, purchase orders, supplier invoices and site consumption are recorded in separate files.
  • Unclear quantity ownership: A site engineer records executed quantities, while the QS team maintains a different measurement sheet.
  • Manual budget updates: Approved changes are not consistently reflected in the project budget or procurement commitments.
  • Weak variation visibility: Additional work is performed before its commercial and contractual impact is properly assessed.
  • Difficult project reporting: Management cannot easily distinguish original quantities, revised quantities, executed quantities and remaining work.

The problem is not that spreadsheets are inherently unsuitable. It is that they become difficult to govern when multiple departments depend on the same commercial information.

BOQ management from tender to approved project budget

A reliable workflow starts before the project reaches the site. The information prepared during tendering should remain useful after contract award.

1. Receive and structure the tender BOQ

Start by importing the client's BOQ or creating an internal estimate from drawings, specifications and tender documents. Preserve the original item references and descriptions wherever possible.

Organize the BOQ into a practical hierarchy:

  • Project and contract.
  • Main work sections or disciplines.
  • BOQ groups and subgroups.
  • Individual measurable items.
  • Units, quantities and rates.
  • Technical references and supporting documents.

For MEP projects, for example, electrical containment, cabling, distribution boards, HVAC equipment and plumbing installations may need separate cost classifications. This makes later procurement and cost reporting more meaningful.

2. Validate quantities and assumptions

Quantity takeoff should be traceable to its source. Record the drawing reference, revision, measurement basis and responsible estimator or QS where applicable.

Before pricing, identify:

  • Missing or duplicated items.
  • Differences between drawings and BOQ descriptions.
  • Unclear units of measurement.
  • Scope exclusions and qualifications.
  • Provisional quantities and allowances.
  • Items requiring supplier quotations or specialist subcontractor input.

A quantity that looks reasonable in a tender spreadsheet may still be based on an outdated drawing or an incomplete scope. The estimating team should resolve these issues before the commercial submission.

3. Build the tender estimate

Each BOQ item needs a defensible rate. Depending on the work, its estimated cost may include:

  • Materials and consumables.
  • Direct labour and installation activities.
  • Equipment, machinery and tools.
  • Subcontractor work packages.
  • Transportation and delivery.
  • Site overhead and allocated project expenses.
  • Applicable risk allowances and commercial assumptions.

Separate direct costs from indirect costs and identify the assumptions behind the selling rate. This is particularly important when procurement prices, labour requirements or site conditions may change between tender submission and execution.

A useful estimating process preserves both the unit rate and its underlying cost build-up. This allows the commercial team to investigate why an item was priced in a particular way instead of treating the tender amount as an unexplained figure.

4. Convert the tender into a controlled project budget

After award, the tender estimate should not simply be renamed as the project budget. The commercial team must reconcile the submitted tender, negotiated contract, approved scope and execution assumptions.

Create an approved baseline with:

  • Original contract BOQ quantities and rates.
  • Agreed contract value and commercial adjustments.
  • Approved project budget by cost code.
  • Planned procurement and subcontractor packages.
  • Labour and equipment allocations.
  • Relevant project overheads.

This is where BOQ management becomes an operational control process rather than a document-management activity.

The project team should be able to trace a budget allocation back to the relevant BOQ item, cost code and contract scope. If a project includes additional internal cost categories, retain the relationship rather than forcing every expense into a customer-facing BOQ line.

Connect BOQ items to procurement and site execution

An approved project budget becomes useful when operational transactions are connected to it.

Procurement and material control

Material requests should reference the project, relevant cost code and, where appropriate, the BOQ item. Purchase requisitions, purchase orders, goods receipts and supplier invoices should retain these references.

For example, if a project requires a specific cable type, the procurement team should be able to identify the relevant electrical work package, planned requirement, purchased quantity and received quantity. The project manager can then review whether procurement is aligned with the approved scope and budget.

A connected ERP workflow can also distinguish between requested materials, ordered materials, received materials and materials actually issued to the site. These are different operational events and should not be treated as interchangeable quantities.

Site quantity measurement

Site engineers and quantity surveyors should record actual work against identifiable BOQ items. Each measurement should include its project reference, location, measurement period, supporting documentation and approval status.

The system should distinguish between:

  • Contract BOQ quantity.
  • Revised approved quantity.
  • Planned execution quantity.
  • Measured completed quantity.
  • Quantity submitted for valuation.
  • Quantity accepted or certified, where applicable.

These distinctions matter because physical progress, contractual valuation and financial recognition do not always happen at the same time.

For companies evaluating construction ERP in Riyadh or construction ERP in Jeddah, this connection between commercial records and site reporting is more important than simply having a digital BOQ screen.

Managing BOQ revisions and variation orders

Construction projects change. Revised drawings, site conditions, client instructions and design coordination can affect quantities and scope.

A controlled revision process should preserve the original BOQ and record subsequent changes rather than silently replacing existing values.

A practical workflow includes:

  1. Register the proposed change and its source document.
  2. Identify the affected BOQ items and project locations.
  3. Measure the additional, omitted or revised quantities.
  4. Estimate the cost and schedule implications.
  5. Submit the required commercial assessment and supporting documents.
  6. Record the relevant review and approval status.
  7. Update the approved contract baseline and project forecast when authorization is established.

Do not automatically treat a site instruction as an approved commercial variation. Contractual entitlement, authorization and valuation requirements depend on the actual agreement and project circumstances. The company's legal and contracts team should confirm the applicable process.

The same principle applies to provisional quantities and remeasurement contracts. The system should preserve the original commercial basis while allowing authorized revisions to be tracked independently.

For a deeper look at the commercial workflow, see our guide to construction tender management.

What a contractor should see in a BOQ dashboard

A useful dashboard should answer commercial questions rather than simply display the number of BOQ lines.

At project level, management should be able to review:

  • Original contract value: The commercial baseline established at award.
  • Approved variations: Changes that have passed the required authorization process.
  • Current contract value: The updated contractual position based on recorded approvals.
  • Original budget: The approved internal cost baseline.
  • Committed cost: Purchase orders and subcontractor commitments recorded against the project.
  • Actual cost: Posted transactions and allocated costs according to the company's accounting policies.
  • Remaining budget: The available budget after relevant commitments and actual costs are considered.
  • Forecast final cost: The current estimate of the total cost required to complete the project.
  • Quantity progress: Original, revised, executed and remaining quantities by BOQ item.

The distinction between budget, commitment and actual cost is essential. A purchase order represents a commitment, not necessarily an expense already recognized in the accounts. Similarly, an approved supplier invoice and a material receipt represent different stages of the procurement process.

Project directors and CFOs should be able to investigate variances at the BOQ and cost-code level, not just at the total project level.

How ERP supports BOQ management in Saudi Arabia

A contractor-specific ERP should connect commercial, operational and financial information without requiring teams to maintain parallel versions of the same project data.

For Saudi contractors, important capabilities include:

  • Arabic-first interfaces with bilingual document and reporting support.
  • Project and contract structures that reflect local contracting workflows.
  • ZATCA-ready invoicing processes integrated with the finance workflow, with applicable requirements confirmed during implementation.
  • Purchase and supplier document tracking.
  • Site-friendly quantity and material capture through mobile devices.
  • Approval workflows for requisitions, commitments and commercial changes.
  • Project-level accounting and profitability reporting.
  • Document history and traceability for revisions and approvals.

LtsThink, خلينا نفكر, implements Odoo for contractors and also designs custom ERP systems when standard configurations do not adequately support the company's contract cycle. The choice depends on the complexity of the BOQ structure, the required integrations, approval responsibilities and the level of customization needed.

You can explore the available Odoo construction ERP approach or review the broader contracting ERP solution.

When should a contractor implement ERP for BOQ control?

An ERP becomes worth evaluating when the commercial team repeatedly reconciles different BOQ versions, procurement cannot see the approved project budget, site measurements are disconnected from financial records or management cannot explain project cost movements.

However, not every contractor needs a new ERP immediately.

Do not buy an ERP or a Manufacturing Execution System (MES) just because the current estimating spreadsheet looks untidy. A small contractor with limited projects, a stable scope and clear approval responsibilities may be better served by improving its existing estimating templates, document control and review procedures first.

MES is generally intended for production-floor execution and manufacturing processes. A construction contractor should not purchase an MES simply to manage site BOQs, quantities and subcontractor costs.

Before selecting a system, establish:

  • Who owns the BOQ at tender stage and after award?
  • How are revisions approved and distributed?
  • Which departments need access to the same project information?
  • How are cost codes linked to procurement and accounting?
  • What information must site teams capture?
  • Which existing accounting, HR or document systems need integration?

A discovery exercise should identify the actual workflow gaps before software configuration or custom development begins.

Choosing between Odoo and custom BOQ management

Odoo can provide a practical foundation for companies whose commercial and operational requirements can be supported through its standard applications and appropriate configuration. LtsThink implements Odoo and adapts workflows where necessary.

A custom ERP may be more appropriate when the contractor has specialized contract structures, complex quantity measurement rules, unusual approval hierarchies, or integrations that require a different application architecture.

The decision should consider the entire business process, not just the BOQ screen. A system that handles quantity takeoff but cannot connect procurement, site execution, contract changes and accounting will leave the original problem unresolved.

A sensible implementation begins with the most important commercial workflow, validates it using real project documents and expands through controlled releases. The exact scope depends on the contractor's operations, existing systems and data quality.


Work with us: Explore LtsThink's contracting ERP software in Saudi Arabia to connect tender BOQs, project budgets, procurement and site execution. You can also read our guide to construction tender management or contact our team to arrange a discovery discussion. We define the implementation scope after understanding your actual contract cycle. LtsThink provides a fixed-price proposal after a discovery visit.

FAQ

What is BOQ management in construction? BOQ management is the process of organizing, validating, pricing, revising and tracking the quantities and rates included in a construction contract. It connects the tender estimate with the approved project budget and execution records.

How does BOQ management software help contractors? It connects BOQ items with project budgets, procurement, site measurements, variations and financial reporting. This helps teams work from controlled project information instead of maintaining disconnected spreadsheets.

Can an ERP manage BOQ revisions and variation orders? Yes. An appropriately configured ERP can preserve original BOQ versions, record proposed changes, track supporting documents and approvals, and update the approved project baseline when the required authorization is established.

Should a contractor use Odoo or a custom ERP for BOQ management? Odoo is suitable when its standard applications and configuration can support the required workflows. Custom ERP is worth considering when contract structures, measurement rules, approvals or integrations require specialized functionality. The decision should follow a review of the actual business process.

Construction ERPBOQ ManagementQuantity SurveyingProject Cost ControlSaudi Contractors
Let's talk

Like how we think? Let’s build together.

Tell us about your project — we usually reply within one business day.