We built a regulatory change NLP platform over 12 weeks. (1) Regulatory Monitoring Engine: automatically processing all regulatory publications. The engine: ingesting regulatory publications from all relevant sources (FCA, PRA, Bank of England, HM Treasury, EU regulators — via RSS feeds, publication APIs, and web scraping where APIs were unavailable), classifying each publication by type (final rule, consultation paper, supervisory statement, Dear CEO letter, guidance, thematic review), subject matter (prudential, conduct, AML, operational resilience, consumer duty, ESG/climate — 28 regulatory categories), and relevance to the bank (based on: regulatory perimeter — which FCA sourcebooks apply to the bank's authorisation, business line applicability — retail, commercial, wealth, products affected — mortgages, savings, investments, lending). Relevance classification accuracy: 94.7% (validated against 6 months of manual classification). The system processed the full corpus (2,350+ publications annually) — not a triaged subset.
(2) Requirement Extraction Engine: extracting specific regulatory requirements from natural language text. The engine: identifying obligation language ("firms must", "the FCA expects", "banks should ensure"), extracting specific requirements with their regulatory context (which rule, which sourcebook section, applicable from date, affected entities), classifying requirements by implementation type (policy change, process change, system change, training requirement, board reporting, client communication), and linking requirements to the bank's existing policy framework (identifying which existing policies are affected by the new requirement). Requirement extraction: 92.3% recall (capturing requirements the manual process missed) with 89.1% precision (minimising false positive requirements). (3) Impact Assessment Engine: automatically mapping regulatory requirements to affected business areas.
The engine: maintaining a structured model of the bank's organisation, products, and processes (updated quarterly), matching extracted requirements to affected organisational units using semantic similarity (not keyword matching — understanding that a requirement about "treating customers fairly" affects the complaints handling process, the product design process, and the marketing approval process), generating impact assessment drafts with: affected business units, affected policies and procedures, required changes (categorised by type), estimated implementation complexity, and recommended priority. Impact assessment time: reduced from 3-8 days to 4 hours (analyst review of AI-generated assessment). (4) Implementation Tracking Engine: managing regulatory change implementation across the organisation.
The engine: generating implementation task lists from impact assessments (specific, actionable tasks assigned to responsible owners), tracking task completion against regulatory deadlines, escalating overdue or at-risk tasks to management, producing compliance dashboard (regulatory changes in pipeline, implementation progress, overdue items, upcoming deadlines), and generating regulatory examination evidence packages (demonstrating implementation, staff awareness, and ongoing compliance for each regulatory area). (5) Dual-Tracking Engine: monitoring UK and EU regulatory divergence. The engine: identifying equivalent UK and EU regulatory requirements, flagging divergence (where UK and EU rules differ on the same topic), highlighting provisions requiring different compliance approaches for UK and EU operations, and maintaining a divergence register for management reporting.