Corporate announcements: from unread notices to measurable communication
Why company announcements go unread and how to measure them. Targeting, read receipts, announcement tiers and scheduled publishing that turn internal comms into a process.
The announcement is the oldest tool in internal communication and the most wasted channel. In most companies the process runs like this: someone writes a text, sends it to everyone, and assumes the job is done. But the purpose of an announcement is not to be sent — it is to arrive. And the gap between those two stays invisible as long as nobody measures it.
Why don't people read them?
Three reasons repeat. The first is channel inflation: when the same content is split across email, a chat group and a noticeboard, none of them becomes the real channel. The second is lack of targeting: an announcement sent to everyone is special to no one; a reader who works out in the first three sentences that it doesn't concern them won't open the next one. The third is the absence of tiers: if an urgent safety notice carries the same visual weight as the canteen menu, both become ordinary.
The three-tier rule
The distinction that works is simple:
- Critical — acknowledgement required and tracked. Should not exceed a few uses a month.
- Informational — stays in the feed, no acknowledgement.
- News — cultural content; archived and searchable.
What protects the value of the critical tier is how rarely it is used. In an organisation that marks every announcement critical, employees soon turn acknowledgement into a reflex click and the acknowledgement means nothing.
Targeting: who should receive it?
Targeting by department, location and segment produces two gains. Read rates rise, because what arrives is genuinely relevant. Notification fatigue drops, because people aren't disturbed by things that don't concern them.
A practical test: if the audience of an announcement is the whole company, make sure it genuinely concerns the whole company. "I'm not sure, send it to everyone" is the easy decision, and it consumes the value of the channel.
Targeted announcements also carry a privacy dimension: content sent only to one department must not surface for someone outside that group in search results or in an AI assistant's answer. That boundary has to be enforced in the data layer, not in the interface — our security approach is built on that principle.
Read receipts and follow-up
For critical announcements, knowing who read what serves two purposes: a compliance record and genuine follow-up. Being able to prove that a safety instruction, an ethics policy or a new procedure was communicated is a legal requirement in most companies.
The detail that matters here is who can see the tracking list. It is natural for a manager to see their own team's status; it is unnecessary transparency — and a source of discomfort — for every employee to see everyone's.
Scheduled publishing and freshness
A good announcement system carries two notions of time together: when it goes live and when it stops being valid. The first makes it possible to publish at 09:00 without preparing outside working hours. The second is more valuable: a campaign announcement that lingers in the feed past its date erodes the credibility of the whole board.
The draft → review → publish flow serves the same purpose. Communications writes, HR reviews, then it goes out; withdrawing a wrong announcement is always more expensive than never publishing it.
Measurement: which number matters?
View counts mislead. Three indicators are meaningful:
- Read rate — what share of the audience opened it?
- Acknowledgement rate and speed — how many hours did a critical notice take to reach 80 per cent?
- Channel comparison — the gap between desk-based and frontline teams.
The third says the most. A read rate of 90 per cent at head office and 30 per cent in the field is not a content problem but an access problem; the answer is mobile and shared-area screens. We cover that in our engagement article.
The ticker and screens
The feed is not the only route. Genuinely urgent information — a system outage, an early finish due to weather, a safety warning on the production line — can be carried by a ticker at the top of the page. Its value also lies in rarity: a ticker with something always scrolling becomes an invisible part of the interface within days.
For teams away from a desk, shared-area screens do the same job. An announcement rotating on the break-room display reaches more people than an email that is never opened — and it requires no sign-in.
Where should you start?
For companies setting this up, the order is clear: first move all announcements into a single channel, then define the tiers, then switch on targeting. Leave read receipts until last — an obligation introduced before the channel has become a habit produces resistance.
We walk through the first three months in the 90-day plan, and content ownership in our operations article.