This guide explains how to design and scale workflows in Legl to support firm-wide growth and compliance. It is intended for teams setting up or optimising onboarding processes across departments.
What this covers
This article outlines:
How to design workflows aligned with your firm’s risk policy
How to structure onboarding journeys for consistency and scalability
How to manage firm-wide vs department-specific workflows
Key workflow components, including CDD and document collection
How to analyse and improve workflow performance using reporting
How this works at a high level
Designing workflows in Legl involves mapping your client onboarding journey and translating it into structured, repeatable steps.
At a high level:
You define what information and documents are required at each stage of onboarding
You structure workflows into clear phases (e.g. 1A, 1B, 1C) to guide teams
You build workflows using configurable steps such as:
Sending documents
Collecting signatures
Running CDD checks
Collecting proof of address
You create variations of workflows to handle different scenarios (e.g. high-risk clients, in-person verification, department-specific needs)
You monitor performance through workflow reporting to optimise completion rates and efficiency
Workflows act as fixed templates, ensuring consistency, compliance, and preventing teams from skipping required steps.
When you would use this
You would use workflow design and scaling when:
Setting up onboarding processes for the first time
Aligning workflows with your firm’s risk appetite and compliance requirements
Expanding processes across multiple departments
Standardising document collection and verification steps
Improving onboarding speed and completion rates
Key things to be aware of
Important: Workflows are fixed templates
Users cannot skip steps within a workflow
If a scenario differs, you must create a separate workflow variation
Important: Risk policy should guide workflow design
Consider risk levels (high, medium, low)
Decide appropriate CDD levels (basic, standard, enhanced)
Determine when checks (e.g. ID, proof of address) should occur
Important: Sequential steps can impact completion rates
Enabling sequential steps forces clients to complete tasks in order
Disabling them allows flexibility but may reduce control
Important: Proof of address verification may incur additional cost
Verified proof of address is an additional, stackable check
Costs can be passed to the client if required
Note: In-person CDD cannot be embedded into workflows
Teams must follow separate internal processes for this
Where to find this in Legl
You can manage workflows in:
Engage → Workflows
Reporting and performance insights can be found in:
Insights → Engage → Individuals → Workflow performance