Building a corporate communications report with its evidence states kept apart

Corporate communications measurement is useful only when the report preserves what is known, how it was calculated and what decision it can support. A count from a publishing system is not automatically evidence that a person understood a message. A later business event is not proof that the communication caused it.

This guide uses one fictional case: Cedar Vale Engineering Ltd is considering consolidating an England customer-support site. No announcement has been approved, issued or measured. The exercise is to design a reporting system before any authorised release. It creates no sample figures, client results or assumptions disguised as evidence.

Records were reviewed on 6 September 2026. The UK government's communication functional standard says outputs, outtakes and outcomes should be monitored through government campaigns. HM Treasury's Magenta Book, updated on 15 May 2026, separates implementation, outcome and impact questions. Those are useful disciplines here, but neither source supplies a benchmark or proves results for an England private company.

Begin with a decision, not a dashboard

Cedar Vale's decision owner first writes the question the report must answer. For example: did each authorised recipient group receive the approved information through its intended route, and is there evidence that any group could not access or understand what it needed? That is narrower than asking whether the communication was successful.

The record should then name:

• the decision owner and the people allowed to change the question;
• the communication version, approval reference and controlled release window;
• each eligible recipient group, without treating employees, customers, journalists and suppliers as interchangeable;
• the buyer-owned manual baseline, such as an approval ledger and controlled distribution list;
• the evidence needed to continue, correct, pause or withdraw;
• the review date and the point at which a measure expires.

If the organisation cannot state the next decision, collecting more numbers merely creates a larger archive.

Keep five evidence states apart

Controlled delivery observations

These are events Cedar Vale can define and retrieve: an approved file entered the newsroom, a message left an authorised account, a delivery system returned a stated status, or an accessible alternative was supplied. The exact event name matters. "Sent", "accepted" and "viewed" belong in separate fields because systems may define them differently.

Each observation needs a source system, query or export version, timestamp and owner. NCSC guidance on logging for security purposes explains why configuration, needed fields and synchronised time matter when logs must answer incident questions. Its focus is security, so it does not validate communication effectiveness.

Audience evidence

Understanding, recall, concern or ability to act cannot be inferred from dispatch records. Evidence might come from an authorised research method, a service request or a documented correction. The population, recruitment route, question wording, non-response, accessibility and privacy decisions must travel with the finding. A third-party platform's estimated audience is retained as that provider's estimate, not relabelled as a Cedar Vale observation.

Organisational outcomes

An operational event, such as a correctly routed employee query, can be observed if the event and eligible population were defined beforehand. It still needs a denominator, period and exclusions. A later commercial, employment or reputational development may have many causes and should not be attributed to the message by chronology alone.

Rule-based attribution

A rule can allocate credit, perhaps to the last controlled channel recorded before an enquiry. The report must call this an allocation rule. It should state the matching key, window, deduplication logic, excluded journeys and unresolved records. Changing a window may change the allocation even though the underlying events remain the same.

Causal inference

A causal question asks what would probably have happened without the communication or under another approach. The Magenta Book's supplementary quality guidance for impact evaluation says outcome monitoring alone cannot show whether an intervention caused the change. A qualified evaluator should choose a proportionate design and test its counterfactual assumptions. Where that evidence does not exist, the causal field stays unresolved.

Admit a measure through a data contract

No chart should be built until its measure card is complete. For each candidate, record:

1. Purpose and decision: the question answered and the action an authorised owner may take.
2. Event: the observable occurrence, including its technical status definition.
3. Population: who or what could enter the measure, with England, UK or other geography kept explicit.
4. Calculation: numerator, denominator, unit and treatment of repeat events.
5. Time: start, stop, reporting period and timezone.
6. Boundaries: inclusions, exclusions and known data loss.
7. Lineage: source system, query or transformation version and evidence location.
8. Control: owner, reviewer, access route, correction procedure and retention decision.
9. Uncertainty: missingness, estimation, sampling, classification or attribution limits.
10. Decision rule: buyer-set threshold, response, stop condition and retirement date.

The fields may be blank while the design is on hold. Blank is more honest than a made-up target or a number copied from an incompatible organisation.

