Service standards for corporate communications that specify the measure, not the aspiration

Corporate communications service standards are useful only when a buyer can tell whether a defined event passed. They are not universal response times. Cedar Vale Engineering Ltd, a fictional England employer, must set its own thresholds for the proposed site-consolidation message after checking risk, affected people, channels and contractual evidence.

Leave every threshold blank until an authorised owner supplies it. Start with a record that another reviewer can reproduce.

Specify the measure, not the aspiration

For each standard, write:

Field	Buyer definition
Purpose and decision
Triggering event
Eligible items or people
Numerator and denominator
Unit
Clock start and stop
Timezone and working calendar
Pauses and exclusions
Source, query and version
Evidence owner
Threshold and tolerance
Failure action
Review and retirement date

A completion rate, for example, is meaningless without an eligible population and a definition of completion. A response duration needs a timestamp source, pause rule and timezone. Do not turn an average from unlike messages into a target.

The NCSC's logging guidance recommends deciding which questions logs must answer and identifying where records arise, how long they are retained and how they are protected. That security guidance does not establish a corporate publishing service level. It supports the narrower requirement for reliable evidence.

Build standards around controllable events

Cedar Vale could define blank measures for source-copy completeness, claim-evidence review, accessibility acceptance, approved-version release, correction acknowledgement, controlled-copy replacement and archive closure. Each measure ends at a buyer-controlled state. It must not claim that an employee understood the proposal, a journalist accepted a view or the public trusted the organisation unless separate research supports that conclusion.

Write the acceptance event in plain language before expressing a rate. For source completeness, the eligible population might be the claims admitted to one version, while the numerator is claims with a current evidence ID and authorised owner. For controlled-copy replacement, eligibility might cover destinations the buyer can change. Third-party discussion outside that control belongs in monitoring, not the denominator.

Accuracy needs a challenge path as well as a target. The ICO's accuracy guidance addresses personal information, source status and correction; it is marked under DUAA review. A personal-data correction and a correction to general corporate copy are different events, even if one incident triggers both.

Accessibility should be tested against a named task and format. Government accessible-formats guidance discusses early planning, audience needs and supplier briefs. Because its operational context is government communication, Cedar Vale must not present it as a private-sector pass certificate.

Treat failure as designed work

Every standard needs a failure queue. Name who can stop publication, who diagnoses the problem, what evidence is preserved, which controlled copies are affected and who may restart. A missed threshold cannot be cured by changing the denominator after the event.

Separate timeliness from quality. A quick review with a missing rights record fails even if its clock passes. A fully evidenced correction that exceeds a contracted response threshold has one quality result and a different service result. Report both. The buyer should also state how missing timestamps affect the measure rather than excluding inconvenient records silently.

Incident communication needs its own standard set. NCSC guidance for cyber incidents supports preparation and coordination among relevant functions, but supplies no universal clock. Security owns technical facts; legal and regulatory owners decide applicable notifications; communications controls approved wording and channels.

Review a standard when the message scope, affected population, source system, contract, risk or channel changes. Retire it when its event no longer exists. Until an owner, evidence source and response are present, the field is unresolved and cannot support a service claim.

At the review meeting, show the underlying records before any summary. Confirm that the query version matches the data dictionary and that corrections have flowed into past reports. If the measure no longer changes a decision, retire it with a reason. If it still matters but cannot be reproduced, stop reporting it until the evidence chain is repaired.