Missed Coaching Homework: Five Practical Review Steps
Nour
Founder, Coachful

Missed coaching homework calls for understanding what happened and whether the agreed task still serves the client’s purpose. Incompletion can reflect a changed priority, unclear instructions, access, resources, timing, disagreement, or another concern. It does not diagnose an unconscious fear or a lack of commitment.
The five steps below help a coach respond respectfully, examine the actual circumstances, and choose what happens next. They include original questions, complete worked exchanges, and a short review record. The aim is a useful decision about the work, not a forced confession or an easy win at any cost.
Coachful is our #1 recommendation for organizing supported tasks, selected resources and follow-up when those workflows fit the engagement. We build Coachful, so this is a maker’s recommendation. The platform remains optional. A task status can help locate a question; it cannot establish the client’s motive, diagnose a difficulty or replace their account of what happened.
Keep the task and the coaching purpose in view
Before discussing the missed action, recall what it was meant to support and what was actually agreed. A suggestion, a reflection question, and a firm client commitment are different. Check that the coach and client understood the same task and timing.
The client may no longer want the original outcome or may have learned something that changes the next step. Begin with curiosity about the actual situation rather than classify the person as noncompliant.
A useful opening is: “We planned to review the draft today. What happened, and is that still the thing you want help with?” The client can give a practical answer, correct the premise, or choose another focus.
A five-step response
| Step | Purpose | Original question |
|---|---|---|
| 1. Respond respectfully | Make it possible to explain what happened. | What would help us review this without turning it into a judgment about you? |
| 2. Understand the sequence | Identify actual events and information. | What happened between agreeing the step and today? |
| 3. Review scope and feasibility | Check instructions, capacity, access, and dependencies. | What needed to be in place, and which part was missing? |
| 4. Examine competing priorities if relevant | Explore the client’s chosen goals and concerns. | Was there another priority or concern you wanted to protect? |
| 5. Choose the next arrangement | Keep, revise, replace, pause, or stop the task. | What, if anything, would be useful to agree now? |

