At most companies, the corporate digest looks the same: a holiday greeting, a deadline reminder, an invitation to the office party. Employees open these emails out of habit, and gradually stop.
Let's break down which topics people actually read and how to structure a digest so employees look forward to it.
Why employees don't read corporate emails
People read emails that are useful to them. A digest gets ignored when it's unclear why anyone should open it.
Three reasons this happens:
No personal value. An email about the sales department's quarterly results isn't relevant to an accountant. An announcement of an Excel training isn't relevant to a developer. When the content doesn't concern someone, they don't read it.
No new information. If the digest just repeats what was already said in chat and at the team meeting, there's no reason to open it. A digest should offer something not available through other channels.
No reason to read it right now. "April news" isn't a reason. "New vacation request rules starting May 1" is a reason. If the subject line doesn't make it clear why to open the email, most people won't.
What to write so your digest gets read
Results and numbers
Once a month or quarter, show what's changed: revenue, new customers, closed projects, team growth. Employees want to understand where the company is heading and whether they've contributed to the overall result.
Important: not just numbers, but context. Not "revenue grew 12%," but "revenue grew 12% — our best result in two years."
Behind-the-scenes stories
A short piece about how a specific team solved a tough problem or launched a new process. First-person storytelling with details works well. These emails get read, forwarded, and discussed.
Format: what the challenge was, what was done, what the outcome was. Three paragraphs are enough.
Useful for work
A roundup of tools, templates, guidelines, or articles that make everyday tasks easier. Three items work better than a list of twenty links.
Specificity matters: not "useful materials," but "three templates for approving time off that will save you time."
New people and team changes
Who joined, who moved to a different department, who got promoted into a new role. This matters especially for distributed teams, since employees don't run into each other in the hallway and don't know who to ask about new questions. A short introduction with a photo and their area of responsibility solves that.
Answers to employee questions
Collect real questions through a form or company chat and answer them in the digest. This format feels alive and shows the company listens to people. If one person asks, ten more are probably thinking the same thing.
Recognition and results
An email about "who did something notable this month" works as a retention tool. People want to be noticed.
Minimal format: name, what they did, one line from their manager. Takes twenty minutes to put together, works for a month.
Announcements that hit close to home
Process changes, new benefits, system updates — anything that affects a specific employee's work. These emails get opened because not opening them costs more. Write specifically and to the point, without three paragraphs of preamble.
Internal Communications 2026: How to Build a Newsletter Employees Won't Send to the Trash
How to structure a digest
A good digest can be read in three minutes. That takes a clear structure.
Element | What's inside |
|---|---|
An announcement at the top | One sentence about what's inside. The reader immediately understands whether there's anything here for them |
2–3 content blocks | Each block covers one topic, one focus, with a subheading |
One call to action at the end | Take a survey, read an article, register for a meeting |
Don't try to cram everything into one email. It's better to send more often and shorter than to send a ten-screen email once a month.If you want to understand how to properly build an email from blocks, read An Email as a Construction Kit: Why Modular Coding Saves Recurring Campaigns.
Why people read some emails and ignore others
A person opens an email if they expect to find something useful in it. If a digest turns out to be useful several times in a row, people start looking forward to it. If it turns out empty a few times, they stop opening it.
That's why not just the topic of a single issue matters, but the reputation of the newsletter as a whole. One boring digest lowers the open rate of the next one. One genuinely useful digest raises it.
It's better to send a digest less often but with real content than to keep a regular schedule just for the sake of regularity.
How often to send it and when
A weekly digest works well for fast-growing teams, where there are lots of events and information goes stale quickly. A monthly one works for companies with steady processes.
The best time is Tuesday or Wednesday morning. Employees are already in their work rhythm but not yet overloaded. Thursday and Friday perform worse: by the end of the week, inboxes are full, and the email gets put off and forgotten.
The main rule: send when you actually have something to say. An empty email sent just to hit a schedule only erodes trust in the newsletter.Welcome Emails for New Employees: How to Build Onboarding
How Letteros helps with corporate digests
Internal digests often get thrown together in a rush: copy the old email, tweak the text, the layout shifts, tweak it again. Three hours later, it's sent. Next week, the same thing happens again. A digest is one of the few formats where a company speaks directly to its employees. Write about what matters to people, not just what needs to be reported.
In Letteros, a master template for a digest is built once: brand colors, blocks in the right formats, responsive coding. The next issue is just swapping text and images in the ready-made blocks. Twenty minutes instead of three hours, and the email looks equally professional no matter who put it together.