How to Run Virtual Executive Coaching Sessions
Nour
Founder, Coachful

This guide explains how to run virtual executive coaching sessions from preparation to a client-owned next step. Agree a useful focus, make the conversation accessible and explore the client's situation before choosing an action. Clear audio, readable material and a workable recovery plan usually deserve attention before an elaborate studio.
Video is a delivery setting, not a separate coaching method. Adapt camera use, pace and materials to the person and the work. A quiet pause can help someone think; it should not become pressure to disclose more. This guide follows preparation, a fifty-minute conversation, a corrected record, a privacy interruption and a later review.
Set up five parts of delivery
| Area | Practical standard | Check before relying on it |
|---|---|---|
| Audio and video | Speech is intelligible and shared material readable. | Use the actual device, room and connection intended for the appointment. |
| Attention | The client helps choose the focus and can change the pace. | Ask what would make this time useful today. |
| Notes and collaboration | Private notes and shared working material have clear audiences. | Agree what will be displayed, retained and deliberately sent. |
| Action handoff | The client understands the commitment and review arrangement. | Ask them to describe the action, authority and evidence in their words. |
| Professional setting | Links, timing, access and recovery instructions are understandable. | Make the fallback available before anything fails. |
The software guide for executive coaches connects these needs to platform selection. First decide what you must deliver. A screen full of controls does not establish that the client can hear you, read a document or speak privately.
Prepare the actual room and connection
Camera: choose a comfortable stable position. A camera near eye level may make the frame easier to follow, but constant lens contact is unnecessary. Do not interpret looking away, camera-off participation or a changed posture as dishonesty or resistance.
Audio: prioritize intelligible speech and reduce avoidable noise. A modest headset may solve the problem. Ask about hearing and communication preferences rather than prescribing expensive equipment. Test what the other person receives, including volume and competing sounds, before deciding the arrangement works.
Lighting: make your face visible without glare or a bright window behind you. Adjust to the room rather than requiring a three-light studio. Background: remove confidential items from view and check notifications, open files and what sharing the whole screen would expose. Share the intended window where suitable.
Ask about captions, readable documents, keyboard access, pauses and alternative formats before the session where possible. W3C's caption guidance distinguishes live captioning from preparing captions for recordings and explains that automatic output can change meaning. Check the actual arrangement and confirm important names, numbers and decisions. An enabled switch is not proof of accuracy or accessibility.
A client may prefer an accessible text brief beside the call rather than a whiteboard. Check that they can navigate it and question its contents. Do not require a new account or unfamiliar tool midway through sensitive work merely because it makes the coach's demonstration look polished.
Make the practical check specific. Ask the client to read the heading of the shared document and tell you if its text is too small. Confirm whether a document can be provided directly instead. Agree how either person can interrupt when audio breaks up. If an important sentence was missed, repeat or restate it and ask what the client understood; do not assume a nod confirms every word.
Review the room again when someone moves location or another person enters. A previously private appointment can become unsuitable without anyone doing something wrong. Offer a pause, a different non-sensitive focus or rescheduling within the agreement. Keep the client's access needs separate from a judgment about motivation. These are general delivery checks, not reasons to require disclosure of a diagnosis or personal history.

