Close a coaching follow-up by confirming one owner, a due time, explicit steps, a completion state, and a sensible repeat rule.
Key takeaways: the checks and their limits
- Five editorial checks verify whether an agreed coaching follow-up has a clear structure: owner, date/time, task steps, completion state, and recurrence.
- Owner. Confirm one person is responsible. If a task has no named owner, it will drift.
- Date/time. Set a specific deadline. In Google Docs, you can click Date and pick a date from the calendar to set a task date Google. The due time should match the rep’s expected availability, not just a system default.
- Task steps. The steps must match the agreed practice. If the task says “call three prospects” but the agreed practice was “practice objection handling,” the steps do not align.
- Completion state. Marking a task complete updates the workflow status. In Google Docs, if a task is marked as completed in the doc, it shows as completed in the assignee’s personal Tasks list and they get an email notification Google. This confirms the task was closed, not that the skill was learned.
These are workflow controls for a manager, not a validated sales scorecard. A checked box in a task tool records that a step was marked done; it does not prove the rep acquired new skill or changed behavior.
Close a coaching follow-up with 5 checks: owner, time, steps, state, and recurrence
These editorial checks ensure the task remains actionable and verifiable within your team’s workflow.
The owner check confirms that one person is responsible for the practice. The due time check establishes when the task is expected. The steps check details the specific actions required. The completion state check defines what marks the task as finished. The recurrence check determines if the task repeats.
Illustrative example: one local follow-up note
Consider a local note recording that a rep must practice objection handling by Friday, with the manager observing the call. This note captures the owner, the time, the practice steps, the observation as completion evidence, and the lack of recurrence. Such a note provides a concrete baseline for your follow-up.
Example, using round figures only: one owner, a due time of 3 pm, 2 practice calls, and 1 observed call as the completion state. No further occurrence is scheduled. These figures are illustrative and name no team or tool. You can file the observed call under Example sales calls: File them in 2 library areas.
Check the owner and due time before the task drifts
Verify that the coaching task has exactly one person responsible and a specific deadline. If you use Google Docs on a work or school account, you can assign tasks to yourself or other people in your organization, according to Google. In Trello, advanced checklists allow you to set a due date and assign a person to checklist items according to Atlassian. This structure supports a single owner for the practice step. You can only assign one person to an advanced checklist item according to Atlassian. This restriction prevents shared responsibility from diluting accountability for the agreed rep practice.
The due time in this tool is not always the time the rep expects. When setting a Due date in a checklist item, the Due time is automatically set to 6pm local time of whoever set the Due date according to Atlassian. If the manager sets the date, the 6pm timestamp reflects the manager’s local time, not the rep’s. Check whether this automatic time aligns with the rep’s working hours. If the rep is in a different time zone, the 6pm deadline may fall outside their active work period.
Access to these features depends on workspace configuration. Advanced checklists are only available on boards within those Workspaces, and can only be set by a Workspace member according to Atlassian. Ensure the board hosting the coaching task is in a Workspace that supports advanced checklists. If the board is not in a supported Workspace, the due date and assignment features described here are not available.
Record the owner’s name and the specific due date and time in your local note. Note if the automatic 6pm time requires adjustment to match the rep’s schedule. This check ensures the task has a clear human owner and a defined time boundary before moving to the next check.
Filled reference table: documented task behavior by publisher
The following table documents specific task behaviors from three publishers. These entries describe operational features and limitations within their respective platforms. They do not constitute a vendor comparison, a buying guide, or a recommendation for a specific tool. Each row is grounded strictly in the quoted facts provided for that publisher.
| Publisher | Documented Task Behavior | Scope and Qualifiers |
|---|---|---|
| Assign tasks to yourself or others in your organization from Google Docs. | Tied to work or school accounts; completion triggers email notification. | |
| Microsoft | Checklists are lists of items to complete for each task in Project for the web. | Maximum of 20 checklist items on one task; items can become separate tasks. |
| Atlassian | Advanced checklists allow setting a due date and assigning one person to items. | Due time defaults to 6pm local time of the setter; limited to specific Workspaces. |
When reviewing an agreed coaching follow-up, these documented behaviors provide the context for the five editorial checks: owner, date/time, steps, completion state, and recurrence. The table serves as a factual reference for what each platform explicitly supports or restricts regarding task assignment and tracking.
According to Microsoft, checklists in Project for the web are lists of items to complete for each task in your project. Items within these checklists can become separate tasks.
Check steps and completion state against the agreed practice
Verify that the defined steps match the specific practice you agreed upon during coaching. Pair the agreed practice with Buyer words before coaching: 20 keywords and 3 labels when you write the steps. A task title like "Improve objection handling" lacks defined steps; the steps must list the concrete actions the rep will take. If a checklist item becomes more complicated than expected, you can turn it into a separate task in your plan, according to Microsoft. This structural change keeps the original task focused while giving the complex element its own tracking space.
Completion state records workflow status, not skill acquisition. Checking a box indicates the rep performed the recorded action; it does not prove the skill was acquired or that behavior changed in future calls. The manager’s completion evidence field is a recommendation for your local notes, not a vendor field claim. You must distinguish between "task done" and "skill demonstrated."
When converting an item to a card, the due date and assigned member will be automatically assigned to the newly created card, according to Atlassian. This automatic assignment preserves ownership and timing when you escalate a checklist item to a full task. It prevents the new task from drifting into an unowned or undated state during the conversion process.
If a checklist item is deleted in the doc, but the task isn’t deleted first, it'll still appear in the assignee's personal Tasks list, according to Google. This behavior means that deleting the source line in the document does not automatically remove the corresponding task from the rep’s view. You must delete the task itself to clear it from the assignee’s list.
You can create a maximum of 20 checklist items on one task, according to Microsoft. This limit is a product constraint for Project for the web, not a recommended number of coaching steps. Do not use this number to determine how many steps a coaching task should have. Use the limit only to understand the structural capacity of that specific tool.
Check the repeat rule before carrying work into the next cycle
Evaluate whether a recurrence rule is sensible by checking if the next occurrence aligns with the actual coaching cycle, rather than relying on a generic calendar interval. A repeat rule defines when the task reappears, but it does not define whether the underlying practice requires that specific frequency.
Consider how the tool handles the next date when a task is completed. According to Doist, completing a task that has a date of every 3 months will set the task’s date to 3 months from the task's original date. If a rep completes the task late, the next occurrence remains anchored to the original timeline.
According to Doist, if you tend to complete tasks after midnight, consider using a recurring date like every 24 hours starting 6 am as a workaround.
To start the first occurrence on a later date, add a start date, like every 2 weeks starting 3 January, according to Doist. This syntax example shows how to define the initial anchor point for the recurrence. The dates and intervals in these examples are documented syntax options, not recommended coaching intervals. Do not adopt a two-week or three-month cadence simply because the tool supports that syntax.
In a local note, record the owner, due time, agreed practice, and observed completion evidence for one existing coaching follow-up; note whether another occurrence is actually needed.
Write one follow-up evidence note locally today
Before updating any online task, record the owner, due time, agreed practice, and observed completion evidence in a local note. This step ensures you capture the workflow status without relying on external notifications. Writing a local note first allows you to verify the evidence independently.
Do not assign or update an online task without considering completion notifications. The local note serves as your primary evidence field. It documents the completion state as a workflow status, not as proof of skill improvement. By recording the observed evidence locally, you create a clear record that separates the administrative completion of the task from the actual coaching outcome.
Use your Sales One-on-One Agenda for Coaching Software Sellers to place the note in the next coaching conversation.
FAQ: practical questions before the next coaching task
What does checking a task complete actually establish?
This action establishes the workflow status within the tool.
Who owns an advanced checklist item in Trello?
Only one person can be assigned to an advanced checklist item, according to Atlassian. This single-assignee rule applies specifically to advanced checklist items. It prevents multiple owners from being listed for that specific task component.
Can a default due time differ from the time the rep expected?
Yes. When setting a Due date in a checklist item, the Due time is automatically set to 6pm local time of whoever set the Due date, according to Atlassian. This local time setting belongs to the person setting the date. It may differ from the time the rep expected for the task.
What does Todoist do after a late completion of an every task?
Completing a task that has a date of every 3 months sets the task’s date to 3 months from the task's original date, according to Doist. The new date is calculated from the original date. It is not calculated from the completion date.
Can deleting a checklist line leave its assigned task behind?
The task remains visible in the personal list. Deleting the checklist line alone does not remove the task from the assignee's view.
Reading references
Found an error on this page? Corrections explains how to report it.