How to track construction expenses across multiple sites.
To track construction expenses across several sites, use one process everywhere: give each project a code, require a request before each purchase, have someone else approve it, record each payment with its reference, and review budget against actual every week. Consistency matters more than the tool.
Why expense tracking falls apart with more than one site
On one project, a good site manager can hold the numbers in their head. Add a second and third site and the same habits stop working. Suppliers serve more than one job, money moves between project accounts, and requests arrive by phone and WhatsApp. By month end, finance is rebuilding the story from statements.
Most of that effort is unnecessary. The information existed when the money was requested. It just wasn't captured at that moment.
Step 1: Give every cost a home
Decide on a short list of codes before you record anything: the project, then the type of cost, then the cost item if you need that detail.
| Level | Example | Why it matters |
|---|---|---|
| Project | Kitengela Apartments | Tells you which job paid |
| Cost type | Materials, casual labour, subcontractors, overheads | Tells you what kind of money it was |
| Cost item | Concrete works, formwork | Lets you compare with the budget or BOQ |
Keep the list short. People stop using a list of 200 codes. If you have a BOQ, group it into items your site team recognises.
Step 2: Capture the expense when it is requested
This is the change that makes the rest easy. If you record costs when the receipt arrives, you always learn about spending after the fact. If you capture them at the request, you know about each cost before it is committed, and you can see what is coming.
A site requisition form is enough to begin with. The aim is one route for every request, not a perfect form.
Step 3: Approve before money leaves
An approval only counts if a different person gives it, and it happens before the purchase. Set clear rules for who approves what, and keep them simple enough to follow on a busy day. See how construction approval workflows work for examples.
Step 4: Record every payment with its reference
Each payment should point back to the request it settles. Record the amount, the date, the method and the reference: the M-Pesa code or bank reference. This is what lets you reconcile quickly, because each line on a statement has an explanation waiting for it.
Also record part payments. A request for KES 200,000 with KES 120,000 paid still leaves you owing KES 80,000. That is a real obligation, even though it doesn't show in your bank balance.
Step 5: Review weekly, in 30 minutes
Reviewing monthly is too slow. By then, the money has gone. A short weekly review should answer four questions:
- What did each project spend last week, by cost type?
- What is approved but not yet paid?
- Which cost item is running ahead of the work actually done?
- What is waiting for a decision?
An example across three sites
This is what that weekly view might show. Projects and figures are illustrative.
| Project | Spent this week (KES) | Approved, unpaid (KES) | Budget used | Work done |
|---|---|---|---|---|
| Kitengela Apartments | 640,000 | 210,000 | 41% | 45% |
| Ruiru Warehouse | 1,120,000 | 480,000 | 68% | 52% |
| Westlands Fit-out | 295,000 | 60,000 | 33% | 35% |
Ruiru is the one to question. It has used 68% of its budget with 52% of the work done. Finding that out in week six leaves time to act. Finding it out at the end of the job doesn't. Our guide to construction cost leakage covers what usually sits behind numbers like these.
Which tool should you use?
For one small job, our free expense tracker template may be all you need. Once several people are spending across several sites, a spreadsheet can't enforce the approval step or keep everyone on the same figures. That is when construction expense tracking software earns its place.
Tell us how many sites you run. We will show you how they would look in one view.
Book a 20-minute demo