Automate Executive Coaching Check-Ins: Questions and Workflow
Nour
Founder, Coachful
To automate executive coaching check-ins, start with scheduled invitations to reflect between conversations. A short set of questions can help a client notice what happened and prepare for useful follow-up. Automation can deliver the invitation; the coach still needs an agreed purpose, review window and response process.
This guide develops three design principles, four workflow controls, a complete three-question template, an optional reflection rating, eight software checks and a filled operating record. The examples are original and fictional. A check-in is not continuous monitoring, a diagnostic instrument or a crisis alert system.
Coachful is our #1 recommendation for organizing this workflow: configure the reflection, audience and reminder separately, then maintain a realistic human review and response process. It supports the administration; it does not turn a questionnaire into continuous executive monitoring.
The ICF Code of Ethics addresses agreements about roles and information exchange. Use that distinction when a sponsor funds the service: agree what is shared rather than infer that payment authorizes private reflections.
Choose the right level of between-session contact
| Route | Potential use | What needs agreement |
|---|---|---|
| Scheduled sessions with no routine check-in | The client prefers to prepare and reflect within appointments. | How changed circumstances or a need for another conversation are handled. |
| Manual message by an appropriate channel | A limited follow-up fits the actual coaching relationship. | Purpose, audience, response window, privacy and information retention. |
| Scheduled reflection flow | A repeated short question set helps the client and coach review the work. | Actual recipients, timing, completion route, review owner and what happens after a response. |
No route is automatically careless or premium. A biweekly appointment can be suitable without constant contact. A dedicated app does not by itself guarantee better security or a more useful relationship than another appropriately chosen channel.
Ask whether a check-in helps this client think, creates an unnecessary reporting burden or feels like employment surveillance. A sponsor’s interest in progress should not silently turn a private coaching reflection into a management feed.
Use three design principles
- 1. Brevity with useful choice: Ask only what serves the agreed purpose. A ninety-second response may suit one person, while another needs more time or prefers speaking. Do not enforce a speed target as evidence of engagement.
- 2. An accessible, appropriate route: Agree where the client can respond privately and comfortably. Check device access, language, communication needs and notification preferences rather than assume native mobile push suits everyone.
- 3. Bounded human feedback: Explain when the coach reviews and whether a reply follows every submission or only relevant ones. A short voice or text response is a service choice, not an automatic promise.
A pause to reflect can be useful without claiming a change in the prefrontal cortex or guaranteed emotional safety. Keep the wording respectful and let the client report uncertainty, setbacks or no notable change.
Configure four workflow controls separately
| Control | Decision | Common misunderstanding to avoid |
|---|---|---|
| 1. Cadence and availability | Which cycle is useful, when the flow is available and which time zone applies. | Availability all day does not mean reminders are sent all day. |
| 2. Questions and response methods | The actual prompts, optional fields and supported text, dictation or voice-note route. | Allowing audio does not mean every recording becomes searchable text. |
| 3. Optional self-rating | Whether one clearly defined reflection rating adds useful context. | A low rating is not a clinical finding or proof of a leadership problem. |
| 4. Review and routing | Who reviews, when, what appropriate follow-up may happen and when the process pauses. | A submitted answer does not automatically produce an urgent coach alert or an immediate reply. |
These controls should serve the agreed coaching scope. Do not build an apparent twenty-four-hour safety service around a weekly questionnaire that no one reviews over the weekend.
Copy a complete three-question executive reflection
Suggested introduction: This reflection supports our agreed coaching work. Short notes are enough. Share only information appropriate for this record and audience. I review responses during the stated review window. This is not continuously monitored; use your appropriate existing support routes for a need that cannot wait.
| Original question | Optional guidance |
|---|---|
| 1. What changed or felt significant in your leadership work this week? | Include something that worked, a setback, no notable change or a question you are still considering. |
| 2. What constraint, uncertainty or support need would be useful to explore? | Describe your experience without naming employees, customers or restricted company material unnecessarily. |
| 3. What would you like to focus on next? | A decision, experiment or question is enough. You can change the priority when we meet. |
The questions do not require a strategic victory or assume that the client is resistant. They also do not make every reflection an organizational KPI report. Use a separate appropriately agreed reporting process if the sponsor needs specific information.
Add an optional rating only if its meaning is clear
Choose one construct rather than combine confidence, energy, focus and wellbeing into an undefined number. For example: “If useful, rate your available energy for the agreed work this week, where 1 means very little available energy and 10 means plenty. You can leave this unanswered and add context.”
This is an original self-reflection item, not a validated scale, diagnosis or assessment of capacity for employment. A person’s response depends on their own interpretation and circumstances. Do not compare employees as though their numbers have identical meaning.
If someone reports a low number, ask about the account they want to share and the coaching support that is appropriate. Do not infer burnout, danger, poor motivation or an automatic need to notify the sponsor. Use the relevant actual professional process for concerns that require it.
Complete a fictional three-cycle pilot
All people, messages and actions in this case are fictional. Iris is an operations director working with coach Nate on clearer delegation. They agree three invitations on 6, 13 and 20 November 2026, followed by a usefulness review. Participation is optional; a missed answer does not affect Iris’s purchased sessions.
Iris chooses short typed responses, one Friday invitation at 16:00 Europe/London and no push or WhatsApp reminders. Nate normally reviews on Monday between 09:00 and 10:00 in the same time zone. His declared absence on 16 November means the second review will be Tuesday 17 November instead. They agree that exception before enabling the pilot, rather than leaving an unattended Monday promise.
The three prompts above and the optional defined energy item form the reflection. Iris understands that submitted answers are available to the authorized coaching-team audience, rather than being private from every staff or technical access path. Her employer receives no individual reflection feed. She can omit names and restricted information, skip a rating or bring the topic directly to a session.
Check the saved workflow before the first invitation
Nate creates a dedicated custom flow, selects Iris as its sole recipient and checks the actual audience. Available all day permits opening outside a display-time window; Friday reminder delivery is configured separately. Show once a day limits completion on a given day, not once per week. Their service agreement asks for one optional reflection per invitation without pretending the daily control enforces a weekly quota.
They use an agreed access check. Iris opens the correct flow on her actual device and confirms the three questions, optional rating, audience explanation and review times are clear. This does not test future email delivery. Nate separately checks the saved reminder and channel settings, with no earlier test response counted as a pilot submission.
Read the first answer and repair the actual reply
The 6 November invitation is dispatched; Iris subsequently confirms receiving it. Those are separate facts. At 16:30 she submits: “I asked a project lead to prepare the first capacity-plan draft. We disagreed about whether that included final approval. I need to distinguish preparation from authorization. I want to clarify the boundary in our next conversation.” She chooses six on the optional energy item.
Nate reviews the answer on 9 November within the agreed window. He initially replies, “It sounds as though you delegated the approval decision.” Iris corrects him: she delegated preparation and still holds final approval. The energy response supplies no evidence about either person’s authority.
Nate checks her actual submission and sends a correction:
Thank you for correcting me. Your note says you delegated the first draft, while final approval remains yours. My earlier wording changed that meaning. I have corrected my review record. Would it help to examine what the project lead understood and how to state the preparation and approval boundary? We can confirm the focus when we meet.
Iris acknowledges the revised account. In their next scheduled session, she chooses that topic and prepares a clarification for the project lead through the company’s normal work channel. The reflection has supported preparation and an actual correction; it has not proved that the workplace misunderstanding is resolved.
Handle a missing response without inventing its meaning
The 13 November dispatch record shows the invitation was sent, but there is no confirmed response. It does not show that Iris read it. At the agreed 17 November review, Nate uses the one optional manual check they had authorized for a missed cycle: “I do not have a response for this invitation. Is the process still useful, or would you prefer to leave this week and use our next session?”
Iris replies that she was busy and wants to leave that cycle unanswered. She asks for no catch-up reminders. Nate acknowledges that choice and sends none. He does not backfill a score, mark a missing answer as zero or contact the sponsor about engagement.
Review the last answer and close the right workflow
On 20 November Iris receives the third invitation and submits a response without the optional rating. She reports that the first draft exists, but a cost assumption still needs checking before she can approve it. Her requested next focus is how to ask for that evidence. Nate reviews it on 23 November and they discuss the process in a separate fifteen-minute usefulness conversation already agreed for that date.
Iris values the first correction and the ability to skip a cycle. She also finds a recurring Friday prompt burdensome during busy periods. She chooses to stop routine invitations and prepare within sessions instead. Two confirmed submissions from three intended cycles describe this pilot’s use; they do not establish a validated leadership score or a general completion benchmark.
Nate removes Iris from this dedicated flow’s audience and checks the saved empty recipient list and relevant client availability. He checks that no separate follow-up message remains queued for this pilot. He does not pause her entire workspace membership, alter other flows, cancel billing or erase previous responses.
On 27 November, Nate checks that this flow generated no new invitation for Iris, and Iris confirms that none arrived. That supports the closure of this particular process, rather than a claim that every notification from the platform has stopped. Their ordinary coaching arrangement continues.
Nate records ninety minutes of his pilot administration and review: twenty-five for setup and the access check, sixteen for reading two responses, sixteen for writing, sending and reading the first reply-and-correction exchange, five for the missing-cycle exchange, fifteen for the usefulness conversation, seven for closure and six for the later delivery check. This is coach time only. It excludes the regular coaching sessions, Iris’s work and replies, and the company’s operational decisions.
Complete an operating record before enabling delivery
| Setting or responsibility | Filled example to adapt |
|---|---|
| Purpose | Support reflection on agreed delegation work, not monitor employment performance. |
| Recipient | One named active client who has agreed to the process and can use the chosen route. |
| Flow and version | One short weekly reflection with the three prompts and optional defined rating. |
| Cadence and time zone | Friday at 16:00 in the client’s saved local reminder time; check the actual schedule and travel settings. |
| Availability and completion | Choose the intended display window and relevant completion cycle separately from reminders. |
| Response method | Text, or supported dictation/audio if configured and suitable; an alternative route remains available. |
| Notification channels | Only the supported enabled channels and the client’s actual preferences. |
| Review owner and window | Named coach reviews Monday morning during the agreed staffed window, excluding declared absence. |
| Follow-up | A relevant reply or topic for the next session within the agreed scope, without an immediate-response promise. |
| Information audience | The actual authorized coaching audience, with staff and technical access explained appropriately. |
| Pause and end | Review the flow audience, delivery, active access and any separate queued messages at the actual end. |
| Usefulness review | At the agreed pilot review, ask whether the questions, burden and timing still help. |
A saved configuration is not proof that a client received or completed a reflection. Review the actual record and intended client experience before making that claim. The example is not an instruction to change an account or a statement that every setting is available in every context.
Understand the current Coachful flow distinctions
Morning, evening and weekly check-ins collect reflection. A custom coaching flow may collect feedback, provide information or do both. Completing an informational flow is not automatically a written response or a request for the coach to review it.
Custom flows have separate display and reminder controls. Available all day changes availability, while reminder days and times remain separate. Show once a day is a daily completion rule, not a twice-per-day allowance or an automatic-opening switch. Existing audience and access restrictions still apply.
Placing a flow in the client’s Reflection widget or a Dynamic section does not itself enable delivery, widen recipients or change reminders. Both placements show the same flow and completion state rather than creating a second assignment.
A template can create an enabled custom flow with an empty audience. The coach must choose the actual recipients and review the settings. Do not describe installing a template as sending it to every client. Explore Coachful’s features for the supported workflow, then check the relevant controls.
Keep dictation and recorded voice answers distinct
For a supported configured Voice Text Input question, typing, voice-to-text and a voice-note answer can be alternative response methods. Existing questions need the appropriate settings; this is not a universal property of every form or program-completion screen.
Dictation produces editable text. A voice note remains audio for the coach to play through the appropriate response view. Choosing one mode does not mean all drafts are submitted or that audio is automatically transcribed into a searchable executive record.
Ask permission for microphone access through the actual device process. If dictation fails or is unsuitable, offer typing or another agreed route. Do not encourage a client to record while driving or in a setting where others can hear sensitive details. The voice coaching guide develops the delivery boundaries.
Use eight checks when assessing software and settings
| Check | What to confirm |
|---|---|
| 1. Timing | The saved cycle, reminder days, local time and any relevant travel behavior. |
| 2. Completion route | An appropriate device, accessible prompts and supported response methods. |
| 3. Response record | Where a confirmed submission appears and who can review it. |
| 4. Coach review | Actual notification behavior and a human review process, without an invented low-score emergency feed. |
| 5. Session preparation | A way to bring a relevant response into the discussion without automatically fixing the agenda. |
| 6. Information protection | Actual permissions, staff and technical access, retention and any processing providers. |
| 7. Historical comparison | Definitions, dates and missing data; a trend is not automatically a validated leadership measure. |
| 8. Client presentation | Real branding, access and plan settings, without assuming every channel is fully white-labeled. |
A reminder send, push dispatch, client read, submitted answer and coach reply are separate events. A notification can be disabled or missed. Do not claim flawless real-time visibility or a guaranteed completion rate.
Do not turn every answer into an automation
A branch within a coaching flow can use supported earlier answers to guide the next screen. That is different from an external automation condition. Check the actual trigger and schema before claiming that a reflection automatically grants resources, alerts staff or creates tasks.
Coachful’s Form answer automation condition applies to a Questionnaire completed trigger tied to one specific form. It evaluates supported fields from that triggering submission. Do not assume that every coaching-flow answer is the same questionnaire event or that an unconfirmed answer silently matches a condition.
When follow-up involves a client action or goal, use the appropriate ordinary plan workflow. Turning a worksheet response into a personal next action requires the response owner’s explicit choice through the appropriate supported workflow. A saved reflection is not a coach shortcut for silently creating that person’s task.
The milestone check-in guide develops practical progress follow-up. Keep the client’s choice and the actual supported workflow visible.
Connect check-ins to sessions and recaps carefully
At the next session, ask whether the submitted topic is still the client’s priority. A useful opening is: “I read your note about delegation. Is that what you want to explore today, or has something else become more important?”
A post-session recap is separate from a weekly check-in. In Coachful, summarized-session recaps send automatically by default, with a workspace approval setting and session-type overrides. A coach can review the relevant held recap before choosing to send or keep it private.
Check the actual summary, next steps, audience, channels and settings before assuming the client receives an immediate message or that the content is appropriate. A held recap and private coach notes should not be treated as already visible to the client.
A recap does not replace the client’s account of what happened next, and an automated reminder cannot ensure permanent behavior change.
Budget the human work behind automation
In an original planning example, twenty clients complete a weekly reflection. At three minutes of review each, the coach needs sixty minutes. If eight receive a five-minute reply, that adds forty minutes. A further twenty minutes for appropriate administration gives 120 minutes, or two hours.
If every one of the twenty receives a five-minute reply, replies require 100 minutes and the total becomes 180 minutes, or three hours. Longer responses, access problems, live follow-up and absence coverage are additional work.
Use your actual volume and effort rather than advertise a ninety-second form as a ninety-second service. If you cannot review within the stated window, change the scope or process before the invitation implies a level of support you cannot provide.
Respond to missing or concerning answers proportionately
A missed reflection can mean the invitation was not seen, access failed, the person was busy or the process did not help. Use a proportionate agreed reminder and ask about fit rather than label the client disengaged.
A reflection mentioning a difficult situation should be reviewed according to the actual role, competence, agreement and relevant obligations. Do not promise an immediate response simply because a field can accept urgent words or a low rating.
Keep appropriate support routes clear for needs that cannot wait. The coaching form should not be presented as a route for emergency help or as technology that detects every crisis. Nor should ordinary uncertainty automatically be escalated to an employer.
Measure usefulness and end the workflow deliberately
Pilot the process and ask whether it helps. If fifteen of twenty invited clients complete the relevant cycle, the response rate is 75% for that defined set. It is not evidence that executive completion should exceed 85% or that the non-respondents lacked commitment.
Check burden, access difficulties, relevant use in conversations and whether clients want another cadence. A rating chart or reflection count is not proof that coaching caused a commercial result, reduced turnover or improved health. Share sponsor information only through the actual agreed reporting process.
When the process ends, review the flow’s recipients, delivery and relevant access, plus any separate queued messages. Uninstalling the app does not necessarily stop email. Pausing one program does not silence workspace-wide flows if access continues through another program.
Check-in reminders are suppressed when the client’s workspace access is appropriately paused, disabled or archived. Confirm the actual account state and saved configuration before claiming reminders stopped. Closing a reflection process does not itself cancel billing or decide retention of past records.
Frequently asked questions
Are Friday afternoons always best?
No. Choose a cadence and time that suit the client and the actual review window. Friday is an example, not a proven universal optimum.
Will every executive finish in ninety seconds?
No. Response time depends on the questions, access needs and the person. Keep the form proportionate and offer an appropriate alternative.
Does a low rating automatically alert the coach?
Do not assume that. Check the actual notification behavior and maintain an agreed human review process. A self-rating is not a crisis detection tool.
Can a client answer by speaking?
Supported configured questions can offer dictation or a recorded voice note. They are distinct modes, and availability depends on the actual flow and device.
Does homepage placement send reminders?
No. Placement, audience, delivery, display and reminders are separate settings with their own access conditions.
Does ending one program stop every check-in?
Not necessarily. Workspace-wide flows may still apply through other access. Review the actual flow and membership state, and handle billing separately.
Automate the invitation only after the human process is clear. A useful check-in gives the client a manageable reflection route and gives the coach a realistic responsibility to review and respond.
The questions, operating record, fictional example and workload calculations are original. Product descriptions follow the verified Coachful release snapshot for coaching flows, response methods, automations, reminders and recaps. They do not establish a particular account’s configuration, delivery or deployment.
