Free event no-shows: plan with a headcount you can explain

Count the people behind each booking

A form with 35 responses might represent 35 people or 70. Before ordering anything, decide which number each report contains. Count the lead attendee and their guests as people, and keep waitlisted places separate from confirmed places.

Also account for the people who did not register through the public form: volunteers, performers and organisers. They may need meals and they may count towards the venue's occupancy limit. Confirm the limit and the relevant room layout with the venue rather than treating an RSVP cap as a building assessment.

Make changing plans easy to report

Put the cancellation route where someone will look for the booking: the confirmation and the event information. Use a neutral sentence. A person who can release a place without an awkward explanation gives the organiser better information.

Eventbrite's reminder-email guidance focuses on putting useful event details back in front of attendees. For a small community event, I would use a short practical reminder and a clear way to cancel. There is no need to copy a commercial event's whole marketing sequence.

Source: Eventbrite: event reminder email templates

Use your own history, with its rough edges visible

A general no-show percentage is a poor substitute for your own events. A free outdoor activity during school holidays and a seated annual dinner have different reasons for late changes. Record actual arrivals, including guests, before building an estimate.

Keep confirmed people at the booking cut-off, later cancellations, arrivals from bookings and walk-ins as separate numbers. If you only keep a final edited guest list, you can lose the evidence of what changed. Compare similar events and note weather or transport problems that made a date unusual.

Separate the food decision from the door limit

If a caterer needs a firm number a week ahead, use the history available at that same point in earlier events. Discuss what can be adjusted later and whether some food can be purchased closer to the date. Write down the assumptions so the treasurer can understand the decision.

Do not overbook a fixed-capacity venue because a percentage of guests might stay home. A forecast can be wrong. Capacity is the maximum you can admit; a purchasing estimate is a judgement about likely demand. Keep those two decisions separate.

Make next time less of a guess

After the event, record the actual headcount and any food left over. Include whether the leftovers could be reused safely under your caterer's arrangements. One clear note is more useful next year than a committee member's memory that ‘we bought too much’.

fullhall includes guest counts, free RSVP waitlists and a door list. Use the event report to review attendance. Automatic waitlist promotion belongs to the free RSVP flow; do not assume a paid-ticket queue reserves or charges a card. Keep practical booking messages separate from promotional broadcasts, which use confirmed marketing opt-in.