Scoring every draft against a UK utility's own guidelines
A UK water utility with 6,000 employees sends thousands of regulated communications a month, and its own guidelines were hard to follow under deadline. Twistag built a Chrome extension that scores each draft against the utility's rules as it is written and suggests rewrites when a draft falls short. The communications team saves around 18 hours a week, and the pilot recorded zero non-compliant language flags in regulatory bulletins.

- 18 hrssaved per week by the communications team
- 3,000+communications scored per month
- 0non-compliant language flags in the pilot
- Client
- UK water utility
- Industry
- Utilities & public sector
- Practices
- AI & Agents
- Timeline
- 8-10 weeks workshop to pilot
- Stack
- OpenAI, Python, GCP, Next.js
Six thousand writers, one set of rules.
Twistag built an AI communications assistant for a major UK water utility — a Chrome extension deployed across 6,000 employees that scores every draft against the utility's own guidelines in real time, saving the communications team around 18 hours a week and scoring more than 3,000 communications a month. The pilot recorded zero non-compliant language flags in regulatory bulletins. Twistag built it as a compliance system: five scoring dimensions calibrated on hundreds of the utility's real communications, and a custom prompt layer encoding its regulatory language rules, updated without model retraining or redeployment.
The utility had six thousand employees, thousands of communications going out every month, and no reliable way to keep any of it consistent. Internal guidelines existed; nobody followed them under deadline pressure. Water utilities communicate under scrutiny in a way most industries do not. A service disruption notice that sounds defensive, a regulatory filing with ambiguous phrasing, a public announcement that reads like a different company wrote it from last month's — all of it erodes public trust slowly and visibly. Some of that inconsistency is more than a brand problem: the wrong sentence in a regulatory bulletin can be treated as an admission of liability. The client is not named publicly.
Built as a compliance system.
Two weeks of discovery.
Working sessions with communications leads, IT and the people writing every day set the brief: a compliance system, with its own scoring rules and its own definition of success.
Scoring calibrated on real writing.
A labelled set of hundreds of the utility's own communications taught the pipeline the difference between a regulatory filing and a community update, and between plain language and phrasing that reads as an admission of fault. Each draft is scored on clarity, empathy, actionability, tone and accuracy.
Inside the tools already open.
The extension works in email clients, document editors and internal content systems, stays out of sight until a draft needs attention, and leaves every decision with the writer. Regulatory language rules update without retraining or redeployment.
- DraftWritten in the email client or document editor
- AnalysisSent to the scoring service on Google Cloud
- ScoringFive dimensions against the utility's own guidelinesKey step
- WriterDecides what to do with each suggested rewrite
Risk removed, hours returned.
Six weeks into the pilot, the assistant was processing more than 3,000 communications a month. The communications team recovered around 18 hours a week, which went into proactive stakeholder outreach and the strategy work senior editors had been hired to do but could not reach because they were reviewing first drafts. The pilot recorded zero non-compliant language flags in regulatory bulletins. For a utility under regulatory scrutiny, that is risk removed.
An improvement to clarity can't introduce compliance risk. The two are evaluated together.
- OpenAI
- Python
- GCP
- Next.js
Twistag built a Chrome extension for a UK water utility that scores every draft against its own guidelines, saving 18 hours a week.










