Financial Services FCA / Consumer Duty Vulnerability & Affordability

Customer Vulnerability & Affordability Assessment Platform

FCA-regulated transformation of customer vulnerability identification, affordability assessment, support-plan management, communication preferences, audit evidence, and fair customer outcome monitoring.

Assessment Time

45m → 15m

Review Compliance

58% → 92%

Repeat Disclosure Complaints

-50%

00 Summary 01 Problem 02 Stakeholders 03 AS-IS 04 TO-BE 05 Requirements 06 Process Diagrams 07 Risks 08 Deliverables 09 KPIs

00 — Executive Summary

A regulated financial-services firm needed a consistent operating model for vulnerable customer support and affordability assessment.

A UK financial services company was under increasing operational and regulatory pressure to improve how it identified, assessed, supported, and monitored customers in vulnerable circumstances.

Vulnerability disclosures, affordability concerns, arrears indicators, complaints, and support requests were handled across disconnected systems, creating inconsistent customer outcomes and weak audit visibility.

The organisation needed a platform that could identify vulnerability indicators, assess affordability risk, trigger tailored support workflows, and maintain clear evidence that customers were being treated fairly.

As Business Analyst, I led the discovery and process transformation initiative to design a customer vulnerability and affordability assessment platform aligned with FCA expectations around vulnerable customers and Consumer Duty outcomes.

The solution introduced structured vulnerability capture, affordability assessment workflows, support-plan creation, specialist-team referrals, communication preferences, audit logging, and management information dashboards.

The transformation improved consistency, reduced manual handling, strengthened compliance evidence, and helped the firm deliver better outcomes for customers at risk of financial harm.

01 — Business Problem

Vulnerability and affordability handling was inconsistent, fragmented, and difficult to evidence.

The firm had multiple customer-facing teams dealing with vulnerability and affordability issues, but there was no consistent operating model.

Customer vulnerability signals appeared through contact centre conversations, missed payments, complaints, affordability reviews, collections interactions, bereavement or power of attorney requests, digital self-disclosure forms, and third-party support notifications.

  • Vulnerability disclosures were not consistently recorded
  • Customers often had to repeat sensitive information to multiple agents
  • Affordability reviews were manually assessed using inconsistent criteria
  • Support options were applied unevenly across teams
  • Audit evidence was difficult to compile
  • Management lacked reliable MI on vulnerable customer outcomes
  • Communication preferences and reasonable adjustments were not always visible to frontline staff

This created regulatory and customer-risk exposure. The business needed a centralised platform that could make vulnerability and affordability handling consistent, traceable, and operationally manageable.

02 — Stakeholders

Customers

Fair treatment, privacy & appropriate support

Needed safe disclosure journeys, accessible communications, and support that reflected their circumstances.

Contact Centre Agents

Clear prompts & support workflows

Needed guided capture, visible reasonable adjustments, and consistent next-step support prompts.

Collections Team

Affordable repayment plans & risk controls

Needed structured affordability evidence and clear support options for customers in payment difficulty.

Vulnerable Customer Support Team

Specialist case handling

Needed referral workflows, support-plan monitoring, and review-date controls for complex cases.

Compliance Team

FCA alignment & audit evidence

Required evidence of fair treatment, decision traceability, Consumer Duty outcomes, and governance controls.

Risk Team

Customer harm & conduct risk monitoring

Needed reliable MI on customer harm indicators, affordability risk, and outcome trends.

Product Team

Ethical journey design

Focused on low-friction, accessible customer journeys without over-collection of sensitive data.

Complaints Team

Evidence for disputes and complaints

Needed clear case histories, decision trails, and support evidence for complaint handling.

Data Protection Officer

Sensitive personal data governance

Required data minimisation, access controls, consent controls, retention rules, and privacy safeguards.

IT & Engineering

Secure workflow and integration

Needed secure integration with CRM, collections, support-plan, audit, and dashboard services.

Senior Leadership

Regulatory confidence & operational performance

Needed stronger assurance, clearer MI, and measurable customer outcome improvements.

Stakeholder Conflicts

  • Product and operations wanted low-friction customer journeys.
  • Compliance and risk teams required stronger controls and evidence.
  • Collections teams needed commercially viable repayment workflows.
  • Vulnerable customer specialists pushed for more flexible support options.
  • Data protection stakeholders were cautious because vulnerability information can be sensitive.

BA Balancing Role

  • Defined a model that protected customers without excessive journey friction.
  • Avoided unnecessary collection of sensitive data.
  • Balanced customer support, conduct risk, operational practicality, and audit evidence.
  • Translated FCA-aligned expectations into practical business and system requirements.

03 — AS-IS Workflow

1
Customer Contacts Firm
2
Agent Identifies Possible Vulnerability
3
Manual CRM / Case Notes
4
Transfer to Collections, Complaints or Support
5
Manual Affordability Assessment
6
Support Selected by Agent Judgement
7
Manual Follow-Up Tracking
8
Separate Compliance Evidence
9
Manual MI Extracts

Key Pain Points

  • Customers had to repeat sensitive circumstances because information was not captured in a structured and reusable way.
  • Affordability outcomes varied by team, agent experience, and manual interpretation.
  • The firm struggled to prove why a support decision was made and whether it led to a fair outcome.
  • Leadership could not easily compare outcomes for vulnerable and non-vulnerable customers.
  • Agents did not always see communication preferences, reasonable adjustments, or existing support plans.
  • Processes were not strong enough to consistently evidence FCA expectations around support, communications, product/service design, and outcome monitoring.

