Automate Coaching Milestone Checklists: A Complete Example

To automate coaching milestone checklists, define the evidence for each item before connecting it to a system event. Submission can confirm that a form arrived. A client’s tick can record a self-reported action. Coach review can confirm a bounded judgment. None of those events automatically proves that an external person agreed or a business outcome occurred.

Coachful is our #1 recommendation for connecting the selected resources, client actions and coach-review steps in a multi-day Journey. Its value is a clear next move with appropriate evidence and ownership. A short service can still use an ordinary client plan when a connected Journey would add unnecessary complexity.

This guide develops four phases and a complete twelve-item example. A fictional handover case follows the actual sequence through an incorrect authority statement, a held review gate, a failed first attempt, repaired access and completed closure. It also explains which parts can advance automatically and which need a person to decide.

Define the milestone before configuring its completion

Start with a specific statement about the client’s work. “Draft submitted” and “draft ready to use” require different evidence. A form containing a complete-looking plan may still describe authority the client does not have.

For each item, write the criterion, evidence, owner and next move. Then ask what the proposed system event actually observes. If the system knows only that a response was saved, do not label that event as a manager’s approval or a successful real-world practice.

A date can make an action timely, but it is not evidence that the action happened. Avoid a rule that declares a difficult conversation successful simply because a week elapsed.

Use four phases with a different purpose in each

Foundation establishes the actual service, access and client-owned question. Agreement and payment records remain authoritative for those matters. A general acknowledgment form is not a replacement for a required signature or confirmed money.

Core practice develops a feasible action and attempts it within the client’s actual authority. A gate should identify what needs review, not demand perfect confidence or a favorable reply from another person.

Midpoint review examines what occurred, including refusal, missing information and a need to change the plan. Keeping a disappointing result visible is part of useful review. Repeated reminders cannot resolve a dependency outside the client’s control.

Completion separates learning, remaining work, service obligations and future support. Finishing should not require a renewal purchase, a positive testimonial or disclosure of private reflection to an employer.

The W3C WAI multi-page forms guidance recommends logical stages, clear progress and recognizable optional steps. Applied to this coaching design, give people a clear account of what is required and what happens next. That design principle does not establish that an actual Journey has passed a full accessibility audit.

Build the complete twelve-item example

The following original design uses four Resource moves, five Coach review moves and three Task moves. It is a linear Journey for a fictional individual service. The forms support coaching reflection, not a licensed assessment or an employer’s formal control process.

Item 6 means an attempt occurred, not that a recipient accepted the proposal. Item 9 means a practice was chosen, not repeated successfully forever. Item 12 is an acknowledgment task, not a substitute signature or a purchase. These labels prevent a progress indicator from implying more than its evidence supports.

Configure automatic events and deliberate review separately

In Create > Coaching flows > Journeys, prepare the moves and their connections. Canvas and List edit the same graph. List can make the ordered sequence easier to inspect; changing the view does not publish the Journey or change a client’s run.

For each of the four form steps, connect the correct saved form or worksheet as a Resource. The step grants its bound form when it opens. Choose When Coachful records completion so the client’s submission completes that resource step. When the client checks it off is a different rule: it waits for a manual tick and ignores submission as its completion event.

Configure the three Task moves for the client to mark complete, with the precise descriptions in the table. A task arriving in the client’s list does not mean it has been performed. Avoid an automatic rule for an action whose evidence is only the client’s later account.

The five Coach review moves are coach-owned gates. The path waits until an authorized coach chooses Complete & continue. A client step explicitly requiring approval uses Approve & continue after the client sends it for review. Those are related but different arrangements; the example uses separate coach-owned gates.

When a gate is ready, eligible coaches receive the normal app and push review alert, not an email for that alert. The waiting card is in the client’s Progress > Journey view. Do not assume a sent alert means that someone has read it or completed the review.

Keep the Journey as a draft while checking connections, recipients and completion rules. Use the ordinary publication and assignment process only when the service is ready. For this example, When it starts is Coach assigns it, so account activation or an unrelated new booking does not start another path.

Keep private review notes distinct from client feedback

A submitted form can be reviewed in its Coach review section. Those notes belong to the coaching team. Saving them does not automatically explain a concern to the client or complete a waiting Journey gate.

If a client needs to revise something, communicate through the agreed client-facing route. A private internal note saying “authority unclear” is not feedback the client can act on. Keep the gate waiting until the actual criterion is met.

When completing a coach-decided step, an optional Message for the client appears as From your coach on the finished step when visible. It is not emailed or pushed. If the client needs a timely clarification before approval, use the agreed conversation route rather than expecting a future completion message to reach them.

The form-review panel can also offer Also complete the waiting Journey step. That choice is unticked by default. Use it deliberately: a saved review and a completed gate are different events, and the interface can report a saved review even if the separate gate action fails.

