From Estimation to Execution: How GCC Contractors Close the Data Gap

Most contractors win bids with one set of numbers and run projects with another. The estimate is built, the contract is signed, and the project is handed to the delivery team — who may never have seen the estimating assumptions in detail. By the time final costs come in, the distance between the tender BOQ and the actual cost report is so wide that no one is sure what caused the gap.

This is the estimation-to-execution data gap. And it costs GCC contractors millions every year.

The Two Worlds That Never Merge

Estimation lives in spreadsheets or standalone tools. It produces a BOQ: quantities, unit rates, allowances, contingencies. That document wins the job.

Execution lives in the ERP or project controls system. It tracks committed costs, work confirmations, subcontract certifications, labour hours, and material receipts. Those numbers tell the story of what actually happened.

The problem is these two worlds rarely share data. The rates in the estimate do not automatically populate the budget. The budget codes do not match the cost report codes. And when the project closes, the actual unit rates do not flow back into the estimating database.

The result: every new bid is priced from inherited rates, gut feel, and whatever the senior estimator remembers from three years ago.

Where the Gap Actually Costs You

The estimation-to-execution gap creates three distinct financial risks.

Tender rates that drift from reality

If steel fixing was budgeted at SAR 42/m two years ago and nobody has updated that rate since, you are bidding blind. Winning a job at an outdated rate is worse than losing it — you are committing your team to a margin that does not exist.

Budget baselines that nobody trusts

When the project budget is not built directly from the estimate — when it is retyped, reformatted, or re-entered into a different system — assumptions change in translation. The delivery team manages to a budget that already disagrees with the contract sum. Nobody owns the variance because nobody created it deliberately.

Closeout data that goes nowhere

When a project finishes, the actual cost per cubic metre of concrete, the hours-per-tonne of steel, the wastage rate on MEP materials — this data exists in the system. But if there is no structured process to extract and store it, it disappears when the project team moves on. The next estimator inherits nothing.

What Closing the Gap Actually Requires

This is not about buying new software. It is about connecting the handoff points that currently break down.

Handoff 1: Estimate to Budget

The estimate should generate the project budget directly, not be retyped into a separate system. Cost codes in the estimate must map to cost codes in the cost report. When the contract is signed, the approved tender rates become the budget unit rates — no rekeying, no translation loss.

This single step eliminates the most common source of baseline disputes. When the delivery team asks where this budget came from, the answer should be the signed BOQ, line by line.

Handoff 2: Budget to Cost Report

The cost report should pull committed and actual costs from procurement (POs), subcontract certifications (work confirmations), timesheets, and material GRNs. If any of these systems are disconnected, the cost report is lagged and incomplete.

For a SAR 200M civil works project, a two-week lag in PO committed costs means the PM is managing with potentially SAR 8 to 12M of invisible commitments. That is not a reporting problem — it is a financial control problem.

Handoff 3: Project Close to Estimation Database

This is where most contractors fall down entirely. At project close, no one systematically extracts actual unit rates by trade and material, productivity benchmarks (hours per unit of output), wastage factors by material type and site conditions, or subcontractor rate comparisons between tender, actual, and final account.

Without this structured closeout, the estimating team prices the next bid from the same spreadsheet they have been using for years.

Building the Feedback Loop

The feedback loop is not complex — it just needs to be deliberate.

At procurement: Every purchase order includes a WBS cost code and a unit rate. When GRNs are processed, actual prices are captured against the budget rate. Variance is visible immediately — not at invoice reconciliation three months later.

At certification: Work confirmation quantities are recorded against BOQ items. When certified quantity differs from the estimate quantity, the estimating team needs to know — especially on unit-rate contracts where quantity drift changes the contract value and the underlying cost assumptions.

At project close: A structured closeout report extracts actual unit rates for the top 20 cost codes by value, productivity benchmarks from timesheet and work confirmation data, and final account variances by trade. This goes into a shared cost database — not a personal spreadsheet, not the outgoing PM's laptop.

For a GCC contractor running four to six projects per year at SAR 100 to 300M each, this feedback loop compounds. After three years, the cost database holds actual performance data from SAR 1.5B or more in completed work. That is a competitive advantage that new market entrants cannot replicate with off-the-shelf benchmarks.

The Vision 2030 Dimension

The scale of Saudi Vision 2030 programmes — NEOM, ROSHN, Qiddiya, Red Sea Global — is raising the bar on estimation accuracy. Clients are running independent cost estimates and comparing them against contractor submissions line by line. Unit rates that do not reflect current market conditions stand out immediately.

Contractors that can reference actual historical performance data when defending their rates are in a stronger commercial position than those relying on outdated price books or internal rates that predate the material and labour cost movements of recent years.

In a tendering environment where BOQs run to 10,000 or more line items and variations are scrutinised clause by clause, the margin between winning a well-priced contract and accepting an underpriced one is exactly the size of the data gap.

Five Practical Starting Steps

• Map your cost codes. Confirm that estimate cost codes and ERP cost codes match. If they do not, this is the root cause of most baseline disputes. Fix it before the next project starts, not during it.
• Run a rate comparison on your most recent closeout. Take the top 10 cost lines by value. Compare tender rate to actual unit rate. A gap of more than 10% on a major cost code is a material estimating accuracy problem that cannot be explained away.
• Make budget import automatic. The signed BOQ should generate the project budget in one step. If it currently requires manual rekeying, quantify the translation errors on your last project — then make the case to fix the handoff.
• Add a closeout extract to your project completion checklist. Two pages: actual unit rates for top 20 cost codes, productivity benchmarks for key trades. Mandatory. Filed in the cost database. No exceptions.
• Set a quarterly estimation review. Once per quarter, estimating and commercial teams review cost database entries from completed projects. Rates are updated, productivity benchmarks are revised, and assumptions are challenged against evidence — not precedent.

The contractors who will price Vision 2030's second wave most accurately are those building institutional cost knowledge now — not importing a spreadsheet from 2019 and adjusting it for inflation.