Start from an explicit acceptance step
An enquiry is not the same as an approved client. The workflow needs a clear trigger that confirms onboarding should begin.
We establish who authorises that step and what information must be available. This avoids treating a form submission as permission to create commitments or grant access.
Make the required steps visible
Your onboarding process may involve several people and tools. We map what each person needs to provide and when the next stage can proceed.
The agreed scope can include:
- Creating a project or onboarding checklist.
- Assigning internal tasks and owners.
- Preparing agreed folders or records.
- Requesting information the team needs.
- Sending reminders for outstanding actions.
- Flagging work that is blocked or incomplete.
Permissions and customer-facing messages are agreed as part of the brief.
Keep missing information in view
A useful workflow recognises when something has not happened. If a required detail is absent or a connected system fails, the next step should not simply be marked complete.
We plan review paths and alerts around the process. The team needs a clear way to identify the issue, recover the work and continue manually where required.
Hand over a process your team can own
Documentation explains the trigger, connected systems, important rules and responsibilities. We identify who can pause or change the workflow and what ongoing support covers.
Running costs and software requirements are considered separately from the build fee. New steps or changes to the business process can then be scoped explicitly.