A Template for the Internal Newsletter That Survives a Real Organisation

By Nicolas Saliba · Published August 2025, Updated August 2026 · 8 min read

It is Wednesday afternoon and eleven items have been submitted for Friday’s newsletter. Two are genuinely operational: a change to expense approval and a plant shutdown date. Four are department updates that a director asked to be included. Three are event promotions. One is a 900-word message from a function head who has asked twice why their last piece was cut. One is a photograph of a charity run.

The template you are about to open decides all of that, or it decides none of it. That is the actual test of an internal newsletter template, and it has almost nothing to do with fonts. A template is an editorial contract: a written agreement about what goes in, in what order, at what length, decided by whom. Design it that way and Wednesday takes twenty minutes. Design it as a layout and Wednesday takes three hours and produces something no one finishes reading.

Why the layout-first template fails

Most internal newsletter templates are built from the organisation outwards. Someone maps the stakeholders, gives each of them a block, and the result is a document that describes the org chart rather than the week. It fails in a predictable way: the blocks all fill, every issue is the same length regardless of whether anything happened, and priority becomes invisible because everything has equal visual weight.

The reader experiences this as noise. They are reading on a phone, between two meetings, and they are giving you somewhere between twenty and sixty seconds before they decide whether this issue is worth scrolling. If nothing in the first screen tells them what changed for them, the honest response is to close it, and most of them do.

The alternative is to build the template from the reader inwards, starting with a single question: what does this person need to know or do that they did not know on Monday? Everything else in the structure is subordinate to that.

The five-slot structure

This structure holds up across manufacturing, retail, healthcare and professional services, in organisations from around 1,500 people upwards. The caps matter as much as the slots. A cap you can enforce is what turns a template into a decision.

Slot	Its job	Hard cap	What failure looks like
1. The one thing	The single most important item this issue, chosen by the editor	One item, 60 to 90 words, one link	Two or three items competing, so none of them lands
2. Changes that affect you	Operational changes: policy, systems, sites, safety, pay	Three items, 30 words each	Aspirational content smuggled in as an operational change
3. From the business	Rotating slot for functions and units, on a published rota	One unit per issue	Every function every week, so the section is unreadable
4. People	Appointments, arrivals, recognition, milestones	Five lines	Recognition only ever for head-office populations
5. Dates and actions	Anything with a deadline the reader owns	Five lines, each with a date	Items with no deadline and no owner parked here

Two of these carry most of the weight. Slot one is where the editorial judgement lives: choosing it is the job, and refusing to choose is the failure mode. Slot three is where the political pressure lands, and a published rota is what protects you, because “you are in the 14 October issue” is a far easier conversation than “not this week”.

Writing for the forty-second scan

Assume the reader scans headings, reads slot one, and leaves. That has three consequences for the writing. Headings must carry the information rather than tease it, so “Expense approvals move to Concur on 3 November” and not “An update on expenses”. Each block needs exactly one link, because a block with four links has no call to action. And the first sentence of each block should be readable on its own, since it is often the only sentence read.

The 900-word message from the function head is not a slot problem. It belongs on the intranet as a news post, with a 40-word summary and a link in the newsletter. That is not a demotion, and it is worth explaining it that way: the newsletter is a routing layer, the intranet is where things are read at length. Microsoft’s guidance on setting up an organisation news site is the practical starting point for that split^[1].

Design decisions that change behaviour

Very few visual choices in an internal newsletter change anything measurable. These few do.

Single column, mobile first. Two-column newsletters reflow unpredictably in Outlook on Android and iOS, and a substantial share of your readership is opening it there. Test in the clients your organisation actually uses, not in the design tool.
Legible with images off. Many corporate mail clients block remote images by default. If your slot one headline is inside an image, a portion of your audience receives a blank rectangle.
No attachments. A PDF attachment is unmeasurable, unsearchable, and invisible to anyone reading on a phone. Link to the document in SharePoint instead.
One consistent link style. Descriptive anchor text, never a bare URL and never a generic button label. It helps screen reader users and it makes the click data interpretable afterwards.
A stable send time. The template is a habit as much as a document. Moving the send time is the fastest way to break the habit you spent a year building.

