Most builders already know they're holding on to too much.
The trouble is that "delegate more" isn't something you can act on at 6am on a Tuesday, when there are eleven things waiting on your desk and every one of them looks like it needs you personally.
So the pile stays where it is.
And the reason is rarely a shortage of willingness. It's that nobody has ever given you a way to decide which of those eleven items is safe to hand over, or how much authority to send with it once you do...
So let's correct that.
What should a building company owner delegate?
A building company owner should delegate any task that someone else in the business could complete to 80 percent of the owner's standard or better. The comparison is against your own output, not against perfection, and 80 percent is the threshold at which the task should move.
The instinct is to argue about the accuracy you've given up. That argument costs more than the gap it protects, because while you're polishing every little minor detail nobody is working on the client relationships or the strategy that only you can work on.
This also stops you delegating the wrong things. If a task genuinely can't be done by anyone else to 80 percent of your standard yet, the answer isn't to hand it over and hope. The answer is to train someone until it can be, and to keep it in the meantime.
How much authority should go with the task?
Handing over a task and a decision are different transfers, and confusing the two is what produces the situation where someone technically owns a process but still rings you before every step of it.
There are five levels of delegation. They're worth knowing as a sequence, because a person moves up them over time rather than arriving at the top.
Level 1, Task Delegation. You say exactly what to do and they do it. An apprentice follows your precise instructions for completing something on site. It's basic, and it's still a start.
Level 2, Decision Delegation. They have authority to make a decision inside clear boundaries. A site supervisor can approve material deliveries up to the scheduled quantities without checking with you first.
Level 3, Problem-Solving Delegation. They identify the issue, recommend a solution, and execute once you've signed off. A construction manager spots a scheduling conflict, proposes moving the plumber to the following week, and gets your agreement before making the call.
Level 4, Ownership Delegation. They own a complete process and you review the results. A construction manager owns the whole site delivery process, makes decisions inside agreed budget and timeline parameters, and you look at weekly scorecards rather than individual jobs.
Level 5, Leadership Delegation. They lead other people using the same approach you modelled for them. That construction manager is now coaching their own site supervisors through delegation, which builds the next layer of leadership underneath them.
The goal is to move every capable person up that ladder over time, from doer to decision-maker to leader. A company where everyone is stuck at level one has a delegation problem that no amount of extra hours will fix.
What has to be in place before you hand anything over?
Authority without context produces decisions that are confident and wrong. Three things have to be clear to the person taking the work on, and if any of them is missing the transfer will come back to you.
The first is the mission. Not "grow the business", which tells nobody anything, but something specific enough to make decisions against, like completing six projects on time and on budget this quarter. When your team knows the actual target, they can judge whether an option supports it. Without it, they're guessing, and they will guess conservatively by asking you.
The second is the parameters. What can they decide alone, what needs a conversation first, and where does the line sit between the two.
The third is accountability, meaning the outcomes they personally own and how progress gets measured. One or two metrics that genuinely matter, not ten. A sales leader owns the conversion rate and pipeline value. A construction leader owns on-time completion and budget adherence. A finance coordinator owns payment cycles and cash flow forecasting. If you're unsure which numbers belong to which role, the 12 KPIs every builder should track is a reasonable place to start narrowing them down.
Where exactly is the line on decisions?
This is the part most building companies leave vague, and vagueness here is expensive, because it converts every borderline call into an interruption.
The useful test is whether a decision happens inside the framework you've already built, or whether it changes the framework itself. Decisions inside it belong to the person doing the work. Decisions that alter it come back to you.
For example, a sales leader can adjust payment schedules within your standard terms, while anything needing custom financing comes to you. A construction leader can authorise minor scope changes that don't affect the critical path or the budget, while structural changes and timeline shifts escalate. A finance coordinator can release supplier payments according to agreed terms, while early payments, payment plan variations and disputed invoices need your sign-off. A site supervisor can approve standard material substitutions from the approved alternatives list, and anything not already on that list comes to you first.
Notice what those four have in common. Each one names a standard, then names the specific situations that fall outside it. Write them down and make them visible. Boundaries that live only in your head aren't boundaries, they're things your team has to guess at, and they will keep checking rather than risk getting it wrong. If you want a broader view of how written authority operates alongside your other rules, how policy works in a building company covers the same ground from the policy side.
Why does delegation keep failing?
Usually because the owner intervenes, and does it for understandable reasons. You built the company. You know every client, every risk and every place a job can go wrong.
But the more often you step in, the less capable the person becomes. It feels like help and it functions as training in not thinking, because they learn that a decision is only safe once you've confirmed it.
There's also a sequencing problem. You won't start trusting someone until they have proved themselves, and they can't prove themselves until you've trusted them with something first. Somebody has to go first, and it has to be you. Start with a task that's low risk and reasonably visible, let them own it properly, and coach through the process rather than taking it back at the first wobble.
Three supports need to sit underneath all of it. Weekly check-ins, so nothing drifts for a month before you hear about it. Scorecards, so performance is a number rather than an impression. Clear metrics, so the person knows what success looks like without asking. When those exist, your team knows what's expected, how it's measured and where to go for help, which is the point at which you stop chasing people. This is also the structural work that makes growth survivable, and it sits alongside everything else in how to grow a construction business.
None of this requires a personality change. It requires deciding, once, what "standard" means in each part of your business, and then writing down who gets to work inside it.
Frequently asked questions
What is the 80 percent rule for delegation?
If someone else in your business could complete a task to 80 percent of your standard or better, you should delegate it. The comparison is against your own output rather than against a perfect result. The rule exists to stop owners holding on to work because of a small quality gap that costs far more in owner time than it saves in accuracy.
What are the five levels of delegation?
Task delegation, where you specify exactly what to do. Decision delegation, where they decide within set boundaries. Problem-solving delegation, where they diagnose and recommend, then act after sign-off. Ownership delegation, where they run a whole process and you review results. Leadership delegation, where they lead others the same way. People move up the levels as they demonstrate judgement.
What should a building company owner not delegate?
Anything nobody else can currently do to 80 percent of your standard, which is a training gap rather than a permanent exclusion. Beyond that, decisions that change the framework your team works inside, including custom financing arrangements, structural or critical-path changes, disputed invoices and material substitutions that aren't on your approved list.
How do I stop my team asking permission for everything?
Define decision-making boundaries for each role, write them down, make them visible and review them in team meetings. Most permission-seeking is a symptom of unwritten limits, because checking with you is the only risk-free option available to someone who doesn't know where the line is.
How many KPIs should each person own?
One or two that genuinely reflect whether they're succeeding. A longer list dilutes accountability, because when everything is measured nothing is owned, and the person ends up managing the report rather than the outcome.
The decision in front of you isn't whether to delegate. It's which of the eleven things on your desk today fails the 80 percent test, and how much longer you're prepared to pay for the ones that don't. Every quarter you spend as the approval point for standard decisions is a quarter your team spends learning to wait for you.
If you want help setting the authority boundaries for each role in your company, book a 15-minute chat with our team.


