Coaching Client Paid but Paperwork Is Missing: What Next?

A payment arrives, but the agreement hasn't come back. Or the intake form is in your inbox and nobody has reviewed it yet. What should your new client receive now?

Check what is complete, acknowledge what you've received and ask only for the missing requirement. Keep the welcome or first-session decision with someone who can see the current agreement, payment arrangement and preparation record. That gives the client a clear next step without sending them through completed tasks again.

This walkthrough is for an accepted adult client in non-clinical coaching. Set the requirements from your actual service, agreement and professional obligations.

Write down what must happen before each next step

Decide separately what you require before sending the main welcome materials and before beginning the first coaching session. These may be different moments.

For example, a welcome message might contain the link to book the first session. In that process, a missing booking can't be a reason to hold that same welcome. The session still needs a confirmed appointment and a usable joining route before it is ready to begin.

Use the requirements you already have. An agreed payment plan may satisfy your payment requirement without the whole package being paid in full. An optional intake answer can remain blank. If a requirement is unclear, resolve it before building a reminder around it.

For ICF professionals, the ICF Code of Ethics calls for discussing the nature of coaching and co-creating a coaching agreement before coaching begins, including roles, responsibilities, confidentiality and financial arrangements. It does not prescribe one universal welcome-email sequence. Follow the obligations that apply to your practice.

Check the three records separately

Create one short operational record for the engagement. Give it a client reference, service, responsible person and next review time. Then record the status of each required item.

Agreement: Check that it concerns the correct service, uses the current version and has the acceptance required by your process. Keep the evidence in the agreement system.

Payment: Match the actual payment status or approved arrangement to this engagement. An invoice being sent or a checkout page being visited doesn't establish that your requirement has been met.

Intake: Separate received from reviewed. Check that the essential answers are usable and that the coach has read what they need. If something raises a scope question, arrange the appropriate conversation before marking the client ready.

For each item, record a plain status such as waiting, complete or needs review, plus where to verify it. Keep detailed intake answers, signatures and payment credentials out of the operational checklist. ICF's confidentiality and record-handling standards are a useful reference for ICF professionals; configure access around each person's actual role.

Acknowledge the payment and name the actual gap

The client doesn't need silence while you wait for paperwork. Send a brief acknowledgement or missing-item request that accurately describes the next step.

Here is a fictional example. Maya offers leadership coaching. For this service, her existing process requires the accepted agreement, the agreed initial payment and review of essential intake before she releases the main welcome guide. Sam's payment arrives first.

Maya records payment complete. The agreement is still waiting, and intake has been received but not reviewed. She checks that no one has already asked Sam for the agreement, then sends:

Subject: One item before your coaching welcome Hi Sam, I've confirmed your initial payment, thank you. I've also received your preparation form and will review it next. I'm still waiting for the accepted agreement. Please open the agreement link I sent and let me know if you have a question or can't access it. I'll confirm the next step once that and the preparation review are complete. Maya

The names, service rules and message are fictional. In your version, use the verified agreement route and add a deadline only if one has actually been agreed. Avoid another payment request when the payment requirement is already satisfied.

Give the outstanding item an owner and a review time on your side. If it remains incomplete, check for a reply or access problem before sending another request. Follow your agreed pause or escalation process when a personal decision is needed.

Check whether missing really means inaccessible

Ask a practical question: can the client open the document or form using the intended account? A lost email, expired invitation or wrong permission can leave a task looking unfinished.

Life Coach Hub's welcome-package support guidance explicitly covers clients who accepted an agreement but haven't finished intake, as well as lost invitations. It is an example of a provider handling partial completion, rather than evidence about how often coaches encounter it.

Check your own platform's recovery route. Restore access for the intended client and resend only what they need. Don't make a folder public or ask for a password to get someone past a login problem. If the format is difficult to use, agree on an appropriate alternative.

Release the welcome after a fresh check

When the missing item arrives, update that item without restarting the entire process. Recheck the current requirements and any unresolved issue before sending the main welcome.

In Maya's fictional example, the agreement arrives later that day. She verifies it, reviews the intake and checks that the welcome hasn't already been sent. She then sends the guide with one next action: book the first session through the current booking route.

She records the welcome version, sender and send time. The client is still waiting for the session-readiness check because the appointment and access haven't been verified yet.

Keep a separate note if a message fails. Before retrying, check the address and the actual send result. Treat the retry as recovery of the same welcome, so it doesn't also create a second set of onboarding requests.

Prevent a repeated signup from sending everything twice

A second submission could be a retry, a new engagement or another person with similar details. Compare the verified client, service and active engagement before deciding.

If it is a retry, use the current engagement record and check what already happened. Keep the history and skip completed message jobs. Avoid deleting agreement or payment records simply to tidy the list.

If the same client starts genuinely new work later, give that engagement its own checklist. A blanket rule that says “welcome this contact only once” may stop a legitimate future welcome.

For automated setups, ask whoever configures the tools how two close-together events are handled. Two runs could both check “welcome not sent” before either records a result. The setup needs a dependable way to allow one send, or one person should control that step manually.

Test the order that doesn't go neatly

Use controlled records and recipients to test these cases:

• Payment arrives first: record it, keep missing requirements open and avoid another payment request.

• Intake arrives but is unreviewed: hold the relevant next step until the coach checks it.

• The signup arrives twice: keep one active engagement and one eligible welcome.

• The same client buys a new engagement: start the new checklist without losing the older history.

• A booking changes after welcome: recheck its date and access without repeating the welcome.

• The engagement pauses while a message waits: verify that the affected message stays stopped through its former due time.

Write the expected status and message count before each test. Then compare the actual records and send history. Leave failed or untested cases open rather than assuming the normal path covers them.

Wix's automation troubleshooting guidance explains that once-per-person limits can prevent repeat runs, delay changes can affect pending work and triggers don't run retroactively. Check current apps, permissions and account capabilities. A flow can only verify a requirement if it can read the information that establishes it.

Keep a small manual queue when a connection fails

If a tool cannot retrieve the agreement or payment status, leave that check unresolved and give it to the responsible person. Use the original records to decide the next safe action.

Record any manual message against the same engagement before the automatic process resumes. Otherwise, recovery may send a welcome that someone already sent by hand.

A useful handoff can be one sentence: “Payment verified; agreement awaiting review; Maya will check it tomorrow morning; no new payment request.” Include the actual review time and timezone where needed, and share only records the receiving person needs.

Build around the next real client

Choose one coaching service and map its actual requirements first. Keep the checks short enough to maintain and specific enough that another person can see what happens next.

Marketing PMP's New Client Onboarding Workflow Kit provides a fillable client tracker, missing-item and duplicate-signup branches, handoff pages, a manual fallback and ten acceptance tests. It helps you coordinate your existing agreements, intake and booking process. It does not install an automation or supply a new coaching contract.

If you need a starting point for the client-facing welcome copy, Your Next Client's Welcome Pack is available free by email when you subscribe through the resource page.