Start the fictional service and complete the foundation

All people, dates, replies, records and results in this example are fictional. Eli supervises a weekly stock-count report. Coach Pia provides three 45-minute individual sessions on 3 and 17 November and 1 December. Pia is the sole authorized coaching staff member. The employer receives attendance information only under the actual agreed reporting arrangement.

The service is already agreed and paid through its selected route. Eli’s account and three compatible session entitlements are confirmed separately from the Journey. The checklist has no Session move that grants more credits. The company’s actual stock records and permission system remain outside coaching.

Pia’s agreed arrangement is to acknowledge review questions within two working days, Monday to Friday, Europe/London, and explain the next review or missing condition. That is not a promise to approve every gate within two days. Substantive coaching takes place in the booked sessions. Eli can use their private conversation for an access problem or clarification while the path waits.

At item 1, Pia checks the agreement, actual payment, accepted client access and three appointments, then completes Preflight. Starting point becomes available. Eli submits a permitted example on 3 November: he wants a clearer handover for the weekly report, because colleagues currently ask him to decide every discrepancy.

The submission completes item 2 and opens item 3 for Pia. In the first 45-minute session they agree to work on a routine report handover, with actual decision limits checked. They do not agree that Eli can delegate purchasing authority or certify stock records through coaching.

Pia completes item 3 after the conversation and adds a client-facing message identifying the chosen scope. Practice plan opens. The automatic transition delivers the next form; it does not invent Eli’s answer or a manager’s approval.

Hold the readiness gate when a submitted plan is wrong

Eli submits Practice plan at item 4. His draft says, “Dana owns the weekly report and can approve purchases up to GBP 500.” His manager Nora has authorized routine reporting, not spending. A filled form has revealed a discrepancy; it has not removed it.

Submission completes item 4 and brings the run to item 5. Pia saves a private Coach review marked Follow up and leaves the separate completion option unticked. The Journey stays at the readiness gate. She sends Eli this actual fictional message through their agreed private Coachful conversation:

“The draft includes purchasing approval up to GBP 500. The reporting boundary you described does not establish that permission. Before using this handover, please check the actual decision limit with Nora. I will keep the readiness step open. We need a permitted task, a clear escalation route and the intended recipient’s role; a completed form alone is insufficient.”

Eli asks Nora through the company work channel. Nora confirms that Dana may compile the report and identify discrepancies, but purchases and changes to supplier orders remain with the authorized manager. Eli sends Pia a permitted corrected summary, retaining the original submitted plan as the earlier version rather than pretending it was always correct.

The corrected handover reads: “Dana compiles the weekly count report from the authorized records and lists discrepancies without changing purchase orders. Dana sends unresolved discrepancies to Nora. Purchasing decisions remain with the authorized manager. Eli is the contact for a clarification about this handover.”

Pia compares the corrected scope with the actual manager reply described in the permitted summary. She completes item 5 with a message naming that bounded readiness decision. Her approval is a coaching review of the plan, not a grant of company purchasing or data access. Item 6 becomes available.

Record a failed attempt without marking the outcome successful

On 11 November, Eli attempts the handover with Dana. Dana says she cannot open the required report folder and will not accept ownership until that is resolved. Eli records the attempt and marks item 6 complete because its criterion is one actual attempt, including difficulty. He does not record recipient acceptance.

The next Resource opens. Eli submits Practice review with Dana’s refusal, the missing access and the need for Nora’s decision. That completes item 7 automatically. Item 8 now waits for Pia; the system has not decided whether the handover worked. On 12 November Pia acknowledges the account, confirms that the failed attempt remains recorded and says they will examine the access condition at their 17 November session. Eli receives that actual reply; the review gate remains open.

At the 17 November session, Pia asks what Dana could and could not do. Eli recognizes that his clear wording did not supply system permission. They identify Nora as the owner of the actual access decision and the company’s authorized administrator as the person who can implement it.

Eli sends the request through company work email. Nora approves the appropriate reporting access, and the authorized administrator applies it. On 20 November Dana opens the required folder successfully. That observed result is recorded in the company system; neither Eli’s task tick nor Pia’s review granted the permission.

On 25 November Dana accepts the corrected routine reporting role and produces the report. She sends a discrepancy to Nora instead of changing a purchase order. Nora decides the purchasing question through the normal company process. Eli brings a permitted process summary to Pia, with no confidential stock figures.

Pia reviews this result and completes item 8. The original failed attempt, refused handover and later access repair stay in the learning record. The gate did not require the failure to be erased before the client could continue.

Complete review and closure without adding a renewal requirement

