Asynchronous Group Coaching Framework: Prompts to Review

An asynchronous group coaching framework connects shared material, individual reflection, peer exchange and coach attention without requiring everyone to meet at the same time. The central design question is what happens between contributions: who reads, who responds, what the person can revise and when the service ends.

A library of videos is not automatically group coaching. Nor is a busy discussion feed evidence that members are receiving useful coaching attention. State which parts are education, optional peer conversation and an included response from the coach.

This guide develops an original four-cycle model with a complete fictional participant case, a response timetable and an actual workload review. For choosing themes across a longer engagement, see the group coaching curriculum guide.

Define the exchange before choosing the platform

Start with a purpose people can work on in small pieces. “Prepare a clearer request and examine what happens” is easier to support asynchronously than promising to transform every aspect of someone’s leadership. Members can have different workplace situations while examining a related question.

The group element should add something useful: another interpretation, a clarifying question or an example of how a different constraint changes the options. It should not require a member to expose a confidential incident so everyone else has something interesting to discuss.

Make feedback informative rather than merely frequent

Wisniewski, Zierer and Hattie’s 2020 meta-analysis of educational feedback covered 435 studies and more than 61,000 learners. It reported an average effect of d = .48 after excluding 35 extreme effect sizes, with substantial variation and an important role for the information conveyed. This is education research, not a trial of the coaching program described here.

It offers a reason to examine the content of a reply rather than count comments alone. “Great work” and “Which decision can the receiving person actually make?” do different jobs. The former may acknowledge effort; the latter can help someone inspect a missing part of a request. Neither guarantees a workplace result.

Use a simple response sequence: describe what you understood, ask about the consequential uncertainty and let the member choose a revision. Avoid rewriting every draft into the coach’s preferred voice. The learner needs to understand why a change matters and retain responsibility for using it.

Choose a problem that can wait for the response

Ask whether the member can make useful progress while another person is offline. Comparing a draft with stated criteria often fits. Resolving a live operational incident, obtaining specialist legal advice or getting an immediate decision from an employer does not become suitable because the group has a discussion space.

Consider the cost of delay alongside convenience. A participant with one short period of reliable access may need material available earlier. Someone who communicates more easily through another medium may need an agreed alternative. Check the actual person and task; avoiding a meeting removes one scheduling demand while adding reading, writing and self-organization.

Keep those choices separate from individual attention. A shared explanation may serve everyone, while each draft still takes time to read. Adding a private route protects a different audience but does not remove its response workload. If the promised service does not fit the available capacity, narrow the scope or offer a different arrangement before enrolling the group.

Set a timetable that includes the final reply

Asynchronous does not mean immediate or deadline-free. Publish dates in a named timezone, give people time to read and respond, and check the intended members can use the window. A global cohort may need different windows from a group working similar hours.

Instructions should name the task, destination, audience and response. The W3C WAI writing guidance recommends meaningful structure, clear instructions, understandable content and appropriate multimedia alternatives. A short text prompt can make an async task easier to navigate than essential instructions available only in a recording.

Decide what happens when someone cannot meet a deadline. A limited agreed extension may fit; unlimited rolling submissions may not. Specify the new submission and reply dates when making an exception. Otherwise a small accommodation can become an indefinite support promise.

A weekly prompt ready to adapt

“Choose one request you are considering, or use a fictional situation. In up to 180 words, say what you want, who can decide, what you know about their capacity and which uncertainty you want help examining. Post beneath this week’s prompt if you want the cohort to read it, or send it through our agreed Direct conversation for the private feedback round. Say whether you welcome peer questions. Do not include identifying third-party details. Use the published submission and reply dates; ask through Direct if you need to discuss an exception.”

Add the actual dates and named coaching audience when using this text. The private feedback audience needs to match the real staff permissions; if an authorized support team can read the conversation, explain that before submission. A short prompt should not conceal a broader audience.

Worked pilot: four cycles of clearer requests

All names, dates, work records and outcomes in this case are fictional. Ari owns the coaching workspace and coaches five members: Tala, Mia, Noel, Uma and Sid. They choose a text-based group with no live meetings. Each wants to prepare clearer workplace requests; they are not a team making one shared business decision.

