Separate an internal update from a public statement

Copying an internal email onto a public page can expose confusing shorthand, unfinished options and details that do not help customers. Sending staff only a public statement can create the opposite problem: they know the announcement but not what to do when someone asks about it. Write for the tasks of each audience while keeping the underlying facts aligned.

Start from a shared factual core

Establish the confirmed change, its timing, who is affected and what remains undecided. Both versions should draw from that core. If the public statement says a service ends in December while the staff note assumes November, the issue is not tone; it is a factual conflict that needs resolving before either message is sent.

For a hypothetical change to opening hours, customers need the new schedule, effective date and alternative ways to get help. Staff may also need rota arrangements, how to handle existing appointments and where to send unresolved questions. The public version does not need the internal escalation tree, but the internal version must not contradict the published schedule.

Give staff answers, not just awareness

Include a short response to likely customer questions and mark which points are still awaiting confirmation. Separate approved external wording from internal planning notes so that colleagues can tell what may be repeated. Do not distribute personal or sensitive details merely because the audience is internal; share what the work actually requires through the appropriate channel.

Sequence the communication so customer-facing people are not learning the change from an enquiry they cannot answer. The amount of lead time depends on the situation, but even a short briefing should explain where the maintained answer lives. Avoid relying on a long email chain that leaves different teams with different versions.

Keep updates connected

When a fact changes, update both versions and tell the relevant people what changed. A new public FAQ can be missed if the staff briefing remains untouched. Keep the internal operational detail separate enough to maintain, while linking it to the current external source.

Before publication, ask someone who was not involved in drafting to play each role: a customer trying to act and a colleague trying to respond. The customer should not need internal terminology; the colleague should not have to invent an explanation. Different documents are justified when they help those different tasks, not when they allow the organisation to tell incompatible stories.