The budget meeting is thirty minutes and you are the fourth item. The CFO has already reduced two other functions this morning. You have a deck showing engagement scores, intranet page views and a sentiment trend, and you have about four minutes to explain why the internal communications team should not lose a headcount. This is the moment where most IC functions discover that the evidence they have been collecting all year was collected for the wrong audience.
The uncomfortable truth is that internal communications budgets are almost never cut because leadership believes the function is worthless. They are cut because the case was made in a currency the room does not trade in. Communications teams argue in engagement and sentiment. Finance decides in cost, risk and time. This piece sets out four arguments that translate, the evidence each one needs, where that evidence comes from in a Microsoft 365 estate, and two arguments to stop making.
Argument one: the cost of a message people had to ask about
Every ambiguous internal message generates a second conversation. Someone asks their manager, the manager asks HR, HR writes a clarification. That loop has a cost, and unlike most communications claims it is arithmetic rather than assertion.
The estimate is simple enough to build in an afternoon. Take a policy change that generated a measurable spike in queries to a shared inbox or service desk. Multiply the number of queries by an average handling time and a loaded hourly cost, then add the time of the people who asked. A benefits change that produces 900 queries in an organisation of 12,000 is not a communications inconvenience. It is a five-figure operational cost, and it recurs annually.
Why this argument works: it is bounded, it uses the finance function’s own unit of account, and it points at a specific fix rather than a general aspiration. Do not overreach. Claim the queries you can count, not a modelled organisation-wide productivity figure that nobody in the room believes.
Argument two: communications is a controllable variable in a change programme
Large change programmes carry approved business cases with adoption assumptions baked into them. An ERP rollout that assumes 80 per cent of users on the new process by the end of quarter two has made a communications assumption, whether or not anyone called it that. When the adoption assumption fails, the business case fails, and the number attached to that failure is already written down and already approved.
This is the strongest argument available to most IC functions, and it is underused because it requires attaching your reporting to somebody else’s programme. Deloitte’s human capital research repeatedly identifies communication and manager capability as the variables that separate transformation programmes that hold from those that stall[1]. In practice it means asking, at the start of every major programme, which populations must adopt by when, and then reporting coverage of exactly those populations rather than tenant-wide reach.
Argument three: coverage as a control, not a metric
Safety and compliance communications sit in a different category, because failure has a named cost. An audit finding, a regulatory action, an incident that a documented briefing would have prevented. In these cases the useful sentence is not “our safety bulletin performed well”. It is “we can evidence that 94 per cent of operators in scope received the instruction within 48 hours, and we can name the remaining 6 per cent”.
That reframes internal communications as a control that produces evidence, which is a category the audit committee already understands and already funds. It also raises the bar on your data, because a control that cannot be evidenced by population is not a control. Our note on measuring communications that reach frontline workers covers the practical side, since the populations that matter most here are usually the hardest to see.
Argument four: attrition concentrated where the message never lands
The generic version of this argument, that engagement drives retention, is true and useless in a budget meeting, because it is unattributable to your function. Gallup’s long-running research does link engagement to business outcomes including retention and productivity[2], but a CFO has heard that citation before and has never once released budget because of it.
The specific version is different. Overlay your reach data on regretted attrition by site or function. If the three locations with the lowest communications coverage are also the three with the highest regretted attrition, you have a local, specific, testable claim, and the replacement cost of those leavers is a number HR already holds. You are not claiming causation. You are proposing a targeted intervention with a measurable outcome, which is exactly what a budget request should look like.
What each argument needs, and where it comes from
| Argument | The currency it trades in | Evidence required | Where it comes from | Likely objection |
|---|---|---|---|---|
| Cost of clarification loops | Operating cost | Query volume tied to a specific message, handling time, loaded cost | Service desk or shared inbox, plus publication dates | “Those queries would have happened anyway”. Answer with the before-and-after on a comparable message |
| Change programme adoption | Capital or programme business case | Coverage of the specific populations named in the programme, over time | Channel activity joined to function and site | “Adoption is the programme’s job”. Answer by co-owning the number rather than claiming it |
| Compliance coverage | Risk and audit | Percentage of an in-scope population reached within a defined window, and the identity of the gap | Channel activity joined to role and contract type | “We already send it to everyone”. Sending is not receiving, and the audit distinction matters |
| Targeted attrition | Replacement cost | Reach by site or function, overlaid on regretted attrition | Your data plus an HR extract | “Correlation is not causation”. Correct, so propose a test on two sites, not a claim |
The two arguments to stop making
The first is the engagement score with no baseline and no denominator. A number that moved from 68 to 71 with no explanation of what would have made it move to 65 reads as noise, and presenting noise to a finance audience costs you credibility you will need later. Our companion piece on the internal communication KPIs that hold up in 2026 covers what to present instead.
The second is the appeal to importance. “Communication has never been more critical” is not an argument, it is a mood, and every function in the building has its own version of it. Gallagher’s State of the Sector research has found for years that measurement is the capability internal communicators rate lowest in themselves[3], and the appeal to importance is what fills the gap when the measurement is not there.
The concession worth making out loud
There is a limit to all of this, and stating it yourself is more persuasive than being caught by it. Internal communications cannot claim sole credit for a business outcome. A safety improvement involves training, supervision, equipment and communication, and no honest analysis separates them cleanly. What you can claim is the part you control: that the message reached the people it was for, in the time it needed to, and that where it did not, you can name who and why. Make that claim precisely and refuse the larger one, and the smaller claim becomes far more believable. How to calculate the ROI of internal communications works through the arithmetic without overstating it.
Getting the evidence out of a Microsoft 365 estate
The Microsoft 365 admin centre reports are free, already switched on, and adequate for the operational half of your reporting[4]. If you want to know which SharePoint site was busy last week, native reporting answers it and nothing else is needed.
Every argument above, however, needs a denominator drawn from workforce attributes: a population defined by function, site, country or contract type. Native reports do not hold those attributes, their retention window makes multi-year comparisons awkward, and they report per surface rather than per person across surfaces. That is a structural limit rather than a fault.
Teams often close the gap with Power BI on the Microsoft Graph reporting API. It can be done well, and it costs more than the first estimate. 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 the worst possible thing to discover in the middle of a budget conversation. A dependable build needs a robust ingestion process and scheduled reconciliation against native figures, with a named owner. Budget for the pipeline rather than the dashboard.
Where Tryane fits
Tryane reads SharePoint, Viva Engage, Teams and your newsletter platform together, joins that activity to your organisational structure through Entra ID or an HR file, and holds history across product transitions so a year-on-year argument survives a migration. That is what turns each of the four arguments from an assertion into a number. For the format of the conversation itself, the board pack that earns budget and how to prove internal communications works to leadership are the practical companions to this piece.
Tryane is SOC 2 Type 2 certified and GDPR compliant by design, hosts in the EU by default with US data residency on request, and deploys in a couple of hours with single sign-on through Azure AD or Entra ID.
Frequently asked questions
Why do organisations invest in internal communications at all?
Because coordination failures are expensive and largely invisible until someone measures them. People acting on outdated information, duplicated work across sites, safety instructions that never reached a shift, change programmes that miss adoption targets. The function exists to reduce the cost of everyone not knowing the same thing, and the business case is strongest when it is expressed in exactly those terms.
What is the single strongest argument for an IC budget?
Adoption inside an already-approved change programme, in most organisations. The money is already committed, the assumption is already written down, and the failure cost is already quantified by someone else. You are not asking for a new business case, you are protecting one that exists.
How do I answer “prove communications caused that outcome”?
Do not try. Concede that no honest analysis isolates communication from training, supervision and management, then claim the part you own: the message reached this population in this time, and here is who it missed. A narrow claim you can evidence beats a broad claim you cannot.
Is an employee engagement survey enough evidence?
No, and it is the wrong instrument for this job. Surveys measure how people feel at the moment they were asked, typically once or twice a year, with self-selection in who responds. Behavioural data measures what happened, continuously, for everyone. Use both, but take the budget argument in with the behavioural data.
Can I build this case with Microsoft 365 native reporting alone?
Partly. You can evidence that content was published and viewed. You cannot express any of it as a percentage of a defined population without joining to workforce attributes, and every argument in this article depends on that denominator. You will need either a recurring export and join, or a measurement layer that performs it.
Sources
• Deloitte, Global Human Capital Trends
• Gallup, employee engagement and business outcomes
• Gallagher, State of the Sector
• Microsoft Learn, Microsoft 365 activity reports
Further reading
• How to calculate the ROI of internal communications
• Executive reporting: the board pack that earns budget
• The annual internal communications report: a C-suite template
• Building an internal communications maturity model
• Engagement surveys versus communications data
Tryane runs a 15-minute call with Heads of Internal Communication, taking one of these four arguments and showing which parts you could already evidence from your own tenant before your next budget round. Book 15 minutes with Jérémy.