The Internal Newsletter: Format, Cadence and Content That Works

Most internal newsletters die the same death. Issue one lands with fanfare. Issue three ships a week late. Issue six is a wall of links nobody clicks. By issue ten, the person writing it quietly stops, and nobody asks where it went.

The failure is almost never effort. It is design. The newsletter was built around what leadership wanted to say instead of what employees needed to read, on a cadence the writer could not sustain, with no system for sourcing content and no way to know whether anyone read it. All four of those problems are fixable, and this guide walks through fixing each one: purpose, cadence, structure, voice, sourcing, production, distribution, and measurement.

Decide what job the newsletter does

An internal newsletter can do three jobs. It cannot do all three well, so pick a primary.

1. Alignment. Tell everyone what the company is doing and why, so a support rep in Denver and an engineer in Berlin describe the quarter the same way. Content skews toward strategy, metrics, and decisions.
2. Visibility. Surface work that would otherwise stay invisible: what teams shipped, what customers said, who solved a hard problem. Content skews toward project updates and cross-team show-and-tell.
3. Culture. Make a distributed group feel like one company: new hires, anniversaries, wins, photos, the human texture. Content skews toward people.

Here is the test for your primary job. Finish this sentence: "If someone reads nothing else all week, this newsletter guarantees they know ___." If you cannot finish it in ten words, you do not have a newsletter yet; you have a bucket.

A 40-person startup usually needs visibility first — everyone already hears strategy directly from the founder, but nobody knows what the other squads shipped. A 500-person company usually needs alignment first, because the all-hands can no longer carry it. Culture content belongs in every issue but almost never as the spine, because a newsletter that is only birthdays and dog photos trains people that it is skippable.

Write the job down as a one-line charter at the top of your planning doc, for example: "A weekly, five-minute read that guarantees every employee knows what shipped, what changed, and what is coming." Every section you consider later gets tested against that line.

Know your real audience count

Before designing anything, count your audiences. "Everyone" is not an audience. A typical mid-size company has at least three: individual contributors who want to know what affects their work, managers who need talking points for their teams, and leadership who read to check the message. If your company has frontline or deskless staff, that is a fourth audience with different access patterns — see Reaching Employees Who Do Not Sit at Desks for that specific problem. When audiences diverge sharply (for example, engineering versus retail staff), you eventually need two newsletters, not one bloated one. Under roughly 200 people, one newsletter with clearly labeled sections usually holds.

Choose a cadence you can survive

Cadence is a promise. Breaking it costs more than choosing a slower one, because an unreliable newsletter teaches readers not to expect it, and expectation is the entire asset.

Cadence	Best for	Production cost	Failure mode
Weekly	Fast-moving companies under ~150 people; visibility-focused letters	2–4 hours/issue	Writer burnout; thin issues that erode trust
Biweekly	Most teams; balances freshness and effort	3–5 hours/issue	Content ages awkwardly; "was that this sprint or last?"
Monthly	Alignment-focused letters; companies with a strong weekly feed elsewhere	4–8 hours/issue	Becomes a magazine; news arrives stale
Quarterly	Almost nobody	High	It is a report, not a newsletter

Two opinionated rules. First, choose the cadence you can hit on your worst week — the week with two launches and someone on vacation — not your best. If that is biweekly, ship biweekly. Second, pick a fixed day and time and treat it like a deploy window. Thursday morning is a strong default: Monday inboxes are hostile, Friday afternoons are dead, and Thursday gives managers material for Friday team meetings.

If news breaks mid-cycle, do not rush a special issue. Urgent news goes through your announcement channel immediately — that is a different mechanism with different rules, covered in Company Announcements That Do Not Get Ignored — and the newsletter recaps it with context later. The newsletter is the digest of record, not the alarm system.

The section stack: a structure that survives contact with reality

A newsletter is a stack of recurring sections. Recurring matters: readers scan for their favorite section the way they flip to a favorite column, and writers fill slots instead of facing a blank page. Here is a proven stack for a biweekly, visibility-primary newsletter at a 50–200 person company, in order:

