Give the decision an owner and a boundary.

Start with the question arriving at your desk.

You have explained the role. The person understands the work and wants to take responsibility. Yet the same questions return: can we agree this change, move that commitment or make this exception? The missing detail may be the decision boundary rather than the job description.

A role describes a continuing contribution. A decision boundary describes what somebody can choose in a particular situation, what they need to check and what must come to you. Both matter. Asking somebody to own an outcome without making their authority usable can leave them responsible for work they cannot move.

Begin with one decision that keeps coming back. This guide is practical ScaleOn editorial analysis, not empirical research or a report of observed client work. It proposes a small working format. It does not determine your legal, employment, financial, safety or contractual approval requirements.

Can the person make the ordinary choice?

Write the decision in everyday language. Choosing when to update a customer is different from changing a delivery commitment. Checking the information in a quote is different from approving its commercial terms. One broad instruction can hide several choices requiring different authority.

Identify the person who can make the ordinary choice and the information they need. Use the actual role in the business: the person responsible for delivery, whoever handles hiring or the person leading the team. Do not create a department or senior title simply because a diagram looks more complete with one.

Then describe the boundary using the business's existing commitments and controls. If those controls are unclear or disputed, mark the decision unresolved and agree the boundary before transferring it. A written instruction cannot make an unsafe or unauthorised commitment acceptable.

Responsibility also requires practical access. Can the person see the relevant record, contact the people involved and confirm the result? If the information stays with you, delegation may exist in the instruction but remain difficult in the work.

A fictional delivery change, with judgement kept in place.

Imagine a customer asks to move the start of an agreed service to a later date. The person responsible for delivery can check the current commitment and available capacity. That information gathering does not itself authorise a change to the agreement.

For this fictional example, assume the business has already approved a written rule allowing certain date changes when capacity, customer agreement and the existing terms are unaffected. The delivery owner can decide only within that rule. The guide does not recommend a particular time allowance, financial threshold or contract interpretation.

If the request changes price, scope or a commitment outside the agreed rule, it comes to you or the person already authorised for that exception. The delivery owner still owns collecting the information and communicating the approved answer. Escalation transfers the decision that needs authority, not every surrounding action.

If two commitments conflict or capacity cannot be verified, the owner records the uncertainty. They do not invent availability to keep the process moving. You retain the judgement that the ordinary rule cannot safely carry.

What comes back should become more specific.

A useful escalation states the choice needed, the evidence available, the relevant boundary and the proposed next action. Please approve is incomplete if you still have to reconstruct the situation. A concise record helps you judge the exception without taking over the whole task.

Keep the person requesting the decision involved. After your decision, they need to understand what changed, who acts next and whether the ordinary boundary remains the same. Otherwise the next similar case may return without any useful learning.

Do not punish reasonable escalation by calling every question a lack of ownership. Somebody who identifies a limit or missing evidence may be protecting the business. Examine whether the question was avoidable, whether the boundary was usable and whether the necessary information was accessible.

Repeated exceptions deserve review, but not necessarily wider authority. You may need clearer instructions, better information, a different allocation of responsibility or specialist input. The cause should determine the change.

Review the boundary in the operating week.

Test the format with a few ordinary decisions and an exception where appropriate. Use records you are authorised to examine and avoid copying confidential employee or customer details into a new document unnecessarily. This small review is not evidence of a company-wide performance improvement.

Ask whether the right person could decide, whether the necessary information was available and whether the next person understood the resulting commitment. Include a case where escalation was justified. A lower count of questions is not automatically better if people have begun hiding uncertainty.

You stay at the head of the business. The aim is to turn the judgement you want others to carry into usable limits, responsibilities and ways of working. Your team can own ordinary decisions while your attention remains available for the choices that require it.