Community Event Page Checklist: What to Include for Sessions, Activities and Drop-Ins

1. Introduction and quick answer: what every community event page needs

Use this community event page checklist before you publish a one-off activity, recurring session, short course, workshop, member activity or informal drop-in. The aim is simple: give someone enough practical information to decide whether the event is relevant, whether they can attend, and what they need to do next. Quick answer: every community event page should clearly state what the activity is, when it happens, who it is for, whether people need to book, where to go or how to join, what it costs, what access information is known, what to bring, who to contact, and how updates or cancellations will be shown. If you do not yet know one of those details, do not hide the gap. Say what is still to be confirmed, who is responsible for confirming it, and when the page will be updated.

2. Copy-paste community event page template

A consistent event page structure helps editors avoid missing details when time is short. Copy the template into your CMS, document, directory form or shared draft, then remove any sections that genuinely do not apply. Write for someone who has never attended before. Avoid internal project names, unexplained acronyms and venue nicknames unless you also give the public-facing name.

3. Event basics, recurrence, audience and eligibility checklist

Start with the facts people use to decide whether the activity is relevant to them. For time-bound community activities, recurrence often causes confusion, so spell out dates and exceptions rather than relying on short phrases. For example, “Tuesdays, 10am to 12 noon, from 4 June to 16 July, excluding 25 June” is clearer than “every Tuesday”. If the session is ongoing, add a review date or state when the next break will be confirmed. Audience wording should be practical rather than promotional. Say whether the event is for beginners, existing members, local residents, parents and carers, young people, older adults, volunteers, people referred by a partner organisation, or anyone interested.

4. Booking, drop-in and capacity checklist

Attendance rules need to be visible before someone travels, invites another person, or tries to arrange care or transport. Do not make people infer whether booking is required from a button, poster or social media caption. Choose one clear attendance model and write the page around it: Booked places: people must reserve a place before attending. Include the booking route, deadline, confirmation process and what to do if they can no longer attend. Drop-in: people can arrive without booking. Include the arrival window, any capacity limit, and what happens if the room is full. Book or drop in: both are possible. Explain whether booked places are prioritised, how many drop-in places may be available, and whether people should check the page before travelling. Fully booked, postponed or cancelled: make the status obvious near the top of the page and update any linked listings where possible.

5. Location, arrival and accessible event information

Location information should help someone get from “I want to attend” to the right door, room or online space. A venue name alone may not be enough, especially for buildings with several entrances, reception desks, locked doors, shared spaces or rooms known by local nicknames. For in-person sessions, include the full venue name, address, room name, entrance to use, reception instructions, arrival time, parking or public transport notes if known, and what to do if the door is closed. For outdoor activities, include the meeting point and what happens in poor weather. For online or hybrid sessions, include how people receive the joining link, whether they need to book first, what name they should use to join, whether cameras or microphones are expected, and who to contact if they cannot get in. For accessibility, give known event-specific information without overstating certainty. Useful details may include step-free access, lifts, accessible toilets, hearing loop availability, seating, quiet space, lighting, noise levels, interpreter or caption arrangements, accessible parking, and whether support workers or carers can attend. If you do not know an access detail, say how someone can ask before attending.

6. Cost, safety, safeguarding, conduct, privacy and safe contact

Cost and safety details affect whether people feel able to attend, but an event listing does not need to become a full policy page. Keep the listing practical, then link to fuller policies only when they are useful. For cost, state whether the event is free, paid, donation-based, pay-what-you-can, member-only, concessionary or funded for a specific group. If payment is needed, say how and when people pay. If donations are optional, say so clearly. For safety and conduct, explain any boundaries that affect attendance: age limits, supervision requirements, safer-space expectations, photography rules, food or allergy considerations, equipment risks, outdoor clothing, or whether attendees must follow instructions from session leaders. For safeguarding and privacy, use a monitored contact route and make clear who handles attendance questions. Do not ask attendees to share more personal information than is needed for the event. If someone needs to discuss access, safety or support needs, offer a safe route that does not require them to post sensitive information publicly. When drafting, reviewing or moving event information between tools, do not send credentials, private records, analytics exports, screenshots containing private information, or identifiable sensitive records.

7. Updates, cancellations, expiry, promotion and page ownership

Event pages need ownership after publication, not just before launch. Before you share the page in newsletters, posters, directories or social posts, decide which listing is the source of truth and who updates it. Put visible update information on the page: last reviewed date, cancellation status, fully booked status, postponement details, and the next review point for recurring sessions. If the same event appears in several places, keep the wording consistent enough that people are not choosing between conflicting dates, prices or booking rules. Expired listings should not sit online as if they are still current. For a one-off event, archive it, redirect it, or mark it as past after the date. For a recurring activity, review it before breaks, venue changes, holidays, funding changes or staff changes. For a short series, decide whether the page should remain as a record, become a new series page, or be removed from active listings.

8. Final pre-publish community event listing checklist and attendee FAQ

Before you share the page, run through the final checklist as a person who has never attended before. If a detail is only known by the organiser, it belongs on the page. Use this as a self-serve publishing aid. Chestnut Communities is not currently offering paid reviews, implementation, urgent support, or automatic AI replies, so keep urgent safeguarding, access or operational issues inside your organisation’s normal human escalation routes.

Copy-paste community event page template

Recurring and time-bound listing decisions

Minimum publishable community event page checklist

Event basics, recurrence, audience and eligibility checklist

Booking, drop-in and capacity checklist

Avoid vague recurrence wording

Use one source of truth for updates

Do not share sensitive records while drafting event pages

Frequently asked questions

Do I need to book or can I just turn up?
Your event page should answer this near the top. State one of the following clearly: booking required, drop-in welcome, or booking and drop-in both possible. Include the booking link, phone number, email address or in-person route, and say whether people receive confirmation before attending.

What happens if the session is full when I arrive?
If capacity is limited, explain what happens before people travel. For example: booked attendees have priority, a waiting list is available, late arrivals may not be admitted, or the organiser will suggest the next available session. If a drop-in regularly reaches capacity, say when people should arrive and where updates will be posted.

Is the event free?
State the cost even when the event is free. If donations are welcome, make clear whether they are optional. If there are concessions, membership fees, materials costs or payment deadlines, include them on the page.

Can I come late or leave early?
Say whether late arrival or early departure is acceptable. Informal drop-ins may have flexible arrival windows, while workshops, safety briefings, performances or group courses may need people to arrive on time.

Can I bring a child, carer, support worker or friend?
Do not leave this to guesswork. State whether children, carers, support workers, interpreters, friends or guests can attend, whether they need their own place, and whether any age, supervision or safeguarding rules apply.

Who do I contact if I have an access question before attending?
Give a monitored contact route, such as an event inbox or phone number, and say when someone can expect a human response. Do not ask people to post access needs publicly or send unnecessary sensitive information.