The four prompts appear on Mondays 2, 9, 16 and 23 November 2026. Each member receives up to four individual coach-feedback rounds, one per cycle. Each round covers one draft of up to 180 words and one clarification of up to 60 words. It does not include reviewing full documents, a private call or ongoing advice to a member’s employer.

The shared route is a dedicated Coachful custom community channel. Its audience is the five participants and authorized workspace staff. Ari starts the weekly prompt posts; participants reply beneath the relevant post. Peer comments are optional, and a member states whether they welcome them. For a personal concern, administrative issue or a draft they do not want peers to read, the named private route is their Direct conversation with Ari. Coach replies return through that same chosen route.

The timetable is agreed before the pilot begins. London time applies to every listed deadline; all these dates fall after the October clock change.

The closing review is on 1 December. Coaching responses end at 17:00 that day. On 2 December at 09:00, new participant posts and replies stop; members can still read and react. Reference access continues until 15 December at 09:00, when Ari will remove their channel membership and check the result. These are service commitments and manual administrative actions, not an assumed automatic program expiry.

Cycle 1: choose a question with enough context

The first prompt asks members to select one request they could appropriately examine. They can use a fictional situation instead of workplace details. The submission identifies the purpose, receiving role, decision needed and one uncertainty. Names of customers, colleagues and employers are unnecessary.

Tala chooses asking a colleague to help with client-start preparation. Her first question is how to stop doing all the work herself. Ari asks which part she can actually offer someone else and what authority she holds. Tala identifies checklist drafting, while retaining responsibility for client commitments. She records that distinction for her next draft without sending a first-cycle clarification. The exchange narrows the question without claiming a delegation has occurred.

All five members submit a first-cycle draft and receive their included reply. Ari keeps the distinction between membership, a submitted draft and an action taken outside the program. A reply in the channel proves none of the latter by itself.

Cycle 2: show the actual draft and response

The second prompt asks for a short request, with the kind of feedback the member wants. Tala submits on 11 November before noon and welcomes questions from peers.

Tala’s initial draft: “Can you take over client starts so I can focus on strategy? Use your judgment about what needs doing.”

Mia’s permitted peer question: “Does taking over include promising the start date, or only preparing the information?”

Ari’s reply on 12 November: “You described wanting help with checklist drafting while retaining responsibility for client commitments. Your draft now asks someone to take over a wider activity. Which exact output are you requesting, and how will you find out whether the person has time?”

Tala uses her clarification on 13 November to ask whether stating her retained responsibility would make the request too controlling. Ari replies on 16 November that she can distinguish a real authority limit from dictating every step, then asks which choice the colleague should genuinely have. Tala reads the reply and writes this revision:

“Would you be willing to draft the checklists for two standard client starts this week using our existing templates? I will review them before any commitment goes to a client. Do you have 90 minutes available? If not, please say so and we can look at another arrangement.”

The revision names work and capacity while preserving a refusal. It does not establish that the colleague accepts, that the estimate is accurate or that Tala can release other work without her manager’s agreement.

Repair an unwanted judgment within the group

Noel also replies to Tala’s initial draft, saying she lacks confidence and needs to stop being controlling. That judges her character and supplies advice beyond her invitation for questions. Ari contacts Noel through Direct, names the difference and asks him to withdraw the judgment.

Noel edits his comment to a factual question about who can approve a client commitment. Ari privately asks Tala what she wants to happen next. Tala says she does not want further peer comments on her draft. Ari acknowledges the choice and states that boundary in the thread without repeating her private account. The members stop commenting there; coach feedback continues.

Ari checks again the following week. Tala says the revised question is usable but the original judgment made her uncomfortable. She keeps peer comments closed. There is no claim that an apology or smaller group guarantees safety. Ari counts both the intervention and the later check as moderation work.

Handle the one actual late submission explicitly