Operational Impact

  • Repeat disclosure and poor customer experience.
  • Inconsistent affordability decisions.
  • Weak audit evidence for complaints and compliance reviews.
  • Manual support-plan tracking.
  • Limited vulnerable customer outcome MI.
  • Conduct, privacy, and regulatory risk exposure.

04 — TO-BE Solution

Centralised customer vulnerability and affordability platform with human review for complex cases.

The future-state solution introduced a centralised customer vulnerability and affordability platform.

The solution did not automate sensitive decisions blindly. It used structured rules and risk indicators to guide staff, while requiring human review for complex or high-risk cases.

The platform captured vulnerability categories, support needs, consent status, communication preferences, affordability data, support plans, specialist referrals, review dates, audit logs, and outcome dashboards.

01

Vulnerability Disclosure & Identification

Customers self-disclose vulnerability or agents identify vulnerability indicators during interactions.

02

Structured Vulnerability Capture

The system captures vulnerability category, support needs, consent status, and communication preferences.

03

Affordability Triggering

Assessments trigger when payment difficulty, arrears, or financial stress indicators are detected.

04

Guided Affordability Workflow

Income, expenditure, commitments, dependants, arrears, and risk indicators are captured consistently.

05

Support Recommendations

The platform calculates affordability outcomes and recommends suitable support options.

06

Specialist Referral

Specialist workflows trigger where vulnerability or customer harm risk is high.

07

Support Plan Monitoring

Support plans are created, reviewed, and monitored with review dates and responsible teams.

08

Outcome Monitoring & Audit

Dashboards monitor outcomes, SLA performance, repeat contacts, complaints, and support effectiveness.

05 — Requirements

Functional Requirements

  • The system must allow customers to self-disclose vulnerability through digital channels.
  • Agents must be able to record vulnerability indicators during customer interactions.
  • The platform must support vulnerability categories such as health, life events, resilience, and capability.
  • Users must capture consent where required.
  • The system must record what information can be shared, retained, and displayed to staff.
  • Sensitive notes must be access-controlled.
  • The platform must capture income, expenditure, debts, dependants, arrears, and financial commitments.
  • The system must calculate affordability indicators using configurable rules.
  • Staff must be able to record customer context and override recommendations with reason capture.
  • The platform must recommend appropriate support options.
  • Support plans must include review dates, actions, communication preferences, and responsible team.
  • High-risk cases must route to specialist teams.
  • Customers must be able to select preferred communication channels.
  • Reasonable adjustments must be visible to authorised staff.
  • Templates must support plain-language and accessible communication.
  • All vulnerability, affordability, support, and decision records must be auditable.
  • Dashboards must show outcomes, trends, support-plan effectiveness, complaints, and review compliance.

Non-Functional Requirements

  • Sensitive customer data must be encrypted in transit and at rest.
  • Role-based access controls must restrict access to vulnerability and affordability records.
  • The platform must support GDPR-compliant processing, retention, minimisation, and deletion rules.
  • The system must avoid unnecessary collection of sensitive data.
  • The platform must support FCA Consumer Duty and vulnerable customer evidence requirements.
  • Audit logs must be immutable and available for compliance reviews.
  • Customer-facing forms and communications must be accessible and written in plain language.
  • Support-plan alerts, review dates, and escalation triggers must operate reliably.
  • Failed notifications must support retry handling.
  • The platform must support multiple products, brands, and customer segments.

06 — Process Diagrams

AS-IS vulnerability handling workflowTO-BE vulnerability disclosure and support workflowCustomer self-disclosure journeyAgent-led vulnerability capture workflowAffordability assessment processSupport-plan creation and review workflowSpecialist referral workflowCollections hardship workflowComplaint-linked vulnerability processConsent and data-sharing workflowCommunication preference workflowOutcome monitoring and MI reporting flowCross-functional swimlane across customer, agent, collections, specialist support, compliance, risk, and complaintsData flow diagram across CRM, affordability engine, support-plan module, audit logs, and dashboards

07 — Risks & Constraints

Risk

Over-collection of sensitive data

Creates GDPR and customer trust risk if unnecessary vulnerability information is captured.

Risk

Poor staff training

Can lead to inconsistent customer handling and poor support-plan outcomes.

Risk

Algorithmic or rules-based bias

May create unfair outcomes if affordability or support rules are not governed carefully.

Risk

Customers reluctant to disclose vulnerability

Missed support opportunities when journeys do not build trust.

Constraint

Excessive journey friction

May reduce customer engagement and prevent completion of support workflows.

Risk

Weak consent controls

Creates privacy breach risk and undermines responsible data handling.

Constraint

Poor CRM / collections integration

Could create operational workarounds and fragmented frontline visibility.

Risk

Inconsistent support-plan reviews

Can cause customer harm and compliance risk if review dates are missed.

Risk

Misuse of vulnerability labels

Creates ethical and reputational risk if labels are used without care and governance.

The implementation approach had to be cautious. Vulnerability handling is not just a workflow problem. It is a trust, privacy, conduct, and staff capability problem.

08 — Deliverables

09 — Outcomes & KPIs

+65%

Vulnerability disclosure capture consistency improved from low baseline

15m

Affordability assessment completion time reduced from 45 minutes

-50%

Repeat disclosure complaints reduced

Lower

Manual support-plan tracking reduced significantly

Centralised

Vulnerable customer outcome MI moved from limited to dashboard-driven visibility

92%

Support-plan review compliance improved from 58%

Same Day

Complaint evidence preparation time reduced from several days

Standardised

Customers routed to appropriate support through consistent workflow

The transformation improved customer support consistency, reduced operational risk, strengthened audit readiness, and helped the firm evidence fairer outcomes for customers in vulnerable circumstances.