An internal newsletter is a recurring update sent to everyone in an organisation, and it is one of the few communication habits that either works well or wastes everyone's time — there is very little middle ground. The ones that work share a shape: short, arriving on the same day every time, written in a voice that sounds like a person, and containing at least one thing the reader could not have found out otherwise.
The failure mode is consistent enough to describe precisely. It starts as a genuine update, then departments ask for space, then it becomes a newsletter about the newsletter's contributors, then it is twelve sections long and the open rate is nineteen per cent. Nobody decided this; it happened because nothing was ever removed.
What belongs in an internal newsletter
- Decisions, and what they change for the reader. This is the single item people actually want and the one most often left out because it is uncomfortable to write.
- Numbers that matter to everyone, including the ones going the wrong way. A newsletter that only reports good weeks is read as marketing within two months.
- Who joined and who moved, with what they work on — the most-read section in almost every organisation.
- One thing worth learning from — a customer story, a post-mortem, a thing that went wrong and what changed.
- What is coming that needs the reader to do something, with the date and the ask stated plainly.
What does not belong
Congratulations rounds that name half the company, restated strategy with no news attached, department updates written to prove a department is busy, and anything that is really an announcement needing acknowledgement. That last one matters: a policy change, a deadline or something requiring action belongs in a direct message to the people affected, not buried in section seven of a weekly digest. If it is important enough that you would be upset it was missed, it should not be in a newsletter at all.
Making it survive the sixth issue
- Fix a slot and keep it. Same day, same time. Predictability does more for open rates than any subject-line technique.
- Cap the length before you start writing — a screen, or five items. A cap forces editorial decisions; without one, everything submitted goes in.
- Give it a single named author with the right to cut. A newsletter assembled from submissions has no editor and reads like it.
- Lead with the thing people most want to know, even when it is the awkward one. Burying it teaches people to skim.
- Write subject lines that say what is inside. Team update, week 34 tells the reader nothing they can act on.
- Ask three people every quarter what they remember from the last month. That is your real metric; opens only tell you the subject line worked.
Bad news is what earns a newsletter its readership. An update that reports a lost customer, a slipped deadline or a decision that did not work is read carefully, because it establishes that the good weeks are also being reported honestly. A publication that has never carried anything uncomfortable is understood, correctly, as a channel rather than a source.
Sending it
Ettex Mail sends it and keeps the template consistent from issue to issue, which matters more than it sounds — a familiar shape is what lets people find the section they care about in ten seconds. Where a discussion is wanted rather than a broadcast, a channel in Ettex Chat is the better home, and the tooling question generally is covered in internal communication tools. The formatting side, including the parts that break in Outlook, is a separate write-up in email templates.
What we do not do: there is no read-tracking of individual employees, no engagement scoring per person, and no intranet-style publishing portal. Deliberately, in the first two cases — measuring who opened an internal email is a fast way to make people stop reading it honestly, and the useful signal was never in the open rate anyway.
Frequently asked
How often should an internal newsletter go out?
Weekly or fortnightly, at a fixed time. Monthly is usually too infrequent to build the habit, and daily turns into noise unless the organisation genuinely changes daily.
How long should it be?
One screen, or about five items. Set the cap before writing; it is the constraint that forces the editing which makes it worth reading.
Should you track who opens it?
Aggregate open rates are a weak but harmless signal. Tracking individuals is a bad trade — it changes behaviour without telling you anything you could act on, and people notice.
What if nobody reads it?
Usually it contains nothing the reader could not get elsewhere. Add decisions and numbers — including the bad ones — cut the length by half, and give it one editor with the authority to say no.