How ERP Improves Construction Project Management

Why Construction Projects Are Hard to Control

A contractor does not sell a product off a shelf. It delivers a one-off contract on a specific site, for an agreed price and duration. Each project behaves like a small company of its own, with a bill of quantities, suppliers, subcontractors, labour, equipment and its own cash flow. Then the contractor runs several of these at once, often in different cities.

In mid-sized Saudi contracting firms, the recurring problem is rarely a lack of engineering skill. It is late information. The project manager knows what is happening on site, the accountant knows what has been paid, procurement knows what has been ordered. The combined picture only appears when the progress claim is prepared or the quarter closes, and by then the overrun has already happened.

An ERP system does not run the project for the engineers. What it does is put cost, schedule, resources and billing in one place, so everyone sees the same numbers at the same time. This article shows how that works at each stage of a project, with worked numbers and the Saudi requirements that apply.

The Project Lifecycle Seen as Data

To understand what the system contributes, follow the information through the project:

1. Estimating and tender: cost and revenue estimated for every line of the bill of quantities.
2. Award and budget: the winning estimate becomes an approved budget broken down by work item.
3. Execution: materials bought, labour and plant deployed, subcontracts let, daily progress recorded.
4. Billing: progress claims raised against work done, net of retention and advance recovery.
5. Control: actual compared with plan, and a forecast of cost at completion.
6. Close-out: handover, release of retention and analysis of project profit.

Done manually, every stage lives in a different file. In an integrated system, the stage 1 estimate becomes the stage 2 budget, every cost in stage 3 is charged to a budget line, and stage 5 control falls out of the data automatically instead of being extra work.

From Bill of Quantities to Approved Budget

Control starts with the work breakdown structure: dividing the project into measurable, priceable items such as excavation, concrete, blockwork, electrical, mechanical and finishes. Each item has a quantity, a unit rate and an estimated cost split into materials, labour, plant and subcontract.

When the estimate is built in the system using that structure, it becomes the budget once the job is won. That avoids a familiar problem: the tender priced in Excel, a different budget built in accounting, and nobody sure which is the reference. Tranquil covers cost and revenue estimation and project budgeting within its contracting solutions.

Committed cost: the number most reports miss

Most manual reports compare budget with actual spend. Construction needs a third figure: committed cost, meaning purchase orders and subcontracts already issued but not yet invoiced. A line with a SAR 1 million budget and SAR 400,000 spent looks comfortable. If approved purchase orders worth SAR 550,000 are outstanding, the real remaining budget is SAR 50,000. A system that ties purchasing to the budget shows that automatically.

Cost Control by the Numbers: A Hypothetical Example

Take a commercial building with a contract value of SAR 12 million and an estimated cost of SAR 10.2 million, a planned margin of 15%. Six months in, the project engineer assesses progress at 40%, and recorded actual cost to date is SAR 4.6 million.

An index below 1 means each riyal of work done is costing more than planned. If the trend holds, margin drops from 15% to about 4%. Known in month six, this can still be fixed: review the overrunning items, renegotiate with a supplier, or submit a variation claim for extra work that was never approved. Discovered in month fifteen, all that is left is to book the loss.

The only condition is that every cost hits the right project and item when it is recorded, and progress is measured consistently. That is exactly what linking purchasing, stores and payroll to projects inside one system delivers.

Progress Claims, Retention and VAT

A progress claim (often called an interim payment application) is the periodic invoice for work completed. It usually includes:

• Cumulative value of work done to date, less amounts already claimed.
• Retention at the contract percentage, typically released at handover or after the defects liability period.
• Recovery of part of any advance payment.
• VAT at 15%.

Hypothetical claim

Work done this month is SAR 800,000, retention is 10% and advance recovery is 10% of each claim:

• Value of work: 800,000
• Less retention: 80,000
• Less advance recovery: 80,000
• Net before VAT: 640,000

VAT timing deserves care. Saudi VAT is due on the earliest of supply, invoice issue, or receipt of payment to the extent received. An advance is taxed when it is received. For government contracts, since November 2021 VAT is due on the earlier of the payment order or receipt of payment. When VAT on retention becomes due depends on the contract terms, so agree the treatment with your tax adviser and configure it once, so it does not change from claim to claim.

A system that holds the contract terms and calculates cumulative values cuts claim preparation from days to hours, prevents billing the same work twice, and issues the compliant e-invoice from the same data.

Subcontractors: Contract, Progress and Payment

On medium and large jobs, subcontractors can deliver half the work or more. Managing them is the mirror image of your own claims: now you receive applications, check them and make deductions.

• Record each subcontract against the project items it covers, with value, retention and payment terms.
• Approve an application only against progress certified by your site engineer, not the percentage the subcontractor declares.
• Track retention held for each subcontractor and its release date.
• Link back-charges for materials you supplied to the subcontractor's applications.

We go into this cycle in detail in our article on subcontractor management in Saudi Arabia.

Materials on Site