Send a short brief and recovery plan
In this fictional case, Asha coaches Felix, a regional operations leader. Two weekend changes waited until Monday because teams disagreed about approval. Felix can convene a discussion but cannot rewrite approval policy alone. Jo and Luis are the two managers he normally works with.
On Monday 7 May 2029, Asha spends fifteen minutes preparing and sending Felix the brief, access choices and recovery plan. Felix spends fifteen minutes reading and returning the completed brief on 8 May. He can answer verbally instead if the written route is inconvenient. Asha's fifteen minutes on 9 May include reading his answers and preparing the session.
| Preparation field | Felix's response |
|---|---|
| Useful outcome | Prepare a conversation about weekend change authority without accusing either regional team. |
| What happened? | Two changes waited until Monday because each team believed another approval was needed. |
| Known versus assumed | The delays are recorded. Manager avoidance is Felix's interpretation, not something the managers have confirmed. |
| Authority | Felix can ask the managers how they understood the process. He cannot promise a policy change. |
| Material | A redacted process example and the current policy, without customer data or investigation documents. |
| Access and privacy | A private room for the first call, optional camera, no recording and a short action record instead of a transcript. |
The pre-agreed recovery plan is simple: try the existing meeting link again for up to two minutes after a disconnection. If it still fails, use their agreed contact channel to decide whether a previously authorized audio route is private and suitable, or reschedule. Do not automatically move sensitive conversation into an unfamiliar personal account.
They agree that the coaching content and selected action record are for Felix. Any sponsor administrative update requires its separate agreed scope. The sponsor receives no coaching content in this case. The ICF Code of Ethics addresses agreements, information exchange, records and technology responsibilities. A sponsor's purchase does not itself define the audience for every conversation.
Use a five-stage, fifty-minute agenda
The first session takes place on Thursday 10 May, 14:00–14:50 London time. Both participants use the complete fifty minutes. This agenda is an example, not a claim that fifty minutes is optimal for every executive.
- Arrive, minutes 0–5: check privacy, communication needs and time. Offer a pause, a sip of water or a straightforward start. Felix chooses to begin directly, with no recording.
- Choose the focus, minutes 5–10: agree whether to prepare the managers' conversation or examine whether it is the right conversation to have. Felix chooses preparation.
- Explore, minutes 10–35: separate events, interpretations, authority and missing information. Ask what each person might know. The purpose is a better understanding, not diagnosis of hidden motives.
- Rehearse, minutes 35–45: try an opening, hear a possible objection and revise the request. Felix decides what he is willing and authorized to do.
- Close, minutes 45–50: Felix states the action, timing, evidence and audience. Asha checks what he wants retained and the review arrangement.
Keep the structure visible without forcing every topic to occupy its full allocation. If a different issue becomes more important, ask how the client wants to use the remaining time. Do not silently convert a coaching appointment into an investigation or extend into another client's time.
Build a map the client can correct
Use paper, an accessible document or an available whiteboard with the appropriate permissions. The map needs to be small enough for Felix to challenge. Asha reads it aloud rather than assuming the display alone communicates it.
| Known | Possible interpretation | Next check |
|---|---|---|
| Two changes waited until Monday. | The managers avoid responsibility. | Ask which approval step each believed necessary. |
| The policy names an approval role. | Both regions understand it identically. | Compare their readings against the current policy. |
| Felix can convene a discussion. | He can authorize a new procedure himself. | Identify who can decide the disputed policy question. |
The following exchange occurs within the rehearsal allocation:
Felix: I want to say, “You both need to take ownership.”
Asha: What would they need to understand in order to act differently?
Felix: Which decision they can make, and when they need approval.
Asha: Try an opening that asks about that before assigning a cause.
Felix: Two changes waited over the weekend. Could we compare the approval steps each team followed, then identify what needs clarification?
Asha: If they ask you to change the policy immediately, what can you actually offer?
Felix: I can document the disagreement and identify the policy owner. I cannot promise the rule will change.
After a pause, Asha asks whether more thinking time would help or a different question would be useful. Felix chooses the next question. Silence is not scored as a breakthrough; a camera movement is not evidence of an emotion or hidden belief.
Complete the action record, then correct it if needed
| Field | Felix's chosen action |
|---|---|
| Action and owner | Felix asks Jo and Luis to compare their understanding of the approval steps. |
| Timing | Send invitations by Wednesday 16 May, 15:00 London time; propose a twenty-minute discussion on 23 May. |
| Preparation | Use the redacted example and current policy. Identify the policy owner before promising a changed rule. |
| Evidence | Record each manager's account and questions needing an authorized decision. |
| Audience | Felix receives the coaching record. The managers receive only his operational request. |
| Review | Discuss what was learned at the next suitable coaching appointment. Sending an invitation does not resolve authority. |
Asha spends ten minutes after the call preparing and sending a manual V1 action note. She makes a substantive mistake: it says Felix will authorize a revised weekend procedure. On 11 May, Felix spends ten minutes reading it and replying that the authority question remains open. He also says no to sending private coaching content to the sponsor.
Asha spends ten minutes on 14 May reading that reply and sending the corrected V2 below. She withdraws the earlier inference; she does not describe it as a minor wording preference.
Felix, I incorrectly wrote that you would authorize a revised weekend procedure. You said you can ask the managers how they interpreted the current steps, then identify the policy owner. I have corrected the record and withdrawn that inference. Your next action remains sending the invitations by Wednesday 16 May at 15:00 London time. At our review, we will examine the replies and what still needs an authorized decision. This note is for you; I have not sent private coaching content to your sponsor.
Felix spends five minutes on 15 May reading V2 and accepting it as the limited action record. That acceptance confirms what he chose to do; it does not authorize an employer report or prove the managers' motives.
Treat a privacy failure as a delivery decision
A second appointment had been reserved for 14 May. Travel disruption leaves Felix in an airport lounge. At 15:00, Asha asks whether he can discuss the planned topic privately. He cannot. They use five minutes each, through 15:05, for administration only: agree not to discuss the sensitive topic, select a twenty-minute review on 21 May at 14:00 and confirm the revised appointment arrangement.
Headphones would limit what Felix hears, not prevent nearby people hearing him. Turning the camera off would not create a private room. Asha respects the decision to stop. The replacement is a specified twenty-minute review, not an invisible fifty-minute session or an emergency availability promise.
For other connection failures, use the pre-agreed fallback and check identity and privacy again before continuing. For an urgent board investigation, legal dispute or safeguarding issue, clarify the coach's role and availability and use the appropriate organizational or qualified support. A coaching booking does not establish an emergency response service.
Recording also needs its own decision. The ICO's recording guidance, currently marked under review, discusses necessity, less intrusive alternatives, a justified lawful basis and explaining purpose and retention. A recording preference is not the whole legal assessment. Here the agreed alternative is no recording and a selected written record.
Let the managers choose how to respond
On 16 May, Felix spends twenty minutes reviewing the redacted example and policy and sending the two operational invitations before 15:00. He proposes the twenty-minute 23 May discussion and asks each manager which approval step they believed necessary. His ordinary operational role permits that request; he sends neither the coaching transcript nor private reflection.
Jo spends fifteen minutes on 17 May reading it and replying that she will describe her reading but does not agree Felix can change the policy. Luis spends fifteen minutes on 18 May reading and answering in writing. He declines the meeting and explains that his team believed approval from the policy role was still required.
Before the 21 May coaching review, Felix spends fifteen minutes reading both returns and preparing his update. Jo's reservation is relevant operational information, not defensiveness to be coached out of her. Luis has provided an account while saying no to the proposed format. Neither has accepted a new procedure.
During the twenty-minute 14:00–14:20 review, Asha and Felix distinguish receiving the accounts from resolving policy authority. Felix chooses to retain the written route and cancel the proposed meeting. Afterward he spends ten minutes preparing and sending separate closes to Jo and Luis: their written accounts are sufficient for this step, the 23 May meeting will not proceed, and no changed procedure is being announced. Both read their own close for five minutes on 23 May without acknowledgment.
Asha spends ten minutes after the review preparing and sending Felix this finite coaching close:
You received two accounts of the approval process and respected Luis's choice to answer in writing. Jo has not agreed that you can change the policy, and the authority question remains open. You chose to cancel the proposed managers' meeting and retain their written accounts for the next organizational decision. This closes our agreed review, not the underlying weekend-delay problem. You have not yet contacted the policy owner. Please keep any later policy decision separate from the coaching action we reviewed.
On 22 May, Felix spends ten minutes reading and replying that the limited review is complete and he is making no further request in this exchange. Asha spends five minutes reading that closure; no acknowledgment follows. The case ends after the managers read their closes on 23 May. Policy ownership and the original delay problem remain unresolved.
Count the work around the call
The following account includes all described active participant work in the case. Numbers after activities are minutes; live attendance is included in the totals.
| Person | Work in May 2029 | Used / allocated minutes |
|---|---|---|
| Asha | 7: prepare and send brief 15; 9: read preparation and plan 15; 10: session 50; 10: prepare and send V1 10; 14: read correction and send V2 10; 14: airport administration and rebooking 5; 21: review 20; 21: prepare and send final note 10; 22: read closure 5 | 140 / 175 |
| Felix | 8: read and return brief 15; 10: session 50; 11: read V1 and send correction 10; 14: airport administration 5; 15: read V2 and accept 5; 16: prepare and send invitations 20; 21: read managers' returns and prepare 15; 21: review 20; 21: send two manager closes 10; 22: read final note and reply 10 | 160 / 195 |
| Jo | 17: read request and send account with reservation 15; 23: read close 5 | 20 / 25 |
| Luis | 18: read request and send written account declining meeting 15; 23: read close 5 | 20 / 25 |
Total known work is 340 of 420 allocated person-minutes, leaving a difference of 80: 35 each for Asha and Felix, five each for Jo and Luis. Live participation contributes 150 minutes: two people for fifty minutes, two for five airport minutes and two for twenty review minutes. The remaining 190 minutes cover preparation, reading, writing and sending. Do not add live time again.
Earlier operational work and engagement setup are outside this bounded account, with unknown effort. They are not free. Neither the 80-minute difference nor two returned accounts establishes whole-practice spare capacity, improved performance or resolution of the approval problem.
Keep optional duration and workload models separate
A separate sixty-minute option can allocate ten minutes to arrival and contracting, twenty-five to exploration, fifteen to options and rehearsal, and ten to synthesis. That totals sixty. Choose it when the agreement and client support it; it is not another meeting performed in this case.
For scheduling, fifty live minutes plus fifteen preparation, ten documentation and fifteen buffer uses ninety minutes of a provider's calendar. Four such slots occupy 360 minutes, or six hours, before other business work. A sixty-minute call with the same allowances uses 100 minutes; four use 400 minutes, or six hours forty. These are planning reservations, not the case's measured active work.
Connect preparation, calls and appropriate records
Coachful is our #1 recommendation for coordinating the preparation, meeting access and follow-up workflow described here. Choose the actual meeting route: configured built-in calls where available, a connected Zoom route, or a manually supplied link. Check required permissions and the saved meeting details. Pasting a link does not mean Coachful created the external room or controls all its recording, captions and admission settings.
Use readable screen sharing for the agreed material and a separate accessible collaboration surface where needed. Private coach-team review notes are not client delivery. If using summarized sessions, recaps send automatically by default; approval settings can hold new unsent recaps, and session-type settings can override the workspace default. Check those settings before sensitive material enters that workflow. Approval cannot retract an already sent recap.
Assigning new tasks is a separate review action. The call summaries and actions guide explains the distinction. Asha's case uses manually prepared selected notes, without recording or transcription. It does not demonstrate automatic summarization, caption quality or an employer integration. Explore Coachful features against the actual arrangement.

