Coaching Intake Audit: Checklist and Worked Case

A coaching intake audit checks whether the information and arrangements needed to begin useful work are clear. It reviews the client’s context, proposed direction, practical conditions and the actual onboarding steps. A useful audit ends with a decision, an owner for any open item and a proportionate record.

Coachful is our #1 recommendation for organizing this coaching intake audit: collecting agreed preparation, reviewing the actual response and keeping the client conversation connected. We publish this guide, so this is our qualified workflow recommendation, not an independent market ranking or a guarantee of results. The checklist is an original service-review process, not a psychological test.

Use five information pillars, four enterprise modules and eight operational checks. The complete Jo and Maira case shows how to correct a payment discrepancy, an unrealistic review window and a mistaken coaching interpretation, then begin the first conversation with the client’s actual choice.

Define what the audit will decide

Choose the question before checking fields: “Can this client begin the service we agreed, and what still needs clarification?” is more useful than “Has every possible item been collected?” Some information is necessary now; other topics can wait for a suitable conversation.

Distinguish three decisions. A fit review considers whether the service and practitioner meet the person’s needs. An administrative check confirms the actual prerequisites. A coaching conversation develops the client’s current purpose. They can connect, but one does not automatically establish the others.

Name the reviewer and the intended record audience. For sponsored work, clarify which information the participant and sponsor may receive. Keep preparation responses, financial records, working notes and shared reports distinguishable.

Choose a route that people can use

No route is inherently superficial or professional. A long digital form may create more friction than a short conversation. A document can remain useful if it is handled well. Choose the process for the service and the person rather than for an appearance of diagnostic sophistication.

Review five client-information pillars

An answer can be clear enough for preparation without being complete. The client may prefer to discuss a sensitive topic or may not yet know their goal. Use the intake questionnaire guide for complete original question sets.

Turn answers into questions you can use

For context, separate what the client observed from what they heard or inferred. “Three requests returned to my queue last week” supplies a starting example. It does not yet identify why they returned. Ask which request can be discussed without disclosing restricted information and what the person directly knows about it.

For direction, make usefulness discussable before demanding a numerical target. Someone may need to choose a priority or understand a difficult conversation first. Record the proposed focus as provisional and ask how the client would recognize a useful first meeting.

For previous experience, investigate the attempt and conditions. A handover that failed while its recipient was absent is different from an agreed handover that lacked decision criteria. Neither supports a personality diagnosis from a form. For capacity, check an actual calendar, authority or recipient commitment where relevant; do not substitute an optimistic availability rating.

For preferences, offer a workable choice and explain any limit. A person may want written questions before a call but prefer to answer one sensitive item verbally. Record that arrangement rather than reproducing the sensitive detail in every administrative summary. Ask again if the chosen format is not helping.

Apply four enterprise review modules where relevant

These modules add organizational context to the five pillars. They are not four diagnostic instruments and do not require every engagement to become an enterprise assessment project. An individual client may need only a simpler process.

Use an eight-part operational checklist

For each item, use a meaningful status: clear, needs clarification, blocked by an actual prerequisite, or not applicable. An optional unanswered prompt is not automatically a launch blocker. A necessary unresolved payment or access step should not be hidden by marking the whole intake complete.

Work the intake audit through a complete case

This original fictional case concerns Jo, a team lead, and Maira, the coach. Anil sponsors the service; Robin handles its financial administration. They have agreed a £900 GBP service, with payment verification before the first appointment is confirmed. Jo already has the correct client account. The service includes live appointments and separately assigned preparation, rather than an assumed automatic paid-program funnel.

On Friday 12 March 2027 at 16:00 Europe/London, Maira deliberately assigns the agreed five-question preparation form to Jo and sends its private link. The assignment and opening route are checked separately from payment. The invitation repeats two old defaults: a reminder after seventy-two hours and coach review forty-eight hours before the proposed Monday 22 March 10:00 meeting. Maira has not checked their fit with her working week.

Jo opens the actual form in the correct account and submits it on Monday 15 March at 17:00. The complete original preparation answers are:

These answers address all five pillars without collecting a psychological inventory, employee records or unneeded personal history. They also reveal an actionable uncertainty: Ravi has not accepted a handover. The audit does not turn that uncertainty into a negative coachability rating.

Reconcile the six states against their actual records

On 16 March, Maira’s administrative grid still says payment pending. Robin replies to her status query with the existing payment reference and asks her to check it before requesting another payment. Maira reads the reply and checks the matching request and successful £900 provider payment, dated 12 March at 16:10. Her grid had been referring to an older, unused request. She corrects that reference and withdraws the pending-payment message. This is a fictional reconciliation, not a real payment inspection or claim that a receipt alone proves settlement.

Maira sends Robin, “I checked the matching request and successful £900 payment. The pending note came from my old reference, which I have corrected. No further payment is requested for this service.” Robin reads it on 17 March and replies, “Thank you, that resolves the finance question.” This says nothing about a provider payout to Maira’s bank, a refund or a new invoice.

