The SOW is signed. The consultants cannot get into the building.
A client signs a statement of work and wants the team on site on Monday. Then their procurement portal asks for a supplier registration: company details, bank details, insurance certificates, modern slavery statement, data protection policy, information security questionnaire with a hundred questions, financial accounts. Separately, their IT team needs each consultant's details for laptop and system access, and security wants background checks for anyone touching certain data.
Your operations lead spends days finding the latest versions of each document, answering security questions that are slightly different from the last client's, and chasing consultants for their details. The start date slips a week.
Why onboarding takes so long
- Every client asks for similar documents in their own format and portal.
- Current versions of policies and certificates are hard to find.
- Security questionnaires are answered from scratch each time.
- Consultant details and vetting are collected separately for each client.
- Nobody tracks which client step is waiting on whom.
Timing is the other issue. Onboarding usually starts when the SOW is signed, but most of the paperwork could start earlier, as soon as the client indicates they intend to proceed. Firms that wait for the signature lose days they did not need to lose.
What slow onboarding costs
| Delay | Effect |
|---|---|
| Start date slips | Revenue and staffing plans pushed back |
| Consultants waiting without access | Paid time with nothing billable |
| Security answers inconsistent | Credibility with the client's security team |
| Expired certificate sent | Onboarding rejected and restarted |
It also affects first impressions. The client's sponsor is keen, but their procurement and security teams see your firm first through its paperwork. Slow, inconsistent answers give them a poor view of an organisation they are about to let into their systems.
How we build a reusable onboarding pack
- Your standard supplier documents, policies, certificates and accounts are held in one library with owners and expiry dates, with reminders before they lapse.
- Previous answers to security and supplier questionnaires are stored as an approved answer bank, reviewed by the person responsible for security.
- A new questionnaire is matched against the bank, and a language model drafts answers from approved text, for your security lead to check before submission.
- Each client's onboarding steps are tracked: procurement registration, questionnaire, contract, consultant access, vetting.
- Consultants complete a single profile once, and their details are provided to each client in the format asked, with their consent.
- Reminders go to whoever owes the next step, internally or at the client.
- The engagement partner sees onboarding status against the start date.
Answers to security questionnaires must be true of your firm. The answer bank helps reuse what is already approved; it does not make claims your firm has not made.
We usually start by gathering your current supplier documents and the last few security questionnaires you answered. Building the answer bank from those is the largest single step, and it pays back on the very next client onboarding.
The week before an engagement, afterwards
Onboarding starts as soon as the SOW is close, using current documents and approved answers. The operations lead tracks steps rather than hunting for files. Consultants have access on day one more often.
Each client's onboarding makes the next one easier, because every approved answer is kept.
Is this slowing your engagements?
- Start dates slip because of supplier or security paperwork.
- Security questionnaires are answered from scratch.
- Finding current certificates and policies takes time.
- Consultant details are collected again for each client.
- Nobody knows which onboarding step is holding things up.