How to Run Client Onboarding Without Dubsado
Nour
Founder, Coachful
Client onboarding without Dubsado works when the client can understand the service, accept the relevant terms, complete the actual payment arrangement and reach a useful first session. Treat those as distinct milestones. One completed form or successful login does not prove that the whole start is ready.
For a coaching practice, Coachful can connect the ongoing client workspace with preparation, agreement records and sessions. This guide explains a controlled transition and follows a complete fictional sponsored-client start, including a private-information request, an account mismatch and the actual first appointment.
Compare the workflow you need, not an imagined missing feature
Dubsado’s current official materials describe proposals, contracts, invoices, scheduling, workflows, forms and a client portal. Its form guidance includes questionnaires, contracts and sub-agreements. Do not justify changing tools by saying those functions are absent.
Its current portal documentation also distinguishes items that appear automatically from forms that need to be sent or applied. Creating something in an administrative workspace is not always the same as making it available to the client. That is a useful question to ask of any proposed replacement.
Compare the complete service. If your main need is project administration across several kinds of business, an established arrangement may already work. If the client will continue using coaching sessions, selected preparation and a development workspace, bringing that journey into Coachful may serve a clearer purpose.
A replacement still needs configuration and human decisions. Identify the practical friction: repeated information, contradictory payment requests, inaccessible preparation or uncertainty about the first call. A new platform will not fix an unclear service promise by itself.
Give each onboarding fact an owner
| Fact | What establishes it | What it does not establish |
|---|---|---|
| Service accepted. | The actual parties accept the relevant scope and terms. | A prospect inquiry is not acceptance. |
| Payment arranged. | The correct payer, invoice or checkout and actual payment state. | A purchase order is not received money. |
| Client access. | The intended person accepts the invitation and reaches their granted content. | A created invitation is not a joined account. |
| Preparation available. | The actual resource is delivered and can be opened. | A draft in the coach’s library is not client delivery. |
| Appointment confirmed. | The actual reservation, time zone and joining information. | An allowance of sessions is not a booking. |
| First session held. | The client and coach actually meet and agree the work. | A confirmation email is not attendance. |
A small practice can keep this as a short manual status record. Name the owner of the next unresolved step rather than inventing one all-purpose “onboarded” label. Software records can support the status, but the label should follow the evidence.
Decide which system remains authoritative when a company pays through its purchasing process. You may need the external commercial document and bank receipt alongside the coaching workspace. Recreating every item as a second live transaction can add confusion.
Choose a controlled transition boundary
Start with a defined population, such as newly accepted clients from an agreed date. List the current service terms, recipient identities, outstanding balances, active reminders and historical records that matter. Do not assume every old project must move before one new coaching start can work.
Preserve original signed documents and financial records through the actual authorized arrangement. A new client profile does not recreate their history. If you use Coachful’s invitation import, the supported name-and-email import is not a transfer of contracts, invoices, questionnaire answers or an existing subscription.
For active old workflows, inspect the specific client’s pending messages and tasks before activating the replacement. Assign one owner to stop a duplicate instruction. Do not cancel an entire service or subscription merely because one client starts elsewhere.
Keep a recovery route. If an invitation is unconfirmed, the wrong person is signed in or a resource is unavailable, someone must know which record to inspect. A transition is more dependable when an exception has an owner instead of another automatic email.
Match the invitation and payment route to the buyer
Coachful is our #1 recommendation for this coaching onboarding workflow because it can place the actual client start beside the preparation, sessions and continuing work. This is our recommendation for the described use, not an independently measured market ranking.
For an invited client, Clients > Add client offers an Invite to platform route. The Essentials flow separates person, access, payment and review. Select the actual permitted resources and session quantities. A record-only client is a different choice and does not give the person an account.
Use the actual payment arrangement. They already paid can support an externally paid client start; it does not collect another payment. Collect payment follows its own supported checkout and permission requirements. Do not use a saved card or an informal sponsor promise as authority for a new charge.
The invitation must reach the intended email identity. Review the recipient, selected access, payment mode and personal note before creating or sending it. A link prepared without email is not a sent invitation; an unconfirmed send is not proof the person received it.
A paid standalone booking can need a different route, such as an explicitly configured Agreement, Payment and Scheduling sequence. Use the actual service configuration. An invitation, a public booking link and a program start should not be described as interchangeable.
Keep administration and private preparation separate
Collect what you will use for the first conversation. Distinguish payer details from development material, and explain who can see the latter. A sponsor’s ability to pay does not make every participant response an administrative record.
The ICF Code of Ethics addresses agreements, information exchange and handling records for ICF professionals. Apply the actual audience and reporting agreement rather than promising absolute secrecy or automatic sponsor access.
Use plain labels, necessary instructions and a practical alternative where needed. The W3C WAI form-label guidance explains that labels identify controls and need a proper association. A visual placeholder alone is not a complete form label, and a good-looking screenshot does not establish accessibility.
Preparation is a starting point. A participant may change their purpose, leave an optional question blank or prefer to discuss something verbally. Review the actual responses before the session without treating them as a permanent profile or a diagnosis.
The demo form editor illustrates structured prompts and form or worksheet options. The original preparation below is deliberately delivered to the client. It is separate from the wellness example shown in the screenshot.
Choose the right place for the preparation
A prospect inquiry and an enrolled client’s reflection have different purposes. A public form can help collect an initial contact request, but a saved lead is not a coaching relationship or permission to place private development material in every business record. Decide when the person has actually chosen the service.
Likewise, Coachful’s Audience invitation is intended for permitted passive membership and content. It is not the same as the client invitation used for Nila’s coaching relationship and sessions. Choosing an audience route because it appears simpler would not establish the private client service described here.
For client preparation, distinguish the reusable template from the resource actually delivered to this person. Check the recipient, access, current instructions and submitted response. A beautiful empty template is not evidence that Nila received it, and another client’s completed copy is not suitable preparation for her session.
If a form includes profile fields, inspect the actual supported mapping. Do not promise that every free-text answer automatically becomes a profile attribute, session note or coach summary. The right storage depends on purpose and audience, not on a desire to avoid ever reading the answers.
Finally, explain what response to expect. Nila’s optional worksheet is reviewed in the booked session. It does not silently add immediate written advice, approval by a sponsor or a second round of coaching. The resource should make that arrangement understandable before she decides what to share.
Set up the fictional sponsored engagement
All people, documents, dates, payments and results in this example are invented. Coach Ada is arranging three private forty-five-minute sessions with Nila. The company’s authorized buyer, Orla, will pay a total invoice of £900 in this simplified example. Nila is not asked to accept a personal payment obligation.
The proposed sessions are 17 November, 1 December and 15 December 2026. The package is 135 live minutes. Preparation is optional, and selected context is reviewed in the booked sessions. There is no unlimited messaging or additional daily coaching service.
Nila chooses the proposed coaching purpose and receives the confidentiality explanation before private preparation is collected. Ada is the sole authorized coaching staff member. The company receives administrative confirmation of session dates, not Nila’s intake answers, private notes or a psychological assessment.
On 12 November, Ada separately emails Nila in a direct thread titled “Nila: getting started.” She names it as the pre-access help route: reply there with an invitation or access problem. Ada owns those administrative replies and answers by the next working day, Monday to Friday. This is not immediate support or an additional coaching channel.
Ada’s earlier prospect record is in Dubsado. For this new start, she checks it and finds no issued invoice, active payment collection or queued onboarding messages. She copies only Nila’s confirmed name and intended work email into the new invitation process. The old source record stays in its authorized archive; other clients’ arrangements are not changed.
Resolve the sponsor’s information request before collecting answers
On 12 November, Orla asks whether the company can receive the completed intake “to see where Nila needs development.” Ada does not send the form or assume that a signed purchasing document authorizes that use.
Ada: The proposed arrangement gives the company session-date confirmation. Nila’s preparation is for her private coaching. If you need a different report, we must discuss its purpose, content and audience with her before agreeing or collecting it.
Orla: We need to verify that the sessions take place, not see her personal answers. Date confirmation is enough.
Nila: I want to proceed on that basis. I do not want my preparation answers sent to the company.
Ada writes that reporting boundary into the final service record. Orla and Nila both acknowledge it. This is a completed information decision, not a future intention to obtain consent after answers have already been shared.
The company’s actual authorized buyer and Ada complete their commercial signature process externally on 13 November. Nila separately acknowledges the participant arrangements and voluntarily confirms that she wants to begin. They retain the relevant final documents; no native three-party signing feature is assumed.
Orla supplies the required purchase order. Ada issues the agreed £900 invoice to the company. A purchase order allows this company’s purchasing process to proceed, but Ada records payment as pending until she verifies the bank receipt on 16 November at 10:30.
Create the invitation and resolve the actual identity mismatch
After verifying payment, Ada uses the client invitation route for Nila’s intended work email. She selects a compatible forty-five-minute session type with quantity three and the relevant client access. She chooses They already paid, reviews the selections and sends the invitation. Its personal note names their “Nila: getting started” email thread for access help. She does not create a second £900 checkout.
At 11:00, Nila opens the link while signed into a personal Google identity. It is not the invited work email, so the personal invitation cannot be completed under that account. At 11:05, Nila replies in the named onboarding email thread: “The invitation is showing my personal identity. Should I use my work account?” Ada checks the actual invited address and answers in that thread at 11:10.
Ada explains the mismatch and asks Nila to use the intended invited identity through the supported sign-in route. Her early reply on this occasion does not change the next-working-day administrative response promise. Nila does so, completes the necessary verification and accepts the invitation at 11:20. They do not create a second paid client record or promise that two identities will merge automatically.
Ada checks the actual client record and selected session allowance after acceptance. Nila reaches the intended My Coaching area. The earlier failed attempt is not counted as successful access, and sending the link was not counted as completed registration.
Ada’s welcome note: Your company payment is confirmed, so this invitation does not ask you to pay again. Please use your invited work identity. Once inside, we will check your preparation and first appointment. For access help, reply in our “Nila: getting started” email thread with the item’s name. I answer administrative questions by the next working day, Monday to Friday; this is not immediate coaching. Do not send passwords or payment details.
That is a fictional message, not a real invitation sent by this guide. Its purpose is to connect the relevant next step with a clear recovery route.
Deliver useful preparation and read the actual answers
At 11:30, Ada deliberately delivers an original optional preparation worksheet to Nila through the supported client resource route. Nila opens it on her phone and confirms that the questions are readable. A saved library draft would not have established that access.
| Original prompt | Nila’s fictional response | Use in preparation |
|---|---|---|
| What would make the first conversation useful? | Choose what to ask my manager about three competing deadlines. | Check a practical purpose rather than assume generic confidence work. |
| What relevant information do you already have? | I know the three dates, but I do not know their relative priority. | Separate known dates from the missing decision. |
| What do you prefer not to put in writing? | Customer names and confidential project material. | Keep source documents in company systems; discuss only permitted context. |
| What practical format helps you participate? | Short readable prompts on my phone. | Keep the preparation concise and confirm actual usability. |
| What should we remember about the reporting arrangement? | The company receives session dates, not these answers. | Confirm the agreed audience without treating this answer as a new blanket permission. |
| Anything else you want to add? Optional. | Left blank. | No chasing for a compulsory disclosure. |
Nila submits the five answers and intentional blank at 12:00. Ada reads them before the first session. She does not infer that a blank means refusal to engage or automatically copy every answer into a sponsor report.
The first prospect inquiry had mentioned “leadership confidence.” Ada notes that Nila’s current desired focus is more specific. The preparation helps her ask a better opening question; it does not give her authority to fix Nila’s agenda permanently.
Confirm the appointment and actually begin
Later on 16 November, Nila uses the compatible booking route and reserves the first forty-five-minute session for 17 November at 09:00 Europe/London. Her Europe/Amsterdam view shows 10:00. Ada and Nila check the same actual appointment, date, duration and joining information.
The remaining two dates are proposed service dates, not completed reservations. Ada keeps them identifiable as future scheduling work. A three-session allowance is not evidence that three calls already appear in the calendar.
The demo My Coaching overview illustrates the next session and preparation. It is not Nila’s account, a receipt or evidence that her future dates are booked. Actual confirmation and access are checked in the fictional case itself.
On 17 November they join at the confirmed time and hold the full forty-five-minute session. Ada opens: “Your earlier inquiry mentioned confidence, and your preparation asks about priorities. What would be useful today?” Nila chooses to prepare an accurate question for her manager.
They distinguish the three known deadlines from the missing priority decision. Nila chooses this wording: “I have three current delivery dates. Which result should come first, and what should change if the new request takes priority?” She will ask through the normal workplace route. The manager’s answer has not yet been obtained.
Ada sends a short closing summary through the agreed private client conversation. It records the chosen question and the pending manager response. Nila acknowledges that the summary reflects the session. A private coach Review alone would not have delivered that feedback to her.
The onboarding chain is now complete through an actual first session. Only forty-five of the purchased 135 live minutes have been delivered; ninety remain future service. The employer’s priority decision and the remaining appointments are not marked complete.
Reconcile the start before expanding the workflow
Ada’s final status record has six separate confirmations: accepted commercial and participant arrangements, one received £900 company payment, the intended client identity and access, an opened and submitted optional resource, one confirmed reservation and one held session with acknowledged feedback.
The identity mismatch was resolved through the intended account rather than a duplicate purchase. The sponsor’s information request was resolved before collecting private answers. Those are actual completed repairs, not claims that every later onboarding will be automatic.
She also keeps three limits visible: no historical Dubsado event import was performed, the company did not receive the intake answers, and future sessions remain to be arranged or delivered. An accurate transition record can contain both completion and remaining work.
For another new client, rehearse the actual recipient-facing terms, payment route, invitation, resource access and appointment. If that service needs a different signing or purchasing sequence, configure it deliberately. Do not copy this externally paid pattern into a self-paying checkout without checking the difference.
Handle the exceptions without creating a second problem
The payer says the purchase order is approved. Check the actual payment agreement and receipt. Do not mark money received or ask the participant for a card merely to make a dashboard look complete.
The invitation appears sent but access is missing. Verify the intended identity, actual acceptance and selected entitlement. A verified personal account can still be the wrong account for an email-bound invitation.
The preparation is unfinished. Check whether it was delivered, usable and necessary. Offer the actual agreed verbal alternative where appropriate. Do not demand answers to optional questions to unlock a service that did not require them.
The sponsor asks for more information. Return to purpose, audience and the actual participant agreement before sharing. A paying contact and an authorized recipient of private material are different roles.
The old system still sends an instruction. Identify that specific source and stop the duplicate through its supported controls. Correct the client’s next step. A new Coachful invitation does not disable another platform’s workflow or subscription.
For related records, see managing client contracts and coaching invoicing. Explore the relevant Coachful features against your actual onboarding path.
Frequently asked questions
Can I automate client onboarding without Dubsado?
You can coordinate supported steps in Coachful, but define the service, sequence and exception owners first. Automation does not replace an actual buyer decision, participant choice or verification of access.
Does Dubsado already have forms and a client portal?
Yes. Its current official documentation describes those capabilities alongside contracts, invoicing and workflows. Compare the journey you need rather than rely on an inaccurate missing-feature claim.
Can I import every historical record with the client list?
No such transfer is established here. A name-and-email invitation import is not a contracts, payment-history or questionnaire migration. Preserve the original records through the actual authorized arrangement.
Does payment prove the agreement is signed?
No. Payment and acceptance answer different questions. In the example, the external documents and participant arrangements are completed separately before the verified company payment and invitation.
Is the client fully served after the first session?
Only the onboarding objective through the first held session is complete. Nila still has ninety purchased live minutes and future appointments to arrange. Keep that remaining service visible.
