1,500 hours a month given back to the team
Up to 8 hours per report, 400 reports a month. Now under 15 minutes each.
Results
- Forecast savings
- Up to £300K a year across 2 businesses
- Review time
- Up to 8 hours → under 15 minutes per report
- Volume
- 400 reports a month
- Time given back
- An estimated 1,500 hours a month
The problem
Every document, some up to 25,000 words, had to be read line by line against the organisation’s rulebook before it could be signed off. Team members were spending up to 8 hours on a single report. AI had been talked about for a while, but nothing had been implemented, and the team were not sure if AI could reliably match their quality.
What happened next
-
Proved it
Proof of concept on 15 real reports, each reviewed manually and by the system, every flagged issue judged by the lead QA manager and the senior subject-matter expert. The system found more valid issues than the manual review. 2 weeks.
-
Approved it
Business case approved by the executive team: forecast savings of up to £300K a year across 2 businesses, benefits tracking set up before build. The blocker cleared: sensitive data could not go to models processed in the US, so I found and validated a route that keeps every AI call inside the UK, designed with the DPO and signed off before go-live.
-
Built it
8-week production build. 3 independent AI reviews per report against an approved, versioned rulebook, then a rules gate that rejects anything that fails before it reaches a reviewer. QA managers can overrule the AI with a ruling that binds every future report (180+ in pilot). Tamper-evident audit trail. Penetration tested.
-
Live
10 reviewers trained, rulebook and go-live criteria signed off by the QA and subject-matter leads. The QA lead co-built it and now trains reviewers without me. Rollout to the second business under way.