Automate Client Homework Tracking in Coaching
Nour
Founder, Coachful
Automate client homework tracking in coaching by connecting an agreed assignment to its due date, submission and review workflow. Let the software update the relevant records and surface work needing attention. Keep the coach’s judgment and the client’s chosen next step visible alongside those updates.
Coachful is our #1 recommendation for this workflow because resources, client tasks, worksheet submissions and coach reviews can sit in the coaching workspace. This guide explains the actual controls and a complete fictional two-week example. It distinguishes an automatically updated queue from a reminder you deliberately send and feedback the client actually receives.
Decide what useful tracking should accomplish
Start with the coaching purpose. Between-session work might help a client test a conversation, reflect on an attempt or prepare a question. Agree what they want to try, what evidence would be useful and whether they want to report it. A template’s empty fields do not create an obligation to assign more work.
Tracking describes the state of that agreement. Accountability is the conversation about what happened and what the client chooses next. A completion mark can support that conversation, but it cannot establish the quality of an attempt or whether the wider goal was achieved.
Harkin and colleagues’ 2016 meta-analysis of 138 studies involving 19,951 participants found that interventions increasing progress monitoring improved goal attainment on average. This supports considering useful monitoring, with attention to its purpose and burden. It does not establish the effectiveness of Coachful, compulsory homework disclosure or this article’s original workflow.
Choose the lightest useful record. A short reflection may need three answers; a substantial draft may need a different review arrangement. Agree the submission route, audience, deadline and review window before relying on a dashboard to represent the service.
Choose what the software can update for you
| Supported workflow | Useful automatic behavior | Coach decision still needed |
|---|---|---|
| Assign a worksheet resource with a due date | The assignment adds a linked client task. | Confirm the right client, resource, instructions and date. |
| Client submits the worksheet | The linked task completes and that work leaves the Not completed queue. | Read the actual answer and decide what feedback is useful. |
| Configured choice answer needs follow-up | A matching submitted answer opens a linked follow-up. | Configure the intended answers and resolve the actual issue. |
| Due worksheet remains unsubmitted | Relevant work appears in Worksheet follow-ups under Not completed. | Check circumstances and choose whether to use Remind, revise or discuss it. |
These connections reduce manual bookkeeping. They do not mean every task receives an automatic sequence of deadline emails or that saving a private review sends feedback. Use the actual function appropriate to the promise you made to the client.
For a genuinely recurring reflection, a Coaching flow can have its own audience, days and reminder settings. Its Display, reminder timing and Home placement serve different purposes. Show once a day limits completion frequency; it does not set a reminder schedule. Keep that recurring check-in distinct from the individual assignments in the example below.
1. Write the assignment as a useful agreement
Give the task a purpose, a bounded action and a clear reporting request. “Work on confidence” is difficult to track meaningfully. “Try the opening sentence you chose, then record what you said and what happened” identifies a usable experiment without promising that the other person will respond favorably.
Explain what counts as doing the work. Reading instructions, trying the action, submitting a reflection and receiving feedback are different events. A client may complete an experiment but decide to discuss it verbally. Record that route accurately rather than insisting that only a platform submission makes the action real.
Include practical limits. How long should preparation take? Which information should stay in another system? Can the client decline or change the action? A coach does not need identifying customer records, an employer’s internal document or personal medical details merely to fill an evidence column.
The homework accountability guide develops the commitment conversation. Use it alongside tracking, particularly when an assignment has become irrelevant or the client is waiting on something outside their influence.
2. Deliver the resource and set the actual due date
In the client’s assignment workflow, choose Assign something, then Resource, select the intended form or worksheet and set Due date if that is the agreement. The due-dated assignment creates a linked task. Confirm the intended client can open the resource and understands what to submit.
A resource provided without a due date can still be accessible, but it does not become a due-dated entry merely because the coach expects an answer. Included program material and a general resource grant are also different from a specific assignment. Audit the actual item instead of assuming access means work is owed.
Set a realistic date prospectively. If the coach forgot to record it, discuss and correct the arrangement rather than retroactively labeling the client late. For a cutoff that includes an hour, communicate the agreed time and time zone in the instructions; do not assume a date field expresses every part of that service arrangement.
A simple test is practical: the intended client opens the right worksheet, can read the instructions and knows the review point. Saving the resource alone does not establish those facts. The test should use the actual permitted route rather than another person’s account or a public copy of private work.
3. Use the due queue and reminders deliberately
Worksheet follow-ups has a Not completed tab for relevant due-dated worksheets. It brings together overdue work, work due by an upcoming session and work due soon. The list uses its supported time windows, including seven-day upcoming work; it is not an unlimited inventory of every resource ever shared.
Open the actual item before deciding what to do. The client may have saved a draft, completed the work elsewhere or agreed to a different plan. A missing submission is a question to clarify, not proof that the person has ignored coaching.
The row’s Remind action sends the supported in-app notice, push where the client uses the app and email where available, linking to the relevant work. This is a deliberate coach action. Its daily cooldown is shared with the same task’s reminder elsewhere, so another button does not create an independent opportunity to send again.
A recorded send does not prove reading or completion. Avoid combining a native reminder, a separate email and a personal message without a reason. If there is a delivery or access problem, address it through the agreed contact route rather than escalating the number of nudges.
4. Configure answer-based follow-up for a real purpose
A single- or multiple-choice question can use Create a follow-up for this answer. Select the answer or answers that should open the follow-up. For example, an optional process question might offer “Ready to review,” “I want to change the plan” and “Prefer to discuss in session.”
If the client submits a selected answer, the linked follow-up becomes available to the coach. Explain what this means: it brings the request into the review process, not an immediate response or an emergency channel. Choose the review arrangement you can actually deliver.
Keep the trigger and its resolution separate from the private Coach review status. The coach must still understand the request and complete the appropriate follow-up. A changed answer should not be used to conceal what was previously reported, and resolving a flag does not establish a wider goal has been achieved.
Use only questions that serve the engagement. Do not turn a routine homework tracker into a clinical screening system or create automatic assignments from every answer. A client’s statement that they want to change the plan calls for discussion and choice.
5. Review the evidence and communicate feedback
Open the submission and read the actual answer before marking it reviewed. The Coach review section can hold the authorized coach team’s notes and Reviewed or Follow up status. Saving a review marks the submission reviewed and removes it from new-to-review work.
Those notes remain private to the coach team and are not included in the client’s response PDF. If the service includes feedback, communicate it separately through the session or appropriate individual client conversation. “Reviewed” is not itself evidence that the client received a useful response.
Make feedback specific. Refer to the client’s reported attempt, ask a relevant question and distinguish their choice from your suggestion. “You recorded ten minutes against the twenty-five-minute plan; which part would you change?” gives a concrete basis for a conversation. “Great progress” alone may leave the actual problem unexplored.
Keep the next action proportionate. The client may choose to repeat, revise, pause or stop. Review session recap tasks deliberately through the appropriate task workflow; every sentence in a summary or worksheet answer need not become another instruction.
Agree the fictional two-week service
All people, assignments, answers and communications in this example are invented. Coach Maya has three existing active clients, Mila, Jon and Eva. Each has chosen one short between-session reflection. Maya is the sole coaching staff member authorized for their work; no group or sponsor receives their submissions.
They agree that ordinary submissions received by Tuesday at 16:00 London time are reviewed in Wednesday’s 09:00–10:00 window. Later work goes into the following Wednesday’s window unless they agree otherwise. This is a bounded feedback arrangement, not unlimited asynchronous coaching or an urgent-support service.
Maya reserves sixty minutes across these clients on 11 November and another sixty on 18 November 2026. The client instructions identify both the due date and the ordinary review rule. Maya will check an access question in the review window and tell the client the actual next step rather than claim an unread answer has already been considered.
The first worksheet asks three original prompts: “What did you choose to try?”, “What actually happened?” and “What would be useful to discuss?” A separate optional choice question can flag a request to change the plan. The prompts collect relevant reflection, not a required success story.
Trace the first three assignments
Mila chooses a study experiment. She planned twenty-five minutes of reading after work but tried ten before stopping. Maya assigns the worksheet with a 10 November due date. Mila confirms access. At 09:00 on the due day, Maya deliberately uses Remind once; it is not an automatic scheduled chase.
Mila submits at 14:00, before the agreed 16:00 cutoff. She reports the ten-minute attempt and selects “I want to change the plan.” Submission completes the linked task and removes it from Not completed. The selected answer opens the configured follow-up. None of those updates means Maya has already read the reflection.
Jon’s assignment concerns rehearsing a presentation opening. He completes the practice and writes a private paper note, but prefers not to submit its full contents. In the 11 November review window, he gives Maya the agreed brief account through their individual client conversation: he tried the opening twice and wants to shorten the introduction.
Maya records the proportionate account and marks the linked task done as work completed another way. She does not submit invented form answers for Jon. The row leaves Not completed, while the record still shows no worksheet response to review. They agree that Jon will discuss the next version in his booked session.
Eva can open her reflection resource, but it does not appear as due work. Maya checks the assignment and discovers that she granted the resource without setting a due date. This is Maya’s configuration error. It is not a missing response that the software should have chased automatically.
On 11 November, Maya explains the mistake. Eva agrees to a 12 November due date and understands that review will be on 18 November because the ordinary cutoff has passed. Maya uses the due-dated assignment route, verifies the linked task and confirms the correct resource still opens. No earlier date is imposed retroactively.
Show Mila’s actual feedback and changed plan
During the 11 November window, Maya reads Mila’s submitted answer and saves a private Follow up review while the plan question remains open. She separately writes: “You tried ten minutes against the twenty-five-minute plan. What made you stop, and what would you want to change before another attempt?”
Mila replies that beginning late after work was the main difficulty; she does not want a stronger reminder. She proposes fifteen minutes after Saturday breakfast, when she expects to have free time. Maya asks whether the earlier commitment still matters. Mila confirms she wants to test this different arrangement rather than abandon the reading interest.
They agree a second experiment on 14 November and a short reflection due on 17 November. Maya deliberately provides a separate second-review worksheet with the revised question and date, preserving the first submission’s meaning. They confirm access. It is not an automatic task created from Mila’s choice answer.
Maya resolves the original answer-based follow-up after this actual exchange and updates the private review to reflect the completed discussion. She sends Mila the agreed plan summary, which Mila acknowledges. Resolving the flag records that response to the request; it does not describe the new experiment as already completed.
On 14 November, Mila reads for fifteen minutes after breakfast and stops at the agreed limit. She reports that the earlier timing suited this attempt but that she has not tested a normal workday version. Her second worksheet is submitted on 17 November before 16:00. The first ten-minute attempt remains a different observation.
Review the late submission and reconcile the register
Eva submits her reflection on 12 November. It concerns preparing a question for an ordinary project discussion. She writes: “I drafted two questions, then chose the one about which information the discussion needs. I have not held the conversation yet.” Her submitted worksheet leaves Not completed while still awaiting Maya’s review.
On 18 November, Maya reads Eva’s answer and sends: “You have chosen the information question. What would make it clear enough to ask, and is the conversation still the next step you want?” Eva replies: “What information do we need before choosing the next project step?” She confirms that asking it is still her chosen next step. The conversation itself remains future work; Maya records the distinction and Eva acknowledges the short feedback summary.
In the same window, Maya reviews Mila’s second attempt. She notes the actual fifteen minutes and asks what Mila wants to retain. Mila chooses another voluntary Saturday trial and declines a daily tracking target. Maya sends that agreed decision back, and Mila confirms it. No future repetition is counted as completed.
| Assignment | Actual evidence at the final review | Recorded outcome |
|---|---|---|
| Mila, first experiment | Submitted 10 November; ten of twenty-five planned minutes; change requested. | Reviewed; actual plan discussion completed and follow-up resolved. |
| Jon, presentation opening | Reported practice through the agreed individual conversation. | Task done another way; no invented worksheet response. |
| Eva, preparation question | Due-date omission corrected; submitted 12 November; reviewed 18 November. | Feedback received; chosen conversation remains future work. |
| Mila, second experiment | Submitted 17 November; fifteen-minute Saturday attempt. | Reviewed; client chooses a future trial, which remains unobserved. |
This is an original manual review register, not four custom native status buttons. Across four assignments, three worksheet responses were submitted and reviewed; one assignment was reported and closed another way. No open due work remains among these four items at the checkpoint, but that does not mean every client goal is complete.
Maya’s first window uses twelve minutes for Mila’s review and exchange, eight for Jon’s discussion and record, and ten for Eva’s assignment repair: thirty of sixty reserved minutes. The second uses fourteen for Mila and ten for Eva: twenty-four of sixty. Across both windows, fifty-four minutes are used and sixty-six remain unallocated. The reserved capacity is not a promise of sixty individual minutes to each client.
The two-week workflow review closes with the actual feedback and corrections recorded. The existing coaching engagements continue under their own terms. There is no claim that automation saved a measured amount of time, caused better study or presentation performance, or supplied ongoing support beyond the agreed review arrangement.
Handle exceptions before adding more automation
The client completed the action elsewhere. Agree the useful account and record the actual completion route. Marking work done another way should not create a fabricated worksheet response or imply that an unseen document was reviewed.
A due item has become unsuitable. Discuss a new date, replacement or closure. Retain why it changed. A client waiting for permission or access should not be treated as if repeated reminders can remove that dependency.
A submitted worksheet still looks pending. Check the actual response and linked task before chasing again. Correct the stale completion record through the appropriate task control; do not require another reflection merely to repair tracking.
The queue is empty. Check assignment coverage before announcing everything complete. Undated resources, work outside the list’s time window and completed tasks awaiting substantive feedback may require other views or a proportionate manual record.
Review demand exceeds capacity. Reconcile the actual volume and effort before promising faster feedback. Six submissions taking six minutes to read and four to reply require sixty minutes before access support or deeper discussion. Automation does not make those human minutes disappear.
Check eight things before relying on the workflow
- Purpose: the client understands and chooses the action and reporting request.
- Access: the intended client can open the actual resource.
- Due date: the assignment and communicated cutoff match the agreement.
- Submission: a real response updates the intended linked task.
- Follow-up: any selected answer trigger creates the expected review item.
- Reminder: the chosen action, recipients and daily cooldown are understood.
- Feedback: private staff review and actual client communication are both accurate.
- Exceptions: another completion route, late work and revised plans have an agreed process.
Use the session notes delivery guide when connecting this process to recaps. Keep task selection, private notes and the actual shared summary clear. Explore Coachful’s features around the work you genuinely intend to deliver.
Frequently asked questions
Can tracking be automated without automatic approval?
Yes. The software can update linked tasks, queues and configured follow-ups while the coach reads the evidence and communicates a decision. That division preserves the meaning of a reviewed submission.
Does every resource appear in Not completed?
No. The list has specific assignment and time-window rules. Check due-dated work and the intended client instead of assuming every granted or included resource is owed.
Is a completed task proof of a successful outcome?
It records the relevant completion action. Review the evidence, context and actual wider result before making an outcome claim.
Must feedback arrive within twenty-four hours?
Agree the service you can deliver, including working days, cutoff and late-work route. A daily reminder cooldown is not a promise of a twenty-four-hour coaching response.
