A service manager at a mid-size HVAC company gets a call from a customer whose install went sideways two weeks ago. The manager knows the account, knows the technician involved, and knows exactly what needs to happen: a partial refund, a follow-up visit at no charge, and a personal call to the homeowner before the day is out. It’s the right decision. Anyone who reviewed it later would agree.
Instead, the manager writes it up in a text to the owner. “Here’s what I’m thinking, let me know if you’re good with this.” The owner is in a truck, or a meeting, or asleep. The customer waits. The technician waits. The manager, who already knew what to do, waits too.
This is not a story about a bad manager. It’s a story about a manager who got the decision right and still could not tell whether the decision was theirs to make.
The behavior is easy to miss because the decision itself isn’t wrong
Owners tend to notice authority problems when someone makes a bad call. They rarely notice them when someone makes a good one and still asks permission. But that second pattern is often the more expensive one, because it hides in plain sight. Nobody flags it as a problem. The decision was correct, the customer was handled, the day moved on. The only thing anyone lost was time, and time is easy to write off as the cost of being careful.
Watch it happen a few more times and the pattern gets clearer. The manager isn’t unsure of the answer. They’re unsure of their standing to give it. Somewhere between the org chart and the day-to-day, they picked up the belief that final say still belongs upstairs, even on calls squarely inside their job. So they build in a checkpoint that was never assigned to them, just in case.
What it costs, beyond the delay
The most visible cost is speed. A customer who could have been handled in an hour is handled the next day, after the manager tracks the owner down, gets a reply, and closes the loop. Multiply that by every exception a service business runs into in a given month and the hours add up fast.
The less visible cost is what it does to the owner’s calendar and attention. An owner who is still the real approver on calls that were supposedly delegated is not actually running a leaner operation. They’re running the same operation with an extra layer that looks like delegation but functions like a bottleneck. Every “quick approval” text is a small tax on whatever the owner was actually doing.
There’s a third cost that shows up later and is harder to trace back to its source: the manager’s own read on the job. A person who keeps having their correct calls double-checked, even informally, starts to wonder if their judgment is actually trusted or just tolerated. Some managers respond to that by staying cautious forever, running everything through the owner regardless of how many times they get it right. Others start looking for a seat somewhere else, one where being right is enough.
The missing standard isn’t confidence. It’s authority.
It’s tempting to read this as a confidence problem, something a pep talk or a “trust yourself” conversation would fix. It usually isn’t. The manager in this scenario already showed confidence. They knew the answer before they picked up the phone.
What’s missing is a defined boundary around what the seat owns outright, without a check-in, and what genuinely needs the owner’s input because the exposure is bigger than the manager’s role was built to carry. Most companies never wrote that line down. They hired someone into a manager title, handed them a stack of responsibilities, and assumed the authority would sort itself out through repetition. Sometimes it does. Often it doesn’t, because nobody ever said out loud, “this dollar amount, this type of exception, this category of customer issue: that’s yours, don’t check with me.”
Without that line, every manager has to guess where it sits. Some guess too far and overstep. Most guess too cautiously, because the downside of asking permission you didn’t need is a few minutes of an owner’s mild annoyance, and the downside of acting without permission you did need is a much worse conversation. Given that math, caution wins, and the owner stays the default escalation point on decisions that were supposed to have moved.
What to define before the next handoff
The fix isn’t a pep talk and it isn’t a new layer of process. It’s a written answer to a specific question for the seat in question: what dollar range, what category of exception, what type of customer decision does this person get to close on their own, no sign-off required.
That answer doesn’t need to be exhaustive. It needs to cover the situations that actually come up. If refunds under a certain amount are the recurring case, write that down. If it’s scheduling exceptions, or which vendor issues get escalated and which get handled, write that down instead. The goal is a short, specific list the manager can point to without having to interpret the owner’s mood or guess at a dollar figure that was never confirmed.
It’s also worth being honest about where the current gap came from. If this manager was promoted into the role, the promotion likely came with a new title and a new set of tasks, but not necessarily a new, explicit grant of authority. That’s a common pattern: people move up in responsibility before anyone updates what they’re actually allowed to decide. The correction isn’t to slow down the promotion next time. It’s to pair it with a clear statement of what the new seat owns, at the moment the promotion happens, not months later after the owner notices they’re still approving everything.
Where this fits into a bigger hiring and role problem
This same gap shows up before a promotion, too, not just after one. It’s one of the reasons job descriptions built around a list of tasks tend to underperform: they describe what the person will do, not what they’re trusted to decide once they’re doing it. A company that’s honest about decision authority when it defines a seat, before it interviews or promotes anyone into it, tends to run into this problem far less often down the road.
That’s the piece of the seat Trueseat is built to help a company get clear on early: not just what the role does, but what it owns, including which decisions belong to it without a detour back to the owner. Getting that right before the hire or the promotion is a lot cheaper than untangling it after someone’s been in the seat for a year, quietly waiting for a green light they were never told they didn’t need.
If you’re the one still approving the right calls
If you recognize this pattern in your own business, the useful next step isn’t a conversation about trust. It’s a conversation about scope: what does this seat actually own, and have you ever said so out loud, in specific terms, to the person sitting in it.
If you have a seat you’re hiring for, promoting into, or currently questioning because decisions keep landing back on your desk, a Trueseat call is a working conversation to get clear on what that seat needs to own before you make the next move on it.