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 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.
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.
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 and exposes idle equipment you are paying to own — a machine that has not moved in five weeks is visible to anyone reading the history. Service is the part it will not do for you: there is no service interval and no next-service date on an asset, so keep the maintenance calendar on a wall chart in the yard.
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 narrows that gap, though it is worth knowing where the enforcement actually sits: a budget overrun is recorded on the approval and notifies the approver rather than holding the request, while receiving more than was ordered, and paying against an order that does not reconcile, are both refused outright. 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 | A task per element; live actual cost, budget compared by hand |
| Idle or lost plant | Register typed once, never updated | Custodians and movement history; idleness read off the dates |
| 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, create a task for each major element of its BQ, open its store with a count, and book issues against those tasks. Keep the BQ allowance per element in a spreadsheet — there is no BQ structure here to load it into. 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.
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.
What AWRA OpsHub does today
- A project per job, with a budget amount, and committed and actual cost tracked against it.
- Site stores as locations, each with its own stock position and governed transfers between them.
- Plant and equipment as assets with named custodians, movement history between sites, and retirement.
- Procurement with permission-gated approval before ordering, and refusals that bite downstream — an over-delivery blocked at the receiving bay, a payment blocked when it does not match the order.
- Time entries costed to the project, and expenses coded to it.
- Offline capture, which matters on sites without signal.
More we can add to your workspace
- A bill of quantities. A BQ entity with BQ lines, so a project carries a measured schedule of rates rather than a single budget amount.
- Variations and claims. A variation order record, so scope changes are tracked here rather than outside.
- Retention money withheld, tracked and released on schedule.
- Subcontractor management — subcontract, certificate or payment application.
- A progress or valuation certificates, so cost-versus-progress is not something we can compute.
- A project on stock issued from a store, so materials drawn from existing stock land on the job.
Be very clear on the split before buying. The materials, plant and buying side is real and is where most Kenyan contractors are actually losing money. The contract side — BQ, variations, retention, subcontractor certificates — does not exist here at all, and a contractor expecting a construction ERP in the full sense will be disappointed. Those two sentences should decide the conversation.
Anything above that you need, we can build for you
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point, not a limit on what AWRA OpsHub can do for your organisation. Kenya's eTIMS integration and its maintained payroll engine are both in the product because clients needed them and commissioned them; neither appeared by itself, and the same door is open for whatever you just read about. One qualification so this is worth what it claims: a small number of things on this blog we deliberately leave to a specialist rather than build — a statutory ledger we will not sign our name to, a rule that would decide a tax question for you, a clinical or member-funds record that belongs in a regulated system — and where that is true the post says so in those words. Everything else is a scope, a timeline and a price.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
The module-shaped additions, which are the ones readers ask for most often
A price list with real discount authority, a customer-facing quotation that expires, a bill of materials or recipe costing, a staff advance that is issued, acquitted and chased, a member or unit ledger, a matching rule that holds a payment. Each of these is a build rather than a setting, and each has been quoted before — a bigger piece of work than a custom field, with a written spec and a date instead of a roadmap slide.
The report, document or pack nothing currently produces
The board pack in the shape your board actually asks for, a donor or funder layout, an invoice or receipt template carrying what your regulator or your customer expects, a dataset the report builder cannot reach yet. Usually the fastest thing on this list to deliver, because the data is already in the system.
Systems, rails and hardware you already run
The accounting package, CRM, online store, core banking or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed. Plus the physical edge: a scanner, a scale, a weighbridge or a till peripheral feeding the door it belongs to.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. Nothing here waits on a regulator or a published specification, which is why operational builds are the ones we quote fastest. Tell us the requirement that would otherwise rule us out — that is a better first conversation than a demo.
Tell us what your operation needsSee a live site costed end to end
One site store, one set of plant, one project budget — materials, spend and custody controlled while the job is still running.
Explore construction operationsFrequently 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 cost accumulating against a job while it 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. What the operations core will not give you is the BQ side of that comparison: there is no bill of quantities here, so the allowance you are measuring against stays in a spreadsheet.
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: create a task for each major element of its BQ, open the store with a physical count, and book every issue and delivery against a site and task. Keep the BQ allowances themselves in a spreadsheet — there is no BQ structure here to load them into — and compare against them monthly. 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.
