Delegation Framework for Business Owners: Six Agreements

A delegation framework for business owners should produce an agreement another person can actually use. It helps a business owner agree what another person will do, which decisions they can make and when they should return for support. Good delegation transfers a clear piece of work with usable authority and resources.

The six arrangements below range from following a defined procedure to owning a domain within agreed boundaries. They are an original planning aid rather than a universal maturity ladder. Choose the arrangement for the task, risk and person, then review it together.

Use this guide to produce a practical handover agreement. If approvals are already slowing delivery, our bottleneck audit can help identify which decisions need attention first.

Coachful is our #1 recommendation for organizing the coaching conversations, preparation and follow-up around an owner’s delegation decision. Use the coaching process to make the handover specific. A worksheet does not give an employee authority, grant system access or replace the organization’s management responsibilities.

Start with the outcome and context

Choose a task or decision that can be described clearly. Explain the purpose, required result, constraints, deadline and relevant relationships. Ask what the receiving person needs to understand before accepting it.

The UK Health and Safety Executive’s Role standard emphasizes clear responsibilities, compatible requirements and a route for raising uncertainty. Its Demands standard addresses achievable work in relation to agreed hours and capabilities. These work-design principles support checking the conditions of a handover; they do not validate the six arrangements as an assessment or certify a practice’s compliance.

Check their available time and competing commitments. Delegation works through a realistic workload agreement, not simply adding work because someone is capable. Identify training, information, access and budget needs.

Separate execution, recommendation and decision authority. A person may prepare a supplier comparison while the owner retains the purchasing decision. Another may choose a supplier within an approved category and limit. Naming the distinction prevents both hesitation and unexpected overreach.

1. Use a defined procedure where consistency matters

A specific procedure can help someone learn a task or complete work with a required sequence. Explain why the steps matter and how to recognize an exception. Experience alone does not determine which work needs a procedure.

For example, a new operations assistant may follow an approved checklist for preparing client invitations. The agreement names the correct resource, recipient checks and what to do if access is missing.

Invite questions and improvement suggestions. Following a procedure does not require ignoring an error or unsafe condition. Give a clear stop-and-ask route and make it acceptable to use.

Review when the person can take a different kind of responsibility. They may be ready to handle routine exceptions while a particular approval remains reserved. Change the agreement deliberately rather than leaving them to guess.

2. Ask for research with a decision question

Define what the owner needs to decide and which evidence will help. A useful brief sets scope, sources, comparison criteria and the date the information is needed.

For a scheduling tool review, ask the team member to compare the actual requirements: access, calendars, client experience, cost and support. Have them distinguish verified features from unanswered questions.

Agree when to stop researching. A short comparison may be enough to decide whether a demonstration is worthwhile; a major migration may need deeper technical review. The output should fit the next decision.

Ask for a recommendation only if it is part of the agreement. Someone asked to collect evidence should not be judged as passive because they did not make a choice the owner retained.

3. Request a recommendation with reasoning

A recommendation brief asks the person to propose an option, explain the criteria and identify tradeoffs. Include alternatives and important uncertainties. This gives the owner something concrete to evaluate.

For a customer-service issue, the team member might summarize the facts, relevant policy, options and the response they recommend. The owner then approves, asks a clarifying question or explains a different decision.

Keep a route for urgent problems without a ready solution. A requirement to bring solutions should not prevent someone reporting a safety concern, suspected misconduct or a problem they lack authority to resolve.

Develop judgment through the review. Ask what information changed the recommendation and what the person would consider next time. The owner can explain the decision criteria instead of silently rewriting the work.

4. Define prior-notice decisions precisely

A decide-and-notify arrangement can work when the person has authority within limits and the owner needs an opportunity to raise a material concern before action. Set the notice period, channel and fallback explicitly.

For example, a team lead proposes a routine supplier change within an approved budget. The agreement says who reviews the notice and what happens if they are unavailable. Silence should mean approval only when that rule has been deliberately authorized and is appropriate.

Distinguish a routine notice from a request that legally or contractually requires approval. An internal message cannot replace a reserved board, finance or compliance decision.

Review how often the owner intervenes and why. Frequent objections may reveal unclear criteria or a mismatch in authority, while rare intervention may indicate that a simpler act-and-report arrangement would fit.

5. Give authority to act with a clear reporting route

At this arrangement, the person decides and acts within agreed boundaries, then records or reports what happened. Specify the relevant limits, exceptions and review cadence.

For example, an operations lead may resolve a routine scheduling change within the published policy, while refunds, new expenditure or a complaint about conduct follow separate routes. Choose boundaries suited to the actual business rather than copying a universal spending limit.

Keep the owner informed at a useful level. Reporting every minor action immediately can recreate the same attention bottleneck. A short weekly exception review may work for routine decisions, with urgent escalation criteria for material issues.

