

This study compared the performance of Amplifi (a specialist reg-tech tool) and Microsoft Copilot (in MS Word) in simplifying complex, regulated communications, specifically within the UK financial services sector.
The study concludes that the primary difference between the two tools is systemic: Amplifi functions as an operational risk control, while MS Copilot acts as a generative drafting assistant.
The study highlights several potentially high stakes impacts for firms managing Consumer Duty and other regulatory obligations:
For regulated environments, the study suggests that Amplifi is a risk-managed system that provides defensible proof of improvement. Conversely, MS Copilot is a more unstable environment for sensitive text, where performance is highly dependent on individual prompt engineering and manual human oversight to prevent semantic drift.
MS Copilot’s limitations in text simplification and assessment
Simplification is contingent on how the task is phrased, which introduces user variability into the process.
MS Copilot does not always act only on the selected or intended text, increasing the risk of unintended edits and weakening trust in the editing workflow.
Sometimes allowing the user to review alternative text before applying it, at other times it writes directly into the document. This reduces transparency and control.
Similar prompts can produce materially different outputs, both in content and in how the system applies the task.
Restoring or reviewing the original wording is not always straightforward. This shifts the burden back onto manual document management and version control.
The system not only generates language but sometimes redefines the task itself. That increases the likelihood of unintended changes.
It tends to produce scores that are materially more favourable. It cannot be relied upon to validate the success of its own simplification.
Legally significant wording was frequently softened, qualifiers weakened, and sequencing was altered. This required manual checking, reducing efficiency and increasing risk.
Prompt history, output history, and revision logic are not always captured in a way that supports robust audit trails. Governance controls must be recreated externally.