Most community recaps are written for the people who were there. They thank the contributors, list the threads, and land in the inboxes of the one group that needed them least.
A recap has a different reader, and once you write for that reader instead, almost everything about it changes — including how long it takes you.
A recap is for the people who weren't there
The people who took part already know what happened. The recap's real audience is everyone who missed it.
That reader is not idle. They are quietly deciding whether this is a place where things happen, and the recap is often the only evidence they will see this week. The people who did not attend are the real audience for a meetup recap, and the same is true of every recap you write: it is a report to the absent, not a thank-you note to the present.
Write it for someone who has not opened the community in a month. Every sentence that only makes sense to people who were in the thread is a sentence that reader skips.
The test: would someone who missed it learn that things happen here?
Read your draft as that person and ask one question: after this, do I believe something worth my time goes on in there?
"Great discussions this week — thanks to everyone who joined in!" fails. It asserts activity without showing any. "Three people who run small studios compared what they charge for rush work, and the numbers were not what anyone expected" passes, because the absent reader can now picture a specific conversation they would have wanted to be in.
Show one real thing rather than describe many. A recap that proves a single good conversation happened does more than one that mentions twelve.
What goes in, and what the absent reader gets from it
Most recap items are chosen because they are easy to write, not because they tell anyone anything.
| What goes in | What someone who missed it learns | Keep it? |
|---|---|---|
| "Thanks to everyone who took part" | Nothing — they did not take part | Cut it |
| A list of every thread | That there was volume, not what was good | Only the best two or three |
| One answer, quoted | That questions get real answers here | Yes — usually the best item |
| What is coming up next week | A reason to come back on a particular day | Yes |
If an item only makes sense to someone who was there, it belongs in the thread, not the recap.
Quote, don't summarise
A summary tells the reader a conversation was good. A quotation lets them judge for themselves, which is the only version they believe.
"There was a useful thread about pricing" is a claim. One sentence lifted from the best answer in that thread, with a link, is evidence — and it carries the voice of the community rather than yours, which is exactly what someone deciding whether to come back wants to hear. It also takes less time to write than a good summary, because the member has already written it for you.
Choose the sentence that would make someone click, not the one that sums the thread up. Those are rarely the same line.
Name people, carefully
Quoting someone in a recap is a small public spotlight, and it works best when it is aimed at the right person.
The member who wrote a careful answer to a beginner deserves the mention more than the one who started the loudest thread, and naming what someone specifically did lands far harder than a list of thanks. But a quote in a recap reaches people who were not in the room, so anything that was said in a small or private space stays there unless you ask first.
Credit the behaviour you want more of. The recap quietly teaches the absent reader what counts here, whether you mean it to or not.
Popular is not the same as important
The thread with the most replies is often a heated one, and the most valuable thing that happened this week may be a quiet answer with three reactions.
A recap assembled purely from what got the most attention will slowly tilt towards whatever provokes — which is a strange thing to feature to people who are deciding whether they want to be there. Your job as the editor is to notice the useful thing that did not get noticed, because nobody else is in a position to.
Include at least one item nobody would have found on their own. That is the part only you can add, and it is the reason a recap is worth receiving at all.
Report, don't ask
This is where recaps usually go wrong, and it matters most for the members who have drifted away.
A message to people who have gone quiet that says "we miss you — come back!" tends to backfire: it interrupts a decision they had stopped thinking about and asks them to make it again, consciously, with a button in front of them. A recap is different only if it asks for nothing. It reports what happened, links to it, and stops. The absent reader can come back or not, and nobody has put them on the spot.
No "we miss you", no "come back", no guilt. The moment a recap starts asking, it becomes the re-engagement email under a friendlier name, and it earns the same response. For the handful of people you can actually name, a short personal note still beats any recap.
Keep it small enough to survive
Recaps have a known failure mode: they quietly become a second job.
They start as a quick note, grow a little every week because there is always more worth mentioning, and within two months take an afternoon. Then a busy week comes, the recap is skipped, and the next one feels like it has to make up for two. That is how most of them end.
Cap the length permanently, even in a big week. Two or three quoted items, one thing coming up, a link to everything else. A short recap that goes out every week does far more than a long one that goes out when you have time.
What the software does and does not do
It is worth knowing which half of this can be automated, because the automated half is the part that tends to eat your time.
Mateflow's Community Digest, under Marketing → Community Digest, is described on screen as "A weekly email with the best of your community, sent to members who have not been around lately." It is off by default. When it is on, it goes out once a week on the day, hour and time zone you choose, always includes up to five top posts from the past week, and by default adds two blocks you can switch off: New members who joined in the past week and events and live sessions Coming up. By default it goes only to Members who have not been around for a number of days you set, never to accounts created in the last three days.
Each issue is filtered by the recipient's own permissions, so two members rarely receive the same one, and a member who can see fewer than three top posts gets no issue that week rather than a thin one. Missed weeks are never backfilled. The honest limits: you do not choose which posts go in — it selects the week's top posts itself, and whatever it ranks by, it cannot know which quiet answer mattered most to the person who asked — and it is not on every plan, with sending to all members gated separately. So let it do the list, and keep the part no ranking can do for the recap you write yourself.
Three things not to do
Do not send a recap when nothing happened. A thin issue tells the absent reader exactly what you were hoping to hide. Skip the week and say nothing.
Do not turn it into an announcement. A recap reports the past; an announcement asks people to act. Tucking a rule change into paragraph four of a recap means the people it binds will miss it.
Do not link only to new things. The best answer in the community may be eight months old and still exactly what a newcomer needs; re-surfacing it on purpose is part of the job, not a lapse in freshness.
The bottom line
A recap is not a record of what happened. It is evidence, sent to people who were not there, that this is a place where something worth their time goes on.
So write it for the absent reader, quote instead of summarising, credit the behaviour you want more of, include one thing nobody would have found alone, and ask for nothing. Then keep it short enough to send every single week — because the recap that survives is worth more than the brilliant one that stopped in March.