Delivery confirms that a message arrived. It does not tell you whether people opened it, understood it or agreed with it.
Slide three of the quarterly review reads: five organisational announcements, one hundred percent delivery, zero objections.
And the verbal note is the one made in every organisation: "the team is fully aligned."
Eleven weeks later, three strong performers resign from the same department inside a single month. In their exit interviews the same sentence appears in different wordings: the change announced in March was never clear, nobody asked what they thought of it, and when they tried to ask, there was nowhere to ask.
Slide three wasn't wrong. Every figure on it was accurate. The problem is that it measured exactly one thing: that the message went out.
01Silence is not data
Let's state the rule plainly: the absence of objection is not agreement. The absence of objection is the absence of measurement.
When there's no button to press, no field to write in, and no screen showing who read and who didn't, what you're looking at isn't your team's satisfaction. It's the boundary of your tooling. And a tool that only registers sending will always tell you everything is fine, because that's the only sentence it knows.
The communications lead who said "the team is aligned" wasn't exaggerating or flattering. He was reading the only number available to him, and it was honest about the thing it measured: five messages went out, and they arrived. He had no second number to argue with the first.
That's where the failure sits. Not in the interpretation, but in the fact that only one interpretation was available.
02You're measuring your effort, not their state
Look at what internal communication reports contain in most organisations: messages sent, recipients reached, channels used, and maybe an email open rate.
All output metrics. They describe what the department did, not what happened to the workforce. Useful for defending a budget, useless for making a decision.
The metrics that support decisions are a different kind of thing, and every one is a question about the other party. Which units read this and which didn't? Which message drew a negative response, and from where? Where were questions asked? Who comments constantly, and who hasn't commented in six months?
The difference between the two sets is the difference between knowing you sent and knowing you landed. The first goes in a report. The second supports a plan.
03Who isn't in the equation at all
Before any read-rate metric there's a prior question, and most reports skip it: who never entered the system in the first place?
The Tawasol dashboard monitors app installation and login status for each member. So before any conversation about read rates, you can separate the people who read and didn't react from the people who weren't there to read.
That distinction changes the meaning of every number after it. A unit sitting at forty percent read might be a disengaged unit, or it might be a unit where half the staff haven't installed the app yet. The first is a message problem. The second is a rollout problem. And they were producing the same number.
04What you actually see when the tool measures
In Tawasol, an announcement isn't a message that fires and disappears. It has a record that stays.
For each announcement the dashboard reports views, likes, dislikes, comments, and shares, broken down across total members, units, and groups. Click the views icon and you get the list of people who viewed it, each shown with their unit or group affiliation. Click the reactions icon and you get who reacted, which reaction, and the date and time. Comments are shown in full with the names attached.
Now reread slide three with those instruments available. "Zero objections" becomes a sentence you can take apart: is it zero because nobody objected, or zero because thirty-eight percent of the department in question never opened it? Entirely different situations, calling for entirely different actions, producing the same number.
05The thumbs-down button: the feature you'll ask to disable in the first meeting
Let's talk about the part that will cause an argument inside your organisation.
In the app, an employee can press thumbs down on an announcement issued by management. And in the first demo, someone in the room will ask whether that button can be hidden.
The question is understandable. Nobody wants a dashboard showing that sixty people disliked a board decision.
But consider what you're buying when you switch it off. You're not removing the objection. You're removing your knowledge of it. The sixty don't change their minds because the button disappeared. They just move somewhere you can't see, which is exactly where they were before you bought the system.
And the paradox is that a message drawing two hundred likes and forty dislikes is more successful, in management terms, than one drawing complete silence. The first was read and produced a position. The second passed through.
The correct use of that number isn't disciplinary and isn't individual. It's aggregate — and the dashboard is built that way already, breaking dislikes down across units and groups rather than reporting one total. That distribution is the whole point. Dislikes scattered across the organisation are an opinion. Dislikes concentrated in one unit are a symptom.
When rejection clusters in a particular department, you're not looking at unhappy employees. You're looking at something in that department that information didn't reach, or a decision that arrived phrased in a way that misled them, or an operational reality that makes the decision impossible to execute there specifically.
That's the gain: knowing it in week one with a single phone call, instead of learning it in week eleven through three resignations.
Before you read on, do this now. Take the last five organisational announcements you issued and rank them by which department engaged most. Don't ask anyone and don't open a system; rank them with what you hold today. You won't be able to. That isn't a shortcoming on your part — it's the entire point of the exercise. Then write down three questions you wish you could answer about those five: which department didn't read, which message drew rejection, and where questions were raised. Those three questions are the specification for the measurement system you need, and you wrote them yourself in five minutes without anyone selling you anything.
Why infer their view? Ask them Reactions are an indirect reading of a position. Sometimes you need the position itself.
In the Community section of the app, a vote can be published with options, and results appear live alongside a countdown timer. Employees can post their own views and attach images, video, or polls, with counters for likes, comments, and shares.
The practical difference between this and an annual engagement survey is substantial. The annual survey asks about the last twelve months, reaches you six weeks after it closes, and answers questions written before the events you care about took place. A vote published two days after an announcement and closed within twenty-four hours answers one specific question while it still matters: is the new step clear or not?
And when thirty percent say it isn't, you haven't failed. You've caught the necessary rewording before it turned into incorrect execution across three departments.
06Who actually carries your messages
There's another layer that's rarely used, and it's among the most valuable things on the dashboard.
In organisational structure management, each member's row carries a stats icon that opens their Community Statistics: post count, and total likes received.
This is not a tool for ranking employees or comparing them in performance reviews. Any organisation that uses it that way will destroy it within a month, because people stop writing honestly the moment they know the counter gets read in an appraisal.
Its correct use is different. It reveals the organisation's informal structure: who writes and actually gets read, who people go to with questions, and where the centres of gravity sit that never appear on an org chart.
When you have a difficult decision that needs to be understood rather than merely announced, identifying those people and involving them before publication does what no amount of rewording will.
07The line that matters: moderation is not silencing
Opening comments and posting requires oversight, and that oversight exists in the app. The Community screen in the dashboard shows every post in the system, with a filter to display only flagged posts, actions to show, hide, or block, and the ability to restrict posting privileges for a repeat offender. AI assists with the filtering.
These controls are necessary. They're also the most dangerous thing in the system if misused.
The distinction has to be written into policy rather than left to daily judgement: hide what is abusive, insulting, or unlawful — not what is critical. A post saying the new shift policy can't be executed at the second branch is not a post to hide. It's the most useful item on the dashboard that day.
The reason is practical, not only ethical. The first time a legitimate criticism is deleted, every number on that dashboard loses its value permanently. The team will learn the lesson within a week, and you'll be back to "zero objections" — except this time you'll have paid for an entire system to arrive at the same result.
08Measurement starts before publication, not after
One last point before the replay, and it's what makes every other number meaningful.
When creating an announcement, at least one unit must be selected, and targeting can be narrowed to groups or to named individuals. That constraint looks like an interface detail. It's measurement discipline.
A message sent to the entire organisation can't be measured, because half the recipients had no stake in it, and their low engagement tells you nothing about the message. A message targeted at the relevant units produces numbers you can read: whoever didn't open it should have, and whoever objected was genuinely affected.
The structure that makes this possible is built once: nested units mirroring the reporting hierarchy, cross-functional groups for teams that don't follow the reporting line, and members added individually, in bulk through a downloadable template you fill in and re-upload, or through Active Directory. Built once, and every message afterwards becomes targetable and measurable.
09Replay the quarter
Now replay those three months with all of this in place.
The second announcement, on the shift policy change, is published to three specific operational units. Forty-eight hours later the dashboard opens: two units have read almost completely, the third sits at sixty-two percent. Nearly all the negative reaction comes from the third unit, along with four comments asking the same question in different wordings.
One call to that unit's manager explains it in ten minutes: the new policy assumes coverage by three people per shift, and the unit has been running on two since February.
A clarification is published to that unit alone. A two-question vote opens and closes within twenty-four hours. The result comes back, the policy is amended on one point, and the matter is settled in week one.
At the quarterly review, slide three is replaced: read rates in the affected units, the one unit that lagged and why, the objection that surfaced and how it was handled, and the amendment made as a result.
The first slide is about activity. The second is about management. The difference isn't competence. It's the presence of numbers you can act on.
And the three people who resigned didn't resign, because the question they carried for eleven weeks found somewhere to go in week one.
010The number that will appear on your next slide
The next quarterly review is coming. It will contain a slide on internal communication, and that slide will carry the numbers available to you on the day, not the numbers you'd like.
If your tooling measures sending, the slide will say you sent. It will be honest, and it will be meaningless.
If your tooling measures receiving, it will tell you where your message landed and where it didn't. And it will be the first time internal communication gets discussed in that room as an operational function rather than a support activity.
The communications lead who said "the team is aligned" wasn't wrong about the number. He was wrong to have only one.
Send us the last ten organisational announcements you issued — the text, who each was targeted at, and how you measured the effect, if you measured it — and we'll return them as a written Internal Communication Measurement Framework: what should have been measured for each announcement, which four or five indicators deserve a place in your quarterly report to the executive, and what the slide you present at the next meeting should look like instead of a delivery-rate slide. A document you can use as it stands, not a presentation. Send it to contactus@tawasolapp.com with "Internal Communication Measurement Framework" in the subject line.
Tawasol. Your team, connected.