A client onboarding process flow is easy to draw and hard to keep true, because the version on the whiteboard shows the happy path and the version that happens is mostly waiting. This page describes the four stages every workable flow has, marks where the delays actually accumulate, and explains how to size the thing before you draw it, so the diagram matches the work rather than the intention. It is written for the person who will have to run the flow, not the person presenting it.
The four stages
Accept, collect, set up, start. Accept is the internal decision that this client is one you take and on what terms. Collect is everything you need from them, which is where the calendar time goes. Set up is everything you do without them, accounts, folders, access, introductions. Start is the kickoff and the first real piece of work. Every flow that works maps onto those four, whatever the boxes are called.
Where the waiting is
Almost never in your own steps. It is in collect: the document requested and not returned, the signature waiting on someone who is travelling, the access nobody can grant until a person comes back. Drawing the flow as a chain of your actions hides this, which is why so many flows look like they should take three days and take three weeks.
Size it before you draw it
Count the steps, count the documents you request, decide the window you will promise, and divide. If your target is twenty-one days and your flow has twelve steps, each step gets under two days, and any one of them that routinely takes a week is the flow's real shape. The free checklist worksheet on this site does that arithmetic from your own numbers.
Keep one flow, not one per client
The temptation after two awkward clients is a branch for each. Branches are how a flow stops being followed: nobody can hold six variants, so people revert to memory. Keep one flow with a place to note the exceptions, and change the flow only when the same exception has happened three times.
Questions people ask about client onboarding process flow
How many steps should a client onboarding flow have?
However many you actually do. The number that matters is not the count but the days each step gets inside the window you promise, which the worksheet returns from your own target and step count.
Should the flow include the sales handover?
Yes, as the first step. The handover is where the promises made during the sale become the obligations of onboarding, and a flow that starts after it inherits surprises.
Where do the documents belong on the flow?
Beside the step that needs them, not in a pile at the start. Requesting everything on day one feels efficient and produces one large unanswered email instead of several small answered ones.