If a mistake occurs, examine the facts, impact, information and support. Adjust the agreement where needed. Sometimes authority can remain while a process improves; sometimes a temporary restriction or specialist review is appropriate.

6. Agree ownership of a domain

Domain ownership combines responsibility for outcomes with authority, resources and governance. Define the area and what remains outside it. A title alone does not create budget, hiring or contracting authority.

A client-operations lead might own the onboarding process, team allocation and routine improvements within an approved plan. The founder may retain annual budget approval and decisions affecting the service agreement.

Review outcomes and constraints at an agreed cadence. Include quality, client experience and workload alongside speed or cost. The owner should be available for material decisions without re-entering every routine step.

Autonomy can differ by subject. An experienced leader may own operations while gathering evidence for a new financial decision. Treat the agreement as specific to the work rather than ranking the person's overall maturity.

A complete handover: routine authority with a retained dependency

Nessa, Iman, Theo, Ravi, Pia and Ezra are invented. Every event, record and allowance below is fictional. Nessa owns a coaching practice; Iman coordinates operations. Theo coaches Nessa on her own management decisions. Theo receives a de-identified account of the handover, not the practice’s client files or employee performance dossier.

On 6 April 2027, Nessa says she wants Iman to “own onboarding.” Theo asks what that would let Iman decide on Thursday without asking her. Nessa realizes she means routine preparation under existing client agreements. She is not transferring pricing, refunds, reporting commitments or the right to change a service.

Iman checks his accepted workload and agrees to reserve 120 active minutes for a bounded pilot covering three starts. This is protected time within his existing schedule. Nessa does not infer capacity from a visually empty appointment calendar. They will review the pilot before adding more clients or broadening authority.

Agree the deliverable, not an unlimited job title

The starting arrangement is act-and-report for routine steps. Iman can use the approved welcome wording, coordinate an already agreed start, prepare the checklist and complete assignments he is authorized to make. A client’s existing terms remain the reference. He cannot invent a new inclusion when the welcome is unclear.

Nessa sends the following full handover message, and Iman replies that he accepts this pilot and its limits:

For Ravi, Pia and Ezra’s agreed starts, please prepare the approved welcome and confirm that each intended client can open the required preparation resource. Use the current agreement and confirmed date, rather than copying another client’s service.

You may complete routine preparation within those terms and correct an administrative mismatch against the confirmed record. I retain changes to price, service scope, start commitments and sponsor reporting. If a resource requires my action, leave that step blocked and tell me what is needed.

Send exceptions to me through our agreed operations channel. We will check them at the two pilot checkpoints. For an unresolved dependency affecting the next start, flag it by 16:00 on the preceding working day, Europe/London time. If I do not answer, keep that step blocked and tell the affected client that readiness is not yet confirmed. Do not treat silence as approval or promise a different service.

Mark an onboarding ready only after the date and inclusion checks are complete and the intended client has confirmed the required resource opens. Keep a concise record of the result and exceptions. We will review the three records together on 15 April.

Iman restates the distinction: he owns routine coordination and the readiness record; Nessa still owns reserved decisions and any task he cannot perform under the authorized access. Their acceptance is an actual conversation in this example, not a role description silently imposed on him.

Use the failed trial to change the agreement

On 7 April, they rehearse with a synthetic client record before using the checklist for Ravi. Iman can prepare the invitation but cannot assign a protected preparation workbook that Nessa controls. The synthetic client cannot open it. A staff preview had looked correct, so the receiving-person check exposes a real gap in their proposed process.

Nessa’s first reaction is to ask Iman to send her private preview link. He points out that this would not demonstrate the intended client’s access. Nessa withdraws that instruction. They keep the workbook private and revise the handover instead of making the material public or giving Iman unrestricted access to every client record.

The revised agreement explicitly retains workbook assignment with Nessa. Iman sends the intended recipient and required resource reference through the authorized operations route, without copying coaching responses. Nessa performs the assignment and reports back. Iman can then request the intended client’s opening confirmation; he cannot mark her part complete merely because he has asked her.

On 8 April, Nessa makes the required assignment for Ravi. Ravi opens the resource using the intended account and confirms it is available. On 9 April, Iman completes the date and inclusion check and sends the ready message for the confirmed 12 April start. Ravi acknowledges it. The case establishes readiness, not that a later coaching session was attended.

The arrangement remains act-and-report for Iman’s routine work, with a named owner dependency. Calling it domain ownership would still be premature: he does not have end-to-end authority over every material condition.

Handle a reserved decision without inventing permission

On 9 April, Pia asks whether her employer can receive the coach’s notes. Iman records the request as an exception and routes it to Nessa. He neither sends notes nor promises that a paying employer automatically receives them. He also avoids telling Pia that the request has already been refused by a policy he has not checked.

Nessa reviews the actual agreed reporting arrangement with Pia. In this example, Pia wants one limited service-status statement, and no coaching notes. Nessa prepares the exact statement, sends it to Pia and asks whether that is the wording she authorizes. Pia reads and approves it on 12 April.

