Operational resilience and Consumer Duty are data projects in disguise
Two regulatory regimes quietly created budgeted, deadlined data work at the mid-market tier.
Neither the operational resilience regime nor Consumer Duty says "fix your data" on the tin. Both, in practice, are data mandates — and unlike most data work, they arrive with board attention, a budget line, and a date.
Operational resilience: mapping means integration
Firms must map important business services end to end and prove they can stay within impact tolerances. You cannot map a service across systems whose data doesn't join up, and you cannot evidence recovery of a service whose data lineage is unknown. Every gap that mapping exposes — the spreadsheet bridging two systems, the overnight file nobody monitors — is an integration deficit with a regulatory spotlight now pointed at it.
Consumer Duty: outcomes need joined-up records
Evidencing good customer outcomes means joining product, transaction, communication and complaint data at customer level — across systems that were never designed to agree on who a customer is. Mid-market firms mostly passed their first Duty board reports on manual heroics. Manual heroics don't scale to the second year, and the FCA has been clear the bar rises.
Why this matters to a migration firm
Because these are the door-opening projects: budgeted, deadlined, data-shaped, and small enough to start without a procurement quarter. Fix the reporting pipeline this quarter; be the obvious call when the platform itself moves next year. If you're staring at either regime with a systems estate that doesn't join up — that's exactly the conversation we're built for.
Got a cutover date? Tell us the source system, the target, and the deadline — we'll tell you within 48 hours whether we can hit it and what the Assessment will cost.
freddie@godwit.uk