Forbidden
Book a meeting

Current challenges

02 / 09

To scale effectively Nigel Sloam needs an operational engine capable of managing complex SSAS relationships, high-volume administration and regulatory data in one connected system.

The challenge is not simply that SSAS Pro is old. It is that the current operating model makes everyday administration unnecessarily dependent on manual effort.

A scheme sits at the centre of a complex network of members, trustees, employers, bank accounts, properties, loans, investments, transactions and regulatory activity. The replacement platform has to preserve those relationships while making them considerably easier to navigate and manage.

At the same time, approximately 1,600 pieces of administration can enter the team each working month. The current work log does not provide the structured status, ownership, ageing and workflow information needed to manage that volume efficiently.

MVP therefore creates a scheme-centred operating model where permanent pension data and assets are separated from the temporary cases used to manage work, giving Nigel Sloam both a reliable source of truth and a much clearer way to run the administration function.

The operational picture today.

Tooling

Critical

Legacy System Rigidity

What's happening

SSAS Pro has been in place for more than 20 years and remains difficult to use, report from and adapt to changing operational requirements.

Business impact

Poor usability discourages consistent data entry, while difficult extraction and reporting force additional checking and manual work before information can be trusted.

Process

Critical

Manual Re-Keying & Document Production

What's happening

Information already held about members, schemes and employers still has to be manually re-entered into bank forms, application packs, agreements and other standard documents.

Business impact

Repeated data entry consumes administrative capacity, introduces avoidable error risk and slows processes that should be driven directly from trusted scheme data.

Data

High

Unstructured Work Management

What's happening

Work is logged through a largely free-text work log, while process guidance often sits separately in Word checklists and relies heavily on administrators knowing what should happen next.

Business impact

Management cannot easily distinguish new work from follow-ups, see exactly where cases are blocked or consistently enforce process requirements before work moves forward.

Process

Medium

Complex Data Without a Connected Operational Model

What's happening

Schemes, members, trustees, employers, bank accounts, loans, properties and investments all need to be understood together, but current reporting and extraction make those relationships difficult to work with.

Business impact

Teams spend more time finding, checking and reconciling information, while regulatory and management reporting requires additional manual preparation.