Cognizant Financial Services United Kingdom

Royal London Group

Security and Compliance

Royal London Group needed to review thousands of regulated marketing assets faster while maintaining compliance with FCA Consumer Duty requirements and reducing the burden on human reviewers.

4.2 hours reduced per asset review time
thousands of regulated marketing assets

Reported impact

Business outcome

Royal London Group reduced the time spent reviewing regulated marketing assets, eased manual reviewer workload and established a scalable, auditable model for using generative AI in a regulated content process.

  • Compliance
  • Productivity Improvement
  • Speed to Market

Solution

Cognizant and Royal London Group implemented a governed generative AI review assistant to shorten the compliance cycle for regulated marketing content. The solution uses Microsoft Azure’s OpenAI LLM inside a modular assistant split into three personas—Creator, Refiner and Approver—so content generation, improvement and approval follow explicit stages instead of a single opaque model call. That persona-based architecture mirrors Royal London Group’s existing content workflow and makes outputs easier to audit. Each asset moves through the assistant under human-in-the-loop controls, with subject matter experts performing the final review before anything is approved. Cognizant also refined the assistant through stakeholder feedback, quality assurance checks and scaled evaluation, while embedding generative AI skills inside Royal London teams so the process can be reused economically in a highly regulated environment.

Data flow

Regulated marketing assets enter the modular assistant, where the Creator, Refiner and Approver personas apply staged Azure OpenAI processing rather than a single model pass. Outputs are then checked by human subject matter experts in the final SME review, and the assistant is continuously refined through stakeholder feedback, QA checks and scaled evaluation.

Solution architecture

5 components · 3 layers
  1. Compute
    • Microsoft Azure’s OpenAI LLM Provides the foundation model used to analyze and rewrite regulated marketing content.
  2. Orchestration
    • Creator Handles the content-creation stage inside the assistant’s governed workflow.
    • Refiner Improves draft content before approval so quality and compliance feedback can be applied in sequence.
    • Approver Checks content in the approval stage so outputs align with governance expectations before human signoff.
  3. Governance
    • final SME review Keeps human subject matter experts in the loop for the last compliance decision on each asset.

Architecture clues

  • Human oversight remained central, with every AI-generated output undergoing final SME review.
  • Quality assurance checks and scaled evaluation were part of the refinement loop before reuse at scale.
  • The assistant uses three personas to mirror Royal London Group’s traditional content workflow.
  • The implementation focused on transparency and auditability for a regulated insurer.

Evidence from the source

“A modular assistant was developed using Microsoft Azure’s OpenAI LLM, split into three personas— Approver Refiner, and Creator —each with a distinct role in the content lifecycle.”
“Human oversight remained central, with all AI-generated content undergoing final SME review.”
“Review time reduced by 4.2 hours per asset”
“This cognitive architecture ensured transparency, auditability, and alignment with governance standards.”
“Use generative AI to accelerate the approvals cycle for regulated marketing content, ensuring compliance and reducing the workload of human reviewers.”
Transparency Evidence & methodology 85/100 reference value · 81% confidence · 2 sources

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value85/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth20/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact15/25
    1 metric describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence81%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency10/10
    2 source references document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Cognizant

    Royal London Group—Responsible AI in practice | Cognizant

    First-party
    https://www.cognizant.com/us/en/case-studies/royal-london-group-responsible-ai-in-practice
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
  2. Royal London

    Royal London Careers - Candidate guide

    First-party
    https://jobs.royallondon.com/Candidate-guide/content/Who-we-are/?locale=en_GB

    5,000 Colleagues 7 Sites across the UK and Ireland. All figures quoted are as at 30 June 2026.

    Source type
    Official company website
    Supports
    • Company size

Date evidence

  • First archived Feb 7, 2026 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
  • Sitemap last modified Jan 30, 2026 · Cognizant · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
Not separately sourced Industry, Region. Treat these normalized attributes as lower-confidence until a dedicated source is added.