Build the reporting chain

Preserve raw evidence

Store the authorised source-copy ID, approval and route record before calculating totals. Keep the original export or immutable reference where proportionate, and control access. If a supplier changes a status label, preserve both the old definition and the date the new one began.

Where logs contain personal data, the ICO's current data-protection principles require purpose, minimisation, accuracy, storage and security considerations. The page notes that parts of its guidance are under review following the Data (Use and Access) Act. A privacy reviewer must therefore decide Cedar Vale's actual processing; the reporting need is not itself a lawful-basis conclusion.

Transform visibly

Give every query a version and owner. Write the filter, join and deduplication decisions in plain language. Retain rejected rows with reason codes where lawful and necessary, so a reviewer can distinguish a genuine exclusion from silent loss. Reconcile a sample of source events to the report before use, using authorised or synthetic records.

Publish a compact dashboard

The first view should show the decision, reporting period, freshness, coverage, open data-quality incidents and last correction. Separate panes can then cover authorised delivery, audience evidence, operational response and evaluation. Do not mix supplier estimates into a column of observed counts.

The Government Analysis Function published dashboard design and accessibility guidance on 6 February 2026. It recommends testing and supporting data tables, among other measures. Its official-analysis setting is not a universal private-sector legal standard, but it offers practical design checks. Cedar Vale still needs qualified accessibility and equality review for its channels and users.

Attach a narrative

The narrative says what changed in the data, why confidence may have changed, and which explanations were considered. It names unavailable evidence rather than smoothing over gaps. A chart without that context invites readers to supply their own causal story.

Quality assurance before a report is used

The Office for National Statistics describes quality as fitness for purpose and identifies relevance, accuracy and reliability, timeliness, accessibility and clarity, and coherence and comparability in its quality framework. These dimensions concern official statistics. Cedar Vale can use them as review prompts, not claim official-statistics status.

For every release, an analyst who did not write the final query should inspect:

• whether event definitions match the source system at the stated date;
• whether numerator and denominator cover the same population and period;
• whether timezone boundaries or late records altered the total;
• whether personal data have been unnecessarily exposed;
• whether accessible alternatives preserve the meaning of the visual;
• whether the narrative distinguishes observation, estimate, allocation and inference;
• whether corrections propagate to exports and prior reports.

The UK Statistics Authority explains that quality includes suitable data, appropriate methods, transparency and continuing challenge in its Trustworthiness, Quality and Value framework. It can be applied voluntarily beyond official statistics, but doing so does not turn a corporate report into an accredited statistic.

Corrections need their own workflow

A report is a versioned record, not a perfect final answer. When a source event is corrected, the owner should log the previous value, revised value, reason, affected reports and approval. Material changes should trigger a new issue rather than quietly overwriting the old export. The ICO's accuracy guidance is specifically about personal data and says inaccurate personal data should be corrected or erased as appropriate; it also carries a DUAA review notice. That is separate from the broader analytical reason to preserve a revision trail.

Retire a measure if its source disappears, definition drifts, denominator cannot be recovered, decision no longer exists or collection creates disproportionate risk. Archive the retirement reason and identify any successor. Never backfill the series using a new definition without a break marker.

A bounded decision report for Cedar Vale

The reporting pack should end with four short statements:

• Observed: which approved-version delivery and correction events the controlled records show.
• Reported by others: which estimates or status descriptions came from suppliers or external parties.
• Attributed by rule: which events received credit under the declared matching rule.
• Not established: audience outcome, organisational contribution or causal effect that the evidence cannot support.

Then the decision owner chooses proceed, amend, pause or close. A factual, privacy, accessibility, security or evaluation failure cannot be offset by a favourable delivery count. The Green Book's 2026 guidance concerns government appraisal, yet its insistence on exposing evidence gaps and uncertainty is a sound discipline for this fictional decision.

This draft remains on publication hold. Before any 2027 use, named corporate, statistical, evaluation, privacy, security, accessibility, finance and editorial reviewers must test the real definitions, sources, permissions and decision thresholds. Until then, the framework measures only its own readiness.