That can be useful advisory work. It becomes a poor operating offer when the proposal holds the leader accountable for decisions the client has kept.
Before discussing the title, choose three decisions the person would need to make in an ordinary week. Agree who can decide, what limits apply and what happens when approval is needed. The result should tell both parties what they are buying and selling.
Describe an operating decision, not a broad responsibility
“Improve delivery” is too broad to expose a mismatch. “Move a specialist between two client projects when the weekly plan changes” gives the buyer something concrete to consider.
For each decision, ask:
- Who makes the final choice under the proposed arrangement?
- What information must they see before acting?
- Which limit sends the decision to someone else?
- Who provides that approval, and when can they respond?
- What does the fractional leader do while the decision is pending?
The client's limits may concern spending, customer commitments, people, risk or another part of the business. Have the client set them. Do not insert a standard amount or approval threshold just because a template has an empty cell.
The objective is a mandate the client can support and the leader can deliver. Some decisions may stay with the founder throughout the engagement. The scope and assessment of the leader's work must reflect that choice.
A fictional mandate that does not match the offer
The following company, people and decisions are fictional. They illustrate a scope negotiation, not a completed engagement or business result.
Harbour Works is a B2B implementation agency. Founder Nina wants fractional operations leader Rowan to take charge of delivery coordination while Nina focuses on selling. The draft scope asks Rowan to reduce avoidable schedule changes and make the delivery plan dependable.
In the first discussion, Nina retains every change to project staffing. She also wants to approve every supplier purchase and any message that changes a customer's delivery date. Rowan would see a weekly summary, rather than the current project schedule or supplier commitments.
The parties test a normal event. Two teams need the same specialist on Thursday. Rowan can identify a preferred allocation, but Nina must approve it. Nina is travelling and will review requests the following week. Rowan also cannot check whether the proposed alternative supplier is already committed elsewhere.
Rowan can advise under these conditions. Rowan cannot credibly promise to run the day's coordination. The approval delay and missing information sit directly between the recommendation and the action.
A revised three-decision mandate
Nina is willing to delegate some decisions, but wants to keep control of new spending and customer commitments. They write the following proposed matrix.
| Concrete decision | Rowan's proposed authority | Client-owned limit and approval | Information required | If approval is unavailable |
|---|---|---|---|---|
| Move a specialist between existing projects | Decide within the current staffing plan after consulting the two delivery leads | Nina retains changes that would alter a customer commitment; she confirms the written boundary before work starts | Current project schedule, specialist availability and the affected commitments | Keep the existing allocation until Nina or her named deputy decides; record the consequence and inform the delivery leads |
| Use an outside supplier for a capacity gap | Compare options and recommend a supplier; no purchase authority initially | Nina approves the supplier and spending commitment through the client's existing purchasing route | Approved supplier list, relevant availability, proposed cost and existing commitments | Record the unresolved capacity gap; Rowan does not imply that a supplier has been booked |
| Give a customer a revised delivery date | Prepare the options and operational implications; delivery lead communicates the approved decision | Nina retains approval for changing the commitment and names a deputy for absences | Current plan, customer agreement and the reason the date may move | Delivery lead acknowledges the open issue without inventing a new date; Nina or the deputy owns the next decision |
The matrix is a negotiation record. It takes effect only when the client confirms it through the appropriate approval route and the affected team understands it.
For Harbour Works, the changed proposal now has a clear shape: Rowan may run routine staffing coordination, recommend supplier decisions and prepare customer-date options. Nina keeps the last two approvals. The proposal names those retained decisions rather than burying them in “subject to management approval.”
Resolve the missing information and slow approval
A written authority boundary is unusable if the person cannot see the information needed to apply it. Nina agrees to give Rowan access to the current schedule and relevant commitments before the first operating session. Access should cover the agreed task; the matrix does not require unrestricted access to every company record.
They also agree a daily decision window for retained approvals, with a named deputy when Nina is unavailable. That response arrangement is a choice for this fictional agency, not a universal requirement for fractional work. The buyer must choose a response that fits the decisions it has kept.
Rowan's engagement can begin as limited operating leadership only after the delegated staffing authority, information access and approval cover are confirmed. If those conditions are missing at the proposed start, the first phase is explicitly advisory: inspect the available evidence, identify constraints and recommend decisions for Nina to make. It does not silently become an accountable operating role while access and authority remain pending.
Evaluate the work against the agreed mandate
Use a regular sponsor review to compare the work with the actual decision rights. Review the decisions Rowan made, the recommendations awaiting approval and any missing inputs. Record enough detail to distinguish a weak recommendation from a client decision that has not been made.
For example, a proposed staffing change could be wrong because Rowan overlooked an existing commitment. That is a matter to investigate and correct. A well-supported supplier recommendation awaiting Nina's approval is a different issue. Neither should be hidden in a general progress percentage.
If Nina wants Rowan to take more responsibility later, revise the matrix, access and commercial scope together. An expanded title alone does not change the work or the client's approval route.
Choose the offer the buyer can actually support
There are three credible conclusions to this conversation.
Sell advisory work when the client wants analysis and recommendations while retaining the operating decisions. Define the useful advice or decision material the client will receive and who will act on it.
Agree limited operating leadership when the client can delegate specified decisions, provide the necessary information and support the approvals it retains. Use the matrix to make the limits visible in the proposal.
Decline the mandate when the client insists on operating accountability while withholding the authority, information or response needed to carry it. Leaving those conditions vague does not make the engagement workable.
For the next proposal discussion, send a completed three-decision matrix based on the prospect's own work. Ask the sponsor to correct the decision rights and retained approvals. Quote the role that survives that discussion, with any advisory first phase separately described.
Source context: the Institute of Interim Management's Guide to Interim Management, August 2024, page 13, discusses responsibility, authority, access and regular client contact in interim management. It does not define fractional leadership. The decision matrix, fictional example and offer choices above are original planning aids.