Licence compliance reporting that builds every condition's chapter from your own data and flags breach risks before you file
Licence-condition reports assembled, not chased, with breach risks flagged before filing.
See one case, screen by screen ↓Every licensed electricity and water company reports to its regulator against the conditions of its licence: technical standards such as security of supply and drinking water sampling, economic ones such as separate accounts and availability of resources, customer ones such as complaints, disconnections and the priority services register, and safety and environmental ones. Each condition belongs to a different team and draws on a different system — lab results, outage management, billing, the finance ledger, the producers' own reports.
So the regulatory team builds the report by email and spreadsheet. It sends out dozens of evidence requests, chases them for weeks, copies last year's wording, and finds out in the last fortnight that a month of data is missing or that a figure disagrees with the regulatory accounts. By then the only option left is to disclose a breach with a weak explanation. Regulators now audit the data behind the report, not only the report, and the cost of getting it wrong is large.
Estimated split of the 10 weeks (about 50 working days) the demo utility's own team estimates its last report took by hand, against the target of about 3 weeks (15 working days) with the solution. In working days.
Six specialist agents fill every condition's chapter and flag breach risks; the owner attests and the head of regulatory compliance approves.
Lumina Utilities, a combined electricity and water utility, owes the Northvale Utilities Regulator its Annual Licence Compliance Report for 2025–26 under licence NUR-L-0147: 38 conditions in 7 parts, due Saturday 31 October. On Tuesday 13 October, with 18 days to file, the lab results extract for condition 14 arrives at 07:40. Here is what happens next, screen by screen, in the working solution.
Amira owns the report. Each condition is a chapter with a tab on the binder spine, coloured by status, and the filing bar reads 27 of 38 ready to file: 6 with their owners, 2 waiting for evidence, 2 at risk and 1 not drafted. The open chapter is condition 14, the drinking water sampling programme — the licence's own words, a 12-month data strip still empty, and its evidence list.
“I find out a month is missing in the last week, when nothing can be fixed.” — Amira Haddad
Amira presses Draft chapter 14. The licence reader reads condition 14: at least 99 % of the 182 planned samples in each month, and each monthly return within 10 working days. The data gatherer pulls the lab results for April 2025 to March 2026 across 14 supply zones and fills the strip month by month. December comes in at 178 of 182 (97.8 %), and the storm log explains it.
Breach watcher · Dec: “178 of 182 is under 99%. Storm log INC-2612 explains it: reported as an exception.”
January and February come back empty: 1,812 of 1,820 planned samples in the ten months the lab system holds, and nothing for the other two. The breach watcher stamps the chapter At risk, 2 of 12 months missing, and adds it to Breach watch. The monthly returns record shows all 12 returns filed on time, so the samples were taken; the results are somewhere else.
“No results in the lab system for 2 of 12 months. The returns were filed, so the samples were taken: the results are elsewhere.”
The evidence collector searches the team inboxes and finds two Fenwick Analytical certificate files, received 4 February and 3 March 2026. The lab system was cut over on 6 January and the contract lab's results were emailed, never loaded. The chapter drafter writes four paragraphs with seven citations — and does not state compliance for the two months without data.
Drafted narrative: “No results are held for January or February 2026; compliance for those months is not stated.”
Breach watch sets each at-risk condition out the same way: what the licence requires, what the data shows, and why. Condition 22: two customers on the priority services register were disconnected for debt on 18 November 2025 after their flags were lost in a billing platform move, and all 84,310 register records have since been re-checked. Condition 31: the auditors' letter behind the availability-of-resources certificate is promised for Friday 23 October, the board meets on the 28th. For condition 22 the chapter drafter has an early notice to the regulator ready for Amira's review.
Early notice: “Drafted by the chapter drafter from chapter 22. It is sent only when you press Send.”
The consistency checker compares 214 figures with the 2024–25 submission and the regulatory accounts. Five moved more than 5 %, and four are explained from the evidence — guaranteed standards payments rose from 911 to 1,284 after Storm Imelda. One figure does not match: back-bill credits are $1.92M in chapter 23 and $1.97M in note 14 of the accounts, so Billing and Credit is asked which is right (R-0427).
“Differences over 5% need an explanation; figures that appear twice must match exactly.”
Amira loads the two certificates. The data gatherer reads FA-26-0114 (181 results for January) and FA-26-0227 (180 for February). The breach watcher re-tests the year: 2,173 of 2,184 planned samples (99.5 %). February is under 99 % too, explained by work order WO-55821 — the Ashby Moor reservoir inlet was closed for repair on 16–18 February. The chapter moves to its owner with two explained exceptions.
Consistency checker: “Last year 2,179 of 2,184 (99.8%). Down 0.3 points: within tolerance.”
Tomasz, who owns condition 14, attests from his task list that the data and the explanations are correct. Amira then approves the chapter: 2,173 of 2,184 samples, 12 of 12 months, exceptions for December 2025 and February 2026 in the annex. She signs as Head of Regulatory Compliance, and her name, the time and the meaning of her approval are recorded.
“By approving you confirm the chapter is accurate and ready to file with the Northvale Utilities Regulator.”
Chapter 14's tab turns green and the filing bar moves to 28 of 38 chapters ready to file. Two missing months were found and evidenced with 18 days left, instead of surfacing after filing as an unexplained gap. The rest of the binder carries on: the overdue Marlow Fen event report and the Corran Bay producer report are being chased, and the director of regulation signs once every chapter is approved.
“Chapter 14 approved · 28 of 38 chapters ready to file”
The same report, seen by the five people who build and sign it — what October looked like, and what it looks like now.
Six specialist agents fill every condition's chapter and flag breach risks; the owner attests and the head of regulatory compliance approves.
Splits the licence into reportable conditions, each with its obligation, measure, threshold, reporting frequency and the evidence that proves it, quoting the licence wording exactly, and tracks amendments.
Pulls each condition's measure for the reporting year from its source system — lab results, outage management, billing, the finance ledger, producer reports — and matches it to the plan or target, keeping each extract and its time.
Requests each missing item from the condition owner with a due date, sends reminders 7 and 3 days before, and searches the named team inboxes and shared drives for evidence already received before asking again.
Tests every measure against its condition and checks that every month, return and producer report is present; marks a chapter at risk when a requirement is not met or evidence is missing, and shows how close to the line the compliant ones are.
Writes each chapter in plain, factual sentences from the data, the evidence and last year's wording, and drafts each exception with its cause and remedial steps.
Compares each figure with last year's submission, the regulatory accounts and any other chapter it appears in; flags a move over the 5 % tolerance without an explanation and any shared figure that does not match exactly.
Approves each chapter; the board signs the certificate. The agents propose; a named person decides.
Ask about any condition, figure or request in this year's report, or say what to do. Every answer points to its chapter.
Which conditions are at risk of breach?
Three chapters are at risk. Condition 22: two priority customers were disconnected for debt on 18 November, which the report must disclose as a breach. Condition 31: the board certificate depends on the auditors' letter, promised for 23 October. Condition 14: January and February sampling results are missing.
Why is condition 14 at risk?
The lab results system holds no results for January or February 2026. The monthly returns were filed on time, so the samples were taken. The lab system changed on 6 January, and the contract lab's two certificate files are in the water quality inbox, never loaded. Loading them should complete the year.
What changed since last year's submission?
Of 214 figures, 5 moved more than 5 %. Guaranteed-standards payments rose from 911 to 1,284 after Storm Imelda; SF6 losses rose 12.0 % after the Brannock switchgear leak; leakage fell 5.5 % to 112.4 Ml/d. One figure does not match the regulatory accounts: back-bill credits in chapter 23 are $1.92M against $1.97M.
Chase the overdue evidence requests
Reminders are on their way for the 2 overdue requests: the Marlow Fen event report from Owen Castell, with his director copied, and the Corran Bay January–March report, sent to the producer with Rhys Penhaligon copied. The sends are on the audit trail.
13 screens from the working solution, on its sample data. Pick one to see it large.
How the report is assembled, tested and signed are settings, chosen by the regulatory team. Changes are versioned and on the audit trail.
| Setting | Default | Choose from |
|---|---|---|
| Reporting year and due date | 1 Apr 2025 – 31 Mar 2026 · due 31 Oct 2026 | This year · next year (1 Apr 2026 – 31 Mar 2027 · due 29 Oct 2027) |
| Close to the line | 5 % | 1 % to 15 % — flags a compliant measure within this margin of its requirement |
| Missing data is a risk | On | On · Off — marks a chapter at risk when any month, return or producer report is missing |
| Year-on-year tolerance | 5 % | 1 % to 20 % — asks for an explanation when a figure moves more than this |
| Draft an early notice to the regulator | On | On · Off — the agents may draft it; only the head of regulatory compliance can send it |
| Chapter approver | Amira Haddad | Amira Haddad, Head of Regulatory Compliance · Grace Mbeki, Licensing analyst |
| Report signatory | Daniel Ferreira | Daniel Ferreira, Director of Regulation · Amira Haddad, Head of Regulatory Compliance |
| Reminder cadence | 7 and 3 days before | 7 and 3 days before · 10, 5 and 2 days before · 3 days before — the owner's director copied when overdue |
Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.
“demo” = seen in the working solution, on its sample data · “target” = the design goal, measured in the live solution · “estimated” = our split of the demo utility's own estimate of 10 weeks for its last report · “typical” = published figures: licence breaches can be fined up to 10 % of turnover in Great Britain (Electricity Act 1989 s.27A; Water Industry Act 1991 s.22A); misreported data cost one water company £126M in 2019, a £3M penalty and £123M returned to customers (Ofwat, 25 June 2019). Lumina Utilities, the Northvale Utilities Regulator, licence NUR-L-0147, the producers, the contract lab and the people named on this page are fictional — characters and sample data in the working solution.
Software that builds a licensed electricity or water utility's report against the conditions of its licence. Licence Compliance Reporting turns the licence into a binder with one chapter per condition, and six agents fill each chapter with its operating data, evidence and a cited draft. The condition owner attests and the head of regulatory compliance approves.
The licence reader splits the licence into conditions, measures and thresholds. The data gatherer pulls each measure from its source system, the evidence collector requests and chases what is missing, the breach watcher tests every month against the condition, the consistency checker compares figures with last year and the regulatory accounts, and the chapter drafter writes the chapter with every sentence cited.
The breach watcher tests every measure against its condition and checks that every month, return and producer report is present. It re-runs daily and whenever new data arrives. In the sample case it found that January and February sampling results were missing from the lab system with 18 days to file, and the evidence collector found them in the water quality inbox.
No. The chapter drafter never states compliance for a period without data; the chapter is marked at risk instead. The breach watcher never declares a breach either — the head of regulatory compliance decides how an at-risk condition is reported: obtain the evidence, disclose it as an exception, or tell the regulator early.
Yes. The consistency checker compares every figure with the prior submission, the regulatory accounts and the other chapters. A move over the tolerance (5 % by default) needs an explanation, and a figure that appears twice must match exactly; when it does not, a question goes to the owner. It never edits a figure.
Yes. The agents have read-only access to source data, never mark evidence accepted, never contact the regulator and send nothing to a producer without the contract manager on copy. Each chapter is attested by its owner and approved by the head of regulatory compliance; the director of regulation signs the report and the board signs the certificate.
Yes. The reporting year and due date, the regulator template, the close-to-the-line margin, the missing-data rule, the year-on-year tolerance, whether early notices may be drafted, the chapter approver and report signatory, the reminder cadence, the condition owners and the inboxes searched for evidence are all settings.
The Agentic Solution Engine builds and deploys it from your requirements and documents — your licence and its amendments, last year's report, the regulator's template and your source systems — and it goes live once every quality gate has passed. We will walk you through it on your own licence first.
Every data request answered on time, with one number for one thing.
1-min demoRegulatory Precedent SearchEvery filing position backed by how regulators actually ruled, cited and trended.
1-min demoRegulatory Commitment TrackingEvery directive owned and dated within a day of the order, and closed with its proof.
1-min demoWe'll run Licence Compliance Reporting on your own licence conditions and last year's report.