Between-Session Check-in Cadence: Four Rules and Worked Examples

A between-session check-in cadence defines when a client sends an update, what it is for, and when the coach will respond. A useful arrangement fits the coaching goal, the client’s preferences, and the capacity included in the service.

The four rules below cover the communication route, timing, update format, and response window. They include four illustrative service arrangements, a capacity calculation, a complete agreement example, and a review process for changing the cadence.

Start with the purpose of contact

A check-in can help the client review an experiment, ask a scoped question, share relevant context, or request a topic for the next session. Agree which of those purposes the service supports. A general invitation to send anything at any time leaves both people guessing about the response.

Ask whether contact between sessions would be useful and accessible. Some clients prefer a brief written update; others use audio or want to save reflection for a live conversation. The amount of contact should reflect the work rather than a belief that more messages always mean better coaching.

ICF’s Code of Ethics provides professional context for clear agreements about the service and information-sharing. The cadences below are original planning examples. They are not research benchmarks or a promise that a particular day or frequency improves completion.

If the coaching goal changes, review the support arrangement too. A decision that depends on another person’s reply may need a different review point from a practice the client can repeat independently.

Four illustrative service arrangements

These examples describe service design, not automatic Coachful packages. Define volume, topics, response expectations, holidays, and what happens if demand exceeds the allowance. An executive retainer still needs a clear scope and an appropriate route for urgent needs outside coaching.

Rule 1: Agree a primary route and an accessible alternative

Choose a route that keeps the intended record organized and is practical for the client. Explain where to send the update and how the client will know which conversation it belongs to. Review access and notifications during onboarding rather than assume everyone can use the same device or format.

A primary route can reduce the work of checking several inboxes. If an alternative is needed for accessibility or a technical problem, define how you will handle it and preserve the necessary record. Check privacy and permission before moving personal information between systems.

Be explicit about the audience. A private client conversation and a program-wide channel can have different members. An update about a workplace or personal issue should go to the intended recipients only.

If a client sends an update elsewhere, acknowledge the practical issue and explain the agreed route. Avoid silently copying sensitive content into a shared channel or treating use of the wrong route as a judgment about commitment.

Rule 2: Put the review near the actual decision or practice

Choose timing with the client. Ask when an update could change what happens next. If the client is trying a meeting approach on Thursday, a Wednesday reminder may add little; a short reflection after the meeting may be more useful.

For a fortnightly service, one review point between calls might help. For a weekly service, an additional prompt may be unnecessary if the client already has a clear plan and prefers to reflect at the session. Start with a manageable arrangement and review its use.

An original prompt is: “What happened with the step you chose, what did you learn, and is there a question you want us to consider?” Allow “not attempted,” “no update needed,” or “the goal changed” to be informative answers.

Distinguish the client’s planned action date from a review date and the coach’s reply deadline. The client may send an update on Wednesday, the coach may reply on Thursday, and the underlying decision may remain open until an external answer arrives.

Rule 3: Agree a useful, flexible update format

A short structure helps the coach understand the request. Invite the client to cover what happened, what they make of it, and what support they want. A message can also simply ask to bring a topic to the next call.

Choose a reasonable size for the actual service. For example, a client might aim for a few sentences or an audio note of roughly three minutes, with an alternative when the subject or access need requires it. Agree how you will handle a larger issue before it arrives.

An original fictional update from Ren reads: “I tried the decision summary in two meetings. It helped us name an owner, but the larger meeting has a different chair. I plan to ask that chair whether a summary would fit. Please help me check the wording; I am not asking you to decide whether I should raise it.”

The coach can respond to the actual request: clarify one ambiguity in the draft, ask whether the message reflects Ren’s intention, and leave the decision with Ren. A complex or sensitive matter may need a scheduled conversation or a different professional route.

Rule 4: Define response windows in plain language

State the working days, time zone, cutoff, and the meaning of a response deadline. “Within twenty-four business hours” can mean different things to different people. A concrete example makes the agreement easier to use.

The following is an original fictional service rule: “Working days are Monday to Friday, 9:00–17:00 Europe/Amsterdam, excluding closure dates we agree in advance. A message received before 17:00 is treated as received that working day. A message received at or after 17:00, or on a nonworking day, is treated as received the next working day. I reply by 17:00 on the following working day.”

This rule defines a deadline, not continuous monitoring or a promise that every question will be resolved in the first response. Explain how an absence, unexpected disruption, or need for a longer conversation will be handled.

