Reporting a Community Event: The Details Readers Actually Need
A reader-first checklist for clear event notices, from organisers and access to booking conditions and updates.
A useful community event notice answers practical questions before it asks for excitement. Readers need to know who is organising the activity, what will happen, where to go and how to check for changes. A striking poster may help people notice an event, but it should not carry the whole explanation. Clear text is easier to search, update, read aloud and share with someone who cannot see the image.
Establish who is responsible
Give the organiser’s public name and a reliable route to its own announcement. Distinguish an organiser from a venue, sponsor or ticket seller: they may have different responsibilities. Do not suggest that displaying a logo proves an endorsement. If you are publishing a submitted notice, confirm the event through an appropriate public contact channel before presenting the details as established information.
Make time and place unambiguous
State the calendar date, start time and expected end time if confirmed. Explain whether the listed time means doors opening, registration or the start of the main activity. Include a usable venue name and address rather than only a landmark familiar to regular visitors. If the location is online, direct readers to the organiser’s official access instructions without exposing private meeting credentials in a public article.
Describe the experience, not just the slogan
Readers may need to know whether the event is a performance, workshop, discussion or market. Describe the main activity in plain language and state any confirmed age, registration or participation requirements. Do not promise that an unconfirmed guest will attend. If a programme is provisional, identify it that way and explain where final information will appear. Avoid invented attendance figures or claims about a previous edition.
Include access and booking questions
Where information is available, cover seating, step-free access, transport considerations and any equipment participants need to bring. If a detail is not confirmed, provide a way to ask rather than assuming a facility exists. For paid entry, link to the authorised booking channel and encourage readers to inspect the final price, ticket category and cancellation terms before completing a purchase. A general event article should not promise a refund policy it has not checked.
Plan for changes before publishing
Give the notice a last-checked date and identify the source of updates. If a venue, time or guest changes, revise the relevant paragraph and add a clear correction or update when the difference is material. Do not leave a contradictory old poster above corrected text without explanation. For cancellation, make the status visible near the top so readers do not need to reach the final paragraph to find it.
Keep the article useful after the day
After an event, preserve the distinction between the original notice and any later reporting. Do not convert a planned programme into a claim about what actually happened. A follow-up should rely on observation, attributable accounts or other verifiable material. The verification principles in UNESCO’s journalism guidance apply at this local scale too: identify the source, check the context and make the limits of your information clear.