Write a community digest

You turn the messy pile of updates that volunteer-run groups produce (committee notes, forwarded messages, half-finished event details, pleas for help) into a digest people actually read. Readers of a club, school or neighbourhood digest skim on a phone for three things: what is happening and when, what was decided that affects them, and what they are being asked to do. They miss anything buried in paragraphs. A good digest leads with what needs action, lists dates in one place with weekdays, makes every volunteer ask specific (the task, the time it takes, the date, who to tell), and is warm without being long. It also protects people: it does not publish private phone numbers, children's full names or photos without consent.

Write the monthly digest for: [COMMUNITY].

1. Sort the updates into: action needed (deadlines, sign-ups, payments, forms), dates and events, decisions made, volunteer asks, reminders, thank-yous and good news, contacts. Merge duplicates and drop anything outside the monthly window unless it is a key upcoming date; list what you dropped.
2. Write three subject line options that name the most important action or event.
3. Write the digest:

• an opening of one or two sentences with the single most important thing,
• "Action needed" with deadlines in bold,
• "Dates" as a list with weekday, date, time, place and who it is for,
• "Decisions" in plain words, each with what it means for readers,
• "Help wanted" with each ask as task, time needed, date and how to say yes,
• "Reminders", "Thank you" and "Contacts" (roles and the contact method given).

1. Write a short version (under 120 words) for a chat group or noticeboard that points to the full digest.
2. List what to check before sending.

• Use only the information given. Never invent dates, times, places, prices, decisions or names. Where a detail is missing, write [CONFIRM: …] and list it at the end.
• Write weekdays with dates and spell out ambiguous dates.
• Do not include private phone numbers, home addresses, children's full names or health details unless the updates clearly say they are for publishing; flag them under Check before sending.
• Keep the tone warm, inclusive and plain; avoid in-jokes and committee jargon newcomers would not understand.
• Skip any empty section rather than filling it.

Subject lines

Three options.

Digest

The digest with the headings above.

Short version

Under 120 words.

Check before sending

Every [CONFIRM] item, anything dropped, and any privacy flags.