Company Newsletter Ideas That Employees Actually Read
Company newsletter ideas that people actually open: setting cadence, recurring sections, subject lines, who writes it, how to measure it, when to stop.
Company Newsletter Ideas
How to run an internal newsletter people actually open
I sent a company newsletter every Monday for eleven weeks before I found out that most of the team was not reading it. The discovery was accidental. In a one-on-one I referenced a policy change I had announced in issue six, and the person across from me had no idea what I was talking about. Neither did the next three people I asked.
The newsletter was not bad. It went out on time, it was well written, and it had a clean template. It was also entirely optional to read, because it had never once told anyone something they could not have learned from their manager, a chat channel, or the shared calendar. It was a container with nothing inside it.
This guide is about the version that works. It covers what a newsletter is actually for, how to pick a cadence you can hold, a bank of recurring sections and one-off ideas sorted by what each one is trying to achieve, how to write a subject line that survives an inbox, who should write it, how long it should be, how to tell whether anyone reads it, how to reach people who do not sit at a desk, and how to end it honestly. I run a small team at FirstHR and I have made most of these mistakes personally.
What a Company Newsletter Is Actually For
An internal company newsletter has one job: to move information people need but would not go looking for, on a schedule they can predict. Everything else it appears to do, including culture, morale, and connection, is a side effect of doing that one job well.
The honest answer about most newsletters is less flattering. They exist because someone decided there should be one. An investor asked about internal communication, a new hire arrived from a bigger company that had one, or a founder read that culture requires storytelling. Nobody ever wrote a brief.
There is a one-question test for this. Name the decision, behavior, or piece of context the next issue is supposed to change. If you cannot answer, you are producing content rather than communicating, and content on a schedule is how a newsletter becomes an obligation nobody remembers agreeing to.
Three jobs justify a newsletter at a small company. The first is carrying decisions and the reasoning behind them to people who were not in the room. The second is making work visible across teams that do not naturally see each other. The third is creating a written record that outlasts a chat message.
That third job is badly underrated. A chat channel is a river, and anything said on a Tuesday afternoon is effectively gone by Thursday. A newsletter that is archived somewhere findable becomes the answer to the question of when exactly something changed, asked six months later. Most teams do not need a full intranet to get that property.
A newsletter is also not where bad news breaks first. Layoffs, pay changes, and anything affecting one specific person belong in a conversation. Using a mass email to deliver the first word on hard news reads as avoidance, and people remember exactly how they found out.
Treat the newsletter as one channel inside a larger internal communication strategy, and understand that it is the wrong first channel for most small teams. If your weekly rhythm and your one-on-ones are not working, a monthly email will not rescue them. It performs best layered on top of something that already functions.
How to Set the Cadence: Let the Rate of Change Decide
Cadence should be set by how much genuinely changes in your company, not by what sounds professional. If you cannot fill an issue without inventing content, the cadence is too fast, and your readers will figure that out faster than you will.
Run the count before you commit to anything. List everything that changed in the last 30 days that someone outside the room would want to know: decisions made, people who joined or moved, customers won or lost, policies updated, deadlines that shifted, tools swapped. Count the items honestly and resist padding.
Fewer than five items in a month means monthly is already ambitious. Five to ten supports monthly comfortably. More than fifteen makes every two weeks reasonable. Weekly is rare outside companies in the middle of something unusual, and it should be treated as temporary rather than permanent.
| Items Worth Reporting in 30 Days | Cadence That Fits | Realistic Production Cost | What Breaks If You Go Faster |
|---|---|---|---|
| 0 to 4 | Quarterly, or no newsletter at all | 1 to 2 hours per issue | Sections get filled with invented content and readers learn the whole thing is optional |
| 5 to 10 | Monthly | 2 to 3 hours per issue | Half the issues carry nothing new, and the subject lines start sounding identical |
| 11 to 15 | Every two weeks | 2 to 3 hours per issue | The writer burns out well before the readers do |
| 16 or more | Weekly, and treat it as temporary | 3 to 4 hours per issue | Nothing, until the unusual period ends and the volume quietly drops |
The default mistake is starting weekly because weekly signals commitment. It signals the opposite within a month. Three strong issues followed by a two-week gap teaches people that the schedule is a suggestion, and a monthly issue that has never been late is more credible than a weekly one that skips.
Volume carries a real cost. Research published by Harvard Business Review (May 2023), drawn from a survey of nearly 1,000 employees and managers, reported that 38 percent said they receive an excessive volume of communications at their organization, and only 13 percent said they received less information than the year before. Every issue you send competes inside that pile.
Anchor the send to a fixed slot and never move it. Same day, same hour, every time. People do not consciously memorize your schedule, but they do develop pattern recognition for it. Mid-morning midweek is a sane default for most US teams, since Monday competes with the week starting and Friday afternoon competes with leaving, but the consistency matters more than the slot you pick.
For teams spread across time zones or shift patterns, the exact send time matters far less than the fact that reading it requires nobody to be online at a particular moment. That is the structural advantage a newsletter has over a meeting: it is asynchronous by default and it does not cost everyone the same hour.
The Recurring Section Bank, Organized by What Each One Does
A recurring section earns its slot only if it does one specific job: carrying a decision, making invisible work visible, closing a loop that is currently open, or lowering the cost of asking a question. Sections that exist to fill space get skipped, and the skipping habit spreads to the sections that matter.
The bank below is organized by that test. Under each goal sit sections that reliably do the job at small-company scale. Pick three to five in total, not three to five per category. A newsletter with nine recurring sections is a magazine, and nobody on your team signed up to publish one.
Keep one slot deliberately variable. Four fixed sections plus one rotating slot gives you consistency without monotony, and the rotating slot is where one-off ideas live. Regular readers usually check that slot first once they learn it is the part that changes.
Two warnings about the recognition instinct. Recognition in a newsletter is a supplement and never the primary channel, because praise arriving four weeks after the work lands flat. And if the same two names appear every issue, the section stops reading as recognition and starts reading as favoritism.
One-Off Newsletter Ideas Worth Running
One-off ideas are the ones you run when there is a reason, not on a schedule. Each should be tied to a goal you can state in a single sentence, and each has a specific, predictable way of failing that is worth knowing before you commit an issue to it.
| One-Off Idea | What It Is Trying to Achieve | Run It When | How It Fails |
|---|---|---|---|
| Employee spotlight | Make one person’s actual work legible to teams that never see it | A team is misunderstood, newly formed, or growing fast | Favorite-snack questions that reveal nothing about the job |
| Decision explainer | Give context for a change people already noticed | A visible change landed without a stated reason | Written as an announcement instead of an explanation |
| Customer story | Connect back-office roles to the outcome they produce | A customer result is concrete, recent, and shareable | Sales language that reads as internal marketing |
| Behind the number | Teach the whole company what one metric actually means | A metric appears in meetings that few people understand | A chart with no sentence explaining why the number matters |
| Question recap | Close the loop on questions leadership already answered aloud | An all-hands generated real, unscripted questions | Only the comfortable questions make it into print |
| Policy in plain language | Reduce repeat questions to whoever handles HR | The same question arrives three times in a month | Restating the policy document instead of translating it |
| What we got wrong | Make it safe to surface problems early | A miss is already common knowledge internally | Sanitized until it reads as a disguised brag |
| Tool or process change | Prevent a week of confused support requests | Anything in the daily workflow is about to change | Sent after the change rather than a week before it |
| New hire introduction | Give a spread-out team a face and a scope | Someone joins, ideally in their first two weeks | Long biographies that nobody finishes reading |
| Period recap | Show progress people lived through but never tracked | A quarter or a fiscal period closes | Turned into self-congratulation with the misses removed |
| Open enrollment walkthrough | Cut benefits questions and missed deadlines | An enrollment window opens | One long issue instead of a short series with dates |
Notice what is absent from that table: trivia, memes, riddles, and coworker fun-fact segments with no purpose behind them. They are not forbidden. They are simply not ideas, they are filler, and filler is the evidence readers use to decide the whole thing is safe to ignore.
The employee spotlight is the most requested one-off and the most commonly botched. Done badly it is a template of hobby questions. Done well it answers what this person does all day and what other teams consistently get wrong about their work. An employee spotlight template saves the interview prep; the questions still have to be worth answering.
Work anniversaries and new hire introductions are the two items that hold up over years, because they are often the only way a distributed team learns who joined and who stayed. Hold them to two sentences each and they will never wear out. Expand them into profiles and they will.
Subject Lines and Openings That Survive an Inbox
A subject line has to answer one question in about six words: why open this instead of archiving it. The opening then has to deliver on that promise within the first two lines, because the preview text sitting next to the subject line is doing real work whether you wrote it deliberately or not.
A subject line like Company Newsletter, Issue 14 names the container rather than the contents. It is the internal equivalent of a package with no label. The reader has to open it to discover whether it matters, and after the third time it did not, they stop opening it entirely.
The fix is boring and reliable. Put the single most consequential item of the issue in the subject line. If the biggest thing is a health plan change, the subject line is the health plan change. If the biggest thing this period is that nothing much happened, that is a strong signal your cadence is wrong.
Preview text is the second subject line and almost nobody writes it on purpose. Most email tools pull the first line of the body, which is why so many internal newsletters preview as a greeting about hoping everyone had a great weekend. Write that first line as if it were the subheadline, because functionally it is one.
Skip the greeting paragraph entirely and lead with the item. A reader who decided in two seconds that this issue is relevant will read a greeting on the way past it. A reader who has not decided yet will never reach the item you buried underneath it.
Do not tease. Phrases promising big news inside train people to expect a payoff and then punish them when the payoff is a parking lot update. One broken promise costs more future readership than ten dull but honest subject lines ever will.
Who Should Write It: Why Rotating Authorship Beats One Owner
One person should own the schedule, the format, and the final edit. The writing itself should rotate. A single author produces a single voice, a single point of view, and a single point of failure, and that failure arrives during the first genuinely busy month.
The founder-written newsletter is the most common version at small companies and it follows a predictable arc. The first six issues are excellent because the founder cares. Then a quarter closes, two issues slip, and the newsletter quietly ends. Nobody announces the ending. It simply stops.
Rotation solves three problems simultaneously. Sourcing gets easier, because the writer of the month already knows what happened in their part of the business. Voice varies, which keeps consecutive issues from reading identically. And the format survives any one person being underwater, on leave, or gone.
A practical rotation at small scale: the owner writes one issue in four and edits the other three. The remaining issues go to whoever has the most to report that period, with the assignment made at least a week ahead so nobody is drafting at eleven at night on the send date.
Rotation is not democracy. The owner keeps the deadline, the section list, the word limit, and the right to cut anything. Handing all of that to a committee is how a newsletter turns into a negotiation, and negotiations miss ship dates far more reliably than individuals do.
Give every rotating writer the same brief in writing: the section list, the word limit, the due date, and one sentence about what this specific issue needs to accomplish. Writers at a small company do not need training. They need constraints and one example of a past issue that worked.
If your team already runs a regular all-hands meeting, the newsletter writer should be in the room for it. Half of the content problem is sourcing, and the all-hands is exactly where the sourceable material surfaces in a form somebody has already thought through.
Length and Format: The Scroll Test
Aim for something a person can read completely in under three minutes, which is roughly 400 to 600 words, with every item understandable from its first line alone. If it needs a table of contents, it has stopped being a newsletter and become an internal publication.
The scroll test is the fastest quality check available. Open your draft on a phone. If your thumb has to move more than four or five times to reach the bottom, cut something. Most people read internal email on a phone, standing up, in the gap between two other tasks.
A structure that holds up: one lead item that gets three or four sentences, three to five short items that get two sentences each, and one closing line that either points somewhere specific or asks for something specific. Anything beyond that belongs in a linked document.
Write every item so the first line states the news and everything after it is optional. Open enrollment closes on November 14 comes first, the explanation second. Readers scan first lines and stop where something matters to them, so news buried in sentence three effectively does not exist.
Plain email beats a designed template at small-company scale. Heavy templates load slowly, break in some clients, get clipped by Gmail past a certain message size, and signal marketing rather than internal news. A plain message from a real person’s address consistently outperforms a branded one here.
Email should stay the default channel because it is the only one nearly everyone has, it stays searchable, and it does not scroll away. Mirroring the content into your team communication channels is fine and usually helps. Publishing only there means the record disappears the moment the channel moves on.
Archive every issue somewhere permanent. A shared drive folder works, and so does the document area of an employee self-service portal like the one built into FirstHR. The archive is what converts a broadcast into a record, and it costs about thirty seconds per issue.
How to Launch the First Issue
Write three complete issues before you send one. If you cannot fill three, you do not have a newsletter, you have a single announcement, and the right move is to send that announcement and skip the rest of this.
The three-issue test is the cheapest way to discover that your intended cadence is not real. It also buys you a buffer, so the first month does not depend on every week going smoothly, which no first month ever does.
Announce the newsletter once, briefly, and then stop selling it. Credibility comes from issue four arriving on the day it was supposed to, not from issue one having a logo. Every launch campaign I have seen for an internal newsletter has outlived the newsletter itself.
How to Tell Whether Anyone Reads It
Open rate is the weakest signal you have and the one everyone quotes. The measurements that actually tell you something are click-through on the one link you care about, reply volume, and whether people reference the newsletter without being prompted to.
Open tracking works by loading a tiny invisible image. Privacy features in modern mail clients preload that image whether or not a human ever looked at the message, which inflates opens, while other clients block images entirely, which deflates them. The number moves for reasons unrelated to reading.
The single-link test is far better. Put exactly one link in each issue leading to something a reader would only click if they actually read the item. Click-through on that link, divided by the number of people you sent to, is the closest thing to a real readership number you will get.
| Signal | How to Get It | Healthy at Small-Company Scale | What a Bad Number Usually Means |
|---|---|---|---|
| Click-through on the one tracked link | Clicks on that link divided by recipients | 20 to 30 percent | The lead item was not news, or the subject line oversold it |
| Replies per issue | Count them, including one-line reactions | At least a few percent of recipients | The issue asked nothing and invited nothing |
| Unprompted references | Notice mentions in meetings and one-on-ones | Any at all, every month | Nobody is treating it as a source of truth |
| Recall spot check | Ask five random people what was in the last issue | Two of five name the lead item | The lead item was buried, or there was no real lead |
| Archive visits | Page views on archived issues | Slow, steady growth over months | The archive is not findable, or nothing in it is worth revisiting |
| Open rate | Your email tool | Directional only, never a target | Inflated by image preloading and deflated by image blocking |
The qualitative test costs five minutes and beats every dashboard. Pick five people at random the day after an issue goes out and ask what was in it. Not whether they liked it. What was in it. Two out of five naming the lead item is healthy. Zero out of five is your answer.
Track these alongside your other HR metrics and review them quarterly rather than per issue. Single-issue swings are noise, usually caused by whatever else landed in the inbox that morning. A three-month slide in click-through is a trend, and it almost always means the content stopped being news.
Do not attach the newsletter to employee engagement scores and claim credit. Engagement moves for reasons that dwarf a monthly email: manager quality, pay, workload, and whether people believe what leadership tells them. A newsletter can support those things. It cannot substitute for any of them.
Accessibility and the Employees Who Do Not Sit at a Desk
Reach staff without a company inbox on a channel they already use during the working day, and build accessibility into the email version from issue one rather than after somebody finally asks. Both are cheap at launch and awkward to retrofit later.
If part of your workforce has no company email address, an email newsletter reaches a fraction of your company and you will never notice, because the people who do not receive it also do not complain about not receiving it. Silence gets misread as satisfaction.
In 2025, 35 percent of employed people did some or all of their work at home on days they worked, while 70 percent did some or all of it at their workplace, according to the Bureau of Labor Statistics American Time Use Survey (2025 annual averages, released June 25, 2026). Home working has not replaced the workplace; for most employed people at least part of the job still happens on company premises.
For front-line and shift-based employees, email is the wrong channel and collecting personal email addresses is the wrong workaround. Pick from the channels that already reach them at work, and pick before launch rather than after the first person mentions they have never seen an issue.
| Channel for Staff Without a Company Inbox | What It Reaches Well | What It Costs You | Where It Fails |
|---|---|---|---|
| One page posted at the time clock or in the break room | Anyone who physically shows up for a shift | A few minutes and a printer per issue | Nothing is measurable, and last month’s sheet stays up until somebody takes it down |
| Text message with one short link | Staff who carry phones and are allowed to use them on shift | A maintained number list and per-message cost | It runs on personal phones and personal numbers, and it arrives whether or not the person is on the clock |
| Two-minute readout at shift handover | Crews that already gather at the start of a shift | Two minutes of the shift lead’s time | Every crew hears a slightly different version and none of it is written down |
| Copy handed out with the schedule or pay stub | Everyone on payroll, with no separate list to keep current | Almost nothing beyond what distribution already costs | It arrives on the payroll calendar rather than the newsletter one |
| Screen in a shared space | Sites with a fixed common area and steady foot traffic | Hardware, plus a named person who updates it | It becomes wallpaper within weeks if the content sits there unchanged |
Print still works and gets dismissed far too quickly. In my experience a single dated sheet on the break room wall gets read by more of a warehouse crew than the same message sent to an inbox they open once a month. Print the same content rather than a watered-down version.
Accessibility is the other half of reaching everyone. Federal guidance on accessible email messages published by the General Services Administration covers the practical rules: give every image meaningful alternative text or mark it decorative, use real heading structure instead of bolded lines, keep sufficient color contrast, and keep alt text clear and under 250 characters.
Text inside an image is the most common failure and the easiest to fix. A screenshot of an announcement is invisible to a screen reader, unsearchable in your archive, and unreadable on a small phone. Type it out. If the image has to stay, put the same information in text beside it.
Send a plain-text alternative if your tool offers one, and write it as though it were the only version anyone will see. Some employees read on older devices, some on restricted work phones, and some have images turned off by company policy they did not choose.
When to Kill the Newsletter
Kill it when it stops carrying information people cannot get elsewhere, or when producing it costs more attention than reading it returns. Both happen gradually rather than suddenly, which is precisely why almost nobody notices in time to act.
Four signals, any one of which should start the conversation. Click-through on your tracked link has fallen for three consecutive months. The writer is filling sections with content invented to fill sections. Nobody replies, ever. And you catch yourself describing it to a new hire as something the company does rather than something they should read.
The fifth signal is structural. If the company has changed shape since you started, the newsletter may have been replaced without anyone deciding to replace it. Teams that built a genuine weekly rhythm often discover the newsletter is now repeating things everyone already read three days earlier.
Killing is not the only option, and it is rarely the best one. Slowing down usually works better: a monthly that has run out of material makes an excellent quarterly. Folding in works too, where the content becomes a standing item on an agenda that already has a guaranteed audience.
If you do end it, say so. One short message naming the final issue, pointing to the archive, and stating where this information will appear instead. Newsletters that stop without an announcement leave people unsure whether they were quietly dropped from a distribution list, and that small confusion is worse than the ending.
The real cost of a zombie newsletter is not the hour it takes to produce. It is that it teaches your team that company-wide messages can be safely ignored, which is expensive the first time you genuinely need everyone to read one. That habit also quietly undercuts whatever you claim about transparency in the workplace.
Frequently Asked Questions
How often should a company newsletter be sent?
Cadence should follow how much genuinely changes, not what sounds professional. Run a count: list everything from the last 30 days that an employee outside the room would want to know, including decisions made, people who joined or moved, policies updated, and deadlines that shifted. Fewer than five items means monthly is already ambitious and quarterly may fit better. Five to ten supports a monthly issue comfortably. More than fifteen makes every two weeks reasonable. Weekly is rare outside companies going through something unusual such as a funding round, an acquisition, or a seasonal peak. The bigger risk is not being too slow, it is committing to a pace you cannot hold. A monthly newsletter that has never been late is more credible than a weekly one that skips, because skipped issues teach people the schedule is optional, and readership rarely recovers.
What should go in a company newsletter?
Every recurring section should do one of four jobs: carry a decision and the reasoning behind it, make invisible work visible across teams, close a loop that is currently open, or lower the cost of asking a question. Sections that fail all four are filler. A practical starting set is four fixed sections plus one rotating slot: the decision or change of the period, what shipped or closed, people news covering arrivals and role changes, one company number with a sentence on why it moved, and a rotating slot for one-off items. Keep the total to three to five sections rather than three to five per category. Nine recurring sections turns a newsletter into a magazine and it gets abandoned within a quarter. The rotating slot is the part regular readers check first, once they learn that it changes.
Who should write the company newsletter?
One person should own the schedule, the format, the length limit, and the final edit. The writing itself should rotate. A single author produces a single voice, a single point of view, and a single point of failure, and that failure usually arrives during the first genuinely busy month. A practical rotation at a small company is for the owner to write one issue in four and edit the other three, assigning each one to whoever has the most to report, at least a week in advance. Rotation is not democracy. Handing the deadline and the section list to a committee turns every issue into a negotiation, and negotiations miss ship dates. Give each rotating writer the same written brief: section list, word limit, due date, and one sentence on what this issue needs to accomplish. Writers need constraints and one good example, not training.
How long should an internal newsletter be?
Target something a person can read completely in under three minutes, which is roughly 400 to 600 words. Use the scroll test: open the draft on a phone and count the swipes to the bottom. More than four or five means cut. Most internal email is read on a phone, standing up, between two other things. A reliable structure is one lead item of three or four sentences, three to five short items of two sentences each, and one closing line that either points somewhere specific or asks for something specific. Write every item so the first line states the news and everything after it is optional detail, because readers scan first lines and stop where something matters to them. If a newsletter needs a table of contents or a jump menu, it has stopped being a newsletter and become an internal publication nobody asked for.
What is a good open rate for an internal newsletter?
Open rate is the weakest number you have and the one most often quoted. Open tracking works by loading a tiny invisible image, and privacy features in modern mail clients preload that image whether or not a human ever looked at the message, which inflates the figure. Other clients block images entirely, which deflates it. The number moves for reasons that have nothing to do with reading. A better measure is the single-link test: put exactly one link in each issue leading to something a reader would only click if they read the item, then divide clicks by the number of people you sent to. At small-company scale, 20 to 30 percent on that link is healthy and anything under 10 percent is a warning. The cheapest test of all is asking five random people the day after what was in the issue.
How do you reach employees who do not have a company email address?
Do not solve it by collecting personal email addresses. Use channels that already exist where those employees work. A printed one-page version posted where people clock in usually reaches more shift-based staff than an email sent to an address they open once a month. A text message with a short link works when phones are allowed on the floor, though it runs on personal numbers and lands whether or not the person is on the clock. A two-minute readout by the shift lead at handover works when phones are not allowed. According to the Bureau of Labor Statistics American Time Use Survey for 2025, 70 percent of employed people did some or all of their work at their workplace on days they worked, so on-site staff are the norm rather than an edge case, and in shift-based industries many of them have no company inbox. Whatever channel you pick, distribute the same content rather than a shortened version, and date each issue so people know which one they are holding.
Should a company newsletter be an email or a chat post?
Email should be the default and chat should be the supplement. Email is the only channel nearly everyone at the company reliably has, it stays searchable months later, and it does not scroll away. A chat channel is a river: anything posted on a Tuesday afternoon is effectively gone by Thursday, which destroys the newsletter’s most valuable property, being a durable record of when things changed. Posting the same content in chat as well is fine and usually raises readership. Posting only in chat means the archive does not exist. Plain email also beats a heavily designed template at small-company scale, because heavy templates load slowly, break in some clients, get clipped past a certain message size, and read as marketing rather than internal news.
When should you stop sending a company newsletter?
Stop when it no longer carries information people cannot get elsewhere, or when producing it costs more attention than reading it returns. Four signals are each sufficient to start the conversation: click-through on your one tracked link has fallen for three consecutive months, the writer is inventing content to fill sections, nobody ever replies, and you describe it to new hires as something the company does rather than something they should read. Slowing down often beats stopping. A monthly that has run out of material makes a strong quarterly, and folding the content into an existing meeting agenda keeps the audience you already have. If you do end it, say so in one short message that names the final issue, points to the archive, and states where the information will appear instead. Newsletters that stop silently leave people unsure whether they were dropped from a list.