Construction materials do not always pass through a central store. Some are delivered straight to site, some move between projects, and some are left over when an item finishes. If none of that is recorded, two problems follow: one project carries the cost of materials used on another, and materials disappear without anyone knowing where.

The minimum controls:

• Material requests raised from site against a budget line.
• Site receipts recorded at actual quantities and matched to the purchase order and invoice.
• Transfers between projects posted as stock movements that move the cost.
• Surplus returned to the store or transferred with a document, not abandoned on site.

Tranquil's material management for contracting covers these movements, alongside daily activity management that records what was done on site each day.

Labour, Plant and the Schedule

Labour cost per project is only accurate when each worker's hours are allocated to a project and item. Attendance and timesheets linked to payroll achieve that, and allow overtime, paid at the hourly wage plus 50% of basic wage, to be charged to the right job.

Scheduling has to respect Saudi seasonal rules. From 15 June to 15 September each year, work under direct sun is banned between 12:00 and 15:00. A summer programme that ignores those hours will slip. Working hours for Muslim staff during Ramadan are capped at 6 a day and 36 a week, which changes crew output and belongs in the plan.

Plant, owned or hired, is charged to projects by operating hours. Owned equipment carries its share of depreciation, maintenance and fuel; hired equipment carries the hire charge. With equipment held in the asset register, it can be transferred between sites while tracking its current location and custodian.

Project Cash Flow: Profit Is Not Enough

A project that is profitable on paper can still strain the company's cash. The contractor pays suppliers, labour and subcontractors before the claim is paid, and part of every claim is held back until the end.

Hypothetical funding gap

On the same project, monthly cost averages SAR 700,000 and monthly claims about SAR 800,000, paid 60 days after submission with 10% retention. In the first two months the contractor pays out SAR 1.4 million and receives little beyond the advance. From month three it receives SAR 720,000 a month after retention while paying SAR 700,000. The opening gap closes slowly, and accumulated retention, SAR 80,000 a month, stays out of reach until handover.

This calculation should be visible before the contract is signed, because it sets the bank facilities the company needs and shows whether the payment terms are acceptable at all. Combined across projects, the forecasts reveal which months will squeeze liquidity, early enough to talk to suppliers or the bank. An integrated system builds the forecast from existing data: committed purchase orders and their due dates, subcontracts, payroll and the expected claim schedule. For more on this, see project budgeting and cash flow.

Revenue and Work in Progress in the Accounts

Companies reporting under IFRS as endorsed in Saudi Arabia generally recognise construction contract revenue over time, based on progress, rather than at final handover. Monthly accounts therefore need a reliable progress estimate per project and a comparison of revenue recognised against amounts claimed. The difference appears either as an asset (work done but not yet billed) or a liability (billing ahead of progress).

Without a system holding actual cost, progress and claims per project, this becomes a manual exercise every period and a frequent source of audit findings. Tranquil's work in progress feature tracks these balances per project.

Common Mistakes

• Costs posted to a general account: expenses booked to "project costs" without project and item, so true profitability is lost.
• Extra work without a written variation: requested verbally on site, then disputed later for lack of evidence.
• Estimated rather than measured progress: a manager says 60% without measuring quantities, profit shows early and then collapses near the end.
• Forgotten retention: large sums owed from projects handed over a year ago that nobody has chased.
• Missing indirect costs: site office, transport, labour accommodation and insurance are real project costs.
• Late supplier invoices: an invoice that reaches accounts two months late makes the project look better than it is for two months.

Reports for Each Level

The value lies not in the number of reports but in all four coming from the same source, so the project manager and finance manager stop arguing about which figure is right.

Rolling Out an ERP in a Contracting Firm

1. Standardise the item structure so all new projects share it, with room for project-specific items.
2. Start with new projects. Do not migrate every live job at once. Begin with one or two from day one and bring ongoing jobs in with opening balances per item.
3. Tie purchasing to the budget. No purchase order without a budget line. This is the single most important rule.
4. Train site teams. Site managers supply progress and receipt data; if they do not buy in, the data never arrives.
5. Hold a joint monthly review of project and finance on one report, so the system becomes the basis for the discussion.

To see how Tranquil's contracting solutions would work on your projects, contact our team.

Frequently Asked Questions

Does a small contractor need an ERP?

If it runs two or more projects at a time, or relies on subcontractors and periodic claims, usually yes. A firm with a single project may manage with simpler tools, but complexity grows quickly with each extra job.

How is project management software different from a construction ERP?

Project management software focuses on schedules and tasks. An ERP links those to actual cost, purchasing, stores, payroll, billing and accounting, giving the financial picture of the project, not just the timeline.

How should progress be measured?

By quantities completed per item against the bill of quantities, or by milestones defined in the contract. What matters is using one consistent method across projects, certified by a responsible engineer rather than a general estimate.

Can the system handle variations?

It should. An approved variation adjusts the contract value and the budgets of affected items, and unapproved extra work should appear in a separate report so it is not done without a claim.

When is retention released?

According to the contract, typically part at practical completion and part after the defects liability period. The system tracks retention per project and per subcontractor and flags it when due.