Client Check-Ins
How to Run an Effective Client Check-In Every Time
A client check-in has a narrower job than a full coaching or discovery session: confirm progress, surface blockers, and reset commitments. Run well, it takes fifteen to twenty minutes. Run poorly, it either drags into a full session or skips past the one thing that actually needed attention.
Prepare before the call, not during it
The single biggest lever for a good check-in is opening with the prior session's action items already in front of you. If you have to ask "remind me what we agreed last time?", you've already spent a third of the call re-establishing context that should have taken ten seconds to pull up. This is the practical payoff of tracking client action items properly — the check-in agenda is almost written for you.
A simple four-part agenda
- Status on prior commitments. Go through last session's action items one by one: done, partial, or not started. Don't skip this even when it feels obvious — saying it out loud creates the accountability moment.
- What changed since then. New information, new obstacles, new priorities. This is often where the real conversation happens.
- Address the open question, if there is one. If the prior session ended with something unresolved, this is where you circle back to it deliberately rather than letting it drift. See capturing open questions for your next session for how to make sure this doesn't get lost between calls.
- New commitments. What's the client doing before next time, and what (if anything) are you doing?
This maps closely onto a compressed GROW cycle — reality (status), options (what changed, what's possible), will (new commitments) — without needing the full session-length version. See using the GROW model for session notes if you want the longer-form version of this structure.
Keep it short on purpose
A check-in that runs long usually means either the agenda wasn't followed, or something surfaced that actually deserves a full session. Both are fine outcomes — but name it explicitly ("this sounds like it needs more time than we have today — let's put it on the agenda for our next full session") rather than letting the check-in quietly become a different kind of meeting without anyone deciding that on purpose.
What to write down during a check-in
Given the short format, notes should be even leaner than usual:
- Status of each prior action item (one word: done / partial / stalled)
- Any new blocker mentioned
- New action items, with owner and date
- Anything that got flagged as needing a full session later
Check-ins compound. A weak check-in doesn't just waste fifteen minutes — it means the next check-in starts from a worse baseline, because nobody actually confirmed what happened since the last one. Treat the status review as non-negotiable, even when you're confident you already know the answer.
When to retire a check-in cadence
If three check-ins in a row produce no new information and no new commitments, that's a signal — either the cadence is too frequent for where the client is right now, or the check-in format itself isn't surfacing what actually matters to them. Worth naming directly with the client rather than continuing to run a meeting that's stopped earning its slot on the calendar.
Check-ins by phone or async, not just by video
Not every check-in needs a video call. A well-structured async check-in — a short written status update from the client against last session's commitments, with a quick written reply from you — can cover the same four-part agenda in less time for both parties, especially for clients who are otherwise on track and don't need much discussion. Reserve live check-ins for situations where a blocker needs actual conversation to work through, and use async updates when the main job is simply confirming status and resetting the next commitment.
Setting expectations about check-in scope upfront
Clients sometimes arrive at a scheduled fifteen-minute check-in wanting to use the full time for a new, unrelated topic. That's a fine thing to accommodate, but it's worth naming explicitly in the moment ("sounds like this is actually a bigger topic than a quick check-in — want to use today's time for it, or should we schedule a fuller session?") so the shift is a deliberate choice rather than an accidental scope change that leaves the original check-in items unaddressed.
Recording check-ins the same way as full sessions
Even a fifteen-minute check-in deserves a note, however brief. Skipping notes on "just a quick check-in" is one of the more common ways action item status silently goes untracked — three check-ins later, nobody remembers whether an item from the first one was ever actually resolved.
Rescheduling and cancellations
A check-in that gets rescheduled or skipped shouldn't just disappear from the record. Note it briefly — "check-in postponed to next week, client traveling" — so that when you look back at the client's history later, a gap in the timeline has an explanation attached rather than reading as an unexplained silence in the relationship.
Check-ins as a diagnostic, not just a status update
A well-run check-in often tells you more about how a client is really doing than they'd volunteer unprompted. Someone who's normally prepared and specific but shows up vague and unfocused for two check-ins in a row is signaling something, even if they don't name it directly. Treating the check-in format itself as a small diagnostic tool — not just a box to tick — is part of what makes a short fifteen-minute conversation genuinely useful rather than purely administrative.
A good check-in still needs a clean record afterward. SessionScribe turns the call into a structured note and follow-up email in about a minute, so the admin never eats into time you could spend preparing for the next one.