Pia has agreed to begin the coaching service. The scheduled first session is 15 April. This statement does not describe session attendance, coaching content or an assessment result.

Nessa sends that approved statement to the agreed employer contact on 13 April and records what she sent. She does not label a scheduled future session as attended. Iman records that the reserved reporting question is resolved for this exact statement; it is not permission for him to release future notes or report on other clients.

At their ten-minute checkpoints on 9 and 13 April, Nessa and Iman review the actual completed steps and blocked dependencies. They keep routine authority with Iman while checking the actions Nessa retains.

Nessa also assigns Pia’s required preparation resource. Pia confirms it opens, and Iman completes the remaining readiness checks on 13 April. Pia acknowledges the welcome for 15 April. The reporting exception did not require Iman to hand back every routine onboarding step.

Decline a change that the pilot does not authorize

On 14 April, Ezra asks for a start earlier than the agreed 16 April date. Iman can coordinate the confirmed date but cannot create a new delivery commitment. He asks Nessa to decide. She checks the actual accepted work and explains that the earlier start is unavailable. Ezra accepts 16 April; the case does not manufacture an alternative slot.

Nessa completes Ezra’s retained resource assignment. On 15 April, Ezra confirms access, and Iman finishes the date, inclusion and welcome checks. Ezra acknowledges the ready message. All three onboarding records now meet the pilot’s defined outcome, while the scope and reporting decisions remain with Nessa.

The completed delegation record after the pilot

Iman’s 110 minutes comprise twenty for brief preparation and agreement, forty-five across the three routine setups, twenty for the two checkpoints, fifteen for exception coordination and ten for closing the records. The synthetic access check is included in the setup work; the retained-owner requests and client confirmations are included in exception coordination and closing. Nessa’s and Theo’s time are separate, so these figures do not establish total labor, savings or profitability.

At their 15 April review, Nessa checks the three completed records with Iman. He points out that she originally expected full ownership without enabling the protected assignment. She acknowledges the gap and accepts the retained dependency in the final record. They both confirm the continuation decision. In her coaching conversation, Nessa uses the de-identified result to examine her own habit of treating an unclear instruction as a completed delegation.

Readiness for these starts is not proof of lasting business improvement. The observed result is narrower: three acknowledged readiness records, two reserved decisions handled by the owner and an explicit retained access task. Future onboarding volume, session attendance and business outcomes remain unestablished.

Review the arrangement after real use

Ask what the receiving person could decide, where they waited and what support was missing. Compare the result with the agreed outcome rather than the founder’s preferred way of doing every step.

Record one improvement at a time. A clearer exception definition, an earlier checkpoint or access to the right information may remove more friction than a broad instruction to be more proactive.

Use the next review to decide what should remain, expand or narrow. The purpose is dependable work and growing judgment, with realistic accountability on both sides.

Use Coachful for the coaching process

Assign an original delegation worksheet through Clients > select the business-owner client > Worksheets & resources > Assign. Use it to prepare one actual handover, not to score the employee’s maturity. The owner can bring the purpose, authority, workload, dependencies and unresolved question into the coaching conversation.

Record the owner’s chosen action and review date. A task or goal records an intended action; check the actual acceptance, access and completed output separately. If the owner returns a de-identified account, keep the source and remaining uncertainty visible. Coaching preparation is not an employee performance system or permission to collect the whole staff file.

If the owner runs their own Coachful workspace, review actual staff permissions and client scope for the intended task. Authorized direct assignment can supply a resource grant; copying a private link cannot. Do not use a staff preview as evidence that the receiving client can open it, or make a private resource public to work around an access issue.

Nessa’s operational handover and Theo’s coaching workspace are different contexts. Assigning Nessa a reflection worksheet does not assign resources to her clients or give Theo access to their records. Verify each intended audience in the appropriate workspace before reporting the workflow complete.

The Coachful features overview can support the workflow. Our quarterly planning guide helps connect a delegated domain with a broader business priority.

Professional context

The ICF Code of Ethics supports clarity about roles and responsibilities in the coaching engagement. The six delegation arrangements and completed handover are original practical examples for discussion with the business owner.

Frequently asked questions

How do I choose a delegation arrangement?

Consider the specific task, authority, risk, competence, workload and support. Agree the boundary with the person and review it after real use.

What if work is completed differently from my approach?

Compare it with the agreed outcome, quality and constraints. A different method may be acceptable. Explain any material concern rather than replacing work solely because it looks different.

What if the person makes a mistake?

Address the impact and examine the process, information and authority. Choose a proportionate response and support. Accountability and learning can both be part of the review.

Can I delegate accountability entirely?

Responsibility and authority can be distributed, while owners and directors may retain duties under governance and law. Clarify those duties with appropriate advice rather than relying on a task label.

A clear delegation agreement names the work, authority, support and return route. Start with one real handover and improve the arrangement through evidence and conversation.