The Inbox Where Newsletters Go to Die
In January 2024, I sent the eighteenth issue of our community newsletter. It went to 47 people. I checked the open rate four days later. Six people had opened it.
Six. Out of forty-seven.
I knew most of those six. They were the same six who'd opened the previous twelve issues. The rest of the community had quietly trained their eyes to skip past the "Sanctuary Update" subject line, the same way they skip past the dentist reminder and the supermarket promo.
That night I deleted the template I'd been using for two years and started over. What follows is what we learned. A community newsletter people actually read is a different animal from the ones most communities ship.
Why Most Community Newsletters Fail
Three reasons, in order of how much they hurt.
They read like a bulletin board. "Hi everyone, here are the updates this month: 1) the Council approved the new compost shed, 2) the water bill is due, 3) Maya is leading a foraging walk Saturday." Information dumped into a list. No texture. No reason to read past the first item.
They're written by the steward, for the steward. The steward knows what they care about. They write that. The actual readers don't share the steward's priorities, so the relevance is always a near-miss.
They arrive without a rhythm. The first one comes in January. The next in March. Then nothing until June. By the third gap, people have stopped expecting them. By the fifth, they've stopped looking.
The bulletin-board format hides the deeper problem. A community newsletter functions like a relationship. It's a relationship you only invest in when you feel like it. Which is to say, it's a relationship that stops being one.
Pick One Job, Do It Well
The newsletter that worked for us does exactly one thing: it tells a story about the last two weeks of community life. That's it.
We don't use it for announcements (those go in the Sanctuary). We don't use it for governance updates (those live as Scrolls in the Library). We don't use it for chore reminders (the Rhythm board handles those).
The newsletter is the place where someone who missed dinner Thursday can still feel the texture of what happened. The kid who fell out of the apple tree but only bruised her elbow. The argument about whether to keep the compost loo or finally build the proper one. The visiting permaculture teacher who showed up with three different kinds of mushroom inoculant and ate half our bread.
Story. Texture. Voice. Nothing else.
When I told the rest of our Sanctuary I was going to stop putting reminders and announcements in the newsletter, two members pushed back. "Then where do they go?" In the Sanctuary, where they already live. The newsletter complements those systems. It does the one thing they can't.
The Format That Survived
After about six attempts, the format we settled on is this:
One photo at the top. Phone quality is fine. It should be a moment from the last two weeks, never a stock image and never the community logo. The kitchen mid-dinner. Someone's hand in the soil. Three pairs of muddy boots on the porch.
A two-sentence opener. What this issue is mostly about. Lands the tone.
Three "scenes" of 80 to 150 words each. Each scene is a moment, a conversation, a small thing that happened. Names. Specifics. Quiet humor where it fits.
A "Quietly Happening" footer. Three or four one-line mentions of things going on this week. Linked, with no elaboration. ("Council Sunday, 4pm. Foraging walk Saturday. New Scroll on the well pump in the Library.")
That's the whole newsletter. Total: about 600 words. Reads in under three minutes. Lands in inboxes every other Friday.
The open rate went from 13% to 71% inside three months. Same forty-seven people. They just stopped skipping it.
The Cadence Question
Two weeks is the right cadence for most communities. Weekly is too much: scenes start blurring, the writer burns out, and people begin feeling guilty for not keeping up. Monthly is too sparse: the texture goes stale and people forget what happened.
Every other Friday hits the same psychological slot as a podcast drop. You know roughly when it's coming. You don't have to remember the specific day.
The harder rule: ship it on schedule even when the issue feels thin. A thin issue with three small scenes is fine. A skipped issue breaks the rhythm. Once readers stop expecting you, you have to earn the expectation back. That takes months.
We've shipped over 60 issues since we changed format. Three have been late by a day. None have been skipped. The discipline matters more than the polish.
Who Writes It
This is where most communities trip.
The default assumption is that the steward writes the newsletter. That's wrong. The steward already writes too much. By issue 10, the voice gets tired and the steward starts resenting the deadline.
What works better: rotate the writer among three or four members who can string a sentence together. Each writer does the newsletter for two months, then hands off. The voice shifts a little with each rotation. Readers notice. They like it.
The handover happens through one Scroll that lays out the format, the deadline, the email tool, and a running list of "things that happened this fortnight" that the writer can pull from. About 40 minutes per issue once you're in the rhythm. Two issues per shift. So roughly 80 minutes every two months per writer.
That's a sustainable load. The "one heroic steward writing 26 issues a year" pattern is the one that always breaks.
What to Write About When Nothing Happened
About every fifth issue, the writer says "but nothing really happened this fortnight."
Something always happened. The trick is learning to see at a lower resolution.
Did three new bottles of homemade kombucha appear in the cold room? Who made them? Was the kitchen unusually quiet on Tuesday? Why? Did the dog finally learn to leave the chickens alone? Did anyone almost cry at dinner? Did the new compost bin start to actually smell like compost instead of stagnant lettuce?
The "nothing happened" weeks are usually the most readable issues. They force the writer to notice the small things, which is what community life mostly is.
What to Leave Out
A short list, hard-earned.
No internal politics by name. If a member is having a hard time, don't put their name in the newsletter. The newsletter is a public artifact. Treat it that way.
No grandstanding. A scene that ends with "and this is why community is so important" is a scene that's been ruined. Trust the reader to draw their own conclusions.
No metrics. "We hit 23% reduction in food waste this month" belongs in the Ledger or the annual review. The newsletter is for the texture, not the dashboard.
No fundraising. Asking for money in the newsletter trains people to brace for the ask. They start skipping again. If you need to raise money, send a separate, infrequent email with a different format. Keep the newsletter clean.
The Archive Becomes Something
A surprise nobody warned us about: the archive of two years of newsletters is now one of the most-read things in our Sanctuary's documentation.
New members read it during onboarding. Not the Scrolls of bylaws and policies. The newsletters. They want to know what the place feels like before they read what it formally is.
Visitors who are considering moving in read the last six issues during their stay. We've had two people tell us, six months into membership, that the newsletter was what tipped them from "I'm interested" to "yes."
The archive lives as a public collection in the Library, linked from our website. Each issue is a Scroll. Search works across all of them. The whole thing was an accidental documentation project that turned out to be the best portrait of the community we have. (If you want more on why this matters, the piece on documenting decisions is the companion to this one.)
A Tool That Helps
We send the newsletter through a regular email tool (Buttondown, in our case, around €9 a month for the list size we have). Drafting happens in a Scroll, then gets pasted into the email tool. The footer items link directly into the Library and our calendar, so a reader who wants more can land in the right place in one click.
You don't need fancy infrastructure for this. A free Mailchimp account and a shared Google Doc would do the job. The tool matters far less than the discipline.
Start With One Issue
If your community has no newsletter, or a struggling one, here's the smallest possible start.
This Friday, write 600 words about the last two weeks. One photo. Three scenes. A short footer of what's coming. Send it.
Two weeks later, do it again. Don't wait for inspiration. Don't redesign the template. Don't poll the community on what they want.
After six issues you'll know whether this works for your community. After twenty issues you'll have an archive. After a hundred issues you'll have something the community actively misses if it's late.
A community newsletter people actually read is a small thing. It's also one of the few public artifacts your community will produce that anyone outside the inner circle ever sees. Worth writing well.