# Client onboarding automation for professional-services SMEs

> Onboard an accepted client with a document checklist, a restricted workspace and a delivery handoff. Do not auto-accept terms or skip professional checks.

Source: https://www.fyadvisers.com/blog/client-onboarding-workflow-professional-services/  
Author: Fiona Wang, FYAdvisers  
Published: 2026-11-08  
Last updated: 2026-11-08

Client onboarding automation connects an engagement you have already accepted to the people who will deliver it. It can track required information, open a controlled workspace and remind the team about gaps. It should not accept contractual terms by itself, and it should not complete a professional check that a qualified person must make.

This is not lead capture and not a CRM shortlist. Those sit with [CRM implementation](/services/crm-implementation/) and with the firm’s own sales process. Staff joining the firm are a different checklist: [employee onboarding](/blog/employee-onboarding-workflow-automation-singapore/). Regulated identity or anti-money-laundering procedures are not specified here. If your profession requires them, document that procedure with someone qualified, and let the workflow point at it rather than invent it.

## The handoff from the commercial record

Define the event that means “we may prepare delivery”. A practical set is: accepted scope, an engagement reference, the client entity, an authorised client contact, the service owner and the start condition. A proposal that has not been accepted does not open the workspace and does not email a document list that assumes you are instructed.

If the commercial record and the delivery record disagree on the entity name, stop. The acceptance test is a contact attached to the wrong entity. Files for Company A must not become visible inside Company B because the contact’s email matched.

## Ask only for documents the service uses

Write the checklist from the service you actually sold. A company secretarial engagement and a software implementation do not want the same pack. For each item, record why it is needed. Avoid collecting identity documents by default. The PDPC’s [Key Concepts guidelines](https://www.pdpc.gov.sg/-/media/Files/PDPC/PDF-Files/Advisory-Guidelines/AG-on-Key-Concepts/Advisory-Guidelines-on-Key-Concepts-in-the-PDPA-17-May-2022.pdf) cover protection, retention and the point that business contact information is not a universal exemption. A passport scan “for the file” is personal data with a purpose you must be able to state, access you must limit, and a retention decision you must make. The workflow can enforce the limit only if you have written it down.

## Received is not verified

| Status | Meaning |
|---|---|
| Requested | The item is on the checklist. Nothing has arrived |
| Received | A file is stored against the right entity. It may be the wrong year, the wrong company or incomplete |
| Verified | The responsible professional has accepted it for this engagement |
| Rejected | A reason is stored. The client can be asked for a replacement. The old file is not described as verified |
| Waived | A named person records why this engagement does not need the item |

An uploaded file that is merely received must not tick the project as ready. The acceptance test is that case.

## Workspace, tasks and billing at the agreed stage

Create the client workspace, the internal task list and the billing record when the start condition is met, not when the first file arrives. Do not send a welcome message that attaches confidential documents to an address you have not confirmed as the authorised contact. Reminders are drafts or they use wording the service owner has approved. The team controls anything that interprets the engagement.

Scope that changes after the checklist exists reopens the items the change affects. A paused engagement stops client reminders and leaves access in place only as the agreement requires. Duplicate contacts are merged by a person, not by identical display names.

[Client portal](/services/client-portal-development/) work is justified when the client must submit files and see only their engagement. A shared drive with a mailed password is the design you are replacing. [Workflow automation](/services/workflow-automation/) can carry the status changes. It should not be the place the files live if that tool’s run history is broadly visible. Microsoft and n8n both treat run history as operational, not as a client archive. Put the file in the workspace you intend to keep.

## What to ask a supplier

Ask what event activates the project, how you will prove a client cannot see another client’s files, and which checks remain a manual task a person must sign. Ask who owns the tenant, how you export the engagement, and how a deletion or access request is carried out if the client is an individual. Compare the CRM or practice system first.

Illustrative scenario, not a client engagement: a consultancy treats a signed engagement as the trigger. The client uploads files to a workspace that a permission test has shown is limited to that client. The service manager marks each item verified or rejected. The project does not activate on upload. Reminders are prepared for the team to send. The workflow does not decide that a professional clearance is complete.

This is an operational design guide. It is not legal, regulatory or professional advice, and FYAdvisers is not a law firm. To turn the checklist you already email into statuses, use the contact form or WhatsApp +65 9071 3976 ([chat](https://wa.me/6590713976)).

## Frequently asked questions

### What event is allowed to activate the project?

The event you name: for example the service owner confirms the checklist is sufficient and the commercial record is accepted. A file landing in a folder is not that event.

### Can a client see only their own files?

Yes, and you should test it. A second client user, and an internal user on another account, must fail to open the file. Shared links with “anyone in the company” fail this test.

### Which checks stay manual?

Any check that needs a qualified person: conflict clearance, professional independence, licensing conditions, or sector rules you have been advised apply. The workflow can show that the check is outstanding. It should not mark it passed.

### Should we build a portal if the CRM already has a checklist?

Use the CRM or practice system if it can restrict files, record verification separately from receipt, and export the engagement. Build a portal when those controls are missing, not because a portal looks like a product.
