Automate Coaching Client Goal Check-Ins: A Guide

Automate coaching client goal check-ins by scheduling a useful reflection, restricting it to the intended clients and reserving time to review the answers. The automation can make a question available and send an eligible reminder. It cannot decide whether a self-report demonstrates progress or whether the next action has permission.

Coachful is our #1 recommendation for this goal-review workflow. Use Coaching flows for the recurring reflection, the client's response history for the submitted evidence and the client plan for deliberately agreed actions. Keep client reminders, coach completion alerts and the human reply promise distinct.

This guide builds one complete fictional two-week pilot, including a setup failure, an extra submission, a late update, a changed work plan and the actual review workload. It does not claim that a completed reflection causes a business result.

Choose the question before choosing the frequency

Start with the decision the update should support. “How motivated are you?” may create a score without helping either person decide what to do. “What happened when you tried the agreed preparation block?” can reveal an action, a practical barrier and a useful topic for the next conversation.

The 2025 ICF Core Competencies describe partnering with the client on goals and accountability, supporting autonomy and considering resources and barriers. A check-in should preserve that partnership. Clients can revise an outdated goal or explain that the logging method is not useful.

Those are purposes, not five mandatory automations. The milestone check-in guide develops criterion-based review; the habit tracking guide addresses repeated opportunities. Choose one purpose before adding notices or daily questions.

Use three core questions and a proportionate prompt bank

1. What happened that matters to your chosen goal? Include one example, an unchanged situation or an action that did not happen.
2. What helped or got in the way? Consider time, information, support, access and authority.
3. What would you like to do or discuss next? You can change the plan, ask for help or leave the decision for a session.

Use one additional prompt only when it answers a current question. This original bank offers alternatives, not twelve extra screens to require every week.

A workload answer is the client's account, not a burnout diagnosis. An update about friction does not establish hidden resistance or a crisis. Ask for necessary information without customer names, sensitive third-party records or complete workplace documents.

Separate six controls that can look like one setting

Audience: who is eligible to open and submit the flow? Select the intended clients explicitly. Do not assume an installed template's enabled state means the audience is correct. A flow with nobody selected differs from one available to all eligible clients.

Home placement: where does it appear? In Create > Coaching flows > the flow > Settings, On the homepage offers Dynamic section, Reflection widget or Both, alongside the compatibility option. The chosen surface must also be enabled in Client Dashboard. Choosing Reflection does not itself turn its widget on.

Display: when can the client see the entry? Available all day is a display choice, not a command to send reminders every day. Automatic opening is another choice. A visible card should not be confused with a delivered email.

Reminder schedule and channels: when should an eligible reminder be attempted, and through which supported routes? Current recurring delivery supports app, push, email and applicable WhatsApp settings; availability, preferences and delivery requirements still apply. Do not promise recurring client SMS based on the separate coach-alert SMS option.

Completion limits: what prevents another run? Show once a day is a daily completion rule. It is not a once-per-week rule simply because a custom flow's reminder is scheduled weekly. Built-in weekly reflections have their own configured cycle behavior.

Coach completion alerts: who is notified when a response is saved? Settings > Notifications > Coach completion alerts is separate from client reminder channels. Turning it off suppresses that flow's shared completion notifier, not the response history, independently configured automations or explicit sends. Turning App off can also remove the Home entry; do not use that as a substitute for muting coach alerts.

A reminder and a saved answer are different events. A save is also different from review, and review is different from a client receiving an answer. Give each an owner and do not use one state as evidence for all the others.

Configure one fictional pilot

Evan is an invented coach working with six existing clients: Zora, Rafi, Imani, Leo, Bea and Uma. They agree to a two-update pilot alongside their existing coaching services. The updates concern their own selected work practices, not an employer report. No sponsor receives responses.

Evan creates a dedicated custom reflection with the three questions above. He selects only those six clients, sets explicit Tuesday reminders at 17:00 in each client's timezone, keeps App and Email on, and turns Push and WhatsApp off for this pilot. He selects Reflection widget, enables that Home section and leaves automatic opening off. Display is available all day so late replies have an accessible route. Show once a day is on; he explains that this custom flow can still receive a new run on another day.

This is a custom flow with a weekly reminder, not a claim that it inherits the built-in weekly flow's period rules. Evan records each intended client-week in a separate pilot review register and checks extra responses against that register. He does not market it as an automated weekly deduplication feature.

Coach completion alerts are off for this flow. Evan will inspect the response view in his reserved review windows, rather than depend on alerts as his work queue. No answer-driven task assignment, public celebration, client escalation or extra message automation is enabled.