1. Respond without praise, blame, or a diagnosis
Acknowledge the information plainly. “Thank you for letting me know” can be enough. There is no need to announce that missed homework is fascinating data or require the client to feel reassured by the coach’s preferred script.
Ask whether they want to discuss it and how it relates to today’s purpose. A client may feel disappointed, neutral, relieved, or something else. Nervous laughter, eye contact, posture, or a tense voice does not establish shame or avoidance.
If the coach feels frustrated, separate that reaction from the client’s worth or intentions. Consider whether the task was clearly agreed, within scope, and supported. The coaching relationship can address an unhelpful pattern without treating the person as a student who must earn approval.
Keep the response proportionate. If the missed item was minor and no longer relevant, a lengthy exploration may be less useful than acknowledging the change and moving on.
2. Understand what actually happened
Invite a specific account of the period after the session. The client may have forgotten, faced an urgent responsibility, misunderstood the submission route, awaited permission, or decided not to do it. These require different responses.
Ask questions that leave the cause open. “What happened when you planned to begin?” is different from “Which fear stopped you?” The second question assumes an explanation the client has not given.
Distinguish the action from its record. The client may have completed a conversation but not logged it, or uploaded a draft that the coach could not access. A missing portal update is not proof that the task was untouched.
An original review prompt is: “Which part did you do, which part remained, and what do we know about why?” Collect only the detail useful to the coaching purpose. A client does not need to prove completion by exposing private work or another person’s messages.
3. Check scope, access, and dependencies
Compare the task with the actual resources and responsibilities. Was the request understandable? Did it require a decision-maker’s approval, information from someone else, a tool the client could not use, or time that was not realistically available?
Reducing the size may help when the task exceeds available capacity. Missing authority, unsafe conditions, an inaccessible process, or a changed goal need a response to that particular issue.
The HSE’s Demands standard addresses achievable work in relation to agreed hours, skills and the work environment. That is useful context for checking conditions. It does not turn a missed coaching exercise into an individual diagnosis or make the coach the authority to change an employer’s priorities.
Ask what would make a revised step feasible. That might mean clearer instructions, a different format, another professional, a resource, or no assignment. The homework ideas guide offers different formats rather than one mandatory micro-step.
If preparation is essential to deliver a particular service, explain the relevant agreement and practical options honestly. Do not promise that every session must proceed unchanged regardless of what is needed, or use cancellation as a punishment for the client’s character.
4. Explore competing priorities only when the client finds it relevant
A person may want two things that pull in different directions. They might want a new role while also wanting to avoid a relocation, or want to reduce workload while needing predictable income. Those can be real trade-offs rather than hidden resistance.
Robert Kegan and Lisa Lahey’s Immunity to Change framework examines competing commitments and assumptions. It is a particular approach with its own training and materials. It should not become a universal explanation for every missed task, and this guide does not reproduce its mapping tool.
Minds at Work’s current developer description presents a particular relationship between a desired improvement, actions, competing commitments and assumptions. Those are method-specific ideas, not findings that every overdue item proves hidden resistance. If that approach is relevant and the client wants it, use appropriate competence and materials. Ordinary clarification about an inaccessible resource or missing permission does not require a proprietary map.
An original question is: “Was there another concern or responsibility that mattered more when you reached this step?” The client can say no. If there is a competing priority, ask how they want to weigh it and which information would help.
Avoid treating protection or caution as something to dismantle automatically. A concern about housing, immigration, health, care, or safety can be substantive and may need qualified support. The client does not have to choose growth over an imagined old safety to justify their decision.
5. Agree the next step, including a choice to stop
Review whether the original purpose still matters and which arrangement would help now. Options include keeping the task with better support, revising it, choosing a different inquiry, completing an appropriate part during the session, pausing, or ending it.
If the client wants a smaller action, choose one that still serves the purpose. Check what makes it feasible, what remains uncertain, and when the client wants to review it.
Clarify action, resources, dependencies, and a useful review. A check-in can be agreed when it fits the service and preference. A reminder should support a chosen action, not become repeated contact designed to make the client comply.
If the same issue recurs, consider the goal, service fit, access, and working agreement together. There is no automatic three-week threshold for a meta-conversation or a rule that the person must leave with homework to make the session useful.
Worked exchange: the task depended on permission
In this original fictional example, Priya did not send a customer survey the coach believed was an agreed action. The coach begins by checking the actual situation rather than assuming avoidance.
In the dated extension, Rhea is Priya’s coach. They have a thirty-minute preparation conversation on 3 November 2026 and a forty-five-minute review on 9 November. Rhea’s original note says “send survey,” without separately identifying the approval dependency. At the review she initially suggests Priya may be avoiding feedback. Priya explains the customer-communication rule. Rhea acknowledges the unsupported inference, withdraws it and checks the actual agreement rather than ask Priya to prove commitment by sending without permission.
There is still useful accountability to examine. Priya produced sixteen questions instead of the agreed short draft of eight. The first draft took forty-five minutes against a forty-minute planning estimate. The permission problem does not make that scope difference disappear. They discuss which questions serve the purpose and what Priya wants to revise, without claiming the survey has been sent or that the draft proves lack of motivation.
Coach: “We planned to review the survey response today. What happened after our last conversation?”
Priya: “I drafted the questions, but I cannot send customer communications without approval. I am still waiting for the project owner.”
Coach: “So the draft is complete, and sending depends on another decision. Did we make that distinction clearly last time?”
Priya: “Not clearly enough. I also do not know when the owner can review it.”
Coach: “What would be useful to decide now?”
Priya: “I want to ask for a review date and check whether a smaller internal test would be appropriate. I will not send it without permission.”
The revised plan addresses the actual approval dependency and identifies the next inquiry.
On 10 November, project owner Luca agrees to review the draft by 17:00 UTC on 16 November. The actual reply arrives at 11:00 on 17 November, eighteen hours late. It permits a limited wording test with five colleagues, not contact with customers. Priya keeps the customer survey unsent. A coach’s encouragement, an internal test and approval to send externally are different forms of authority.
Five colleagues receive the permitted internal test on 18 November. Three respond and two remain unknown. Of the three replies, two identify unclear wording and one reports the questions understandable. That is feedback on this small draft, not customer evidence, a representative research result or proof that coaching worked. Rhea initially proposes marking the original survey as sent. Priya corrects the distinction, and Rhea keeps the external action pending rather than use a positive activity count to close it.
Worked exchange: the original goal has changed
In this second original fictional example, Rowan has not updated a résumé because they are reconsidering whether to seek a different job. The coach checks that the client wants to discuss the change.
Coach: “Is updating the résumé still useful for what you want?”
Rowan: “Possibly later. I am more interested in finding out whether my current role can change before I leave.”
Coach: “Which question would help you decide what to explore first?”
Rowan: “Whether there is a realistic route to a different project. I want to prepare that conversation.”
They choose an inquiry about the current role and leave the résumé task paused. They agree to review the actual information Rowan obtains before choosing another task.
This separate fictional case uses different dates and a different coach, Dev. At a forty-minute conversation on 12 November, Rowan chooses to pause the résumé rather than be assigned a smaller résumé task. They want to ask the current manager about a possible project. The coach does not label this a commitment to remain in the job or presume a competing commitment that Rowan has not identified.
Rowan speaks to the manager on 19 November. At a twenty-five-minute review on 26 November, Rowan reports that a different project might exist but its budget has not been approved. The conversation was completed even though Rowan did not update a portal task. Dev first sees the empty record and asks whether the conversation happened; Rowan supplies the account without sharing the manager’s private messages. They retain the budget uncertainty, leave the résumé paused and choose a written request for role information by 30 November. The future answer and job decision remain unknown.
A concise review record
| Field | What to record |
|---|---|
| Original purpose | What the task was intended to help the client learn, decide, or do. |
| Actual agreement | The action, timing, dependencies, and any misunderstanding. |
| What happened | Known events and the client’s account, with uncertainty identified. |
| Current relevance | Whether the goal and service still fit. |
| Chosen revision | Keep, adapt, replace, pause, stop, or seek suitable support. |
| Review | The next useful contact, if any, and what should remain private. |
A short factual note is often enough. Avoid labels such as avoidant, resistant, or unmotivated when the record only establishes that one task was not completed. The session notes guide develops proportionate records and corrections.
A filled version for Priya can stay brief:
- Original purpose: Clarify the survey wording before any permitted customer communication.
- Actual agreement: Draft eight questions; the earlier note failed to distinguish the separate approval needed for sending.
- What happened: Sixteen questions drafted, no customer send, then five permitted internal invitations with three replies and two unknown responses.
- Current relevance: Better wording remains useful; external use still requires the proper decision.
- Chosen revision: Revise the draft and ask about permission, keeping the external action pending.
- Review: Keep Priya’s approved private record at the close and her owned 30 November inquiry distinct from any future answer.
Use co-working only when it serves the agreed role
Completing a part together can clarify the task: outlining a question, checking the first instruction, or rehearsing an opening. Ask whether the client wants this and what help is within the coach’s competence.
Do not take over private work, provide unqualified advice, or mistake typing something for a breakthrough. If the obstacle is missing authority or an inappropriate goal, co-working may not help.
A useful review asks what became clearer and whether the client now wants another step. The client can also decide that the exercise is not useful.
During Priya’s 9 November review, she chooses six minutes of co-working to revise one confusing question. She then says she would rather finish the rest alone, and Rhea stops the exercise. The later revision takes fifteen minutes of Priya’s work altogether, including those six shared minutes and nine outside the call. Added to the first forty-five-minute draft, that is sixty selected client drafting minutes, twenty above the initial forty-minute estimate. It is not a complete work log. The six shared minutes also sit inside the forty-five-minute coaching review and must not be counted as extra live time.
Organize agreed actions and review in Coachful
Check the actual task, due date, intended recipient, and any completion record before assuming what happened. A worksheet answer, a task, a habit entry, and a message can represent different pieces of the work.
After discussion, deliberately update or select the agreed tasks and any review date. Use the actual available reminder settings and client preference rather than promise that every worksheet creates automatic check-ins.
Check what the date and status actually mean before changing them. An assignment date, due date, completed conversation and later record update are different facts. Keep a client’s factual correction visible rather than move a date just to make an overdue list look tidy. A manual reminder or an eligible configured reminder is not evidence that the client received, read or accepted it.
For a standalone preparation form, deliberately grant the intended access and check the private client route; assignment does not guarantee every My Coaching next-actions placement. Check journal sharing per page and audience and the effective recap approval settings, including session-type overrides. Ask for only the evidence needed for the agreed review. Priya’s customer files and Rowan’s manager messages do not need to become coaching attachments.
Review permissions, notifications, and sharing before collecting sensitive evidence. A task record should not require unnecessary customer files or private conversations. Explore Coachful’s coaching features for appropriate preparation, chosen actions, and review.
At a twenty-minute close on 23 November, Priya says clarifying permission was useful, but Rhea’s avoidance inference and proposed sent status were unhelpful. Rhea keeps both parts of that feedback. Priya approves an accurate record for herself only and declines a copy to Luca. She does not want another accountability form. Current coaching ends, with Priya owning a further question to Luca by 30 November about any external communication. His answer and the customer survey outcome remain unknown.
Priya’s three conversations total ninety-five coach-client live minutes: thirty, forty-five and twenty. Rowan’s two total sixty-five. These are separate selected engagement scopes, not evidence of a completed survey, a changed job or the coach’s whole working time. Rowan also chooses to end the current work after the review and keeps the agreed record without a further purchase. The coach can honor a clear ending while leaving a task paused or awaiting someone else’s decision.

Frequently asked questions
Should a coach always cancel or always continue when homework is missing?
Neither universal rule fits every service. Examine the purpose, actual agreement, feasibility, and what can usefully happen, without using cancellation as a judgment about the client.
Does repeated incompletion prove the client is not committed?
No. Review actual relevance, resources, access, dependencies, priorities, and service fit. The pattern may need discussion, but it does not establish a hidden motive.
Should the task always be made smaller?
Only if size is the relevant problem and the smaller step still serves the purpose. Missing permission or an unwanted goal calls for a different response.
Can a client choose no homework?
Yes, an appropriate coaching agreement can include reflection or work during sessions without an extra task. Clarify what serves the client and the actual service.
Is a missing portal update the same as a missed action?
No. Ask what occurred and distinguish the activity from its record. Use an appropriate level of evidence and respect privacy.
Review the actual agreement, understand the circumstances, and choose what happens next together. A respectful response can make the plan more accurate without inventing a psychological explanation.
Primary context: Robert Kegan and Lisa Lahey’s Minds at Work description of Immunity to Change, for its specific competing-commitment framework; ICF competencies for client partnership. The five-step response, questions, examples, and review record here are original general coaching material, not an Immunity to Change diagnostic map.







