Asynchronous Coaching with Loom Videos: Practical Workflow
Nour
Founder, Coachful
Asynchronous coaching with Loom videos lets the client watch a recording and respond later. A screen recording can help discuss an appropriate document, explain a visual or offer a focused reflection between appointments. Its value depends on the agreed question and follow-up, not on replacing every live conversation.
This guide develops four delivery pillars, a complete five-minute review example, sharing and caption checks, response-time examples and a realistic workload model. The templates and financial figures are original illustrations. The service needs clear scope and information arrangements on both Loom and the client-delivery platform.
We build Coachful. Coachful is our #1 recommendation for organizing the agreed client resources and follow-up around these recordings. This is our editorial workflow preference as its maker, not an independent comparison or evidence that a recorded service improves coaching outcomes. Loom's recording and viewing controls still need their own checks.
Choose the format for the actual question
| Format | Potential use | What to agree |
|---|---|---|
| Live conversation | The topic needs immediate clarification, dialogue or an appropriately scheduled discussion. | Purpose, timing, participants and any recording arrangements. |
| A recorded Loom link | A specific visual or example can be reviewed at different times. | Material, viewer permissions, accessible information and how questions return. |
| A recording organized through a suitable client workflow | The person needs an appropriate place to find the clip, context and agreed follow-up. | Permissions on both systems, record ownership and access over time. |
A recorded link can be sufficient for a small agreed task; it is not inherently unprofessional. A portal can help organize delivery, but it does not make the recording private or prove that the client understood it. A live conversation may remain the better choice for an uncertain or sensitive issue.
Build four delivery pillars
| Pillar | Practical decision |
|---|---|
| 1. A focused review | Agree one question, appropriate source material and the type of contribution the coach can competently make. |
| 2. Deliberate sharing | Choose the intended audience and verify both the recording’s permissions and the client resource’s permissions. |
| 3. Clear response boundaries | Define staffed time, volume, what a review includes and what happens when the work needs another format. |
| 4. A coherent hybrid cadence | Connect recorded work with suitable live reviews and client-chosen follow-up, without promising unlimited attention. |
A coaching question, a consultant’s recommendation and specialist legal or financial advice are different contributions. Make the role clear before reviewing a board paper, contract or transaction material. Being able to record a screen does not establish competence to advise on its contents.
Agree the client brief and material first
A useful brief identifies the question, the relevant version, what the client wants from the review and what they are authorized to share. Avoid collecting whole folders when a limited example will serve.
Here is an original fictional brief: “I am preparing a project-update slide. I want to make the decision request clearer, rather than ask you to approve the financial assumptions. The draft contains no customer or employee details. Please help me think about what the audience needs to understand before deciding.”
The coach can then confirm the permitted scope, review allowance and due time. A confusing document or missing information may require a clarification before recording. The client’s submission is not permission to reuse the material in marketing or another client’s program.
Use a five-minute review with four beats
| Beat | Example time | Purpose |
|---|---|---|
| Context and question | Minute 1 | State what the client asked and the limits of this review. |
| Relevant visual example | Minutes 2–3 | Show the specific passage or slide and describe what you notice. |
| Options and inquiry | Minute 4 | Offer a tentative perspective or useful options and invite the client’s thinking. |
| Client choice and review | Minute 5 | Explain how the client can respond and decide what, if anything, to try. |
The times total five minutes. This is a planning format rather than an optimal length. A shorter answer may be enough, and a longer topic may need a different scope. Do not stretch a simple question or compress specialist work to meet a recording target.
Record a complete three-part response
The following original script develops the four beats above into a three-part spoken structure. It continues the fictional project-update example. The exact words do not have to fill every second of the five-minute allowance.
| Part | Original script |
|---|---|
| Opening:0–1 minute | “You asked how to make the decision request clearer. I am looking at the version you shared, specifically the opening slide. I will discuss the communication structure, not verify the financial assumptions or make the decision for your organization.” |
| Review:1–4 minutes | “The slide names the project status, while the requested decision appears in the final paragraph. I wonder whether the audience will know what you need from them at the start. One option is to state the decision first; another is to open with the key constraint and then the request. A third is to separate an information update from the decision slide. Which would fit this audience and the actual approval process? What necessary context could be lost if you shorten the opening?” |
| Choice and follow-up:4–5 minutes | “Please check whether that account fits. If useful, you could choose one version to try with an appropriate reviewer. You can also disagree or identify context I missed. Use our agreed response route to tell me what you learned and whether another conversation would help.” |
The client remains responsible for their own choice within their role. No deadline, task or organizational decision is created by the coach’s recording alone. A specialist concern should be directed to the appropriate qualified person.
Capture only the appropriate screen content
Loom’s current desktop and browser recording options support screen, camera or combined capture, with platform-specific controls. On the Mac desktop app, the documented options include a display, an app window and a custom region. Choose the narrowest suitable capture rather than assume every platform offers identical controls.
Prepare the permitted version, close unrelated client material and check notifications, comments, hidden tabs and other visible information. A selected app window does not remove the need to review the resulting recording.
Record a short preview to check sound and legibility. If the camera bubble covers important content, move it or choose another format. A webcam image is optional where the actual communication and access needs are better served without it.
After recording, review the relevant clip before sharing. An accidental disclosure may require a different response from simply trimming a few seconds; assess the actual situation and appropriate responsibilities.
Set Loom permissions independently of portal access
Current Loom guidance distinguishes public link access, workspace access and restricted access. Anyone with the link can view a public-link recording without a Loom login. Restricted sharing is intended for the specific people added. Confirm the current control labels and actual settings in your account.
Loom’s specific-person sharing guidance says the viewer needs to sign in with the invited email. That can affect an external client’s experience, so clarify the route rather than promise frictionless access without an account.
A password is another access condition where available, not proof that only a named client can view. Check workspace rules, sharing defaults, comments, downloads, previews and the actual recipient list. A workspace-wide permission may be much broader than one coaching relationship.
An authenticated Coachful resource and a Loom recording have separate access settings. Adding a public Loom URL to a private page does not remove the recording’s public-link access. Match both audiences deliberately.
Do not loosen privacy merely to make an embed play
Loom’s general webpage-embedding instructions describe using a link accessible to anyone with that link. That may suit a public teaching resource. It is not a reason to make a confidential client review public.
For restricted material, use an appropriate authorized route and check the actual external viewer experience. A link that opens Loom with sign-in may be preferable to an embed that cannot meet the intended conditions. Do not assume native Coachful-to-Loom sign-in or an automatic private embed.
If downloading and rehosting is appropriate and permitted by the plan, role, rights and agreement, it creates another copy with its own access and retention responsibilities. Editing or deleting the original recording does not necessarily manage a separately uploaded copy.
The dedicated client portal guide develops delivery and audience decisions.
Make the information accessible and check captions
Describe important visual information in the narration and provide an appropriate text explanation. Accurate captions help people who cannot hear the audio. W3C’s explanation of prerecorded captions addresses synchronized audio content and its stated exception; captions alone do not explain a visual that the speaker never describes.
When a Loom transcript is available, captions are based on it. Correcting the transcript updates the captions, while disabling transcription removes the caption option described in Loom’s guidance. Check relevant names, dates, numbers and meaning before relying on automatic text.
A summary and an equivalent transcript serve different purposes. Ask what the client needs and confirm that the actual playback, text and permissions work for them. Translation and downloadable caption features can depend on account controls, role or plan; do not promise every option universally.
Define three response-time settings clearly
| Setting | A bounded example |
|---|---|
| 1. Staffed time | Monday–Friday,09:00–17:00 in America/New_York, excluding declared holidays and absence. |
| 2. Reply allowance | Eight staffed hours for a defined short review, or sixteen staffed hours for a larger agreed review. Explain which applies before submission. |
| 3. Volume and scope | For example, two defined reviews per calendar month, with an explicit rule for clarification and additional work. |
In this example, time outside the staffed window does not count. A Friday 16:00 submission with an eight-staffed-hour allowance is due Monday 16:00, assuming no holiday: one hour on Friday plus seven on Monday. With sixteen staffed hours, the due time is Tuesday 16:00.
A Friday 18:00 submission starts its clock Monday 09:00 and is due Monday 17:00 with the eight-hour allowance. These are defined clock examples, not a promise of twenty-four-calendar-hour access. A declared absence changes the applicable arrangement.
This service should not be advertised as an emergency hotline or instant decision clearance. A client with an immediate operational need must use the appropriate existing decision and support routes rather than depend on an asynchronous recording.
Repair a delivery failure without widening the audience
In this fictional November 2026 pilot, coach Arun and client Sel choose two short slide reviews and one forty-five-minute live review. They use the eight-staffed-hour clock above, with no declared closure on the dates used here. Sel authorizes a slide containing no customer or employee details. They choose restricted Loom access through Sel's nominated email, an external sign-in route and the agreed private email thread for questions. One ten-minute clarification is included for the month.
Sel submits on Friday 6 November at 16:00 New York time; usable delivery is due Monday 9 November at 16:00. Arun sends a restricted link at 15:30 but incorrectly says it will open inside the portal without further sign-in. At 16:00 Sel reports an access failure while using another email account. A sent link has not met the promised usable delivery.
Arun checks the selected recipient and corrects his instructions, without switching the recording to public or adding another person. He also catches a transcript error: the audio says a decision is needed, while one caption word says made. He corrects that word and checks the resulting caption. The extra work takes fifteen minutes: ten for access handling and five for the caption correction. It does not constitute a full security or accessibility audit.
He sends the corrected route at 16:30. Sel signs in using the invited address and opens it at 17:00, one hour after the deadline. Sel finishes the five-minute clip and accompanying explanation, then replies the next morning that the access promise was misleading. Sel also explains that the financial assumption must remain visible on the opening slide. There is no need to expose the recording to everyone to make it easier to play.
Receive a correction and keep the decision with the client
Arun uses the included ten-minute clarification block on 10 November to read Sel's response and send this answer:
I gave you the wrong expectation about sign-in, and usable access was late. I am sorry. The restricted recording requires the invited account; the portal does not remove that requirement.
Your explanation changes the slide options. Keep the necessary financial assumption visible. You could put the decision request beside it, or separate the status update while retaining both pieces of required context. I have not verified the assumption or approved the decision.
Please choose whether either option helps. We can review what your authorized project owner says at our live appointment; this recording cannot create their agreement.
Sel reads the answer on 11 November and chooses the side-by-side version. The project owner reads that version on 13 November but postpones the decision until an analysis is complete. The communication choice has been tried; approval and the business result remain unresolved. A view count alone could not have supplied this account.
Sel's second permitted question arrives Friday 20 November at 16:00. Arun's review is usable on Monday 23 November at 15:00, one hour before its deadline. They hold the agreed forty-five-minute review on 30 November and discuss both recordings, the access failure and the still-open project decision. Sel chooses to end the finite pilot. Arun sends their selected closing account and Sel confirms receipt that day; no further service is assumed.
The baseline workload below covers two thirty-minute reviews, forty-five live minutes, fifteen preparation minutes and fifteen administration minutes: 135. This pilot separately includes the ten-minute clarification, making 145 planned provider minutes. The fifteen-minute repair makes the actual account 160. The live review and close already sit in the call and administration blocks. Sel's and the employer's effort are outside this provider-only account, not free work or evidence of profit. The separate billing illustrations below are not this pilot's receipts.
Use four equipment checks and four production habits
| Equipment check | Practical aim |
|---|---|
| Camera or screen capture | Readable relevant content and a suitable view; an expensive camera is not automatically required. |
| Microphone and room | Clear sound in a reasonably quiet private setting, checked through playback. |
| Lighting | Comfortable visibility if the camera is used, without prescribing an expensive studio. |
| Background and workspace | A setting that protects privacy and avoids unnecessary distractions. |
| Production habit | Practical aim |
|---|---|
| 1. One clear question | State what the recording will help the person explore. |
| 2. A relevant visual where useful | Use an appropriate example and explain it; a diagram is not compulsory for every reply. |
| 3. Clear, concise speech | Make the content understandable and correct errors before sharing. |
| 4. A client-owned next step | Invite a choice and a suitable response rather than assign an unrequested directive. |
Production quality supports understanding. It does not create professional authority, guarantee emotional safety or make a client prefer recorded feedback over a live conversation.
Provide three follow-up reflection fields
| Original field | Purpose |
|---|---|
| What, if anything, was useful or unclear? | Let the client correct the coach’s understanding. |
| What would you like to do or explore next? | Keep the action or decision with the client and the actual authority involved. |
| When and how should we review it? | Agree a meaningful checkpoint within the service scope. |
These prompts can be used through a suitable form or conversation. Do not claim that watching a clip automatically creates them or converts a response into a task. Use the ordinary agreed plan workflow and respect response ownership. A recorded view does not prove attention, understanding or agreement.
Use an original responsibility map where relevant
If the client’s question concerns a handover, a simple RACI-style map can distinguish who does the work, who has decision accountability, whose input is sought and who needs an update. It is a discussion tool, not an assignment of authority by the coach.
| Activity | Responsible for work | Accountable decision role | Consulted | Informed |
|---|---|---|---|---|
| Prepare a project-update draft | Project lead | Actual project owner | Relevant specialists | Agreed review participants |
| Check an assumption | Appropriate qualified analyst | Authorized business decision role | Relevant data owners | Project lead |
| Approve a proposed change | Designated decision owner | Actual authorized approver | Affected functions as required | People who must act on the decision |
The roles are placeholders to check, not a universal governance rule. The coach should not fill them with names or declare a contract amended without the relevant parties’ authority.
This supports three uses from an asynchronous workflow: clarifying a decision, discussing a cross-team handover and reviewing how the agreed roles worked later. It does not establish a native interactive RACI engine or an automatic role-ambiguity alert in Coachful.
Run three kinds of bounded asynchronous sprint
| Sprint option | Appropriate work | Review boundary |
|---|---|---|
| 1. Document review | A permitted slide, memo or rehearsal is reviewed for the agreed coaching or competent advisory question. | Confirm version, scope, access and actual response allowance. |
| 2. Weekly reflection | The client considers a chosen decision or experiment through suitable prompts. | A reflection is reviewed within the agreed window, without real-time monitoring claims. |
| 3. Short audio clarification | A supported message route helps clarify one question where suitable. | An audio channel does not create an urgent hotline or unlimited additional work. |
A hybrid service may include one live review each month to discuss patterns, scope or topics that need conversation. Explain that appointment and its preparation separately from the recording allowance.
Cost the whole service before describing a scaling case
Consider an original monthly service with two reviews per client. Each review uses ten minutes to read or listen, ten to prepare, five to record and five to handle the appropriate record: thirty minutes each, or sixty minutes for two.
Add a forty-five-minute live call, fifteen minutes of call preparation and fifteen minutes of service administration. The total is 135 minutes per client per month, or two hours fifteen minutes. For fifteen clients, that is 2,025 minutes, or 33 hours 45 minutes, before sales, setup, absence and other business work.
If each client receives four reviews, the total becomes 195 minutes per client. Fifteen clients then require 2,925 minutes, or 48 hours 45 minutes. Extra clarification and longer documents can increase it further. An unlimited offer cannot be costed as two predictable short recordings.
For separate fictional billing arithmetic, eight clients at $2,250 per calendar month produce $18,000 monthly gross billings. Fifteen at $4,500 produce $67,500 monthly, or $810,000 annualized at unchanged full occupancy. These are not reported client results, collected cash, profit or proof that the work fits a particular weekly schedule.
Choose scope and price through actual work and suitable evidence. The corporate executive retainer guide develops the wider service arrangement.
Separate client records from a reusable library
A private client review may contain their material, third-party information or a discussion meant only for the agreed audience. It does not automatically become a transferable company asset or an enterprise teaching license.
Keep three categories clear: the client’s permitted service records, your original general teaching resources and any separately licensed materials. Reuse needs the actual rights, permissions and appropriate handling, not just a different folder label.
A successor executive is not automatically entitled to a predecessor’s private coaching content. An employer’s desire to preserve knowledge needs an appropriate separate record and agreement. Do not promise permanent access or a universal annual licensing fee.
Plan retention, access changes, copies and the end of the engagement on both platforms. A link title can help organization, but the actual search, playback and deletion behavior depends on the systems and settings.
Use Coachful for the supported delivery work
Coachful can organize suitable resources, forms, client-plan follow-up and relevant service delivery. Check the actual resource type, sharing, staff permissions, client access and supported link or media behavior. A saved Loom URL is not proof of a private native integration.
Keep unshared journal pages separate from coach notes and any shared recap. Where an enabled Share with coach control is used, that individual page is intentionally exposed to the coach; it is not automatically a sponsor record. Recording permissions, resource entitlement, billing, a booked live review and a client action remain distinct. A platform’s organized appearance does not prove SOC 2 status, end-to-end encryption or a guarantee that only one named person has technical access.
Explore Coachful’s features and choose the supported workflow that matches the actual service. Review the client’s experience and permission needs before claiming a video has been delivered or can be watched.
Frequently asked questions
Is five minutes always the best length?
No. It is a planning example. Use enough time for the agreed purpose, and choose another scope or format when needed.
Does a private portal make an unrestricted Loom private?
No. The recording and the portal have separate permissions. Match both audiences and check the actual viewing route.
Can a restricted external viewer need a Loom account?
Yes. Current specific-person sharing guidance requires sign-in using the invited email. Confirm the actual experience before promising account-free access.
Does a view confirm that the client understood the review?
No. Ask about usefulness, uncertainty and the client’s chosen next step through the agreed follow-up route.
Should asynchronous retainers always cost more?
No universal price follows from the format. Define the work, capacity, client fit and complete commercial terms.
Can I turn every client video into a licensed course?
Not automatically. Review actual rights, permissions, confidential content and the separate intended use.
Start with one useful question and an appropriate visual, then make sharing and follow-up as clear as the recording. The service is stronger when its scope, workload and information arrangements are easy to understand.
Primary technical context: current Loom/Atlassian guidance on capture, privacy, specific-person sharing, embedding and captions; W3C’s prerecorded-caption explanation; related responsibility-mapping guidance. The scripts, tables, time allowances and billing figures are original examples, not client outcomes or a configured account.
