
Outlook
Part of What is actually known about measurement going into 2027, and what still is not
Four bounded uses of AI in measurement, with test sets and stop rules
Measurement teams can assess four bounded AI uses through explicit inputs, test sets and stop rules while keeping privacy permission and accuracy separate.
Useful privacy first measurement AI applications begin with a narrow analytical task, not a promise to recover all missing data. Four possible uses deserve controlled evaluation: data-quality triage, classification assistance, bounded estimation and explanation support. Each remains an editorial scenario until the organisation tests it on its own data.
What to take away
- Start with a narrow analytical task, not a promise to recover all missing data.
- Distinguish accurate personal information from a model's statistical accuracy.
- Keep a reproducible rule-based check beside any learned detector.
- Publish observed and modelled values separately for any declared gap.
- Reopen the gate after any change to model, prompt, supplier or data source.
Start with two different meanings of accuracy
The ICO distinguishes accurate personal information from a model's statistical accuracy. A model can score well overall yet perform poorly for a relevant subgroup or on a changing population. Teams should therefore name the target, correct label, test population, error measures and consequences of a wrong result.
ICO: accuracy and statistical accuracy in AI
That assessment does not answer whether collection is permitted. Device storage and access under PECR, the processing of personal information under UK GDPR, model validity, system security and business value need separate decisions.
Application 1: find broken measurement states
Editorial scenario: a classifier highlights unusual changes in event volume, consent-state combinations or source reconciliation. Its input is a daily control dataset; its output is a queue for an analyst, not an automatic correction.
A typical test set: 40 known failure cases from the last two quarters plus a 90-day seasonal baseline. Stop if false alerts exceed 10 per analyst per week, or if a source schema changes.
The 2025 AQuA Book treats verification, validation and uncertainty as different assurance duties. That supports keeping a reproducible rule-based check beside any learned detector.
GOV.UK: the AQuA Book
Application 2: classify documentation, not people
Editorial scenario: a language model proposes tags for event definitions, ticket notes or change logs. A human owner accepts or rejects each tag. Do not put raw visitor records, free-text customer disclosures or client secrets into a service until contracts, data flows, retention, transfers and access controls pass review.
A typical test set: 200 event definitions with a human agreed gold label, plus 50 adversarial examples. Stop if the human correction rate exceeds 15% across two consecutive weekly batches, or if any personal data appears in a prompt.
The ICO's current AI guidance requires a risk-based approach where personal information is processed and says an organisation may need to stop if risks cannot be sufficiently mitigated.
ICO: guidance on AI and data protection
Application 3: estimate a declared gap
Editorial scenario: a model estimates an aggregate series for a defined reporting gap. Publish observed and modelled values separately. Record training window, target population, exclusions, uncertainty, refresh rule and a parallel holdout comparison. A result is attribution only when that is the specified method, and neither attribution nor prediction establishes causal incrementality.
Worked example: a 14-day gap in paid search conversions. The model estimates aggregate daily conversions from 90 days of pre-gap data. The parallel holdout uses the same 14-day window from the prior quarter. A typical test set: that prior quarter window plus two other seasonal windows.
Stop if the holdout error exceeds 10% of the observed mean, or if the observed value falls outside the modelled 90% interval on any day.
Google's behavioural modelling page illustrates a supplier-specific version of modelled reporting. It describes Google Analytics eligibility and behaviour, not a general method, independent validation or UK legal approval.
Google Analytics: behavioural modelling for consent mode
Application 4: draft an explanation for review
Editorial scenario: an assistant converts a metric card into plain language, while the analyst checks every denominator, period, geography and caveat. Never let it invent a cause for movement. Compare the draft against the signed definition and source result.
Worked example: a metric card shows a 12% fall in newsletter signups. The assistant drafts two sentences. The analyst checks the denominator, period, geography and caveat.
A typical test set: 30 past metric cards with signed definitions and source results. Stop if the draft changes a number by more than 1 percentage point, or if it names a cause not present in the source.
A controlled 2027 gate
ONS observed rising but still shallow AI use among UK businesses in June 2026; the survey is not specific to England measurement teams. Treat that figure as background context only, not as evidence of maturity for any measurement team.
ONS: artificial intelligence in UK businesses
Before release, require a privacy and PECR review, a statistical sign-off, an AI risk owner and a security assessment. NCSC guidance covers secure design, development, deployment and operation, including hosted models and external APIs.
NCSC: secure AI system development
Recheck on publication day, then reopen the gate after a model, prompt, supplier, data source, population or intended decision changes. No application here has been tested, and none promises compliance, accuracy or commercial improvement.
Before you act
- Name the target, correct label, test population and error measures.
- Test with known failures and ordinary seasonal changes.
- Do not put raw visitor records or client secrets into a service.
- Record training window, target population, exclusions and uncertainty.
- Compare the draft against the signed definition and source result.
- Require a privacy and PECR review before release.
Common questions
What is the difference between accurate personal information and a model's statistical accuracy?
The ICO separates accurate personal information from a model's statistical accuracy. A model can score well overall while failing a relevant subgroup. Name the target, correct label, test population, error measures and consequences of a wrong result.
When should a measurement AI application be stopped?
For data-quality triage, stop if false alerts consume the agreed review capacity or if a source schema changes. The ICO's AI guidance says an organisation may need to stop if risks cannot be sufficiently mitigated. Reopen the gate after a model, prompt, supplier, data source, population or intended decision changes.
What must be checked before releasing a measurement AI application?
Before release, require a privacy and PECR review, a statistical sign-off, an AI risk owner and a security assessment. NCSC guidance covers secure design, development, deployment and operation, including hosted models and external APIs. Recheck on publication day, then reopen the gate after any relevant change.



