Challenges - Onboarding
This is a persistent issue across financial institutions.
Despite defined processes, dedicated teams, and service level targets, onboarding outcomes frequently fail to align with Front Office timelines.
Client onboarding often misses the required transaction date.
Why This Happens
Onboarding is not a fully controllable internal process.
It depends on:
Client responsiveness — provision of information and documentation
Quality of inputs — completeness and accuracy of submissions
Third-party dependencies — registries, intermediaries, external checks
Internal coordination — across functions, products, and jurisdictions
These factors introduce variability into every case.
However, onboarding is typically managed using SLAs that measure internal processing time rather than readiness against a required transaction date.
What happens
This creates a fundamental misalignment:
The business need: readiness by a specific date
The operating model: time-based processing targets
As a result:
Cases are worked in sequence rather than in line with urgency
Early-stage cases receive insufficient attention
Progress is not aligned to due date risk
Delays are often recognised too late to recover and meet due-date.
What is occurring
A consistent pattern emerges:
Cases appear to progress steadily in early stages
Work queues build without clear prioritisation
Increasing numbers of cases approach their due date simultaneously
Case managers shift into reactive mode
Urgent cases dominate capacity
Over time:
Most cases become urgent
True prioritisation breaks down
Delivery against transaction timelines becomes inconsistent.
The Nature of the Challenge
The challenge is not simply a process or capacity issue.
It is a function of:
External dependency — onboarding is co-produced with the client
Variability — in demand, effort, and response times
Interdependency — across teams and systems
Finite capacity — within operations
Traditional SLA-based management does not account for these dynamics.
Implication
Improving onboarding performance is not achieved by tightening SLAs or increasing pressure on processing timelines.
It requires recognising onboarding for what it is:
A system operating under uncertainty, where outcomes depend on how work is sequenced, prioritised, and controlled over time.
Understanding the Nature of the Problem
Client onboarding behaves differently from a standard process
It is not a linear sequence of tasks that can be planned and executed to a fixed timeline. Instead, it operates as a system influenced by variability, external dependency, and constrained capacity.
1. Onboarding is Co-Produced
Progress depends on both the bank and the client.
The bank controls internal processing
The client controls key inputs
This means progress is intermittent, not continuous.
Work advances in stages, often with pauses between them.
2. Variability is Structural
No two onboarding cases are the same.
Variation arises from:
Client type and complexity
Product and jurisdictional requirements
Quality and timing of information provided
Number of dependencies involved
This makes duration inherently unpredictable.
3. Demand and Response are Not Synchronized
New onboarding requests arrive continuously.
Client responses arrive unpredictably.
This creates a disconnect:
Cases enter the system steadily
Progress within cases occurs irregularly
Without active control, this leads to accumulation and delay.
4. Capacity is Finite and Shared
Case managers must handle:
Multiple cases at different stages
Different levels of urgency
Interruptions from client responses and escalations
Capacity is therefore not applied evenly.
It must be actively allocated.
5. Work Naturally Becomes Urgent
If unmanaged, cases tend to:
Start slowly
Wait in queues
Accelerate late
This results in urgency clustering, where many cases require immediate attention at the same time.
At that point, control is lost.
Key Insight for Onboarding
Onboarding is not difficult because of inefficiency alone.
It is difficult because it is a variable, externally dependent system being managed as if it were a predictable internal process.
A Different Approach to Onboarding
If onboarding is a variable, externally dependent system, it cannot be managed effectively through linear processes and static SLAs.
It requires a shift from process control to flow control.
The objective is not to move every case through the same steps at the same speed.
The objective is to maximise the likelihood that each case completes when it is needed, despite uncertainty.
1. Manage to Due Date, Not Elapsed Time
The primary reference point should be the required transaction date, not internal SLA clocks.
This means:
Measuring progress against time remaining
Identifying risk to completion early
Actively intervening before cases become urgent
Time is not the metric — readiness at the right moment is.
2. Control Work-in-Progress
Too many active cases dilute attention and slow overall progress.
A controlled system:
Limits the number of active cases
Sequences new work into the system deliberately
Ensures each case receives sufficient focus at the right time
Reducing work-in-progress improves flow and predictability.
3. Maintain a Deliberate Priority Mix
All cases should not be treated equally at all times.
An effective system maintains a balance of:
High priority — close to due date
Medium priority — progressing steadily
Low priority — early-stage cases
This enables:
Flexibility to respond to urgency
Continuity of progress across the pipeline
Avoidance of last-minute compression.
4. Continuously Re-sequence Work
Onboarding is not a fixed sequence.
Cases should be actively re-prioritised based on:
Proximity to due date
Client responsiveness
Dependency status
Remaining effort
This requires ongoing visibility and decision-making, not passive progression.
5. Design for Interruptibility
Case managers must be able to:
Pause work without losing progress
Switch between cases efficiently
Resume work quickly when inputs arrive
This is essential in a system where:
Client responses are unpredictable
Urgent work can emerge at any time.
6. Treat the Pipeline as a System
The focus shifts from individual cases to the overall flow of work.
This includes:
Monitoring pipeline health
Managing inflow and throughput
Identifying bottlenecks early
Smoothing work over time
The question is not “Is this case on track?”
It is “Is the system producing outcomes reliably?”
The Outcome
When onboarding is managed as a flow system:
Work is distributed more evenly
Urgency is controlled rather than accumulated
Case managers operate with greater flexibility
Delivery against transaction timelines becomes more consistent
Key Principle
Onboarding is a variable, externally dependent system that must be actively controlled — not a predictable process that can be managed through elapsed-time targets.
Onboarding as a Service
If onboarding is to be managed as a flow system, it must be structured as a service, not just a process.
This means defining how work enters, moves through, and exits the system — with clear control over prioritisation, sequencing, and outcomes.
Service Objective
The purpose of onboarding is:
To enable clients to transact when required, by establishing valid, complete, and usable client relationships in time.
This shifts the focus from task completion to client readiness.
Service Characteristics
An effective onboarding service has four defining characteristics:
Demand Awareness
Flow Control
Priority Driven
Outcome Focus
1. Demand-Aware
Understands:
When onboarding is needed
What the required transaction date is
The complexity and dependencies involved
Demand is not treated equally — it is qualified and shaped at entry.
2. Flow-Controlled
Manages:
How many cases are active
How work is sequenced
How capacity is applied
The service controls the pipeline, rather than allowing work to accumulate.
3. Priority-Driven
Continuously aligns work to:
Due date proximity
Client responsiveness
Risk and regulatory requirements
Priority is dynamic, not fixed at case creation.
4. Outcome-Focused
Measures success by:
Readiness at the required date
Reliability of delivery
Quality of client enablement
Not by internal processing speed alone.
Service Segmentation
Not all onboarding cases should be treated the same.
Segmentation enables better control of flow and expectations.
Typical segments include:
Standard Onboarding
Known client types
Predictable requirements
Moderate complexity
Accelerated Onboarding
Urgent business need
Short lead times
Requires prioritised handling
Complex Onboarding
Multiple entities, jurisdictions, or products
Higher dependency and coordination requirements
Longer and less predictable timelines
Segmentation allows:
Appropriate allocation of resources
Realistic expectation setting with the Front Office
Better management of system variability.
Entry into the Service
Effective onboarding begins with controlled entry.
This includes:
Clear definition of the required transaction date
Assessment of complexity and dependencies
Validation of minimum information required to start
Poor entry control leads to:
Cases entering too early or too late
Incomplete information at initiation
Increased variability downstream.
Orchestration Model
Onboarding requires active coordination.
A service-based model typically includes:
Case ownership — accountability for progression and outcome
Central orchestration — sequencing, prioritisation, and intervention
Execution capacity — analysts and specialists performing tasks
The key is not who does the work, but how the work is coordinated across the system.
Managing the Pipeline
The onboarding pipeline must be actively managed as a system.
This includes:
Monitoring work-in-progress levels
Maintaining a balanced priority mix
Identifying emerging bottlenecks
Intervening early when cases are at risk
The pipeline is not a backlog to be worked through.
It is a system to be controlled.
Measures of Success
A service model changes how performance is assessed.
Key measures include:
Completion by required transaction date
Distribution of work across priority levels
Stability of the pipeline (absence of urgency spikes)
Quality and completeness at first pass
These reflect system performance, not just individual effort.
Context: Onboarding & Periodic Reviews
Onboarding, like Periodic Reviews, is one of the core lifecycle services.
Both share:
External dependency
Variability in demand and execution
Need for active flow control
Designing onboarding as a service ensures it integrates consistently within the broader Client Lifecycle Management capability.
Onboarding is not simply a set of steps to be completed.
It is a service that must coordinate people, information, and timing to deliver client readiness when it matters.
The Underlying Issue
Client onboarding is not failing because the work is too complex or the standards are too high.
It is failing because it is managed as a process, rather than designed as a system.
Onboarding is a due date–driven, capacity-constrained flow problem with external dependencies. Demand is variable, capacity is limited, work is uneven, and progress depends on client responsiveness.
Without managing these dynamics, delays to required transaction dates are not an exception — they are inevitable.