Why Internal Communication Reporting Became Essential, and What Actually Changed

By Nicolas Saliba · 8 min read

In 2017 the internal communication budget review took twenty minutes, and the sharpest question was whether the intranet redesign would land before the annual results. In 2026 the same review takes an hour, and the first question is what proportion of the workforce the function actually reaches. Nobody in that room has become more interested in analytics. Something else changed.

Articles on this subject usually assert that reporting has never been more important, which is both true and useless. The interesting question is why the demand arrived when it did. Three things that used to stand in for evidence stopped working, each for a structural reason, and none of them is coming back. That is what made reporting unavoidable, and it also tells you what your reporting has to be able to do.

Substitute one: the office stopped being a proxy for reach

For most of the history of the profession, an internal communicator could walk the floor. You saw whether the poster had been read, whether the town hall filled the room, whether people were talking about the announcement in the queue for coffee. None of that is data, but all of it is evidence, and it was available continuously and free.

Hybrid working removed it. Gallup’s tracking of hybrid arrangements shows the pattern settling well above where it sat before 2020 for remote-capable roles, rather than reverting^[1]. The practical consequence for internal communication is that informal observation now covers a shrinking and unrepresentative slice of the audience: the people who happen to be in on the days you are. Everything else has to be inferred from data or not known at all. Teams working through this specifically will find our note on measuring internal communications across hybrid teams useful.

The same shift hit differently in organisations with large frontline populations, where the proxy was never available in the first place. Those teams have always had a measurement problem. Hybrid simply extended it to head office, which is why it suddenly became everyone’s problem.

Substitute two: the engagement survey stopped counting as a communication measure

For years the annual engagement survey did double duty. It contained two or three questions about communication, and the scores on those questions were accepted as the function’s performance. That arrangement was always weak and it held for a practical reason: nothing better was available.

Two things broke it. Survey frequency fell out of step with the pace of change, so a number gathered in March was being used to discuss a reorganisation announced in September. And executives started noticing that a survey measures how people feel about communication, which is not the same as whether communication arrived. A population can rate communication poorly because it disagrees with the message, and rate it well while having missed it entirely. The distinction is set out further in our comparison of engagement surveys and communications data, which argues for using both rather than substituting one for the other.

Substitute three: the budget conversation moved from inputs to outputs

The third change is the one that puts reporting on the agenda whether the team wants it or not. Budget review used to accept input descriptions: we ran 48 campaigns, published 300 news items, held 12 town halls. Those are activity counts, and they answer the question “what did you do” rather than “what did it achieve”.

Deloitte’s Human Capital Trends research has tracked a broad shift towards expecting people-facing functions to evidence outcomes rather than effort^[2]. Internal communication was one of the last functions to be asked, partly because its outputs are genuinely harder to attribute. It is being asked now. Gallagher’s State of the Sector research keeps finding measurement at or near the top of the capability gaps internal communicators report^[3], which is what you would expect from a profession that had reliable substitutes until recently.

What an executive means by asking for a denominator

When a CFO or COO asks how many people you reach, they are not asking for a bigger number. They are asking for a fraction with a stated bottom half, because a fraction can be compared, budgeted against and argued with. An absolute count cannot.

What gets asked	What teams usually answer	What is actually being asked for
Is our communication working?	Views, opens and engagement totals	A rate against a defined population, trended
Did the restructuring message land?	The intranet page got 7,400 views	Coverage of the affected population specifically
Why do we need this budget?	Campaign and channel volumes	Cost per person reached, and what happens if it stops
Are we improving?	This quarter against last quarter	Multi-year trend that survives platform changes
Which groups are we losing?	An organisation-wide average	The segments below the average, named

Producing the right-hand column is what a reporting practice is for. Our guide to executive reporting for internal communications works through how to structure the report itself, including what to leave out.

What changed on the supply side

The demand side is only half the story. The reason this is now a solvable problem rather than a complaint is that most large organisations consolidated onto Microsoft 365, which means the activity data exists and is retrievable. Microsoft 365 usage reports cover SharePoint, Teams, Viva Engage and email in one admin surface^[4], which was not true when the estate was five separate vendors.

What consolidation did not deliver is the join. Each report describes its own product, none of them holds workforce attributes, and none deduplicates a person across channels. That is the specific reason a team can have every number available and still be unable to answer the executive question, and it is covered in detail in our piece on the limitations of native SharePoint analytics.

The minimum a reporting practice needs

Not a dashboard. Four things, in this order.

A written audience model. Populations defined in the same terms your HR system uses, refreshed on a schedule. This is the denominator, and without it nothing else produces a rate.
A fixed set of definitions. What counts as reached, what counts as read, what window applies. Written down and not renegotiated per campaign.
An independent history. Something that holds the baseline outside the native retention windows, so that a redesign or a migration does not delete your ability to show progress.
One number per stakeholder question. Most internal communication reports fail by volume rather than by accuracy. The KPIs worth defending are few and stable.

Doing this without a new platform

The honest position first. If you run one channel for one audience, the native tooling is free, already switched on, and enough. Adding a measurement programme to a two-person team with a homogeneous population is overhead you should decline.

The common alternative is a custom build in Power BI over the Microsoft Graph reporting API^[5]. Some organisations run this successfully, and it is a legitimate route. Three cautions before you commit. The reporting API is not consistently reliable and produces days with missing data. Customers have observed KPI values in Power BI that do not reconcile with the native SharePoint reports for the same period, which is a difficult conversation in front of an executive audience and one that damages the credibility you built the report to establish. And a dependable build needs a robust ingestion process, scheduled reconciliation against the native figures, and a named owner: budget for the pipeline rather than the dashboard. Our note on SharePoint analytics in Power BI covers each failure mode.

Tryane exists to remove that build. It reads SharePoint, Viva Engage, Teams and your newsletter platform together, joins the activity to your organisational structure through Entra ID or an HR file, deduplicates people across channels, and keeps unlimited history so a platform change does not reset the trend. Tryane is SOC 2 Type 2 certified and GDPR compliant by design, hosts in the EU by default with US data residency on request, deploys in a couple of hours over single sign-on with Azure AD or Entra ID, and installs no agent.

Frequently asked questions

Where do I start if we report nothing today?

Write the audience model, then pick three questions your executives actually ask and answer only those for two quarters. Starting with a dashboard is the common mistake: it produces a lot of numbers and no argument. Starting with the questions produces a short report that gets read, which is the only version that changes anything.

How often should internal communication reporting go to leadership?

Monthly for the operational view, quarterly for the version that goes to an executive committee, and annually for the budget argument. The quarterly rhythm matters most, because it is long enough for a trend to be real and short enough that a problem can still be acted on. Our internal communications reporting template is built around that cadence.

Is reporting really necessary if leadership is not asking?

They will ask, and the year they ask is the worst year to start, because you will have no baseline. History is the one thing that cannot be produced retrospectively. Capturing a defensible baseline quietly for two years costs very little and is worth a great deal the first time a restructuring makes the question urgent.

Can we show return on investment for internal communication?

Honestly, not as a single financial figure that survives scrutiny, and claiming otherwise damages your credibility. What does survive is cost per person reached, coverage of populations that matter to a specific business risk, and evidence that a targeted intervention moved a measurable behaviour. Our note on calculating the return on internal communications sets out what can and cannot be claimed.

Does Tryane replace our Microsoft 365 analytics?

No. SharePoint, Teams and Viva Engage carry on recording what they record. Tryane sits above them, reads them together, and joins the result to your organisational structure so the report has a denominator and a person is counted once. You keep the Microsoft 365 investment and add the layer native was not designed to provide.