Onboarding a new client without the back-and-forth

A new client signs. The partner is pleased, the engagement letter is out, and now someone has to actually get the firm what it needs to start work. So they open a fresh email and start listing: the certificate of incorporation, the register of directors and shareholders, IDs and proof of address for the beneficial owners, last year’s financial statements, the bank mandates. They hit send, feel productive, and then spend the next fortnight untangling the reply.

Because the reply is never the whole list. It’s the incorporation certificate and one director’s passport. A day later, a scan of a utility bill that’s fourteen months old and won’t do for proof of address. A week after that, “the prior-year accounts are attached” — attached to a message three threads back, in a file named accounts.pdf with no year on it. The client is trying. The medium is the problem.

Onboarding is a document collection problem in disguise

We tend to talk about onboarding as relationship work, and part of it is. But the operational core of onboarding a new Client is collecting a known, finite set of documents — and it’s the same set almost every time:

• Certificate of incorporation and the memorandum and articles.
• Register of directors and shareholders, and structure charts where ownership runs through other entities.
• IDs and proof of address for the beneficial owners, for KYC.
• Prior-year financial statements and the last set of management accounts.
• Bank mandates and signatory details.

You know this list before the client ever signs. It doesn’t change engagement to engagement in any meaningful way. Which means the worst possible way to collect it is to retype it into an email and then chase the gaps by hand — because you’re rebuilding, from memory, a standard procedure you run every time you take on a client.

Send the pack, not the email

The alternative is to treat that standard set as a standing object rather than a fresh email. In Clivanta, you create the Client and the Engagement, then send an onboarding Pack: a reusable set of Request Items, one per thing you need, each with a title, instructions and a sample format already written.

The Client sees a clean list of specific asks, not a wall of prose to parse. “Certificate of incorporation” is one item. “Proof of address for each beneficial owner, dated within the last three months” is another — and because the instruction travels with the ask, the client is far less likely to send you the fourteen-month-old utility bill. Each item has its own status, its own upload, its own thread. Nothing is buried in a paragraph.

The Pack is written once, at the firm level, and reused on every new client. When you onboard the next one, you’re not starting from a blank email. You’re starting from your own standard procedure, snapshotted into this Engagement so later edits to the template never rewrite what you already collected.

The Client Owner brings in the rest of the team

Onboarding almost never involves a single person on the client side. The incorporation papers sit with a company secretary, the IDs with the individuals, the prior-year accounts with the outgoing accountant or the finance manager.

Clivanta handles this through the Client Owner — the single primary contact you invite first. They reach the passwordless portal by magic link, with nothing to set up and no password to forget, and from there they can bring in colleagues to handle the items that aren’t theirs. The register goes to the secretary, the ID uploads to each director, and everyone works against the same list. You’re not the switchboard routing documents between four inboxes. The Client Owner is your default assignee and escalation point, and the team fills in around them.

That team-visibility model is what turns a “dozen emails to five people” problem into a single shared view of what’s still outstanding.

Let the pre-checks catch the obvious errors early

New clients make new-client mistakes. They upload the parent company’s incorporation certificate against a subsidiary engagement. They send the same passport twice. They attach FY2024 accounts to an FY2025 onboarding.

Clivanta’s AI pre-checks run quietly after each upload and flag these before they reach a reviewer. They classify the document type, extract the document date and entity name, detect duplicates by file hash, and flag a likely wrong entity against the Engagement. The point is not that the AI decides anything — it doesn’t. It never accepts, rejects, or moves a file. It just surfaces “this looks like it belongs to a different entity” so a person at your firm can look before it quietly enters the record. During onboarding, when you don’t yet know the client’s habits, that early flag saves a round-trip you’d otherwise discover weeks later.

Accept to Evidence, and the file is already clean

As each item comes in correctly, you review and accept it. Acceptance promotes the uploaded Document to Evidence on the Engagement record, with your name and a timestamp. By the time onboarding is done, you don’t have a folder of assorted attachments to sort — you have a set of accepted, attributed Evidence, each tied to the specific thing you asked for, with the superseded attempts retained underneath.

That matters most for the KYC portion, where you have to be able to show what you requested, received, reviewed and kept, per beneficial owner. It’s the same discipline we describe in AML/KYC document collection without the spreadsheet, applied at the very start of the relationship. And it generalises well beyond audit and tax — the same onboarding shape works for legal, financial services and any firm that collects a standard document set from a new client.

The first impression is the process

There’s a quieter benefit that’s easy to underrate. Onboarding is the client’s first real experience of working with your firm. If that experience is a messy email thread with three follow-ups and a “can you resend that,” you’ve taught them, on day one, that this relationship runs on chasing.

A clean portal with a clear list teaches the opposite. It says: we know exactly what we need, we’ve asked for it precisely, and there’s one obvious place to put it. The client uploads, sees the item tick over, and moves on. You get a defensible file and a client who now expects the rest of the engagement to run the same way.

Onboarding sets the tone. Make the first ask look like you’ve done this before.