Coaching Client Onboarding Checklist and Software
Nour
Founder, Coachful
A coaching client onboarding checklist should tell both people what is complete, what remains open and who handles the next step. Cover the service, agreement, money, access, preparation and first appointment. Give clients a usable way to ask questions or change their mind as well as a route to begin.
The ten-step checklist below follows fictional coach Luca, participant Amina and corporate buyer Heather. It includes a filled readiness record, a welcome message and a first-session plan. Use the examples to design your own process around the service actually purchased.
In this worked example, the checklist is a shared account of readiness, not a score for Amina’s enthusiasm. Luca keeps the buyer’s commercial record separate from Amina’s preparation. Heather can ask whether the agreed service has started without receiving the content of a coaching conversation. A person can decline an optional prompt and still be ready to begin.
Compare four parts of the journey
| Area | Coordinated documents and email | General form tools | Connected practice software |
|---|---|---|---|
| Welcome | Name the contact and give an ordered set of links. | Explain what happens after submission. | Check the actual trigger, recipient and next action. |
| Agreement | Provide the complete reviewed version through the chosen signing process. | Separate an answer or typed name from an appropriate agreement-signing ceremony. | Inspect the actual agreement and configured booking or program requirement. |
| Preparation | Control the version, audience and return route. | Check fields, required answers, drafts and response permissions. | Find the real submitted response and its review, rather than assume every answer becomes a profile field. |
| Access | Verify each intended resource and contact route. | Check the actual device and account requirements. | Distinguish invitation, accepted account, purchase, enrollment and resource access. |
A well-run manual process can be clear. A connected process can reduce repeated handovers, but it still needs someone to review exceptions. Compare how the journey handles an incorrect email or an unfinished payment, not simply how few screens its best-case path contains.
Coachful is our #1 recommendation when you want to coordinate these records and client work in one practice system. We build Coachful, so this is a maker’s recommendation. Keep a well-run document, form or specialist signing process when it fits your obligations better. Choose from the complete journey you can support, including recovery when something fails.
Set four foundations before sending the checklist
One coherent service: use the same quantities, term and price in the offer, agreement, payment arrangement and calendar.
Useful preparation: choose questions that inform the first conversation, explain their audience and identify the reviewer.
Usable access: provide the supported browser or app route with an appropriate alternative for accessibility or device needs.
A defined first meeting: state what it is for, how long it lasts and whether it is included in the purchased allowance.
The ICF professional code supports explaining roles, confidentiality and financial arrangements before coaching. It does not prescribe a universal onboarding order or require a ninety-minute kickoff.
Complete the ten-step onboarding checklist
Luca proposes a twelve-week service: a sixty-minute opening meeting followed by five forty-five-minute sessions, for six meetings in total. The fictional price is £1,800 GBP, payable in three £600 installments. Heather's company is the buyer; Amina is the participant. Their information-sharing arrangement is established separately from the payment.
| Step | Work to complete | Filled example and evidence |
|---|---|---|
| 1. Confirm scope and agreement | Identify the real parties, recipient, included work and reviewed terms. Allow questions before intentional acceptance. | Company buyer and authorized signer confirmed. Amina receives the participant information arrangement. The issued service agreement is signed; Luca retains that exact copy. |
| 2. Reconcile payment | Check the actual invoice or purchase, currency, schedule and payment result. | First £600 received against the intended purchase; two £600 installments remain scheduled. A sent invoice alone would not establish receipt. |
| 3. Establish the account and access | Send the correct invitation and verify the accepted account's intended workspace and service access. | Amina has accepted her invitation. Luca checks the intended resource with the proper permissions; an account existing elsewhere is not substituted for this check. |
| 4. Offer welcome and orientation | Explain where to begin, how to contact someone and what can wait. Provide text alongside any short video. | Amina receives the concise welcome below and finds the service overview. Watching every video is not required to prove commitment. |
| 5. Collect proportionate intake | Explain the questions, required and optional answers, audience and suitable alternatives. | Three preparation answers are submitted. Luca reviews them and confirms the opening topic with Amina; this is coaching preparation rather than a clinical assessment. |
| 6. Confirm the first booking | Verify session type, date, timezone, duration, joining route and change policy. | The sixty-minute opening meeting is booked and confirmed. It consumes the first of the six included meetings, rather than adding a seventh session. |
| 7. Check the chosen device route | Help the person find the supported browser or app experience and adjust notifications deliberately. | Amina chooses a browser for preparation. An app invitation is optional if available for this arrangement; no separately published branded store app is presumed. |
| 8. Choose a small action | Agree an action or observation relevant to the client, including when it is useful. | Amina chooses to note one occasion when a handoff was unclear. She has not committed to a daily habit or a particular notification schedule. |
| 9. Check the preparation resource | Verify the actual file or course grant, its contents and the intended audience. | Amina can open the short delegation-preparation card. A benefit listed on a sales page is not used as evidence that this resource was granted. |
| 10. Confirm readiness and open items | Send a factual check, identify unfinished work and assign an owner. | Amina confirms the booking and resource access. Luca still needs to confirm the sponsor meeting's audience with Heather; that remains an explicit open item. |
A checkbox is a useful summary only when its meaning is clear. “Agreement complete” needs more than a link being sent. “Ready for the first meeting” can allow an agreed verbal preparation alternative while still requiring the actual booking to be confirmed.
The filled table describes the corrected position, after two access faults. On 9 November 2026, Heather’s authorized signer completes the issued agreement and Luca reconciles the first £600 against its intended purchase. Amina receives the separate participant information arrangement before answering preparation questions. The two future installments remain unpaid obligations on their agreed schedule; neither the welcome nor this example establishes their later receipt.
On 10 November, the welcome addressed to Amina’s obsolete work alias bounces. Luca initially marks “welcome complete” from the send attempt. He withdraws that entry, checks the replacement address privately with Amina and resends the introduction. He does not put her preparation in the support message. Amina accepts the correct invitation on 11 November, which establishes an account, but does not by itself establish access to every promised resource.
The preparation card still fails to open because Luca attached its grant to a duplicate profile. He checks the intended participant and correct account, corrects the authorized grant and provides its private client-access link. On 12 November Amina confirms that she can open the actual card. Luca replaces his earlier account-based assumption with that receipt. He does not create a Program just to make a standalone form appear in a particular dashboard list.
Use six readiness milestones to oversee the checklist
- Commercial readiness: reconcile scope, agreement and payment from steps one and two.
- A clear welcome: confirm the person understands the introduction and support route in step four.
- Useful intake: review step five and identify anything the client wants to correct.
- Usable access: check the account and chosen device route from steps three and seven.
- A confirmed meeting: inspect step six, including its effect on the session allowance.
- Relevant preparation: connect the chosen action, resource and open-item review in steps eight through ten.
These six milestones organize the longer checklist. They are your service-management headings, not a claim that every product displays six native statuses or runs the whole process without review.
For this case, steps one through nine have supporting evidence before the first meeting. Step ten still names the sponsor-meeting audience as open. Luca and Amina agree that their individual opening can proceed under the established private scope while Luca owns that administrative follow-up. This is a considered service decision, not permission to skip an unsigned required agreement or invent a successful payment.
Send a welcome clients can use
Hello Amina, welcome. Our first meeting is the sixty-minute opening session shown in your confirmation. It is included in your six-meeting service.
Please open the short preparation card and answer the three questions if that format works for you. A brief response is enough. You can instead bring the topic to our conversation; tell me if you need another format.
Your employer's payment does not give it your private preparation or journal. We will use the specific information-sharing arrangement agreed with you for any sponsor update.
If an account, link or booking looks wrong, reply to this message so I can check the intended account and next step. Please keep individual access links private. I will confirm the outstanding sponsor-meeting detail separately.
Luca
Replace every reference with the actual service and supported contact. The welcome-packet guide helps organize these instructions without overwhelming the first message.
Turn intake into the opening conversation
What situation would you like to explore? Amina writes: “I delegate tasks, but people return for decisions I thought I had handed over.”
What have you already tried? “I send a written summary. It lists tasks, but it does not say which decisions the other person can make.”
What would make our first meeting useful? “I would like to prepare a clearer handoff conversation for one real task.”
Luca's opening confirmation is specific: “Would it help to work through one task and identify the decisions, check-in and limits you want to discuss? We can change the focus if something else matters more today.” The form provides a starting point; Amina chooses the work.
W3C's form-instruction guidance recommends explaining required and optional input and relevant formats. The ICO's data-minimisation guidance supports collecting information for a defined purpose. Neither source establishes that four questions or a five-minute form is right for every client. Use a licensed assessment only within its permissions and competence requirements; a longer intake is not automatically more informative.
Amina declines Luca’s proposed extra question about personal health because it does not help her delegation goal. He removes it from this preparation, offers a verbal route and keeps the three relevant answers above. Submission initially appears in his record as “intake reviewed,” although he has not read it. He corrects that label, opens the actual response and asks the quoted opening confirmation. A saved answer is evidence of submission; his review and Amina’s choice of topic are separate events.
Required should mean needed for a stated purpose, not “choose the answer the coach prefers.” Explain what happens if information is missing and whether another format works. Avoid asking clients to paste confidential employee records into a general intake. In this example, Amina describes the handoff without naming colleagues. Luca’s later staff-only review is not a message to her, so he sends any agreed clarification separately through their chosen contact route.
Prepare a realistic kickoff and calendar
An optional sixty-minute opening agenda for this case allocates twenty minutes to clarify the situation and desired use, fifteen to examine the current handoff, fifteen to rehearse the next conversation and ten to choose an action and review. The total is sixty minutes. Leave space to agree a different focus or stop an exercise that is not useful.
Configure actual availability, notice and buffers around preparation needs. A thirty-minute buffer or forty-eight-hour notice rule is a possible service choice, not a universal standard. Check the selected booking route and the client's timezone before promising a place.
Capacity also includes work outside meetings. Luca's illustrative six-meeting service has 285 live minutes, ninety minutes of preparation (six times fifteen) and thirty minutes of onboarding administration: 405 minutes, or six hours forty-five minutes. Three new starts represent 1,215 minutes, or twenty hours fifteen minutes, across their planned delivery. That is work to place alongside existing commitments, not a promise that automation removes it.
The opening takes place on 17 November, 10:00–11:00 Europe/London. Amina agrees to the suggested agenda, rehearses one handoff and chooses to clarify one decision boundary with the colleague who actually owns that task. This uses one of the six meetings. It does not establish that the colleague accepted the proposal, that a team metric improved or that Amina completed five future meetings.
By 20 November, the access and readiness repairs raise selected onboarding administration from the planned thirty to fifty-five minutes. Luca has incurred sixty live minutes, fifteen preparation minutes and fifty-five administration minutes: 130 selected minutes. The remaining five meetings and their planned preparation represent another 300 minutes. If those plans hold, the whole selected service becomes 430 minutes, twenty-five above the original 405. It excludes unrelated sales, accounting and other client work. The original three-start model is still a planning comparison, not three observed results.
Adapt the checklist for three services
Individual work: prioritize the participant's purpose, chosen preparation and actual private/shared records.
Corporate sponsorship: separate buyer authority, participant information agreements, billing and a deliberately scoped sponsor update. A sponsor may need an administrative confirmation without receiving responses.
A group or cohort: check the intended program, cohort, schedule and community audience. Joining a program, receiving an account and appearing in a peer directory can involve different permissions. Explain what other members can see before inviting participation.
Make eight software checks
- Follow the actual invitation and purchase route with the correct recipient.
- Inspect the complete agreement and real signing process.
- Distinguish authorized, processing, failed and received payment.
- Try a short intake, a correction and an appropriate alternative.
- Check the intended resource and the account's actual access.
- Verify booking, timezones, notice, buffers and session allowance.
- Inspect configured communications, preferences and remaining human review.
- Walk through a wrong email, unresolved state and support response.
In Coachful, a tracked Welcome Flow can prepare a person without creating an account or granting a paid service. A configured native agreement or Before booking form applies through its supported path; a Before the session resource alone does not block booking. A required Yes/No answer also permits No and should not be mistaken for affirmative agreement consent.
Coach review records are private to the authorized coach team and excluded from response PDFs. Personal journals and private course takeaways differ from intentionally submitted preparation; supported journal pages can also be shared deliberately, so inspect each page’s actual controls and audience. Session recaps release automatically by default after summarization, subject to approval controls and session-type overrides. Check the effective setting for the relevant session type before promising that every recap will wait for review.
Use a small recovery check before automating the welcome. Which person and service did it target? Was the account accepted? Can that person open the intended item? Has anyone read the response? Record a failed attempt and its correction instead of treating a delivery count as proof that all four happened. The demo screenshots illustrate product surfaces, not receipts from Amina’s case.
A response PDF can still contain the participant’s answers even when it omits the coach’s review. Do not use that omission as a reason to forward the whole document to a sponsor. Luca prepares the bounded administrative statement separately and checks its actual contents. Export format, recipient permission and the purpose of disclosure remain separate questions.
Reopen readiness when the people change
Later, Heather asks to substitute another participant and keep Amina's existing preparation “to save time.” Luca checks the change before sending access. He identifies the new participant's actual service, agreement, account and booking needs, and keeps Amina's private material separate.
An approved replacement should receive appropriate fresh preparation rather than another person's answers. Any ending, payment or allowance changes are reconciled with the responsible buyer. Completing the first checklist once does not make it accurate after the participant changes.
Heather makes the substitution request on 18 November. Amina explicitly refuses reuse of her answers and any public account of the service. Luca honors both choices. The buyer’s request remains a proposed change, with no new participant invitation, automatic transfer of private responses or reset of the six-meeting allowance. The first meeting already used must remain visible when the authorized parties consider the remaining service and money.
Luca promises a corrected readiness copy by 19 November at 16:00, but delivers it on 20 November at 10:00, eighteen hours late. His accompanying apology names the missed time and withdraws “all ten complete”: the sponsor audience and replacement decision are still open. At 11:00 Amina reads the copy and corrects one action description. Luca includes her correction and obtains permission at 13:00 to send Heather only the administrative statement that one meeting occurred and the change request remains under review. Heather receives that bounded statement at 14:00, without Amina’s intake or staff review.
That closes this readiness update, not every future obligation. Luca owns the proposed replacement terms and sponsor-audience clarification for 24 November; Heather owns confirming buyer authority for any variation. Their decisions, the two later payments and the remaining meetings are unknown at this point. Amina’s receipt of a corrected account does not authorize a testimonial, more coaching or disclosure of the private material she refused to share.
Use the onboarding automation guide for supported triggers and recovery, and compare Coachful's features against the complete intended journey.
Frequently asked questions
What belongs in an onboarding checklist?
Scope, agreement, money, account and access, welcome, preparation, booking, chosen device route, a useful action and an owned readiness check. Adapt the sequence to the actual service.
Must everything happen immediately after payment?
Provide a clear next step and explain real waiting points. Allow time for review and confirm actual states rather than promise instant completion.
Can intake differ between packages?
Use the supported forms and conditions for the service and audience. Check what is submitted, reviewed and acted on; do not assume every answer populates a client profile.
Will the checklist prevent buyer's remorse?
It can reduce avoidable confusion. Ask about the client's experience and choices rather than promise a particular emotion or infer commitment from activity.
Does every client need a new username and password?
Check the actual invitation and authentication route. A tracked welcome, guest signing link and signed-in client account are different experiences.
Primary context: ICF Code of Ethics; W3C form-instruction guidance; ICO data-minimisation guidance. All people, records, messages, timings and prices are original illustrations.
