How to improve financial accountability on construction sites.
Financial accountability on a construction site means every shilling has an owner: someone asked for it, someone else approved it, someone paid it, and anyone can see that trail later. You improve it by naming who owns each step, recording decisions where they can be found, and reviewing the numbers together every week.
What accountability looks like in practice
On an accountable site, these questions take minutes to answer, not days:
- Who asked for this purchase, and why?
- Who approved it, and what did they check?
- What was paid, to whom, and when?
- What is still owed on this project?
- Which budget line did it come from, and how much is left?
If answering any of them means phoning three people and scrolling through WhatsApp, the trail is broken.
Who owns what
Accountability starts with clear ownership of each step. One way to split it is shown below. Adapt the roles to your company.
| Role | Owns |
|---|---|
| Foreman or site engineer | Raising requests, confirming deliveries and attendance |
| Quantity surveyor | Checking quantities and measuring subcontract work |
| Project manager | Approving within the project budget, and explaining variances |
| Finance | Checking payment details, paying and reconciling |
| Director | Approving large items, and reviewing every project weekly |
The key is separation: no single person should be able to ask, approve and pay. Without it, the leaks in our construction cost leakage guide are hard to trace to anyone.
The audit trail you need
For every outflow, keep these together, in one place:
- the request, with the project, items, quantities, amounts and reason;
- the approval, with the approver's name, the time and any comment;
- the order, usually an LPO, for supplier purchases;
- evidence that the goods, work or attendance were real;
- the payment, with its M-Pesa or bank reference;
- the budget line it was charged to.
Paper can hold this trail on a small site. Across several sites, a system that links each step to the next saves a great deal of searching.
A weekly habit that makes it stick
Accountability is mostly a habit. Once a week, the project manager, finance and a director spend 30 minutes on each project: budget against actual, approved but unpaid, requests waiting, and last week's exceptions. Every gap leaves the meeting with a name and a date. See our 30-minute weekly cost review for an agenda.
Making it last
- Leaders follow the same rules. If directors' own purchases skip the process, nobody else will take it seriously.
- Be consistent. The same response to the same mistake, on every site.
- Recognise good practice. Thank the site that has no exceptions, not only the one that has many.
- Make it easy. Approvals from a phone and simple forms keep people inside the process.
Common objections, and answers
| Objection | Answer |
|---|---|
| "We trust our people." | Good. A clear record protects honest people from suspicion when something goes wrong. |
| "It will slow the site down." | Amount limits and phone approvals keep routine requests moving the same day. |
| "Our site teams are not good with software." | Start with a paper requisition form. The habit matters more than the tool. |
| "We are too small for this." | Even two people can separate asking from paying, and keep the request with the receipt. |
Accountability in MjengoKit
MjengoKit keeps the trail on one record: each requisition, its approvals, comments and rejection reasons in the approval history, and the payment that settles it. Roles and permissions decide who can request, approve and pay.
Bring one disputed payment from your records. We will show you how MjengoKit would have recorded it.
Book a 20-minute demo