Sid asks through Direct on 11 November at 10:00 for an extension to his second-cycle draft. Ari agrees a revised deadline of 12 November at noon, an initial reply by 13 November at 17:00, one clarification by 16 November at noon and a final reply by 17 November at 17:00. Sid accepts those dates and submits on 12 November at 11:20.

Ari completes the initial reply on 13 November. Sid sends his clarification on 16 November and receives the final reply on 17 November. That work crosses into the third calendar week and remains part of his second-cycle entitlement. It does not create a fifth feedback round or change everyone else’s timetable.

Cycles 3 and 4: preserve the refusal and the real change

On 18 November, Tala sends her revised request to a colleague through their ordinary work email. The colleague declines on 19 November because there is no time available. Tala had hoped clearer wording would secure agreement; the result challenges that expectation. The person’s capacity remains a real constraint.

Tala accepts the refusal. She keeps the two checklists and asks her manager whether an optional brochure update can be deferred. Her manager agrees that day to defer the update, releasing the 90-minute work slot Tala had allocated to it. This is an accepted change within the fictional case, not an instruction from Ari to reassign company priorities.

In the fourth-cycle draft on 25 November, Tala writes that she “successfully delegated the starts.” Ari responds on 26 November that the stated events show a declined request and an agreed change to another priority. Tala agrees, uses her 27 November clarification to correct the account, and receives Ari’s final reply on 30 November.

Tala’s corrected review: “I made a narrower request and asked about capacity. My colleague declined, and I accepted that. I kept the checklists and obtained agreement to defer the brochure update. I did not delegate the client starts. I still need to learn whether the time estimate was realistic.”

Tala acknowledges the final reply on 30 November. Completion of the two checklists is not observed in this account. The coaching output is clearer discrimination between a request, an agreement and a business result, alongside one actual resource decision.

Reconcile participation and the whole service workload

Five members have four included round opportunities each, giving 20 possible drafts. The pilot receives 19: five in cycle 1, five in cycle 2 including Sid’s agreed late submission, four in cycle 3 and five in cycle 4. Uma chooses not to submit her third-cycle work and uses her own private reflection instead. There is no coach reply claimed for that unsubmitted draft.

Ari completes 19 feedback rounds, including three actual clarification exchanges across the cohort. Round opportunities, drafts, replies and people are different denominators. Nineteen reviewed drafts do not mean nineteen clients or nineteen successful workplace actions.

The original planning allowance is 130 minutes per active week: 30 for prompt preparation, 30 for three moderation visits, 20 for administration and 50 for reading and feedback work occurring during that calendar week. This allows an estimated ten active-week minutes per member, with the final reply tail budgeted separately. It is not a timer after which a promised reply is abandoned.

Four weeks require 520 planned minutes. Setup and enrollment add 90; final replies after the fourth week add 20; the closing review and 2 December posting change add 30; the 15 December access check adds 15. The service plan therefore reserves 675 minutes plus 25 contingency minutes, for a 700-minute ceiling. It does not stop counting work on the last Friday.

These are actual work dates, not all the time assigned to a cycle’s submission date. The third week includes Sid’s remaining second-cycle response. The active weeks total 545 minutes. Setup, completed before 2 November, is actually 90 minutes. The final reply tail on 30 November is 18; the closing review on 1 December is 20; the posting change on 2 December is 10; and access administration on 15 December is 15. Whole observed coach work through closing access is 698 minutes, leaving two of the 700 minutes unused.

The whole-service result conceals a peak failure. Ari also set a 160-minute weekly allowance, and the second week used 163. Concern handling and fuller replies mattered. Spare minutes in another week did not create capacity on the day a response was due.

Ari keeps the next proposed cohort at five rather than accepting a sixth place. Adding an estimated ten-minute round in each cycle and four more tail minutes would add 44 minutes to the 675-minute base, reaching 719 before contingency. That estimate does not fit the same ceiling. It is a forecast about this service, not a universal maximum cohort size.

Build the actual routes and ending in Coachful

Coachful is our #1 recommendation for coordinating this model. This is our editorial recommendation as its publisher. The relevant Coachful features are a scoped community channel, distinct posting and replying controls, Direct conversations and deliberately assigned resources.

