Two coworkers stand at a small table, each politely gesturing toward a single card between them

Who Decides When You're Not There?

November 05, 2026•10 min read

TL;DR: Who decides when the owner is away is answered by decision rights, the written rule that names who is allowed to make a given call, up to what limit, and when to send it back up the chain. Operations that skip this step end up with a refund, a reschedule, and a rush order all waiting on the owner, or decided inconsistently by whoever answers the phone. The fix is a short rule for each recurring decision.

Key Takeaways

  • Decision rights are the written rule that says who is allowed to make a specific call, within what limit, and when to escalate it.
  • A refund, a reschedule, and a rush order are three everyday decisions that expose whether anyone besides the owner can actually act.
  • Without a written rule, staff guess, stall, or call the owner, and all three outcomes create rework and inconsistent answers.
  • A decision right needs three parts: who decides, the limit they can decide within, and the escalation path for anything past it.
  • The test of a working decision right is whether the business runs the same way when the owner is not there to answer the phone.
  • The call that comes back to the owner by default is the one nobody ever wrote a rule for.

Who Decides When the Owner Isn’t There?

Picture three calls coming into the business on the same afternoon. A customer wants a refund on a product that arrived damaged. A client needs to reschedule an appointment for tomorrow morning. A regular customer wants a rush order pushed ahead of the queue. None of these are rare. They happen in some form in a small operation most weeks.

The question worth asking is simple: who makes the call on each one, right now, today, if the owner is on a plane, in a meeting, or just not answering? For an owner who has not written anything down, the honest answer is that they do, every time, because nobody else has been told they’re allowed to decide. This is a decision rights (who is allowed to make which call) problem, and it’s usually the part of a handoff that never gets written down.

Decision rights differ from job duties. A job duty says someone answers the phone. A decision right says what they’re allowed to do once they pick it up, and where the edge of their authority sits.

What Are Decision Rights, Exactly?

Decision rights are the explicit rules that state who is permitted to make a given decision, the boundaries within which they can make it, and the point at which the decision must go to someone else. They are specific, written, and testable: if you can’t point to the rule, the right doesn’t exist yet, no matter how capable the person is.

Without a written decision right, three things happen instead, and none of them are good. Staff guess, and guesses are inconsistent from one person to the next. Staff stall, because guessing wrong feels riskier than waiting. Or staff escalate everything, which means the call that comes back to the owner (the unresolved decision that lands back on the owner by default) becomes the normal pattern instead of the exception.

Three Sample Decisions

These three decisions are common enough that an operation runs into a version of them regularly. Walk through each one and ask honestly who makes the call today.

A refund. A customer received a damaged item or a service that didn’t meet expectations and wants money back. Right now, does front-line staff have a dollar limit they can approve without checking with the owner, or does every refund request wait for sign-off?

A reschedule. A client needs to move an appointment, often on short notice, and the original slot may now go empty or get filled by someone else. Does staff know which reschedules they can approve on the spot, and which ones need to check the schedule with the owner first?

A rush order. A customer wants to jump the queue, which affects every other order already in line. Does anyone besides the owner know the cost or time trade-off well enough to say yes or no, or does it wait until the owner is reachable?

A decision right that exists only in the owner’s head is a bottleneck with a job title attached.

If the honest answer to all three is “they call me,” the business has no decision rights below the owner. That’s a known fact once checked. What’s still unknown, until tested, is whether staff could handle the limit a written rule would set.

How Do You Write a Decision Right?

A decision right is written as a short rule with three parts: who makes the call, the limit they can decide within, and when the decision escalates to someone else. The format stays the same regardless of the decision. Skipping any one of the three parts turns the rule back into a vague instruction that different people will read differently.

A decision right has three parts: who decides, the limit they can decide within, and when the decision escalates.

A usable rule for each of the three sample decisions might look like this:

Decision Who makes the call Limit Escalation path
Refund Front desk staff Up to $75 (example amount) Above $75, or any complaint involving a repeat customer, goes to the manager
Reschedule Scheduling staff Any reschedule more than 24 hours out Same-day reschedules go to the manager
Rush order Production lead If it doesn’t bump an order already promised for that week If it delays another customer’s promised date, it goes to the owner

The dollar figure and the 24-hour window above are example amounts, meant to show the shape of a rule, not a number to copy without testing it against actual margins and schedule.

SCORE advises small business owners to let employees make decisions on customer issues instead of routing everything back to the owner, which is the same logic behind writing a decision right in place of case-by-case approval.

Decision rights fail quietly. Nobody announces a stall: the refund sits, the reschedule gets forgotten, and the rush order waits.

A rule this short can be written for any recurring decision in the business, not just these three. The work is identifying which decisions repeat often enough to be worth writing down, and which are rare enough that routing them to the owner is still the right call.

What If a Decision Doesn’t Fit a Clean Rule?

