AWRA OpsHub Search

Construction ERP in Kenya: Materials, Sites, Plant & Retention (2026)

A contractor runs three businesses at once — a materials operation, a fleet of expensive machines, and a set of fixed-price promises called contracts. Here is how the ones that stay profitable keep all three under control, and where the money actually leaks on a Kenyan site.

Construction & Contractors Washingtone Aura 10 min read

Construction is the operations problem in its hardest form. Your warehouse moves — it is a different muddy site every few months. Your most valuable equipment changes location weekly. Your revenue is fixed in advance by a bill of quantities, so every shilling of unplanned cost comes straight out of your margin, and you often do not find out it happened until the job is finished. A contractor who cannot see materials, plant, and job cost in real time is not running a business so much as discovering one at the final account. This guide walks the four places construction money leaks in Kenya, and what controlling each actually looks like.

Illustration of a supply chain across sites
A contractor is a materials business, a plant-hire business, and a fixed-price promise — all running on the same thin margin, all at once.

1. Materials: the leak you can walk through

Materials are usually the largest single cost on a job and the easiest to lose. Cement, steel, timber, and fittings leave a central store or arrive from a supplier, travel to site, and are consumed by work — and at every one of those steps, quantity goes missing. A lorry signed for 500 bags delivers 480. A pallet of tiles walks off a weekend site. Offcuts and breakage are never recorded. On paper the job used what the BQ said; in reality it used more, and the difference is invisible until someone reconciles the final material cost against the contract. The fix is not suspicion — it is booking every issue and delivery against a specific site and task, so consumption is measured as it happens and store-to-site variance becomes a weekly report rather than a year-end shock.

2. Job cost: knowing while you can still act

The defining feature of construction is that the price is fixed before the cost is known. The BQ is a set of promises made at tender; the site is where those promises meet reality. The contractors who stay profitable are the ones who track actual spend against each BQ line as the work runs — so when the concrete line is 30% over budget at foundation stage, they know at foundation stage, while there is still a project left to correct. The ones who fail track cost the way a periodic system tracks stock: they find out at the end, when the only thing left to do is absorb the loss. BQ-versus-actual job costing is the single discipline that separates the two.

Illustration of decision intelligence comparing budget to actual
The BQ is the promise; actual cost is the reality. Seeing the gap open while the job runs is the difference between a correction and a loss.

3. Plant & equipment: assets that move every week

A contractor's plant — mixers, compactors, generators, scaffolding, power tools — represents serious capital, and it is designed to move. That mobility is exactly what makes it hard to control: a register typed once is wrong within a month, machines sit idle on a finished site while another job hires in the same equipment, and tools disappear with no custodian to answer for them. Treating plant as assets with named custodians and movement history turns "where is the compactor?" from a phone-around into a lookup, surfaces idle equipment you are paying to own, and keeps service schedules from slipping until a breakdown stops a pour.

4. Procurement, retention & the cash you forget

Two financial disciplines quietly decide whether a profitable job is also a paid one. The first is procurement: on a busy site, staff phone suppliers directly and commit the company's money before anyone approves it, so the first finance hears of a purchase is the invoice. A requisition-then-PO flow with enforced thresholds closes that gap. The second is retention: on most contracts, a percentage of every certificate is held back by the client, released only after defects liability. That retained money is real revenue you have earned — and it is routinely forgotten because it lives in a quantity surveyor's memory rather than a system. Tracking retention and subcontractor certificates as project financials means the cash you are owed reports itself instead of quietly aging.

Leak How it hides What controls it
Materials Consumed "per the BQ" while site used more Issues booked per site/task; weekly variance
Job cost overrun Discovered at the final account Actual vs BQ tracked line by line, live
Idle or lost plant Register typed once, never updated Custodians, movement history, utilization
Uncontrolled buying Commitment before approval Requisition → approval → PO thresholds
Unclaimed retention Lives in one person's head Retention held tracked as a receivable

Start with one site, not the whole company

The mistake is trying to systematize every site at once. Pick one live job, load its BQ, open its store with a count, and book issues against tasks. The first variance report — the gap between what the BQ allowed and what the site actually consumed — usually pays for the whole project by itself, and gives you the evidence to roll it out to the rest.

Illustration of asset tracking across sites
One system across every site: materials, plant, cost-to-date, and retention — the contractor's whole operation in one view.

None of this requires a head-office ERP built for a multinational. It requires the operations core — inventory, procurement, assets, and project cost — connected on one set of records and reachable from a muddy site on a phone. That is precisely the gap construction operations software fills for Kenyan contractors: not estimating, not design, but the discipline of knowing what every site is costing you while the job is still running.

See a live site costed end to end

Bring one BQ, one store, and one set of plant — watch materials, spend, and retention controlled while the job is still running.

Explore construction operations

Frequently asked questions

Do we need a full ERP to run construction operations, or just accounting software?

Accounting software tells you the money after the fact; it cannot see materials leaving a store, plant moving between sites, or spend against a BQ line while the job runs. Construction needs the operations core — inventory, procurement, assets, and project cost — connected together. That is what lets you catch an overrun in time to act on it rather than discovering it at the final account.

Where does construction money actually leak?

In four predictable places: materials consumed beyond the BQ without anyone measuring it, job overruns discovered too late to correct, plant that sits idle or goes missing because the register is never updated, and earned retention money that is forgotten because it lives in one person's memory. Each is a control gap, not bad luck.

What is the fastest way to start without disrupting live sites?

Start with a single live site: load its BQ, open the store with a physical count, and book every issue and delivery against a site and task. The first variance report is usually enough to justify the whole rollout, and you extend to plant, procurement, and the rest of your sites from there.

Does this replace our estimating and BQ software?

No. Estimating software produces the BQ; the operations system takes that budget and tracks actual materials, labour, and costs against it as the work happens. The two are complementary — you keep the estimating tool your quantity surveyors know and add the control layer that measures reality against their numbers.

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center