Keep the support route appropriate to its purpose. Clients need to understand that an ordinary coaching inbox does not provide emergency monitoring, clinical crisis care, or immediate workplace intervention. Agree suitable alternatives for needs outside the service.

Worked response-window examples

All times are Europe/Amsterdam and these examples assume no agreed closure dates. If you offer a different rule, write examples for it. An exception should be explicitly agreed and feasible to provide.

Check whether the promise fits your capacity

Count the time needed for reading or listening, thinking, replying, and recording relevant decisions. Include administration, difficult weeks, leave, and the effect of several clients sending updates at once.

In this fictional example, ten clients each send two updates per week. At an average of six minutes per update including the reply and necessary record, that is 10 × 2 × 6 = 120 minutes. Two fifteen-minute triage blocks add thirty minutes, bringing the scheduled weekly work to 150 minutes, or two and a half hours.

The coach reserves another thirty minutes for variability, bringing the allowance to three hours. This is a planning estimate; actual updates may take longer. Track the real time and review whether the scope, roster, or price is sustainable.

Describe the allowance accurately in the offer. If there is a volume limit, explain it before purchase. If requests exceed the agreement, discuss prioritizing, scheduling a conversation, or changing the service with clear terms. Avoid a vague promise of unlimited attention.

A complete fictional check-in agreement

Purpose: Ren will use one optional update between the fortnightly sessions to reflect on a chosen communication experiment and request one scoped question for review.

Route and audience: Ren sends it in the agreed private client conversation. If the route is inaccessible, Ren and the coach agree an alternative before sharing personal details.

Format and timing: A few sentences or a short audio note covering the attempt, learning, and requested support. Ren plans to send it after Thursday’s meeting when there is something useful to review.

Response: The coach uses the working-day rule above. The reply may address the scoped question or propose a conversation when the issue needs more time.

Limits: The arrangement includes one update and response per fortnight. It is not continuously monitored. Matters outside coaching need an appropriate alternative route.

Review: At the next session they ask whether the update was useful, manageable, and correctly scoped. Ren may change the format or choose to use session time instead.

Review silence, extra messages, and a changing goal

If a client does not use the check-in, ask whether the timing, format, access, or purpose worked. A missing message does not tell you whether the action happened. The client may have completed it, changed direction, or preferred to discuss it live.

If several messages arrive, look first at the content and actual support agreement. Confirm the question that needs attention and explain the response window. A routine topic can be brought to the next session by agreement; an urgent concern needs an appropriate response within competence and obligations.

Review the arrangement after a useful trial period. Ask what helped, what added work, and which part to keep or change. The missed-homework review guide offers a practical way to examine dependencies and changed goals without guessing at motivation.

Set up the practical workflow in Coachful

Confirm the intended client conversation and audience, then review the actual notification, scheduling, and access controls you plan to use. Office-hour wording in an agreement does not itself enforce a technical reply window.

For audio, recording or uploading a clip is separate from sending it. Review the preview and use Send to post, or Schedule where that control is available to queue the selected time. A queued message is not proof that the client has read it.

Choose tasks and habits that match what is being tracked. Three relevant meetings across two days are three opportunities, not three separate habit days. Use a suitable task or reflection record for an event-based experiment.

The follow-up email guide gives complete wording for agreed contact. Explore Coachful’s coaching features for organizing client messages, records, and selected follow-through.

Frequently asked questions

How often should coaches check in between sessions?

Agree a cadence according to purpose, preference, and capacity. One relevant review point may help; some services need more contact, and some clients prefer to use live session time.

Should Wednesday always be the check-in day?

Choose a time when the update could be useful. The client’s actual practice, decision, or external dependency matters more than a fixed weekday.

Can I include asynchronous support in a package?

Yes, when its purpose, volume, response window, and limits are clear and feasible. Price the real work into the service rather than promise an undefined allowance.

Can asynchronous coaching replace live calls?

It can be a service format when it fits the client, purpose, access needs, and scope. Agree its limits and how to handle an issue that needs a different conversation or professional response.

What if a client never sends an update?

Check whether the arrangement is useful and accessible. Discuss the action separately from the message, then agree whether to change or stop the check-in.

A sustainable cadence makes the purpose, record, timing, and responsibilities clear. Review it against actual usefulness and workload as the engagement develops.

Primary professional context: ICF Code of Ethics for clear agreements and information-sharing. The schedules, response-window rule, calculation, update, and agreement above are original illustrative material.