Every internal-comms tool you have ever bought has shown you an open-rate dashboard. The number is always reassuring. 60%. 72%. 81% if you A/B-tested the subject line.
It is the wrong number.
When the CEO sends a Friday-afternoon email about a reorg, the question is not whether the company's mail server delivered it. The question is whether the people in that reorg actually read and understood what was said. Those are different things, and the gap between them is where most internal communication quietly fails.
What "open rate" actually measures
Open rate, in email parlance, is the share of recipients whose mail client loaded the tracking pixel embedded in the message. It is a proxy for whether the email was rendered on a screen for long enough for an image to download.
It does not measure attention. It does not measure comprehension. It does not measure recall. It does not even measure scrolling past the preheader. A preview-pane render fires the pixel; iOS Mail Privacy Protection fires the pixel on every email regardless of behaviour; many corporate gateways pre-fetch images and credit every email with an open.
According to Litmus's 2025 State of Email Engineering report, the median internal-email open rate among 500+ surveyed enterprise comms teams was 64%, but the median recall rate — measured by a follow-up survey 48 hours later — was 21%. Two-thirds of "opens" leave no trace in the reader's memory.
This is not a critique of the people receiving the messages. It is a description of how modern attention works. A typical mid-market knowledge worker now processes between 90 and 130 work emails a day. The cognitive math does not allow for sustained attention on any one of them.
The three things that actually have to happen
For an internal message to do what leadership intended, three things have to be true. The reader has to:
- See it. The message reached their inbox or feed and was not buried under noise.
- Read it. They actually parsed the content, not just scanned the preheader.
- Acknowledge it. They confirmed — to themselves or to the organisation — that they understood the part that mattered.
An open-rate dashboard tells you about step 1 with low confidence. It tells you nothing about steps 2 or 3. Yet steps 2 and 3 are the entire point of internal communication.
The fix is not better subject lines. The fix is structural: redesign the message so the reader has to do something to clear it. Not because you want to surveil them. Because the act of doing something is the moment you actually have their attention.
Acknowledgment as a structural primitive
The shift that internal-comms teams in 2026 are making is treating acknowledgment as a first-class structural element of important messages, not an optional follow-up survey.
In practice that means: when you publish a high-priority announcement, the reader sees the message and a clearly-labelled "Acknowledge" button. They cannot dismiss the announcement from their feed until they click it. The system records who clicked, when they clicked, and what they were told at the time they clicked.
That last detail matters. If the announcement is later edited, the acknowledgment ties to the version the employee saw, not the current version. Compliance auditors care about this distinction; so should you.
What the data looks like when you do this
Companies that adopt acknowledgment-tracked announcements for high-priority messages typically see three changes in their internal-comms dashboards within the first 90 days:
Read time on important messages goes up. Not dramatically — usually from a baseline of 8-12 seconds (a scan) to 35-50 seconds (an actual read). That is the difference between "noticed the announcement" and "processed the announcement."
Acknowledgment rates on critical content stabilise above 90%. Not because compliance suddenly became fashionable, but because the structural friction of having to click "Acknowledge" makes people stop and read first.
Follow-up "I didn't know about that" exceptions drop by 60-80%. This is the actual ROI. The people who used to send "wait, when was this decided?" emails to leadership instead see the announcement, acknowledge it, and move on.
IABC's 2025 global communications survey puts the median acknowledgment rate at well-instrumented organisations at 87% for executive-priority messages, against a baseline recall rate (measured the same way Litmus does) of 21% at organisations without acknowledgment tooling. That four-fold difference is the actual signal that internal-comms teams should be optimising for, not open rate.
Where acknowledgment goes wrong
Two failure modes worth naming.
Acknowledgment fatigue. If every Tuesday status update requires an acknowledgment click, employees will start clicking through them as fast as they appear and the structural friction stops doing its job. The fix is discipline on the publishing side: reserve mandatory-acknowledgment for messages where you would care, six months from now, whether the employee saw it. A reorg, a policy change, a safety incident — yes. A monthly newsletter — no.
Acknowledgment as surveillance. Some organisations roll out acknowledgment tracking with the framing "we now know who has and hasn't read the rules." That framing produces resentment, not compliance. The framing that actually works is "we no longer need to send the same email three times because we can see who already saw it the first time." Employees feel less spammed, not more watched.
What this looks like in practice
A 240-person engineering company we onboarded earlier this year had been running their internal comms on a mix of email, a Slack #announcements channel, and a Notion page. They could not answer the question "who has read the new on-call rotation policy" without DMing every engineer.
After moving high-priority messages to a structured-announcement format with required acknowledgment, the head of engineering can pull up the policy's acknowledgment dashboard, see that 232 of 240 engineers have confirmed they read it, and DM the eight who have not — with the exact timestamp of when the policy was published. The whole question went from "we sent an email and hope" to "we have a list."
That dashboard is what structured announcements with acknowledgment tracking deliver. It is not a magic improvement to attention — humans are still humans. It is a structural acknowledgment (no pun) that "we sent it" is the wrong answer to "did they get it," and that internal-comms teams need a better one.
The shift
Open rate was a useful metric in 2010 when internal comms meant a weekly newsletter and the question was whether the html rendered. It is a vanity metric in 2026, because the underlying problem moved. The new problem is signal in a noisy feed, not delivery.
Acknowledgment tracking does not solve the noise problem. But it does give leadership a defensible, auditable answer to the question that actually matters: did the people who needed to know, know?
If you cannot answer that today, you do not have an attention problem. You have a measurement problem. And measurement problems are fixable.
See how acknowledgment tracking works in Kayden Connect →