Coaching Client Onboarding Checklist: 17 Readiness Checks
Nour
Founder, Coachful
A coaching client onboarding checklist should show why a person is ready for the next part of the service. It needs evidence for agreement, purchasing, access, preparation and the first conversation, with an owner for anything still open.
Coachful is our #1 recommendation for connecting supported agreement, client access, preparation and delivery workflows. Use the checklist to inspect the actual saved records and client experience. Sending an invitation or welcome email is one event, not proof that every prerequisite is complete.
This guide provides seventeen checks in four phases and follows an original fictional case from a purchasing delay through a completed launch and first support round. Its focus is readiness decisions. The separate welcome-packet guide develops the material clients receive.
Define what ready means before counting completed items
Separate a condition required before starting from work that belongs inside the first session. The first thirteen checks below prepare the launch. The final four are completed during and after it. A client cannot finish a collaboratively agreed first-session focus before meeting the coach.
Set the actual start rule for your service. For a self-paying package, confirmed payment might be required. A company contract may instead permit a start after an accepted purchase order, with an invoice due later. Neither rule is universal, and an enthusiastic participant cannot change the buyer's terms.
Use four plain states: verified, waiting, an agreed alternative, or not applicable with a reason. A percentage alone can hide a consequential omission. Twelve completed items do not compensate for sending confidential information to the wrong person.
For each consequential check, retain the source, date and responsible person. “Signed version A1, checked on 29 October” is more useful than “paperwork done.” A different person should be able to understand the evidence without reconstructing every message.
An agreed alternative needs comparable clarity. “Long form skipped” leaves a gap; “Three answers returned by service email, read by Tess before the launch” identifies the replacement and its result. An exception is not a private decision by an assistant to waive a commercial or confidentiality requirement. Obtain the relevant person's actual decision and explain what still applies.
Keep an unresolved item attached to the activity it affects. A missing purchase order can block confirmation under the contract while an optional biographical question need not block a conversation. A wrong joining route prevents usable attendance, even if agreement and payment checks are green. This lets the checklist guide action without making every small imperfection equally consequential.
Phase one: establish the service and its boundaries
| Check | Work to complete | Evidence to retain |
|---|---|---|
| 1. People and authority | Identify participant, contracting buyer, payer and any sponsor. | Names, roles and who can authorize each decision. |
| 2. Actual scope | Confirm meetings, duration, period, resources and support. | One consistent service schedule across relevant records. |
| 3. Agreement | Explain the terms, invite questions and complete the appropriate acceptance. | The actual accepted copy and version. |
| 4. Purchasing condition | Check the condition required to begin, including price, currency and finance route. | Settled payment or the expressly accepted purchasing state. |
| 5. Information exchange | Agree audiences, content, technology and relevant confidentiality limits. | Actual information-sharing arrangement, not inferred payer access. |
The ICF Code of Ethics calls for explaining coaching and co-creating an agreement about roles, confidentiality and financial arrangements before coaching begins. It also addresses agreed information exchange and responsible records handling. It does not prescribe this seventeen-item sequence or make a payment a substitute for participant agreement.
Distinguish the organizational purpose from the participant's private work. “Support a new regional role” does not authorize a manager to read intake answers. Ask what exact administrative or outcome report is needed, who approves it and how it reaches the intended recipient.
Start the fictional case with a genuine blocked state
Fictional example: Coach Tess works with Amira, whose employer Alder Services Ltd is buying four sixty-minute individual sessions for a fixed total of £1,200 GBP under the reviewed contract. Juno is the organizational sponsor; Leon is the authorized finance contact; Iris is the authorized company signer. All people, records, dates and events below are invented.
The agreed service has four sessions between November and December 2026, one preparation resource and one optional written support round between each pair of sessions. Each round permits one message of up to 300 words and one reply, without an ongoing conversation. Resource access lasts through 31 January 2027. There is no included community or recurring billing.
On 29 October Tess, Iris and Amira complete the relevant agreement arrangements. Tess retains the signed A1 copy. Amira confirms she chooses to participate. The commercial start condition requires an accepted company purchase order; the contract permits invoicing with payment due later.
The order is still missing. Tess therefore records purchasing as waiting and the proposed 5 November opening session as unconfirmed. Leon accepts responsibility for checking procurement and promises an update on 2 November. That is Leon's actual accepted task, not an appointment Tess assigns to finance without asking.
Tess sends Amira this accurate update: “We have completed the agreement arrangements. The purchasing confirmation required before we confirm the start is still outstanding. Leon will update us on 2 November, and I will tell you the result that day. The proposed 5 November time is not yet a confirmed appointment.”
On 30 October Juno asks for a copy of Amira's intake. Tess explains the agreed boundary: finance receives purchasing information; Juno can receive a brief attendance confirmation after Amira approves its exact text. Private preparation is excluded. Juno accepts that distinction, and Amira acknowledges the clarified arrangement before submitting anything.
Phase two: establish usable access and orientation
| Check | Work to complete | Evidence to retain |
|---|---|---|
| 6. Correct identity route | Use the intended account, invitation or supported record-only route. | The right person and an understandable entry instruction. |
| 7. Actual entitlement | Check the saved sessions, resources and any required enrollment. | Intended access, not merely a listed benefit. |
| 8. Usable welcome | Give an ordered next step and named service contact. | Actual message and the client's understanding where checked. |
| 9. Participation arrangements | Ask about usable formats, joining and assistance without demanding unnecessary personal information. | A specific arrangement with an owner and a check. |
In Coachful, Clients > Add client distinguishes Invite to platform from Track client, which creates a record without an account. The Essentials invitation follows person, access, payment and review. A created or emailed invitation is not an accepted account, and account acceptance alone does not establish every intended resource grant.
Give free access and They already paid are nonbilling routes: neither captures money or invents a paid invoice. A priced complimentary grant requires the appropriate permission. Use the choice that fits the real arrangement, and keep the commercial record distinct from the technical access state.
On 2 November Leon supplies the accepted purchase order. Tess checks it against the service and confirms to Amira that the start condition is satisfied. Alder receives the invoice through the separate accounting process, with payment due on 2 December. No payment is claimed as received in this case.
Tess has the necessary permission and uses the nonbilling access route for the contract's approved credit terms. Before sending, she verifies four sessions of the intended sixty-minute type and the preparation resource. Starting templates can prefill a session type; the check concerns the actual saved inclusion and quantity.
Amira accepts the invitation on 3 November and opens the resource in her chosen browser. She does not need to give Tess a password or have her manager sign in for her. The readiness record now distinguishes the completed purchase-order condition from the still-future invoice payment.
Phase three: make preparation relevant and the meeting usable
| Check | Work to complete | Evidence to retain |
|---|---|---|
| 10. Proportionate intake | Ask questions that inform this conversation and explain the audience and alternatives. | A response or an explicitly agreed preparation alternative. |
| 11. Confirmed appointment | Verify type, date, time zones, duration, joining and change route. | The actual current booking and usable joining details. |
| 12. Support promise | Name channel, scope, allowance, response clock and absence arrangements. | The client's understanding of the actual service. |
| 13. Coach preparation | Read the relevant material, check open items and prepare useful questions. | A brief preparation record rather than an unexamined form-completion tick. |
W3C WAI's form-instruction guidance recommends explaining required and optional input, formats and relevant instructions. Do not rely on disappearing placeholder text for essential instructions. These are usability considerations, not evidence that a particular form is accessible to every person.
The ICO's data-minimisation guidance connects collection to a defined purpose: enough relevant information, without unnecessary excess. The page is under review following the Data (Use and Access) Act. Apply the appropriate current requirements to your context rather than treating an onboarding form as proof of legal compliance.
Amira can open Tess's original long form but finds it unnecessarily demanding. It asks about annual personal goals and background information unrelated to the proposed opening topic. Amira leaves those fields unanswered and requests a shorter route. Tess agrees by email; missing long-form answers are not recorded as unwillingness to participate.
Tess asks three original questions in their existing private service email thread. Amira chooses that route, and Tess explains that she will read the answers, not forward them to Juno:
- What current situation would be useful to examine?
- What do you already know, and what is still uncertain?
- What would make the opening meeting useful to you?
Amira replies on 4 November: “I have been asked to join a regional project. I know its purpose, but not the weekly work or what can stop. I want to prepare the questions I need before deciding.” Tess reads that actual reply before the meeting and records the agreed shorter preparation as complete.
Repair the joining instruction before marking readiness
The appointment is now booked for 5 November, 15:00–16:00 Europe/London, which is 10:00–11:00 America/New_York on that date. It uses one of the four included sessions. The other three remain available for later meetings; confirming an appointment does not add a fifth session.
Tess's manual welcome message contains an obsolete meeting link copied from an earlier template. Amira notices that its meeting title is wrong and replies on 4 November. Tess checks the actual booking, sends the correct joining link in the same email thread and explicitly withdraws the old instruction. Amira confirms the correct meeting title opens.
This is a completed repair of a manual message. Saving the correct booking did not automatically rewrite Tess's unrelated draft. Tess also updates the reusable welcome text so she does not rely on the same stale instruction for the next client.
They agree that camera use is optional and that Amira can use written notes alongside the conversation. If the joining route fails on the day, Amira replies to the service email. Tess will pause the start and agree a usable route before substantive work; a disconnected client is not counted as having attended.
The written support route is ordinary service email to Tess, with Tess replying in the same private thread. A message received by 12:00 on a London working day is due a reply by 17:00 on the second following working day; later or nonworking-day receipts start the clock on the next working day. The service works Monday to Friday, excluding applicable holidays.
Their instructions state this is bounded coaching preparation, not an urgent or emergency channel. A known absence needs a separately communicated arrangement. Amira confirms the one-round allowance and response clock in her own words rather than Tess treating a delivered welcome message as understanding.
Phase four: complete the launch rather than just schedule it
| Check | Work to complete | Evidence to retain |
|---|---|---|
| 14. Working agreement | Invite remaining questions and confirm the chosen use of the meeting. | Answered questions or an explicit decision to pause a material issue. |
| 15. Initial focus | Agree the client's useful question within scope. | The client's description, not an automatically assigned goal. |
| 16. Feasible next action | Choose an action, observation or information request if useful. | Actual choice, owner and review point. |
| 17. Follow-through | Confirm the summary, remaining meetings and open operational work. | The shared output and honest status of outstanding obligations. |
The 5 November session starts with the corrected joining route working. Tess and Amira use this sixty-minute agenda, adapting the conversation within those limits:
| Minutes | Actual use in the case |
|---|---|
| 0–5 | Check joining, camera choice and what would be useful. |
| 5–15 | Confirm support and sponsor boundaries; answer Amira's questions. |
| 15–30 | Examine what is known and unknown about the project invitation. |
| 30–45 | Draft and rehearse a request for missing information. |
| 45–55 | Choose the request, recipient and review route. |
| 55–60 | Check the summary and remaining service; close. |
Amira does not decide to accept the regional project. Her chosen output is: “Before I decide, please confirm the expected weekly hours, the delivery deadline and who can agree what existing work stops.” She chooses to send it to the project owner. The coach cannot authorize the company's staffing decision.
Amira declines recording for this meeting. Tess therefore does not use a recording or AI-generated session recap. They agree a short written email summary of the chosen request and next review point instead. The summary is sent to Amira that afternoon, and she confirms its wording.
In a different service using generated recaps, check the actual approval settings before the session. Coachful's default automatic sending and session-type overrides matter; a workspace approval hold must apply to the relevant session before relying on it. Consent and audience still need their own agreement.
Complete the first support round and retain the unknown
On Friday 6 November at 11:00 London time, Amira emails Tess a 180-word draft of the project request. This uses the one optional round between sessions one and two. Tess replies on Tuesday 10 November at 15:00, before the agreed 17:00 deadline that day. Amira acknowledges reading the reply at 16:00.
The feedback points out that Amira's draft asks about hours and deadline but omits who can reprioritize existing work. Amira adds the third question and sends the request to the project owner that afternoon. On 11 November the owner replies with an estimated four hours weekly and an 18 December deadline, but does not identify who can authorize removing current work.
Amira records that third answer as unresolved and does not accept the project in this account. The support round is complete; an ongoing exchange is not quietly added to the allowance. The next live session is booked for 19 November to review the decision and any further information.
After the first session Amira also approves the exact sponsor message: “Amira attended the agreed sixty-minute opening session on 5 November. The next session is booked for 19 November.” Tess emails only that text to Juno, who acknowledges receipt on 6 November. No preparation answers, project request or private summary accompany it.
Close the readiness record with remaining obligations visible
At the 12 November operational check, the purchasing prerequisite, accepted account, preparation alternative, repaired joining route, launch and first support round have evidence. The actual completed service is one sixty-minute session and one bounded written round. Three sessions, later optional rounds and January resource access remain obligations.
The invoice is still due on 2 December, with no receipt observed at this cutoff. The regional project's reprioritization authority remains unknown. Neither issue is marked complete merely because the first meeting went ahead.
Tess's final status note reads: “Ready for the booked 19 November session under the existing terms. Amira's project decision remains open. The first support round is used. Monitor the due invoice separately; retain resource access through 31 January.”
Keep this record separate from the client's personal reflections. Unshared journal and takeaway pages remain private; where enabled, Share with coach intentionally shares the individual page. A chosen submitted preparation answer is different. Coach review on a worksheet submission is private to the coach team, so it does not by itself deliver promised feedback to the client.
Adapt the checks for a cohort or a simpler service
For a group service, verify the specific cohort and its dates as well as Program access. A Program entitlement does not silently enroll a person into a live cohort. Explain what peers can see, which activities are optional and how any required participation arrangement will work.
The illustrative Program screen below belongs to that separate group context, not Amira's individual package. A coach should check the intended person's actual cohort and released preparation, rather than use a staff preview or a generic Program card as proof.
A free discovery conversation can have a much shorter process. Identify the purpose, joining route, relevant privacy information and any actual preparation. A four-session purchase, sponsor report or full assessment should not be introduced as an unexplained prerequisite for that limited conversation.
For online coaching, a browser route may be enough; do not require an app installation to demonstrate commitment. Ask about practical use and check the supported alternative. If the arrangement is inaccessible or a material consent question remains, pause the affected activity and agree what happens next.
The onboarding automation guide covers triggers and exception handling. Explore Coachful's features against the specific evidence each check needs, while keeping these readiness decisions under accountable human ownership.
Frequently asked questions
Must all seventeen checks be complete before the first meeting?
No. The first thirteen prepare it; the last four belong to the launch and follow-through. Define the actual prerequisites and acceptable alternatives before scheduling. A material purchasing or information-sharing condition cannot be replaced by a high checklist score.
Does an employer's payment let it read intake answers?
Payment does not establish unrestricted access. Agree the exact information exchange with the relevant parties. In the fictional case Juno receives only the attendance message Amira approved, while private preparation remains excluded.
What if the client does not complete the intake form?
Ask whether the format and questions fit. Agree a shorter written or conversational alternative when appropriate, and ensure the coach actually reviews what is supplied. Do not infer motivation or a diagnosis from a missing form.
Is sending an invitation proof of usable access?
No. Check acceptance and the intended item under the person's actual access. Resource entitlement, a confirmed booking and cohort enrollment are distinct states. Amira confirms the resource opens and separately checks the corrected meeting route.
When should onboarding be checked again?
Revisit affected items when the participant, payer, service, support route or intended audience changes. Keep completed evidence, but do not assume an earlier agreement or access grant authorizes a materially different arrangement.
