SHORT VERSION
You’re the bottleneck because the authority to make a decision on a job was only ever given to you, not because your crew can’t decide. Fix it by writing down what they can approve without calling: a dollar limit they can act under on their own, the handful of calls that come up over and over, and one person who holds a higher limit than the rest. Once the answer is written down, the decision stops traveling back to your phone.
You’ve become the bottleneck for every decision because no one on your crew was ever told what they’re allowed to decide without you. That’s not a trust problem. The authority to act on a job was never written down, so every price above a certain size and every scope change in the field defaults back to your phone.
Where the job actually stalls
A service call comes in as a dead receptacle. Your guy gets there, opens it up, and finds the circuit needs work that runs several times the quote. Now he’s standing in a hallway with his phone out, and you’re under a house on the other side of town.
He can judge the work fine. What he doesn’t have is a number that tells him when he needs you and when he doesn’t. So the safe move is to ask. And asking means you.
Multiply that across every job in a week where the price moved or the scope grew. So the field waits on your phone.
There’s a quieter version that costs more. When he can’t reach you and the customer’s losing patience, he closes it on his own read. Sometimes that’s a discount nobody signed off on. Sometimes it’s work that never makes it onto the invoice.
That’s not him giving your money away. It’s the only move left when the line was never drawn and you’re not picking up. Either way the job moved without you, in the direction you’d least want.

Why does it all route back to you?
Because the limit was never set for anyone else. Early on, you were the only one who could price a job, so every price ran through you. The crew grew. The volume grew. That one rule, everything comes to me, never got rewritten. It just kept scaling.
Now you’ve got a journeyman with ten years in who still texts before he’ll commit to a number. Not because he can’t make the call. Because no one ever drew the line that says: below this, you don’t need me. The line doesn’t exist, so the whole field assumes the line is zero.
Decide it once, so it stops traveling
The fix isn’t delegating more, and it isn’t trusting harder. It’s making the decision one time, in advance, and writing it down so it doesn’t get made again on every job.
Start with a dollar figure your crew can approve on their own. Under it, they proceed and tell you after. You set it where a wrong call costs you a little and a callback to you costs more. You don’t set it by gut, either.
Look at the last month of jobs that stalled waiting on you, mark the ones you’d have been fine letting them close, and the ceiling is sitting in that list.
Then write down the calls that come up over and over. The common scope adds, the judgment calls you’d make the same way every time. The answer gets decided once, so nobody has to reach you to hear it. And give one person, a lead or a service manager, a higher limit than the rest, so the bigger calls land somewhere that isn’t your cell.
Once it’s written, the decision stops being a phone call. It’s already made, so the field keeps moving whether you pick up or not.
FAQ
Should I hire someone to take decisions off my plate, or fix the process first?
Fix the process first. If you hire a service manager but never write down what they’re allowed to approve, you’ve just added a second person who has to text you. Set the limits, then the hire has something real to step into.
What if my crew makes the wrong call with that authority?
Some will early on, and it’ll usually cost you less than the callback would have. Set the dollar limit low enough that a wrong call is cheap, review the ones that go sideways, and raise the limit as it earns out. A wrong call you can see and correct beats a job that sat all afternoon.
Isn’t this just delegating?
Delegating is handing off a task and hoping. This is writing down the exact line where a decision is theirs and where it’s yours, so nobody’s guessing. The answer already exists before the job starts.
How do I set an approval limit without losing control of pricing?
You keep the price book. What you’re setting is how far a job can move before someone needs your sign-off, which is a different thing from what the job costs. You’re not giving up the pricing, you’re giving up being the person who reads it out loud on every job.

