Fractional COO Decision Rights: A Practical Delegation Worksheet

The founder is copied on every difficult email. Department heads attend the same meeting, then leave with different priorities. A fractional COO can help, but adding another executive will not resolve the bottleneck if nobody defines which decisions that person can actually make.

This guide explains how to give a fractional COO a usable decision mandate. It is intended for a growing business with capable functional managers and recurring disputes over capacity, customer commitments, spending, or delivery priorities. The proposed worksheet and examples are editorial planning tools, not claims about a particular provider's results.

If you are still defining the role, start with what a fractional COO does. Here, the narrower task is deciding who can commit the business when several functions need different things.

Start with delayed decisions, not a new organization chart

Collect ten recent situations in which work stopped while people waited for permission. Use real examples: accepting a rush project, replacing a supplier, changing a delivery date, moving an engineer between teams, or authorizing temporary capacity. Record the question, the people involved, the time spent waiting, and what happened afterward.

Separate a decision problem from an information problem. A manager who cannot see delivery capacity needs reliable information. A manager who can see capacity but cannot decline an unrealistic promise needs authority. Hiring a COO without distinguishing these causes can simply add another person to the approval chain.

Choose three recurring decisions for the first version of the mandate. Favor decisions with visible consequences and enough repetition to learn from. Leave rare, complex transactions for a separate governance process. A short, used agreement is more valuable than a complete matrix nobody remembers.

Distinguish input, approval, and execution

A person can contribute important information without having the final say. Someone can also implement a decision without having authority to approve it. These distinctions are central to Bain's guidance on decision roles, which describes RAPID roles for recommending, agreeing, performing, providing input, and deciding.

You do not need to adopt a branded framework to make the distinction operational. For each selected decision, write down who prepares the proposal, whose input is necessary, who approves within a stated boundary, and who carries out the result. Name people or current roles rather than writing “leadership team” in every box.

Ask the implementer whether the proposed decision can actually be delivered. An executive may approve a revised launch date while the support team lacks training or the finance team lacks billing instructions. Execution feedback belongs before the commitment, with a deadline that prevents consultation from becoming indefinite delay.

Give the COO boundaries that managers can use

A mandate should describe the decision and its limits together. “Own operations” is too broad. “Approve project sequencing within the agreed quarterly priorities, unless the change alters a signed customer commitment” gives people something they can apply.

Use several types of boundary where needed: financial amount, duration, customer impact, headcount, and reversibility. A small purchase can create a long commitment; a temporary staffing change can undermine a strategic account. Define the exception that matters, not just the easiest number to measure.

Illustrative decision worksheet: the following assignments are examples for a services business, not a recommended governance structure for every company.

Have the CEO approve the boundaries explicitly. A fractional executive's title alone does not grant spending authority, signing authority, or the right to change another leader's priorities. Record any board or contractual constraints in the actual agreement rather than assuming the worksheet overrides them.

Make authority work on days the COO is absent

A part-time operating leader should not become a part-time permission desk. Every recurring decision needs a default owner while the COO is unavailable. Specify which matters can wait, which can proceed within agreed limits, and which need immediate escalation to the CEO or another designated leader.

For example, a delivery manager might continue allocating work within a confirmed project plan. A new promise that affects another customer's deadline might require the designated executive's approval. The difference should be understandable without reading an entire engagement contract during a customer call.

Agree the communication channel and response window for genuine exceptions. A shared log can hold ordinary decisions; a direct escalation channel can serve urgent issues. Do not interpret silence as approval unless that behavior has been explicitly agreed for the specific decision. Availability expectations should also appear in the provider's scope and fee proposal.

Run one short decision meeting

Use the weekly operating meeting to resolve exceptions rather than recite everything each department has done. Circulate the decisions required, the owner's recommendation, relevant evidence, and the deadline before the meeting. Participants should arrive knowing what they are being asked to decide.

A useful agenda might cover unresolved commitments, capacity conflicts, and decisions whose assumptions have changed. Keep routine progress reporting in a shared update. When discussion exposes missing information, assign someone to obtain it and set a decision date instead of allowing the issue to disappear into “follow-up.”

TechCXO's fractional COO service description includes operating rhythms, accountability, and alignment across functions. That illustrates the kind of leadership scope buyers can request; it does not establish that any particular meeting format will produce a guaranteed improvement. The agreement still needs named owners and practical boundaries.

Record enough to stop reopening settled choices

Maintain a decision log with the question, date, owner, options considered, selected action, execution owner, and review trigger. Add the assumption that would justify reopening the decision. A changed customer requirement may qualify; a participant remembering that they preferred another option usually should not.

Keep this log separate from a task list. A task says “revise the staffing plan.” A decision says “defer the internal project for two weeks to protect committed client delivery.” Recording the reason helps a new manager understand what to preserve and what can change.

Use access appropriate to the content. Ordinary operating choices can be visible to the team; sensitive people matters and confidential commercial terms need a narrower audience. Broad visibility is useful only when it does not expose information to people who do not need it.

Test the mandate with a realistic conflict

Illustration: a sales lead wants to promise a ten-day onboarding period to a new customer. Delivery estimates fifteen days using current capacity. The COO can resequence approved work but cannot change existing customer commitments.

The commercial lead prepares the opportunity context. Delivery describes available capacity and dependencies. Finance explains the cost of temporary support. The COO can approve a feasible sequence inside the agreed envelope; a proposal that exceeds it goes to the designated executive. The account owner communicates the approved promise and records it for delivery.

Now remove the COO from the scenario for two working days. If nobody can explain what happens next, the mandate is incomplete. This tabletop exercise reveals missing delegation more quickly than a general conversation about collaboration. It also helps the team identify which decisions should remain with functional managers.

Review the agreement after a month

Assess a small sample of decisions before and after the mandate. Look at waiting time, repeat escalations, reopened decisions, and commitments made outside authority. These are diagnostic signals, not proof that the COO caused a financial result. Business conditions and the complexity of the decisions may have changed.

Ask managers where the agreement helped and where it created unnecessary approvals. Remove boundaries that add friction without protecting anything important. Tighten unclear exceptions. A good mandate evolves as the executive and internal team learn how the business works.

Before finding a fractional executive, prepare the three decisions, their current bottlenecks, and the authority you are willing to delegate. Use the fractional COO directory and the COO versus operations consultant guide to match the engagement to that work. The deliverable you are buying is an operating agreement people can use, supported by a leader who keeps it working.