One newsletter or several?

The instinct to split is usually right and usually acted on too early. Splitting into six regional editions triples the editorial load and, in most organisations, is done to satisfy internal stakeholders rather than readers.

Two tests are worth applying before you split. First, is the difference between the audiences operational or merely organisational? A shift pattern, a language, a regulatory regime or a site closure is operational. Reporting into a different director is not. Second, do you have someone who will own the second edition editorially, week after week, in eighteen months’ time? If the answer is no, you are creating an edition that will decay into a copy of the main one with a different header.

Where the difference is real, targeting is usually the better first move: audience targeting in Viva Connections and SharePoint lets you vary a block rather than duplicate an edition^[2]. Getting the attributes right first matters more than the mechanism, which is what our note on audience segmentation for internal communications covers. For populations without a personal mailbox, splitting the newsletter does nothing at all, and measuring frontline communications is the more useful problem to work on.

Telling whether the template is working

Open rate tells you about the subject line. It tells you very little about the template, and this is where most newsletter measurement stops. Our dedicated piece on internal newsletter metrics works through the measurement properly. Three tests speak directly to the structure.

Test the slot, not the issue. Click distribution across slots one to five, tracked over ten issues, tells you whether your editorial judgement matches your readers’. If slot one consistently attracts fewer clicks than slot five, your editor and your audience disagree about what matters, and that is worth knowing.

Test order, not just subject lines. A/B testing subject lines is easy and mostly tells you about curiosity. Swapping the order of slots two and three for half the list, then comparing read-through, tells you something about structure.

Test read-through by population. Aggregate engagement hides the only failure that matters. Gallagher’s State of the Sector research has consistently identified measurement as the capability internal communicators name as their biggest gap^[3], and Gallup’s workplace research has repeatedly found engagement to be weakest in frontline and deskless populations^[4]. A newsletter with a healthy overall open rate and near-zero readership in operations is a newsletter that is working for the people who needed it least.

Native email statistics will not answer that last one on their own, because they do not hold your organisational structure. This is the layer Tryane sits in: it reads your newsletter platform alongside SharePoint, Viva Engage and Teams, joins the activity to your organisation through Entra ID or an HR file, and keeps the history when the platform changes. 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 through single sign-on. If your newsletter is one of several channels carrying the same message, cross-channel measurement is the next thing to fix, and content calendar performance covers how the rota in slot three earns its place.

Frequently asked questions

How long should an internal newsletter be?

Set the cap by slot rather than by total length, because a total word count invites padding when the week is quiet. The five-slot structure above lands at roughly 400 to 500 words in a normal week and can honestly run shorter. An issue that is visibly shorter because little happened builds more trust than one padded to a fixed size.

How often should we send it?

Weekly works when there is genuinely something operational to route each week, which is true in most organisations above a few thousand people. Fortnightly is better than a weekly edition that is half filler. Whichever you choose, keep the day and time fixed: the predictability is doing more work than the frequency.

Should the newsletter contain the full article or a link?

A summary and a link, in almost every case. Full text in email is unmeasurable beyond the open, hard to update once sent, and invisible to search. Routing readers to the intranet also gives you a page-level view of who read to the end, which the email alone cannot tell you.

How do we handle a senior stakeholder who wants more space?

Give them the rota rather than the argument. A published schedule showing which unit appears in which issue converts an editorial refusal into a date, and dates are far easier to defend. If the item is genuinely urgent and operational, it belongs in slot two at 30 words, not in a longer feature.

Can we measure the newsletter and the intranet as one campaign?

Not with the native tooling alone. The newsletter platform counts opens and clicks against its distribution list, SharePoint counts views against its own population, and neither holds the organisational attributes needed to compare them fairly. Joining them requires a layer that reads both and resolves them against a single definition of your workforce.

Sources

• Microsoft Learn, create an organisation news site

• Microsoft Learn, audience targeting in Viva Connections

• Gallagher, State of the Sector

• Gallup, State of the Global Workplace