If Everyone Needs You, Nothing Moves

Your employees should not need a search party to get a $90 decision made.

A bottleneck is the point where work piles up because everything needs to pass through it. When that point is you, being responsive isn’t the solution. You’re just getting faster at interrupting yourself.

The symptom isn’t being busy. It’s people waiting.

Owners have full calendars. That alone proves nothing.

The useful question is: What stops moving when you’re unavailable?

Look for these patterns:

• Customers wait for callbacks because only you can resolve ordinary complaints.
• Staff leave gaps in the schedule rather than move an appointment without permission.
• Completed work sits unbilled until you inspect it.
• Employees ask the same questions every week, and you give roughly the same answers.
• You answer messages at dinner so tomorrow doesn’t fall apart.
• Your strongest employee quietly becomes your messenger instead of making decisions.

One complicated estimate needing your judgment is normal. Twelve routine decisions parked outside your office is a system problem.

Sometimes the missing piece is training. Sometimes it’s authority. Sometimes you handed over a task but kept every decision attached to it.

“Handle scheduling, but check with me before changing anything” is not delegation. It’s clerical work with extra steps.

Run the five-day permission test

For one working week, log every request that needs your answer before someone can continue. Use paper, a spreadsheet, whatever you’ll actually use.

Record:

• What decision was needed.
• Who asked.
• How long your answer took.
• How long the work waited.
• Whether the answer required your judgment or just a rule nobody had written down.

That last distinction matters. Signing a new lease needs owner judgment. Approving the same replacement part for the fourth time probably doesn’t.

Measure waiting time separately from answering time. A two-minute answer delivered three hours later is still a three-hour blockage.

Here’s an illustrative week: 30 requests take an average of 12 minutes each, including checking details and restarting your previous work. That’s six owner hours. Eight requests also leave an employee unable to progress for 45 minutes each. Another six hours.

Suppose those six employee hours could instead become billable work at $150 an hour. That’s $900 in potential weekly revenue. At a 50% gross margin after direct delivery costs, that’s $450 toward overhead and net profit. Across 48 working weeks, it’s $21,600.

That is available capacity, not guaranteed cash flow. You still need demand, completed work, and payment. If staff can switch to other productive work, the loss is smaller.

Now answer three questions:

• Did the same kind of decision reach you at least three times?
• Could a trained employee decide it using clear limits?
• Would you accept their reasonable answer even if it wasn’t your exact answer?

Those are working tests, not industry benchmarks. If the third answer is no, start there. No checklist can outrun an owner who keeps taking the wheel back.

Handoff one: routine schedule changes

Give one person ownership of ordinary scheduling decisions: moving appointments, filling cancellations, assigning qualified staff, and notifying customers.

Not “everyone can help.” One person owns the result.

Write down the boundaries. For example:

• Don’t assign work outside someone’s qualifications.
• Don’t promise overtime without approval.
• Don’t displace a confirmed customer without contacting them.
• Escalate changes that threaten a contractual deadline or safety requirement.

Your labor percentage can climb when a rushed schedule creates overtime. Include that constraint rather than requiring approval for every move.

For the first two weeks, review changes once daily. Ask what happened and whether the rules worked. Don’t demand a live commentary all day. That rebuilds the same bottleneck with notifications.

Handoff two: small-dollar approvals

Stop personally approving every minor purchase, replacement, and customer remedy.

Pick limits your business can afford. An illustrative starting policy might allow a supervisor to spend up to $200 per incident, with a $600 weekly total, on specified replacement supplies or straightforward service recovery.

Require a receipt, a reason, and the relevant job number. Prohibit splitting purchases to dodge the limit. Escalate repeat failures, safety issues, and anything outside the approved categories.

This is not permission to improvise pricing or give every unhappy customer a discount. Protect your gross margin by defining acceptable remedies, not just a spending ceiling.

Review the log weekly. Adjust limits using actual results. Don’t revoke the entire handoff because someone made a defensible $120 call differently than you would have.

You’re buying faster decisions. Allow some room for judgment.

Handoff three: routine quality checks

If every finished job needs your eyes, completion has two stages: actually done, then waiting for you.

Give a qualified lead responsibility for checking standard work against a short checklist. Include required photos, measurements, customer signoff, or documentation relevant to your trade.

Keep legally required signoffs with the properly authorized person. Complex work and exceptions still get escalated.

Your SOPs should explain what passes, what fails, and what happens next. “Make sure it looks good” is not a standard.

For an initial trial, audit five completed jobs weekly and every callback. That’s a proposed control, not a universal benchmark. Increase checks if errors rise. Track rework and complaints; reviews can provide another signal, but they aren’t a substitute for inspection.

The goal is consistent quality without your physical presence—not lower standards with a fancy label.

Monday morning: fix the most repeated decision first

Start the permission log. Pick one recurring, low-risk decision. Name its owner, write the limits, and set a review date.

When they ask within those limits, don’t immediately answer. Ask: “What does the rule allow you to do?”

Then let them do it. Otherwise, the handoff is bullshit.