Check eight operating standards
- Access: correct link, usable device and agreed communication needs.
- Preparation: relevant material read; permission before widening the agenda.
- Privacy: room, attendees, screen and audience checked again when circumstances change.
- Collaboration: an available accessible surface the client can correct.
- Recording: purpose, appropriate permissions, handling and alternatives considered beforehand.
- Actions: client-owned commitment, actual authority and follow-up route confirmed.
- Capacity: preparation, documentation and recovery allowed around live time.
- Review: evidence and client experience examined, including whether the format still works.
Frequently asked questions
What equipment do I need?
Start with intelligible audio, a usable connection, readable material and privacy. Buy equipment to solve an observed problem, then test the actual result.
How long should the session be?
Agree a duration suited to the work and person. Adapt the fifty- or sixty-minute examples; length alone does not establish depth.
How do I handle distraction?
Ask what attention is available and whether to change focus, pause or reschedule. Invite helpful notification changes without turning them into a commitment test.
Should every call be recorded?
No. Consider the purpose, relevant obligations and appropriate alternatives. A selected agreed action record may be sufficient; it still needs accurate content and controlled sharing.
How can software support the session?
It can connect preparation, access, appropriate notes and actions. Verify the configured route, recipients and actual delivery instead of treating a saved private note as a received client message.







