The Client Who Wants to Finish Early

The default in this scenario should be client autonomy, with genuine exploration before accepting it.

Arguments for honouring the ending:

• The client defines the goal and the term. A client who has got what she came for is a success story, not an attrition statistic.
• The remaining sessions may have been scheduled for a need that no longer exists. Padding them out wastes her time and teaches her that coaching is a commitment to a calendar rather than to an outcome.
• A coach who resists ending because of a contract clause has made the commercial relationship the client's problem.

Arguments for one honest conversation first:

• The stated goal is 30% and she is at 25%. That gap may be immaterial or may be the whole point - only she can say.
• 'Too busy' plus two reschedules plus a stalled pipeline is a pattern worth naming once, without insistence.
• Ending is also a competency: a planned closing session (learning, what she will sustain, what she will watch for, who she will tell) produces more than a fade-out.

What must not happen: using non-refundability or the accelerator's report as pressure. Ade can state the facts ('unused sessions aren't refundable; here's what I can and can't do about that') and then let the decision be hers.

A strong answer commits to a course of action while showing what would change it - for example, that Ade would argue for at least one closing session if Sofia's only reason is time pressure.

The pipeline is a real signal and Ade has no mandate to make it a goal. The distinction is between offering an observation and setting an objective.

• Locate it in her own words. Sofia's original reason for delegating was to free capacity for fundraising. Ade can reflect that: 'You wanted the space for fundraising. Twenty-five percent in, what's happened to that space?' That is inquiry, not agenda.
• Ask permission before pressing. 'There's something I've noticed and I'm not sure it's mine to raise - do you want it?' Clients rarely refuse, but the asking preserves the frame.
• Do not convert it into a condition of ending. 'You can't stop yet, the pipeline has stalled' would be Ade substituting his judgement for hers.
• Accept the answer. If Sofia says fundraising is deliberately paused until the ops lead is embedded, that is a strategy, not a blind spot, and Ade should update rather than repeat the observation.

Why this is competency 8 and not competency 7: evoking awareness is the questioning; facilitating growth is honouring what the client does with the awareness - including doing nothing, or choosing a different goal. The test is whether the client owns the next step or the coach owns it.

Before session eight, not after. A report requested at the end of an engagement should not be defined after the client has left the room.

• Clarify what is actually wanted. Attendance and completion? Progress against the goal? Aggregate programme data? Each is a different disclosure decision.
• Default to process, not content. Confirming that the engagement ran, how many sessions were used, and that the client reported progress toward her own stated goal is usually enough for a sponsor. Themes, quotes, and personal circumstances are not.
• Get the client's agreement in advance, and be specific: 'I'll confirm sessions attended and that the goal was largely met. Nothing about what you said in the room.' If the accelerator wants more, that is a new agreement requiring Sofia's consent.
• Tell Sofia the report is happening even if its content is mundane. Surprise disclosures of any kind erode safety.
• Watch the sequencing trap: if Ade negotiates the report after discovering Sofia wants to leave early, it will look - to her, and probably to an assessor - like leverage.

A defensible answer also notes that an accelerator expecting completion may need to hear that a client ending early after meeting her goal is a good outcome, and that the coach should say so rather than apologise for it.