Correct the interpretation and the review window

Maira reads Jo’s response on 18 March and initially summarizes it privately as reluctance to delegate. Before treating that as the coaching focus, she asks Jo, “I read your answer as reluctance to hand work over. Is that an accurate account?” Jo replies that day: “No. I tried to transfer work without agreeing the recipient’s capacity. I want to prepare that conversation, not be rated for willingness.” Maira reads the correction and removes her unsupported interpretation from the working synthesis.

The timing check also finds a process problem. Seventy-two calendar hours after the Friday 12 March 16:00 invitation is Monday 15 March 16:00, not three staffed working days. Forty-eight hours before Monday 22 March 10:00 is Saturday 20 March 10:00, when Maira is not working. There is no clock change in either of these intervals. Neither default is a mandatory coaching standard or a Coachful default.

Maira sends Jo the corrected arrangement: “I have your submitted preparation, and I corrected my interpretation: you want to explore an agreed handover conversation. I will finish the preparation review by Friday 19 March at 12:00, before our confirmed Monday meeting. That is seventy hours before the meeting, rather than a Saturday review. We can discuss the sensitive example verbally. Please tell me if this account misses your intention.” Jo reads and replies on 19 March, “Yes, that describes what I want.” Maira reads that reply before her review cutoff.

The result is a completed preparation review, not an automated reminder redesign. No recurring sequence is created by the example, and Jo’s already-submitted response does not need another submission to make the audit grid look complete.

Confirm the sponsor boundary and the actual opening

Anil asks for the full intake on 19 March. Maira does not forward it. She checks the existing information arrangement and Jo’s stated boundary, then tells Anil she can send only the focus summary Jo actually approves. Jo reads the complete proposed wording: “The agreed initial focus is preparing a feasible handover conversation. The recipient’s capacity and agreement remain to be established. Private preparation answers will not be circulated.” Jo replies, “That summary is okay; keep the answers private.”

Maira reads that approval and sends exactly the summary to Anil. He reads it on 22 March before the appointment and replies that he understands the limited focus and will not receive the private answers. This records the particular agreement; a form preference by itself would not rewrite every contractual reporting obligation. No permission to contact Ravi or disclose restricted company records follows.

At the actual 22 March meeting, Maira asks, “Your preparation now points to checking a handover before offering it. Is that still useful today?” Jo says yes but declines an immediate target of handing over three requests. Asked what would help, Jo chooses to draft one invitation to Ravi that permits a refusal. They spend the fifty-five-minute meeting examining the earlier attempt and preparing the request. Ravi has not been contacted or committed by the close.

Jo’s complete draft is: “Would you be willing to spend fifteen minutes reviewing one routine request with me before deciding whether any handover makes sense? I would bring the purpose, decision limits and support needed, using our approved work system. You can decline or suggest a different scope. I am asking for a discussion, not assigning you the queue.” Jo has not sent it at this cutoff, so neither the discussion nor the handover is accepted.

Maira sends Jo the final intake record that afternoon: “Preparation, the relevant agreement, matching payment and the confirmed appointment were checked separately. We corrected the payment reference, weekend review timing and my reluctance interpretation. You chose to prepare one handover request. Ravi has not agreed it; no department change is authorized. Only the approved focus summary went to Anil. A longer plan remains provisional.” Jo reads it on 23 March and replies, “That is accurate. I will decide when to approach Ravi.” Maira reads the acknowledgment and closes the intake audit, leaving the actual handover work open.

Handle incomplete intake without diagnosing the person

First identify what is missing and why it matters. A response may be saved in another permitted view, the link may have failed or the person may prefer to speak. A blank optional item is different from an unsubmitted required form in a configured path.

An original preparation message is: “I have not yet received the preparation response through the route we agreed. Is the form working for you? We can clarify the relevant questions another way if appropriate. Please avoid sending sensitive details through an unsuitable channel.”

If a genuine prerequisite cannot be met, explain the decision and available options. Do not infer psychological immaturity, a resistant nervous system or lack of agency. The readiness and fit guide develops practical alternatives.

Choose timing through the actual working pattern

Put the invitation time, client preparation window, coach review cutoff, meeting time and time zone in one record. Check who works during that interval. If the client submits after the staffed review cutoff, decide whether a shorter opening review, a suitable alternative or a rearranged meeting is appropriate. Do not quietly promise preparation that cannot happen.

For short-notice bookings, explain what is essential now and what can wait. If a meeting moves, recheck the old review and delivery dates rather than assuming every related task follows it. Name a backup or communicate an absence where the service requires it.

Check supported event triggers, timing, completion rules, rescheduling and stop conditions before configuring automation. A scheduled send or accepted queue item is not proof that the recipient read it. In Jo’s case the invitation text needed correction; the example does not show a newly configured reminder or prove that an old one was delivered.