1. The top note (100–150 words)

One short paragraph from a rotating leader — not always the CEO — that frames the period. Not a vision speech. A specific observation: "We closed the two biggest deals in company history this month, and both cited the onboarding revamp the platform team shipped in March. Compounding is real." Cap it at 150 words. If a leader sends 600, edit it to 150 and tell them why.

2. Ship log (5–8 bullets)

What went live since the last issue, one line each, with a link and a named team. Format each bullet as what changed → who benefits: "Invoice export now handles multi-currency (Billing team) — agencies with EU clients stop doing manual conversion." This section is the reason people open the newsletter. Never cut it for space.

3. One number

A single metric with two sentences of context. Rotate it: revenue one issue, support CSAT the next, then activation, then uptime. One number gets remembered; a dashboard screenshot gets skipped. If the number is bad, publish it anyway with what you are doing about it — nothing builds trust in a newsletter faster than an unflattering number, honestly framed.

4. Decision of the week (when there is one)

What was decided, by whom, and the one-sentence why. "We are pausing the mobile app rework until Q4. Reason: the top three churn drivers are all web-side, and we cannot staff both." This section quietly becomes the most valued one at companies that keep it honest, and it pairs naturally with a transparent decision log — more on that pattern in Default to Open.

5. Voices (2–3 items)

A customer quote, a screenshot of a great support interaction, a snippet from a sales call. Raw quotes beat summaries. "The proofing thing alone saved us four hours a week" does more than a paragraph about customer satisfaction.

6. People (3–5 lines)

New hires with one human detail ("Priya joins data from a wildlife-conservation nonprofit and owns two parrots"), anniversaries, internal moves, and one or two kudos pulled from wherever recognition happens in your company. Keep it tight. This is seasoning, not the meal.

7. Coming up

Three to five dated items: the all-hands, the release freeze, open enrollment deadline, the offsite RSVP cutoff. Deadlines in bold.

That is roughly a five-minute read. Resist adding sections until you have shipped ten issues. Every section is a promise to fill it forever.

Sections to steal for other charters

If your primary job is alignment, swap Ship log's top position for a "State of the quarter" section: each company goal, its status, and one line of narrative — honest RAG reporting, not investor-deck green. If your primary job is culture, lead with a "One team, up close" mini-profile: 200 words on what one team actually does all day, written from a 15-minute interview. Other proven sections: "Ask me anything" (one employee question, answered by a leader, sourced from an anonymous form), "From the archive" (a useful internal doc people forgot exists), and "Tool tip" (one workflow trick, 50 words).

Voice: write like a person who respects the reader's time

Internal newsletters drift corporate because nobody edits them the way a real publication is edited. Adopt four rules and enforce them ruthlessly.

Rule 1: Lead with the fact, not the throat-clearing. Before: "As part of our ongoing commitment to operational excellence, we are pleased to announce that the finance team has completed the migration of our expense system." After: "Expenses moved to a new system Monday. Your old receipts came with; your saved approval chains did not — set those up again this week."

Rule 2: Name people and teams. "The platform team" is fine; "we" as a vague corporate entity is not. "Marta and Deniz rebuilt the import pipeline" is better than either. Named credit is half the value of a visibility newsletter.

Rule 3: Include the consequence. Every item answers "so what does this mean for me?" in the same breath. If an item has no consequence for readers, it usually should not be an item.

Rule 4: Keep one register. Plain, direct, warm, occasionally funny. The top note and the people section should sound like the same publication. This means one editor with rewrite authority over every contribution — negotiate that authority explicitly before issue one, including with executives. The pitch to leadership: "You approve facts and framing. I own sentences." Most leaders are relieved.

A useful calibration exercise: read your draft aloud. Anywhere you would not say the sentence to a colleague at lunch — "synergies," "on a go-forward basis," "we are excited to share" — rewrite it as the thing you would actually say.