Some decisions genuinely resist a simple threshold, and forcing one onto them creates a rule nobody trusts, which is worse than having no rule at all. When a decision depends on judgment calls that vary too much case by case, the better move is to name the person responsible for deciding and set a shorter escalation window, rather than inventing a false limit. The trade-off is slower initial speed in exchange for a decision that actually holds up when questioned later.

A rule written broadly enough to cover everything, such as “use judgment on refunds,” names no limit and no escalation path, so it functions as the absence of a decision right rather than one.

In Practice: Writing One Decision Right

This is a general illustration, not a client result, meant to show how one decision right gets built from scratch.

Situation: An office manager keeps a mix of appointments and intake calls, and the owner currently approves every reschedule request personally, including routine ones that come in days ahead of time.

Steps:

  1. List the last 20 reschedule requests from the appointment calendar and note how far in advance each came in.
  2. Separate the list into two groups, requests made more than 24 hours out and requests made same-day.
  3. Draft a rule naming the office manager as the decision maker for the first group, with same-day requests escalating to the owner.
  4. Write the rule in one sentence and post it where the office manager checks the schedule daily.
  5. Test the rule for two weeks and track any reschedule that still gets routed to the owner despite fitting the rule.
  6. Adjust the time threshold or the escalation condition based on what the two-week test shows.

Result: A one-sentence written rule exists, the office manager can point to it, and reschedule requests that fit the rule no longer wait on the owner’s availability.

Common mistake: Writing the rule but never telling the person who answers the phone where it’s posted. Fix this by confirming out loud, not just in writing, that the rule is in effect.

If it goes wrong: If reschedules still land on the owner’s desk after the rule is posted, check whether the escalation condition is too narrow or whether staff don’t trust the limit yet, and adjust one variable at a time.

FAQs

How do I know if I have a decision rights problem?

A decision rights problem shows up when staff routinely wait for approval on decisions that repeat weekly, such as refunds, reschedules, or rush orders. A quick test is to list the last ten decisions that came to the owner and ask whether each one needed specific judgment or just needed someone with a written limit. If most of them could have been handled with a clear rule, the gap is in documentation, not in staff capability.

What is the difference between a decision right and delegation?

Delegation assigns a task, while a decision right defines the boundary of judgment someone is allowed to use within that task. A task like handling refund requests can be delegated without ever stating a dollar limit, which leaves the person doing the task unsure how far their authority goes. A decision right closes that gap by naming the limit and the escalation path explicitly.

Why does a refund request always come back to the owner?

A refund request comes back to the owner because no written limit tells staff how much they can approve without checking first. In the absence of a stated dollar threshold, staff default to the safest option, which is asking, even when the amount is small enough that a rule would have let them decide on the spot. The fix is a stated limit, not a reminder to use judgment.

How detailed should an escalation path be?

An escalation path should name one specific person or role and one specific condition that triggers the handoff, nothing more. A vague instruction like “check with me if it’s a big one” leaves “big” undefined and forces a judgment call every time. A usable escalation path reads closer to “any refund over $75 (example amount) goes to the manager,” which removes the guesswork.

Can decision rights change as the business grows?

Yes, a decision right set for a small team almost always needs revisiting as volume or staff size increases. A dollar limit or time threshold that made sense with one employee handling refunds may need adjusting once three people are handling them, since inconsistency across people becomes visible faster at higher volume. Review decision rights on a set schedule rather than waiting for a visible failure to prompt it.

What happens if decision rights are never written down?

If decision rights stay unwritten, every recurring decision defaults back to the owner, regardless of how simple or repetitive it is. This creates a bottleneck that has nothing to do with staff skill and everything to do with missing documentation. The business becomes unable to run normally whenever the owner is unavailable, which is the exact risk a written rule is meant to remove.

Should every decision have a written rule?

No, only decisions that repeat often enough to justify the effort of writing a rule for them need one. Rare, high-stakes decisions are usually better routed to the owner case by case, since the cost of writing a rule outweighs the benefit for something that happens once a year. Reserve written decision rights for the handful of decisions that show up weekly or monthly.

Next Steps

Writing a decision right for one recurring decision this week, starting with whichever one currently causes the most waiting, is a more useful first step than trying to document every decision in the business at once. I recommend listing the last ten decisions that came back to the owner and checking how many could have been handled with a written limit. Which decision would your team stall on first? Tell me in the comments.

decision rightsowner dependencydelegationbusiness operationsescalation path
May Fundora
May Fundora|Founder | Great Lakes Business Support|LinkedIn logo iconInstagram logo icon
May Fundora founded Great Lakes Business Support (GLBS) to bring structure to the parts of a small business that usually run on guesswork — scheduling, follow-up, intake, the stuff that falls apart when nobody's watching it. Her background is in healthcare IT and airline operations, two industries where a missed step has real consequences and there's no room to wing it. She built GLBS around that same standard: test the process, fix what's actually broken, and only add a system if it makes the business more dependable. If something on this blog sounds practical instead of flashy, that's on purpose.
Back to Blog

Your business doesn't need more ideas. It needs the right next step.

GLBS helps small service businesses identify the operational gaps costing them time, consistency, and revenue.