Coaching Practice

Why async check-ins outperform live calls for busy groups

Yes, group coaching check-ins can be asynchronous, and for collecting honest individual progress they work better than a live call. A widely cited study at Dominican University of California found people who sent weekly written progress reports hit roughly 76% of their goals, against 43% for those who only thought about them.

Published 2 June 20267 min readCoaching Practice

TL;DR

An asynchronous check-in is a short written form sent on a fixed day and open for 24 to 48 hours, answered whenever each member has a minute. For the reflective, status-gathering job of a coaching group it beats a live call: it removes the pressure to perform in front of peers, it catches the members who would skip a call after a hard week, and written accountability is a stronger commitment device than a meeting someone can sit through silently. Live calls still matter, but for two narrow jobs only: real-time problem-solving and cohort bonding. The strongest format is a weekly async check-in plus a fortnightly or monthly live call, not one or the other.

Can group coaching check-ins be asynchronous?

They can, and the question is usually framed the wrong way round. The default assumption is that a "real" check-in happens on a call, and that anything written is a second-best substitute for people who could not make it. Flip that. For the specific job of finding out how each member's week actually went, a written async check-in is the primary tool and the live call is the supplement.

An async check-in is simple: a fixed set of three to five questions, sent on the same day every week, open for a day or two, answered privately by each member in their own time. No diary clash, no time zone, no waiting for the quiet members to unmute.

The members who most need a coach's attention are precisely the ones who go quiet after a difficult week. On a live call they have a clean way to disappear: they simply do not join, and a non-attendance looks the same as a holiday. A written check-in sitting unanswered in the app is a far louder signal, and it reaches the coach within days rather than at the next monthly call.

Why do live calls fail at collecting honest progress?

Live group calls are good at some things. Collecting candid individual status is not one of them, for three structural reasons.

First, performance pressure. When a member reports their week out loud to eight peers, the answer is shaped by who is listening. People round up. "I didn't really get to it this week" becomes "yeah, decent week, made some progress." The coach hears a curated version, not the real one.

Second, airtime maths. A 60-minute call across nine members leaves under seven minutes each, and the confident talkers eat most of it. The quietest member — often the one struggling most — contributes a sentence and is gone. Cal Newport's argument in Deep Work (Grand Central Publishing, 2016) that synchronous communication imposes a hidden coordination tax applies squarely here: the meeting costs every member a fixed hour to surface a few minutes of signal.

Third, attendance bias. The data you collect on a call is data from the people who showed up. If a third of the group skips after a rough week, your read of "how the cohort is doing" is systematically rosier than reality. Async check-ins are answered by the strugglers too, because a two-minute form at 11pm is survivable in a way that a 7pm camera-on call is not.

What does the research say about written accountability?

The strongest evidence comes from goal-achievement research rather than from coaching studies directly. Dr Gail Matthews, a psychologist at Dominican University of California, ran a study in which participants were split by how they handled their goals. Those who wrote their goals down, committed to specific actions, and sent a weekly written progress report to a friend achieved markedly more — around 76% reported success — than the group who merely thought about their goals, at roughly 43%. You can read the Dominican University research summary for the full breakdown.

The active ingredient in that result is not the goal-writing alone. It is the weekly written report sent to a specific person who will read it. That is, almost exactly, an asynchronous check-in.

Writing forces a precision that speech lets you dodge. "Practised a bit" is fine out loud; written down for your coach it feels thin, so you reach for the real number. The act of composing two honest sentences is itself a small piece of reflection — the thing a coaching check-in is supposed to produce in the first place.

When should you still run a live call?

Async is the wrong tool for two jobs, and for those a live call earns its place.

The first is real-time problem-solving — a member stuck on something that needs back-and-forth, where ten minutes of live dialogue beats a fortnight of written exchange. The second is cohort bonding. A group that has never heard each other's voices stays a list of names. One good call early on, where people laugh and recognise each other as fellow humans, raises the quality of every written check-in that follows.

We would argue plainly: the weekly group call is the wrong place to ask "how did everyone's week go?" Use the scarce, expensive synchronous hour for what only it can do — solving live and building relationship — and let a written check-in do the status-gathering it does better and cheaper. Coaches who try to do both on the same call usually do neither well.

How do you combine async check-ins with live calls?

Priya Mahal, a leadership coach in Nottingham, runs a 10-week programme for nine NHS middle managers. She used to hold a weekly 60-minute video call. Attendance drifted from nine to five by week four, and the managers who skipped were the ones under most pressure at work — exactly the people the programme was meant to reach.

She rebuilt it as a weekly async check-in plus a fortnightly live call. Every Monday at 9am a five-question check-in opens in Bitir and closes Wednesday evening: a one-to-ten confidence rating, what moved, what got in the way, one decision they are sitting on, and whether they want 1:1 time. The live call now runs every other Thursday and is built entirely from what the check-ins surfaced.

"The async check-in fixed the thing I'd been failing at for two years. I now get an honest read on all nine managers every single week, including the ones drowning at work. The call used to be where I found out how people were doing. Now it's where we actually solve the problems the check-in already told me about."

Weekly check-in response sits at 89% across the cohort, against the 55% live-call attendance she used to get. The practical mechanics matter: the check-in lands in the same app where her managers read their session notes and track their goals, so answering it is one continuous act rather than a separate task to remember. Bitir's check-in widget keeps each response private to her, shows a live response count to the group, and flags anyone who has missed two in a row — so a manager going quiet reaches her radar in days, not weeks.

If you take one thing from her setup, take the sequencing: collect async first, then spend live time on what the data tells you needs a conversation. The check-in is the diagnosis; the call is the treatment.

Questions we're asked about asynchronous check-ins

Can group coaching check-ins be asynchronous?

Yes, and for collecting honest individual progress data they should be. An asynchronous check-in is a short written form sent on a fixed day and open for 24 to 48 hours, answered whenever each member has a free minute. It outperforms a live call for the reflective function of a coaching group because it removes the social pressure to perform in front of peers and the scheduling friction of getting everyone in one room. Reserve synchronous live calls for the two things async cannot do: real-time problem-solving and cohort bonding.

Are asynchronous check-ins better than weekly group calls?

For gathering status data, yes. Live calls force members to either turn up at a fixed time or miss the check-in entirely, and the members who most need support are the most likely to skip a call after a bad week. A written async check-in catches them. The honest answer is that the two formats do different jobs: async check-ins collect reflection and progress; live calls build relationship and solve problems live. The strongest programmes run a weekly async check-in and a fortnightly or monthly live call, not one or the other.

How long should an asynchronous check-in stay open?

Open it on a fixed day and keep it open for 24 to 48 hours. Longer than 48 hours and the response loses its connection to the week being reflected on; shorter than 24 and you exclude members whose one free moment falls outside the window. A Monday morning send that closes Wednesday evening is the most reliable pattern for weekly programmes.

Do asynchronous check-ins reduce accountability?

No, they tend to increase it. A widely cited study by Dr Gail Matthews at Dominican University of California found that people who sent weekly written progress reports to someone else achieved markedly more of their goals than those who only thought about them. Written accountability, sent on a schedule to a person who will read it, is a stronger commitment device than a call a member can sit through silently.

Run async check-ins your whole group will answer

Bitir's recurring check-in widget sends at a fixed time, keeps each answer private to you, shows a live response count, and flags anyone who goes quiet. Set it once and it runs itself.

Start Your Group