Operations
Service measures for multilingual marketing that replace invented SLAs
Define multilingual marketing service measures with eligible events, clocks, evidence, owners and buyer-set failure responses instead of invented SLAs.
Multilingual marketing service measures should describe observable delivery, not promise audience response. Define each measure before work starts and leave its threshold blank until the buyer sets one from risk, evidence and operational capacity. No defensible universal SLA exists in the sources reviewed.
What to take away
- Define each measure before work starts and leave its threshold blank until the buyer sets one.
- Every card needs an event, population, numerator, denominator, period, clock start and stop event.
- A missing decision counts as a failure, not a zero-duration completion.
- Operational service results stay separate from reach, attribution, customer behaviour and causal impact.
- Review definitions after any change to channel, language, supplier, tool, rights, audience or risk.
Use a complete measure card
Every card needs the event, eligible population, numerator and denominator or unit, period, clock start, permitted pauses, stop event, timezone, exclusions, evidence system, query or log version, owner, buyer-set threshold and failure response. Record uncertainty and missing data beside the result.
Complete measure card fields
- Event and eligible population
- Numerator, denominator or unit
- Period, clock start, permitted pauses
- Stop event and timezone
- Exclusions and evidence system
- Query or log version and owner
- Buyer-set threshold and failure response
The 2025 AQuA Book frames analytical assurance around proportionate, fit-for-purpose work, roles, verification and validation in government. It supports the discipline of defining and checking a measure, not a private-sector target.
Measure 1: intake acceptance
Event: an operations owner accepts or rejects a submitted brief. Population: briefs received in the stated period. Numerator: briefs accepted with source, evidence, language need, rights, account and withdrawal owner present. Denominator: all eligible briefs.
Intake acceptance measure flow
- Brief submitted and recorded
- Check source, evidence, language need
- Check rights, account, withdrawal owner
- Accept or document rejection
- Exclude duplicates and requester cancellations
- Missed threshold: operations owner investigates
Start: recorded submission time. Stop: acceptance or documented rejection. Exclude duplicates and requester-cancelled briefs. Use the versioned intake register in the buyer's timezone. The operations owner investigates missing fields when the buyer-set threshold is missed.
Measure 2: first-pass review completion
Event: every required language, subject and accessibility decision is recorded for one target asset. Population: assets marked ready for review. Numerator: assets receiving all applicable decisions without an uncontrolled version change. Denominator: eligible assets.
The clock starts at reviewer acceptance, pauses only for a logged source question and stops at approval or rejection. Exclude withdrawn work. The quality owner examines failure reasons; the metric does not prove that an audience understood the content.
Write the reporting period and buyer timezone on this card. A missing decision is a failure, not a zero-duration completion.
GOV.UK's inclusive communication guidance discusses accessible formats and channel selection for government communicators. Use it to specify evidence fields, not to declare a private asset accessible.
Measure 3: release fidelity
Event: comparison of the live asset with the approved record. Population: releases in the period. Numerator: releases matching approved copy, language, disclosure, destination, audience setting and account. Denominator: all eligible releases.
Start at platform publication; stop when the live check is captured. Record timezone and platform identifier. Exclude platform-cancelled items before release. Any mismatch should trigger the publishing owner's pause and evidence-preservation route.
Measure 4: validated-defect response
Event: a specialist validates a defect. Population: validated defects entering the versioned incident log during the reporting period. Unit: elapsed working time to confirmed pause, correction or withdrawal.
The clock starts at validation, pauses only for recorded dependencies and stops on evidenced action in the buyer timezone. Exclude unrelated reports but retain their classification. The incident-log query version is the source. Its owner reports the distribution and unresolved cases, then escalates missed buyer thresholds by defect class.
Measure 5: preference and access handling
Event: a valid objection, withdrawal, research exit or access-removal request is accepted. Population: accepted requests in the stated period. Numerator: requests completed with closure evidence. Denominator: all eligible requests. Unit: completion rate plus elapsed-time distribution.
Start at acceptance and stop at evidenced closure in the recorded timezone. Exclude verified duplicates but retain links. Use the versioned request register. The privacy or access owner investigates any case outside the buyer's threshold.
ICO direct marketing guidance supports preference handling; NCSC social-media advice supports account protection. Neither supplies an SLA.
Measure 6: exit evidence readiness
Event: a scheduled closure or supplier transition completes. Population: campaigns closed in the reporting period. Numerator: closures with usable source and target exports, approvals, rights, account-removal evidence and documented retention exceptions. Denominator: all eligible closures. Unit: completion rate.
Start at authorised closure and stop when an independent custodian opens the exports and confirms access removal in the recorded timezone. Exclude suspended campaigns. Use the versioned exit register and query. Its owner logs missing artefacts and blocks supplier sign-off when the buyer's threshold is missed.
Review definitions after any channel, language, supplier, tool, rights, audience or risk change.
Before you act
- Write the reporting period and buyer timezone on each card.
- Record uncertainty and missing data beside the result.
- Name an owner for each measure and its failure response.
- Exclude duplicates, withdrawn work and cancelled briefs.
- Keep operational service results separate from audience outcomes.
- Review definitions after any channel, language or supplier change.
Common questions
Why should the threshold be left blank at the start?
The threshold stays blank until the buyer sets one from risk, evidence and operational capacity. No universal SLA is defensible in the sources reviewed, so a supplier should not invent a target.
What happens when a buyer-set threshold is missed?
For intake acceptance, the operations owner looks into missing fields. For validated defects, the owner reports the distribution and unresolved cases, then escalates by defect class. For exit evidence, the owner logs missing artefacts and blocks supplier sign-off.
Do the cited government and ICO sources provide an SLA?
No. The AQuA Book supports defining and checking a measure, not a private-sector target. GOV.UK inclusive communication guidance helps specify evidence fields. ICO direct marketing guidance supports preference handling and NCSC social-media advice supports account protection. Neither supplies an SLA.
