How to manage construction purchase approvals.
A good construction approval process gives every request one clear path: the right person checks it against the budget, approves or rejects it with a reason, and nobody pays until that is done. Use amount limits so routine requests clear quickly and directors only see the large or unusual ones.
What an approval is for
An approval is not a signature for the file. It is a short check that answers five questions:
- Is this needed now, for this project?
- Is it in the budget, and how much of that budget line is left?
- Is the quantity reasonable for the work?
- Is the price fair, and were quotes compared for larger buys?
- Is the supplier, subcontractor or worker the right one to pay?
If an approver cannot answer these from the request, the request is incomplete, and it should go back to the site. Approval is where procurement leakage, such as split purchases and unchecked prices, is easiest to stop.
Who approves what
Different kinds of spending need different checks. One way a mid-sized contractor might split the work is shown below. The roles are illustrative.
| Request | Checked by | Approved by | Paid by |
|---|---|---|---|
| Materials | Site engineer, against the estimate | Project manager, then director above the limit | Finance |
| Casual labour payroll | Site engineer, against attendance | Project manager | Finance |
| Subcontractor payment | Quantity surveyor, against work done | Director | Finance |
| Site overheads | Site manager | Project manager or finance manager | Finance |
How many levels, and what limits?
Most contractors need one level for small amounts and two for larger ones. A third level is worth it only for very large or unusual items. Every extra level adds delay, and delay is what pushes site teams around the process.
| Amount (illustrative) | Level 1 | Level 2 | Target time |
|---|---|---|---|
| Under KES 50,000 | Project manager | Not needed | Same day |
| KES 50,000 to 500,000 | Project manager | Finance manager | Within 24 hours |
| Over KES 500,000 | Project manager | Director | Within 48 hours |
Speed versus control
A slow approval process does not create control. It creates workarounds. Keep approvals fast by:
- letting approvers decide from a phone, not only at the office;
- naming a deputy when an approver travels;
- setting a target time for each level, and checking it;
- sending incomplete requests back with a clear reason instead of leaving them unanswered.
Approve or reject, always with a reason
A rejection without a reason teaches the site nothing, and the same request comes back next week. Write what is wrong: the quantity exceeds the estimate, the price is above the last quote, or the budget line is nearly used. Keep comments on the record, so that anyone looking later can see why a decision was made.
Handling urgent purchases
Allow a capped emergency route: a named person approves by phone, the approval is confirmed in writing the same day, and a requisition follows within 24 hours. Review every emergency at the weekly cost meeting. Our guide on preventing unauthorised spending includes a sample policy.
Red flags in an approval process
- Rubber-stamping: every request approved within seconds, none ever rejected.
- Request splitting: several requests for the same item from the same site within days, each just under a limit.
- Self-approval: people approving their own requests, or an assistant approving for a manager.
- Approval after payment: requests approved once the money has already gone.
Approvals in MjengoKit
MjengoKit routes each requisition to the approvers set for that approval type, level by level. Approvers work from an "awaiting my approval" queue on a phone or laptop, can comment, and must give a reason to reject. Every decision is kept in the approval history, and roles decide who can make payments. See construction approval workflow software.
Tell us your approval rules. We will show you how they run in MjengoKit, level by level.
Book a 20-minute demo