1. Choose the actual audience. In Community settings, use a custom channel with Selected members for the intended people. A program or resource audience can admit other eligible people, and an Offer can separately grant channel access. Ari’s dedicated channel has only the five direct members and authorized staff; no Program, resource audience or Offer grant also admits them.
2. Set who starts and answers posts. Community > settings gear > Feed and channels provides separate Who can post and Who can reply controls for custom channels. Ari saves Only you and your team for new posts and Everyone in this channel for replies during delivery. No separate channel chat is enabled. This is not a setting assumed to apply to Program communities.
3. Keep the private route separate. Use All messages > Direct for the named personal concern or private draft. Ari reads and replies there within the stated round or administrative arrangement. A community post is visible to its channel audience, not just the coach.
4. Deliver the closing reflection deliberately. Ari assigns an original review through Clients > the client > Worksheets & resources > Assign. Four members return it; one does not. Ari reviews the four and records the missing response without inventing it. That review uses 20 of the 30 closing minutes; the other ten cover the following day’s posting change.
5. Complete the promised access transition. On 2 December, Ari saves team-only posting and replying, then checks that participants can still read and react but cannot start posts or add replies. On 15 December, Ari removes the five people while keeping Selected members, with no program or resource audiences and no other channel grant. Each member subsequently confirms the channel is unavailable. Staff retain their permitted record, and the members’ workspace accounts remain open.

Those closing actions are fictional observed events, not claims that we configured a customer account. The individual closing worksheet has its separate access; removing this channel does not erase that resource, Direct history or the account. A shared page’s removal is also different from deleting the underlying professional record.

Protect useful choice without promising absolute confidentiality

The ICF Code of Ethics addresses agreements and information exchange for ICF professionals. Explain the actual group audience, staff roles and limits. Members can agree not to copy or repeat contributions, but the coach cannot guarantee another person will never do so.

The ICO’s data-minimisation guidance, currently under review following legislative changes, emphasizes collecting information relevant and necessary for its purpose. A useful coaching question rarely needs a pasted client file or identifying employee history.

Offer fictional cases and private alternatives. Unshared journal and takeaway pages stay private; an enabled Share with coach control allows the client intentionally to expose a page to the supported coaching audience. Personal writing should not be treated as a submitted feedback round unless the member actually uses an agreed submission route.

For quieter participants, examine access, timing, relevance and the experience of the group before adding reminders. Our group participation guide develops that conversation. Silence alone does not tell you which explanation is correct.

Frequently asked questions

Can an asynchronous group have no live calls?

Yes, if the purpose, members and service fit that format. State it before enrollment. Some needs may require another form of support, and text alone is not automatically accessible to everyone. Discuss actual requirements and alternatives rather than describing the absence of meetings as a universal benefit.

Does every member need to comment on a peer’s work?

No. Explain what is included and what participation you invite. Optional questions can add perspective, but compulsory advice or personal disclosure can undermine the purpose. Tala’s choice to close peer comments did not remove her included coach-feedback round.

How many people can one coach support?

Calculate the actual service, including concern handling, private routes, response deadlines and the ending. Ari’s whole pilot fitted its 700-minute ceiling while one week exceeded 160 minutes. That mixed result does not establish that another member can be added or that five is a universal limit.

What if a member misses a submission deadline?

Use the stated policy and discuss an exception when appropriate. Name all changed dates, including the final reply. Sid’s revised round crossed a calendar week but stayed one round. An extension does not silently create unlimited support or change everyone else’s deadlines.

Do I need private circles or buddy matching?

Only when they serve a clear purpose and can be supported. This pilot uses one cohort channel plus Direct, without smaller circles. Adding subgroups creates more audiences and moderation responsibilities. Do not treat smaller size as a guarantee of trust or an escape from the coach’s role.

What counts as evidence that the pilot helped?

Keep specific drafts, chosen revisions and actual events alongside the member’s account. Tala clarified her request, received a refusal and obtained agreement to defer different work. She did not complete a successful delegation. Participation counts and coach impressions do not replace that distinction.