How to Know Which Decisions Should Never Reach You
Your project manager called to have you approve a $400 materials line item on a $22K job. You were in the middle of something else. You stopped, took the call, said yes, and moved on. Total time: four minutes.
That decision had no business reaching you.
Not because your PM can't be trusted. Not because you're too important for a $400 conversation. But because a four-minute interruption on a routine call is a system that doesn't exist yet.
And if it happened once, it's happening every day.
This is the month we've been sitting with which decisions should never reach your desk.
Not as a concept.
As a practice.
A filter you can apply to any decision before you answer it.
Here's the filter.
The Call You Shouldn't Have Gotten
The PM knows the job scope. He knows the budget. He knows your standards. He called you because no one ever told him he didn't have to.
That's a story I've had with nearly every client I've ever worked with. Even the one currently looking at more than 8x on their EBITA.
No one sat down with the employees and said:
here's what you own,
here's what you escalate,
here's what you decide on the spot and tell me about later.
So when a $400 question came up, the path of least resistance was your phone.
This isn't a people problem.
It's a structure and leadership problem.
And these problems don't fix themselves through trust or time.
They fix themselves when someone writes the SOP.
The question is: which decisions belong in a Standard Operating Procedure, and which ones still belong to you?
The Decisions That Should Never Reach Your Desk
There's a category of decision sitting in your business right now that is not yours to make.
It's not that you can't make it.
You can.
You probably make it five times a week without blinking.
That's the problem.
The decisions that should never reach you are the ones that already have a right answer. An answer your team could give, if someone had ever written it down.
They're not ambiguous calls.
They're not judgment-heavy moments where your experience is irreplaceable.
They're operational decisions disguised as judgment calls because no one installed the judgment in advance.
You don't need a smarter team to get out of those decisions.
You need a written rule.
Three Questions That Sort Any Decision
Apply these to any decision currently landing on your desk.
They work in real time.
They work on the call before you answer it.
They work when you're reviewing your day and asking why you handled fourteen things you shouldn't have.
Question 1 — Has this exact decision come up before?
If yes, it's a repeat. Repeat decisions are never judgment calls.
They're proof a standing rule doesn't exist. Every time you answer a repeat decision, you're paying yourself to do what a written sentence could do for free.
A project manager asking about a $400 line item is very common unfortunately. It's the same decision in a different job number. If you've answered it before, you've already made the right call. The only thing missing is the written version of it.
Question 2 — Could a clear rule eliminate it?
Some decisions are genuinely complex.
Most aren't.
Most could be resolved with a single sentence.
"Field PMs approve line items under $500 on jobs within approved scope, without calling the owner."
That's not a policy manual.
That's a sentence you write on a notecard and put in a folder.
Better yet, you write out a SOP and put it in the Company Training Library (Trainual) that can be found by searching digitally and referenced in the future.
If you can imagine the rule, if you already know what the right answer almost always is, then the decision doesn't belong to you. It belongs to a rule you haven't written yet.
A team that waits for permission instead of acting isn't waiting because they're lazy. They're waiting because no one gave them written permission to act. One sentence changes that.
Question 3 — If they decide wrong, is the recovery theirs to manage?
This is the gut-check. Not every decision can be handed off.
If the wrong call creates a consequence that requires your direct involvement to fix, a client relationship you have to repair, a financial exposure that's yours to absorb, a reputation risk that lands on you specifically, then the decision carries risk your team can't own.
But if they decide wrong and the correction is within the job scope, within the budget, within the team's authority to fix, then the recovery belongs to them.
And so does the decision.
The most honest audit of owner-dependency you'll ever run is this question.
If the answer is "they could handle it," you already know where the SOP needs to go.
What This Looks Like in a service or trades company
A contractor has a lead tech on a residential job. Mid-job, the client asks the tech to paint a small piece of trim that wasn't in the scope.
He calls the owner.
Before the filter: the owner drives by, looks at it, talks to the homeowner, adjusts the scope, and sends a revised estimate. Half a day gone.
After the filter: the lead tech has a written SOP.
Additional damage under a defined threshold... say, under a single square or linear foot of coverage... gets documented with photos, reported to the PM, and added to a adjusted scope the PM submits.
Over the threshold, the tech stops, documents, and the PM runs the job numbers against the budget.
The owner only enters if the PM declines and the homeowner needs to be walked through options.
The tech made the call.
The PM handled the adjustments.
The owner got a summary at end of day.
That's structure. One page. Three conditions. No phone call.
How to Install the Filter This Week
You don't need a retreat (but sounds amazing!).
You don't need a consultant (but we're here to support).
You need thirty minutes and a list.
Pull out the last two weeks of calls and interruptions.
Anything you fielded that felt like it shouldn't have reached you and write it down.
Then run the three questions.
Which ones repeat?
Which ones could be a rule?
Which ones carry recoverable risk?
For every decision that clears all three, write the rule.
One sentence.
Post it where the team can see it.
Tell them: this is yours now.
That's leadership.
The difference between a business that runs and a business that runs through you is a set of written decisions you made once ... so your team doesn't have to ask every time.
The structure that supports your freedom doesn't come from working less.
It comes from writing down the work, once, and letting the structure do it after that.
Lead Better. Work Less. Live More.
If decisions are still finding their way to your desk that belong on someone else's, the 2700 Advisers Standard is how we fix that.
Structure first, before any tactic.
Start with a free Fit Call. >> Book here <<