The two reminders are intended for 17 and 24 November 2026. Five clients use Europe/London; Rafi uses America/New_York. On those dates 17:00 New York is 22:00 London. The review cutoff is Wednesday at noon London time, leaving Rafi time to respond after his own reminder. The deadline is a service arrangement they agree, not a timezone conversion performed by a motivational score.

The exact participation and reply promise

“Brief notes are enough. Share only information appropriate for our coaching audience. Submit each update by Wednesday noon Europe/London if you want that week's written review. I read them Wednesday afternoon and send one reply through our private Coachful Direct conversation by Thursday noon. One short clarification received by Friday noon is answered by the following Monday noon. Later updates go to your next already agreed session, unless we separately agree another route. This is not an urgent-support channel. The second round's last clarification cutoff is Friday 27 November; its final reply is due Monday 30 November at noon.”

All six choose to participate after seeing that arrangement. An optional update can be left incomplete. Evan will not treat absence as permission to pursue someone through other channels or disclose that person's situation.

Test the whole route before the first reminder

1. Preview the three questions for wording and unnecessary information. Preview alone does not submit a client's response.
2. Use an authorized client account for the actual audience and Home check. Staff access does not prove the client's access.
3. Check the saved display choice, enabled Home surface and explicit reminder schedule separately.
4. Check that the response is saved and visible to the intended coach through the client's Coaching flows response or reflections view.
5. Send and open a permitted test reply through the actual Direct route. A private review note is not that reply.
6. Check completion behavior and how to identify another run without counting it as another client.

In the fictional setup on 10 November, Zora can open a permitted direct flow link but cannot find it on Home. Evan discovers that he selected Reflection without enabling the workspace widget. He enables the intended surface, and Zora then opens the same flow from Home. The correction does not widen the six-person audience. They do not make the flow public to solve a placement problem.

For a missing reminder, inspect schedule, timezone, channels, completion and eligibility before guessing. The released custom-flow reminder checks a completion for that flow on the client's current day; completing a custom flow on a different day is not the same as completing a built-in weekly cycle. Do not promise suppression based on a different flow or an assumed calendar week.

Troubleshoot the state that actually failed

If the client cannot see the flow, inspect the selected audience, enabled flow, applicable access and enabled Home surface first. Do not change a private audience to all clients just to make an entry appear. A working staff preview cannot settle the client-access question.

If the entry works but a reminder is missing, check the explicit days and time, the client's timezone, selected channels and relevant preferences. A custom flow with no explicitly saved reminder schedule is different from a built-in flow using its defaults. Also check whether that same custom flow was already completed that day. Eligibility and a dispatch record still do not prove inbox receipt or reading.

If a client reports completing the flow, inspect the actual saved session before asking them to repeat personal material. Answers left in an open, unfinished flow are different from a confirmed final save. Explain any retry without promising recovery after an unsaved window has been closed.

If the response is present but Evan did not answer, inspect his actual review and reply commitment. Resending reminders to the client does not repair the coach's missed work. If alerts are muted, the reserved manual review is still required. A reply sent through Direct should be checked as that communication, not inferred from a completion badge.

Follow Zora’s update into an actual decision

Zora is a consultant trying to prepare proposal outlines before promising deadlines. Her 17 November update refers to the preceding work period: two thirty-minute preparation blocks were scheduled on 10 and 12 November. One produced an outline; an urgent client call displaced the other.

Evan opens the saved update on 18 November and sends this reply on 19 November at 09:00:

“Your record shows one completed block and one displaced block, not no preparation. Which choice is yours, and which requires your manager's authority? A possible next action is to request a specific tradeoff before the next block. Please choose whether that fits; scheduling another block alone would not settle the conflict.”

Zora reads and chooses a thirty-minute block for Friday 20 November. At 10:00 on 19 November she asks manager Faye through the organization's work chat: “Can I protect Friday's 10:00–10:30 preparation block? If an urgent call competes, will you decide what moves and agree a replacement time?” Faye accepts at 11:00, with the condition that an urgent call still needs her priority decision.

Zora uses her included clarification on Friday 20 November to report the accepted condition through her private Direct conversation with Evan. He replies on Monday 23 November before noon, confirming that the task concerns the agreed block and priority decision, not authority to reject every urgent request. He deliberately updates that chosen task. The check-in has not automatically obtained Faye’s agreement.

The next update exposes a partial failure

For the second period, Zora planned blocks on 16 and 20 November. The first lasted thirty minutes and produced an outline. On 20 November Faye prioritizes an urgent call halfway through the second. Only fifteen minutes of preparation occurs, and they do not agree the promised replacement time then.

On 24 November Zora initially writes “I kept both blocks.” On 25 November at 10:00 she submits another run clarifying the fifteen-minute interruption. Show once a day did not block a run on a different day. Evan retains both records, links them to the same client-week and uses the clarification rather than silently overwriting the earlier account.