Sourcing content without begging

The number one reason newsletters die: the writer spends more time chasing contributions than writing. Solve it with systems, not reminders.

Mine channels that already exist. Your best source is work narrated where it happens — release notes, project status updates, retro outcomes, kudos posts, support ticket highlights. Set a 30-minute calendar block two days before publication to sweep these sources with fresh eyes. If your company runs its updates through a shared workspace, this sweep is fast; in Openbook, for example, a scan of the relevant Feed rooms plus each team's Project Status room typically yields 80% of an issue, because status updates and kudos are already written down in one searchable place instead of scattered across five tools.

Standing submission slot, zero friction. One pinned form or thread titled "Newsletter: brag or flag." Two fields: what happened, why it matters. No formatting requirements — the editor rewrites everything anyway. Expect this to supply 10–20% of content, not 80%. It is a supplement, not the engine.

Rotate a correspondent. Each issue, one person from a different team owes you three bullets about their team's fortnight, booked a full cycle ahead. This costs each person ten minutes twice a year and permanently solves the "engineering newsletter that never mentions sales" problem.

Interview instead of assign. When you want a longer piece, never ask someone to "write something up." Book 15 minutes, ask five questions, record it, and write it yourself in their voice. You will get the piece in one day instead of three weeks of guilt.

A realistic sourcing exchange, for calibration:

Editor: "Saw the migration retro said zero downtime. Newsletter-worthy. What almost went wrong?" Engineer: "Honestly, the dry run failed twice and we nearly slipped the date." Editor: "That is the story. Two sentences on what you changed between dry run two and the real thing?"

The item that results — "The billing migration hit zero downtime, but only after two failed dry runs; the fix was rehearsing the rollback, not the rollout" — is the kind of thing people actually remember and quote.

Production: the 90-minute assembly line

Once sections are fixed and sourcing is systematic, an issue should take 90 focused minutes plus review. A workable schedule for a Thursday 9 a.m. send:

When	Task	Time
Tuesday a.m.	Sweep sources, drop raw material into the template	30 min
Tuesday p.m.	Write the draft top to bottom	60 min
Wednesday a.m.	Fact-check pass: every name, number, date, link	20 min
Wednesday p.m.	One reviewer reads for accuracy and tone; leader skims top note	15 min
Thursday 9:00	Publish	—

Three production rules. Keep a running "next issue" doc and drop material in the moment you see it — assembly is fast only when collection is continuous. Limit review to one reviewer plus one leadership skim; review-by-committee is how newsletters slip and how voice dies. And write issue titles that state the top item ("Newsletter #14: Zero-downtime billing migration, Q3 goals check") rather than "Company Newsletter — July," because the title is your subject line and your archive index.

Succession matters too. Document the process in a one-page runbook and have a backup editor ship one issue per quarter. A newsletter that lives entirely in one person's head dies with their calendar.

Distribution: where it lives determines whether it compounds

Email is where newsletters go to be skimmed once and lost. A workspace post is where they get commented on and found again. The strongest pattern is both, with a clear hierarchy: the canonical issue is a post in your company-wide feed or intranet — commentable, searchable, permanent — and the email is a short teaser (top note plus three headlines) linking to it. Comments are the point: a newsletter item that sparks twelve comments about the pricing change did its job better than one opened by 90% of the company in silence.

Formatting for the skim: bold the first three words of every bullet, keep paragraphs under four lines, use section headers big enough to scan past, and put every link on a verb phrase ("read the full retro") rather than a bare URL. Assume 60% of readers give you 90 seconds; design so that a 90-second scan still delivers the guarantee from your charter.

Build a public archive from day one — a simple index page listing every issue. New hires reading the last eight issues is the cheapest onboarding-context program you will ever run, and several companies formalize exactly that: issues 1 through N as required week-one reading.

Measure it like a product

