The annotated journal
Internal versus external communication, and how to translate between them
Most significant messages go to both audiences. What decides success is the translation between the two versions and the order they arrive. The comparison, the sequencing rules, and a same-message worksheet covering what, channel, timing and replies.

Translation and sequencing
Most messages that matter go to both audiences. A price change is an internal operations change and an external customer message. An acquisition is a colleague briefing and a press release. The choice between internal and external communication is therefore rarely a choice at all. The decisions that matter are translation, meaning what changes between the two versions, and sequencing, meaning who hears first.
Both versions belong in one communications plan, the artefact the stakeholder engagement framework describes. This page covers the translation work inside it. The classification question, who counts as internal and who counts as external, is settled in internal versus external stakeholders.
What changes between the versions
Internal audiences share your context: they were in the meetings, or could have been. External audiences receive translated versions of the work, meaning what changes, what it costs them, and what they must do.
| Internal version | External version | |
|---|---|---|
| Starting context | Shared: they were in the meetings, or could have been | None: they know only what you have told them before |
| Lead with | The decision and its reasoning | What changes for them, and what they must do |
| Detail | Implementation, trade-offs, open questions | Outcomes, dates, prices, actions |
| Candour | What is uncertain, including what is not yet known | What is certain enough to publish |
| Channel | Team meetings and the internal tools people already use | The channels each external audience already reads |
| Sender | The leader closest to the work | The named owner of the relationship |
| Replies | To the decision-makers, on the record | To whoever serves that audience, with a brief |
The external version is shorter because the questions are narrower. External readers ask what changes for them and what they must do. A version written to explain the decision internally answers a different question.
Who hears first
Internal first is the default, for one reason: colleagues who learn your news from the press stop trusting the channels that should have told them, and front-line staff spend the day answering questions they were not briefed for. The internal side of that trust is the role of internal communications in employee engagement.
Two exceptions change the order:
- Market-sensitive announcements, where selective internal briefing is a legal problem rather than a courtesy question. Both versions release at once, and the internal version carries the context the external one cannot.
- Service failures, where the status page must be first because affected customers need the facts immediately. The internal explanation follows within the hour.
Sequencing compresses under pressure. The crisis end of this spectrum, where the first response is measured in minutes, is covered in crisis communication: what changes, and what you can prepare.
The same-message worksheet
One page runs the same message through both versions. The internal column starts from knowing who your internal audiences are, which identifying your internal communication audience covers as its own task.
Here is the worksheet, filled for a typical example: a subscription price change taking effect in 60 days.
| Field | Internal version | External version |
|---|---|---|
| What you say | The new prices, who is affected, why costs moved, and what the team may and may not promise in conversations | The new price, the date it applies, what continues unchanged, and where to ask questions |
| What you leave out | Nothing that shapes the team's own conversations | The margin argument: customers need the outcome and the transition |
| Who sends it | The person who owns the revenue team | The account owner, or the founder for a small customer base |
| Channel | The team meeting first, then the written record | Email to affected customers, then the public pricing page |
| Timing | Before any customer is told | 60 days ahead, when support is staffed to answer |
| Where replies go | The pricing decision-maker | Support, with a brief covering what can be negotiated |
The replies row is the one most plans omit, and the one that keeps the versions aligned: the person answering external questions needs to know what the internal version said, or they will contradict it in good faith.
When the versions drift
The failure this worksheet prevents has a boundary: the moment an employee meets a customer who knows more, or knows different things, than they do. The mechanic is simple. Two versions written by two people, never compared, diverge on a date, a price or a promise, and the divergence surfaces in a conversation the brand does not control.
Employees retell the version they received. If the internal version was thin or late, that is the version that reaches customers. Advocacy programmes cannot fix a bad internal version. They amplify whatever version exists.
Measuring both versions
Whether each version worked is measurable. Measuring stakeholder communication sets out the minimum plan, and its coverage and satisfaction numbers apply on both sides of the boundary.
Fill the worksheet for your next announcement
Take the next announcement you already know is coming. Fill the worksheet's 6 fields for the internal version, then translate rather than copy into the external column. The exercise takes 20 minutes and surfaces, before either version is sent, every place the two would have drifted.