His 26 November reply distinguishes one full block, one partial block and an unfulfilled replacement agreement. Zora asks Faye for that replacement through work chat. On 26 November Faye accepts Monday 30 November at 14:00. That is future work when agreed.

On Friday 27 November Zora asks Evan whether the future replacement makes the previous period “two completed blocks.” He replies on Monday 30 November at 10:00: “No. Keep one full and one partial block in that period. Record the newly agreed replacement separately and review what actually happens afterward.” Zora reads and acknowledges the distinction that morning. At the pilot cutoff, the 14:00 replacement has not occurred.

The check-in has supported a clearer request, an accepted arrangement and a more accurate review. It has also exposed the arrangement's incomplete implementation. It has not demonstrated increased overall productivity, a protected calendar forever or a causal effect of reminders.

Reconcile records, people and opportunities separately

Each of six participating clients has two intended client-week opportunities, giving twelve. These are participation opportunities, not twelve verified email deliveries.

Ten of twelve client-weeks eventually have an update, or 83.3% rounded to one decimal. Nine are timely, or 75%. Eleven saved records are not eleven responding clients or eleven completed client-weeks. Five distinct clients respond at least once; Leo supplies neither update. None of these numbers measures progress toward six different goals.

Evan follows the agreed fallback for Uma's late response: they review it during her already scheduled 30 November session. He makes no earlier written-review promise for it. In his one neutral administrative message about missing updates, he asks Leo whether the route and timing remain useful. Leo replies that he chose not to log these two weeks and wants to discuss it at their next existing session. That future discussion and Leo's actual goal progress remain unobserved.

The CDC's evidence-gathering guidance recommends aligning indicators and sources with the evaluation question. Here, submission timeliness answers a process question. Zora's examples address a specific work practice. Neither supplies a controlled estimate of a business outcome.

Count the whole pilot before expanding

Evan reserved two sixty-minute review blocks, 120 minutes in total, intended to include routine review, replies and closure. His actual pilot work through 1 December is:

The review-and-close work exceeds its 120-minute allowance by ten minutes. Including setup gives three hours twenty-five minutes. Uma's ten minutes occur within an existing session and are allocated here once to pilot feedback; they are not ten additional minutes added to that whole session. Other session work and clients' own practice time are outside this defined staff-work account.

At Monday's noon support cutoff, all included clarifications are answered. Evan disables this dedicated pilot flow's future scheduled delivery on 30 November, before the next Tuesday reminder. That does not delete saved responses, close accounts or silence independently configured flows or automations. On 1 December he reconciles the records and defers expanding the weekly offer until he can reserve adequate review capacity. This is a completed process decision, not a claimed saving over a measured prior system.

Use branching and follow-up automation for their actual jobs

A flow branch can route according to a current or earlier reachable answer; skipped paths supply no answers. It can display an invitation to bring a topic to a session. That is different from alerting a professional, assigning a task or sending an instant personal reply.

A separate App automation on Questionnaire completed can use a Form answer condition only when configured for the specific form and supported question. A coaching-flow answer is not interchangeable with that questionnaire submission. Keep a proposed rule inactive until its exact trigger, audience, conditions and action have been checked.

Evan enables no such downstream rule in this pilot. Human review determines the next conversation, and Faye's work decision still requires Faye's actual agreement. A difficult answer is not permission for an undisclosed intervention.

Frequently asked questions

Should every client receive a Friday check-in?

No. Agree a rhythm suited to the goal, access and actual review service. A convenient send time does not create capacity to answer before the weekend.

Does a weekly reminder make a custom flow weekly-only?

No. Reminder scheduling and completion limits differ. Show once a day is not once per week. Demonstrate the intended flow's actual behavior and define how extra runs will be reviewed.

What if a client says they already submitted?

Inspect saved flow responses, the correct client and period before requesting repetition. A missing legacy summary is not proof that answers were lost. Do not promise recovery of an unfinished submission that was never saved.

Can these check-ins monitor an emergency?

Do not offer that function. State actual review windows and appropriate urgent-support arrangements. A scheduled reflection and an optional coach alert are not continuous monitoring.

Are personal journal and takeaway pages included?

Unshared pages are separate from deliberately submitted responses. Where an enabled Share with coach control is available, using it intentionally exposes that page to the coach team. Ask for the specific selected information needed for review.

Does pausing a program stop every reminder?

Not necessarily. Workspace access and other grants can keep workspace-wide flows applicable. Inspect the particular flow, membership, audience and independent deliveries rather than assume one program pause silences everything.

Explore Coachful's features with one complete client route and a realistic review plan before adding more check-ins.