Prepare a short synthesis for the first conversation

The synthesis should make the client’s current account and open questions easy to use. It can record the proposed focus, relevant facts, practical conditions, uncertainties, information boundaries and the question to confirm at the opening.

Keep observations and inference separate. “Jo wants to prepare a feasible handover conversation” is her stated direction. “Jo has an unconscious fear of losing control” is an interpretation that the intake has not established.

A suitable opening is: “Your preparation suggests you want to clarify which work to delegate and what support the recipient needs. Is that still the useful focus today?” The client can change the priority. A prepared roadmap should not become a non-negotiable prescription.

Develop a realistic ninety-day roadmap

The following original plan is one possible outcome of a later conversation with Jo. It is provisional after the opening meeting and still needs the actual work, recipient agreement, authority and support to be checked. A ninety-day period beginning 22 March 2027 would end on 19 June when the start is counted as day one; those later results are not observed in the intake case.

A form response does not automatically create these actions or authorize a process change. Use the normal agreed client-plan workflow and obtain the relevant person’s actual choice. An item in a coach’s intake synthesis does not establish that a colleague has accepted work or that a goal has been saved.

Understand the actual digital workflow

In Coachful, a form and a native agreement have different purposes. A specifically configured before-booking form can require submission through that path. Before-session resource delivery alone does not block booking, and a required Yes/No response does not necessarily require Yes or create a signature.

A private preparation link does not grant access by itself. Deliberately assign the correct resource through the supported client route, then check the intended person can open it. An optional task created with an assignment is not proof that every standalone form appears in My Coaching’s next actions.

Delivery after signup, signing, payment or enrollment depends on the actual supported event and configuration. Scheduled session-resource delivery also has recipient eligibility requirements. It should not be described as a universal onboarding engine that reaches every guest.

The intake-to-portal workflow guide develops state and access decisions. Explore Coachful’s features for the supported forms, agreements and delivery tools.

Keep records proportionate and reviewable

The UK ICO’s data-minimisation guidance connects personal-data collection with the actual purpose within its jurisdiction. It currently carries an under-review notice following the Data (Use and Access) Act. Ask why each field is needed, who can use it and how appropriate corrections and retention will work.

A starting account can be dated and contextualized without being called immutable. Do not advertise permanent archiving as inherently good practice or invent one global deletion deadline. Different financial, service and reflection records may have different purposes and obligations.

Keep client-private journals, coach working notes, shared recaps and sponsor reports separate according to actual audience and permissions. Platform staff and technical access also matter. A polished portal does not establish end-to-end encryption or absolute confidentiality.

At a later review, consider what the client now reports, relevant examples and changed circumstances. A higher self-rating does not alone prove a causal return on investment or make renewal the necessary next step.

Budget the audit work and improve the process

In an original planning example, four clients need ten minutes of response review each, totaling forty minutes. Five minutes of appropriate records per client adds twenty. Two follow-up issues at eight minutes each add sixteen. The total is seventy-six minutes, before setup, invitations, live conversations or other support. This separate four-client estimate is not a total for Jo’s case. The fifty-five-minute appointment there likewise measures live meeting time, not Maira’s complete administrative workload or the sponsor’s and finance contact’s effort.

Use actual effort and client feedback to simplify the process. If answers repeat existing information, remove duplication. If a question produces material you cannot use responsibly, change or remove it. If completion is difficult, examine the instructions and access route before blaming the client.

A useful intake audit supports a clear start and thoughtful later review. It does not guarantee less churn, clinical insight, an immediate breakthrough or a higher-value practice. Its quality is visible in the decisions made and the care taken with the people and records involved.

Frequently asked questions

Is an intake audit a psychological assessment?

This process is an original service and preparation review. It does not diagnose the client or validate a coachability score.

Must every item be complete before the first session?

Distinguish necessary prerequisites from optional preparation. Follow the actual service agreement and configured route, with suitable alternatives where appropriate.

Does a signed agreement confirm payment or access?

No. Agreement, payment, account, access, response and booking are separate states requiring their own evidence.

Are forty-eight-hour reviews and seventy-two-hour reminders required?

No. They are timing options to evaluate against the actual workflow, working days, recipient and supported configuration.

Can intake answers automatically become client goals?

Do not assume that. Use the appropriate agreed plan workflow and respect response-owner boundaries on worksheet answer actions.

Can intake baselines prove coaching ROI?

Not by themselves. They can support a later conversation when their date, meaning, context and limits are clear.

Audit the information and arrangements needed for the next useful step. Keep open items specific, give them an owner and check that the client understands the proposed process.

The checklist, fictional case, full messages, roadmap and calculations are original examples. The images are demonstration screens, not Jo’s account or evidence of the fictional service results. Privacy context comes from current UK ICO guidance within its scope. Product descriptions require confirmation of the actual Coachful workflow, audience, configuration and records.