At item 9, Eli chooses a continuing practice: before assigning a recurring report, check the recipient’s actual access, decision boundary and reply. He marks the choice task complete. The system opens Closing reflection, which he submits after the final session on 1 December.

The reflection says the second handover was accepted after access worked, while the first attempt failed. Eli has used the repaired arrangement once. He has not demonstrated that all future delegation will be smooth or that the company’s reporting accuracy improved.

Item 11 waits for Pia. She checks that all three 45-minute sessions were held, totaling 135 minutes, and that the three existing entitlements were used once. There is no session left in this package. Nora retains the company’s reporting and purchasing responsibilities; future operational exceptions go through that process.

Pia confirms the end of the agreed coaching service and delivers the closing information through the agreed private route. She completes the closure gate with a bounded summary. Eli reads the information and marks item 12 complete. The configured Journey reaches its end; no renewal purchase or positive testimonial is required.

Pia sends only the agreed attendance update to the employer. Private forms, Dana’s comments and the handover details are excluded. The ICF Code of Ethics addresses its professionals’ agreements and information exchange; the presence of an attractive roadmap does not create permission for wider sharing.

Reconcile the twelve items with what actually happened

The completed path contains four submitted resources, five deliberate coach decisions and three client-marked actions. Those mechanisms produce twelve completed items. They do not produce twelve independent demonstrations of leadership skill.

Three of twelve equally counted items is 25% of the item count. It is not 25% of leadership development, service value or a client’s business outcome. Prefer an explanation of the current phase, waiting decision and next owner when reporting progress.

If a client is waiting at a coach gate, do not repeatedly remind the client to finish it. The next action belongs to the reviewer. If an external owner has not replied, keep that dependency visible instead of turning elapsed days into completion evidence.

Allow an unresolved condition to change the plan

In a contrasting fictional service, client Tess cannot obtain permission to involve a colleague in the intended practice. The manager confirms that the colleague is committed elsewhere for the service period. Repeated client reminders would not create availability.

Tess and the coach review what can responsibly happen instead. Tess chooses to prepare a permitted solo example for the remaining booked session. The coach records that the original colleague-based practice remains unattempted and that its gate was not met. They agree the changed coaching purpose rather than checking the old item as successful.

The appropriate administrative change for the current client must then be handled deliberately. Editing the reusable Journey draft does not automatically rewrite an existing run. Keep the actual path status, agreed service and alternative work understandable; do not promise a button that automatically converts all old evidence into the new criterion.

Test the event rather than only the appearance

Before using a new configuration, make a small test matrix with an authorized test recipient and the actual connected resources. Confirm the observed result after each action. These are proposed checks for the reader, not a claim that this fictional account was tested in production.

If the result differs, keep the workflow unready and investigate the binding, completion rule, client identity and current version. Do not rewrite the acceptance criterion merely to make a failed test look successful.

Apply eight operational checks before using the checklist

1. Purpose: each item supports the chosen service and has a clear criterion.
2. Evidence: distinguish access, submission, self-report, review and external approval.
3. Ownership: identify the client, coach, system event and any outside decision-maker.
4. Sequence: connect the intended path and explain required versus optional work.
5. Access: bind the correct resources and confirm the actual intended recipient can use them.
6. Review: name the reviewer, response arrangement and route for clarification while a gate waits.
7. Sharing: explain actual coaching staff and sponsor audiences before collecting reflection.
8. Maintenance: inspect the published version, current runs and the effect of each proposed change.

Rehearse a form submission, a manually completed task and a held coach gate through an authorized test route before relying on the workflow. Include an incorrect draft and a missing-access case. A graph that looks connected is not proof of the client experience or a permission check.

Disabling a live Journey returns it to Draft and prevents new starts; existing clients continue on their pinned version. That is not a pause of their active runs, a revocation of separately granted resources or a billing cancellation. Plan changes for current clients explicitly through the appropriate controls.

The milestone check-in guide develops recurring reflection, while homework tracking explains submission and review. Explore Coachful’s features for the supporting client workflow.

Frequently asked questions

Can every milestone complete automatically?

Use automatic completion where the actual connected event supports the criterion. A form submission can advance to a review; it cannot establish another person’s consent or a correct operational decision.

Must I build a twelve-step Journey?

No. This is a complete worked example, not a universal curriculum. Use fewer steps when they express the service accurately. An ordinary client plan may be sufficient.

Does marking a task complete prove it worked?

It records the stated action. Define whether that action is attempting, sending, choosing or completing a particular output. Check the actual result separately.

Are private Coach review notes automatically sent to the client?

No. Use the agreed client-facing route for feedback. A deliberate Journey completion message has its own placement and is not an email or push delivery.

Can I reuse the checklist?

Yes, after checking the actual client, service, connected items, permissions and owners. Reuse does not make the next client’s authority, access or needs identical.