The FCA didn't ask for better reports. It asked for demonstrably better outcomes — and outcomes live in the day-to-day flow of lending work, not in a quarterly pack.
Three years in, many lenders still run Consumer Duty as a retrospective exercise: the work happens in one set of systems, and once a quarter somebody assembles proof that it happened fairly. That model has two failure modes. It's expensive — skilled people spend days reconstructing decisions. And it's fragile — reconstruction is exactly what an examiner will probe.
The alternative is to make the lending workflow itself produce the evidence. In practice, on Salesforce Financial Services Cloud, that looks like:
Embedding controls costs effort once, at design time. Reconstructing evidence costs effort forever, at every review. Lenders who make the switch tell us the quarterly scramble simply disappears — the pack becomes an export, not a project.
Pick one journey — new lending applications is usually right — and map where decisions happen against where evidence currently lives. The gap between those two maps is your Consumer Duty risk, and it's almost always closable with configuration rather than custom code.
One conversation with the architect — and a clear view of what your bank could ship next quarter. If we're not the right fit, we'll tell you in that call.