You cannot manage a newsletter on vibes, but the standard metric — email open rate — is mostly noise once previewing and image-blocking are factored in. Use a small stack of better signals:

• Reach: unique viewers of the workspace post within 72 hours, tracked as a percentage of headcount. Healthy is 50–70%; below 30% for three straight issues means the format or the promise is broken.
• Engagement: comments and reactions per issue, and — more diagnostic — which sections they attach to. Zero engagement on a section for six issues is a kill signal.
• Retention proxy: does readership hold from issue to issue, or spike on drama and decay? Decay means you are interesting, not useful.
• The hallway test: once a quarter, ask five people across departments, "What do you remember from the last newsletter?" Unprompted recall of specific items is the single best signal you have. Blank stares from people who technically opened it tell you skimming has replaced reading.
• Qualitative pulse: twice a year, run a three-question survey — keep/change/kill by section, plus "what is missing?" A short well-designed pulse beats a long annual one; the same design principles from Polls and Pulse Surveys apply.

Then act visibly. Kill underperforming sections and say so in the issue: "Retiring 'Tool tip' — nobody clicked it in two months. Replacing it with 'Decision of the week' by request." Publicly pruning your own newsletter is itself a trust-building move; it proves someone is steering.

The economics, so you can defend the time

A biweekly newsletter costs one editor roughly five hours per issue — call it 130 hours a year. Weigh that against what it replaces: if a five-minute read saves 200 employees even one status meeting per month, or prevents one duplicated project because two teams finally saw each other's work, the math is not close. Run the numbers for your own headcount before a budget conversation, and present the newsletter as infrastructure, not a nice-to-have. The broader strategy case — where a newsletter fits among channels, audiences, and cadences — is laid out in Building an Internal Communications Strategy from Scratch.

Failure modes to catch early

• The executive megaphone. Every item is leadership talking down. Fix: enforce the correspondent rotation and the Voices section; count how many named non-managers appear per issue and keep it above five.
• The link dump. Ten links, no synthesis. Readers do not want a feed; they have feeds. The newsletter's value is that a human chose what matters and said why.
• Scope creep. HR asks for a benefits corner, security wants a phishing reminder, and by issue twenty the read is fifteen minutes. Fix: the charter line. Standing requests get one rotating "Notices" slot of three lines, total.
• Toothless positivity. If the newsletter never mentions a miss, a slipped date, or a bad number, readers correctly file it as PR and stop trusting the good news too.
• Silent death. If you must stop, say so in a final issue and state what replaces it. A newsletter that vanishes without explanation damages the credibility of whatever channel comes next.

Start this week: a concrete first-issue plan

1. Write the one-line charter and pick a primary job. Ten minutes, with whoever sponsors the newsletter.
2. Choose biweekly Thursday unless you have a strong reason otherwise, and put the next four publication dates on the calendar now.
3. Copy the seven-section stack into a template doc. Delete one section you know you cannot fill; do not add any.
4. Do a 30-minute sweep of your existing channels and fill the template with real material from the last two weeks. If you cannot fill it, your problem is upstream — teams are not narrating work anywhere — and the newsletter will surface that fast.
5. Recruit one reviewer and one leader for a 150-word top note, with the "you approve facts, I own sentences" agreement stated out loud.
6. Ship issue one to the whole company with a two-line preface: what this is, when it arrives, and the guarantee — "read this and you will always know what shipped and what changed."
7. After issue three, run the hallway test and cut or fix whatever nobody remembers.

The bar is not a beautiful publication. The bar is a reliable, five-minute, honestly written digest that shows people their colleagues' work. Hit that bar for ten consecutive issues and the newsletter stops being a comms project and becomes part of how the company thinks.

If your bottleneck is that the raw material lives in five disconnected tools, that is a solvable problem too. Openbook puts feeds, status updates, kudos, events, and announcements in one workspace, which turns newsletter sourcing from a scavenger hunt into a 30-minute sweep — see what the rooms look like at /features, free to start for teams up to 10.