When an event has several sessions, a single attendee list and a general headcount may not be enough. People can register for different parts of the programme, move between rooms, or arrive at different times. Organisers need a clear way to track who is expected, how many people each session can accommodate, and who has actually entered.
A small event does not need a complicated operating plan. It does need decisions made before registration opens and a shared check-in routine that staff can follow on the day. This guide walks through session capacity, registration details, QR entry, access records, and a useful post-event review.
Map sessions and set capacity before registration opens
Start by listing every session attendees may join. Include its time, location and any practical differences that affect entry, such as a separate room or a distinct check-in point. If people can attend more than one session, make that clear in your plan. The goal is to define what a session means operationally, not just how it appears on the programme.
Next, decide a working capacity for each session. Use the space and your event’s operating needs to set a number you can manage; do not assume that the event’s overall capacity applies equally to every session. For example, a small workshop room and a larger gathering space may need different limits. Keep the figure with the session details so the organiser and check-in team are working from the same plan.
Consider how you will respond as registrations approach the capacity you set. Decide who will monitor the numbers and what action they should take if a session fills. The right action depends on your event: you might stop accepting registrations for that session, direct people to another available session, or ask the organiser to review the plan. Avoid leaving this decision until a queue forms.
Also think through transitions. If one session ends as another begins, staff may need time to confirm departures, prepare the space and admit the next group. A little time between sessions can make check-in calmer and give you a chance to reconcile the attendee list before entry starts.
Set up registration details and attendee lists
Make registration reflect the way the event is actually organised. Give each session a clear name and provide enough information for attendees to choose the right one. If registration is for the whole event rather than individual sessions, decide how you will record which sessions each person plans to attend. Whatever approach you use, explain it in plain language before someone registers.
Collect only the information your team needs to manage participation and check-in. Names and a useful way to identify a registration may be enough for some events; other organisers may need additional details for their specific arrangements. Keep the list readable and make sure the people responsible for check-in know which fields matter. Unnecessary information can slow down a busy entry point.
Before registrations open, test the process from the attendee’s point of view. Check that session names, dates and locations are consistent across the information you provide. Confirm that your team can find the resulting attendee records and tell which session or sessions they relate to. If the registration process allows corrections or changes, decide who will handle them and how updates will reach the check-in team.
Keep a current version of the attendee list available to the people who need it. Avoid relying on several conflicting copies: changes made after a list is shared can otherwise be missed. If more than one person is handling entry, agree on a single process for checking a registration and recording that the attendee has arrived.
Plan how staff will validate QR entry across sessions
QR check-in can make it easier to identify a registration, but it still depends on a clear process. Before event day, decide where QR validation will happen, who will do it, and what staff should do when a code cannot be validated. Brief the team on which session they are admitting people to and how to distinguish one session’s entry from another.
Make sure the check-in team knows what a successful validation means for your event. Is it entry to a particular session, or entry to the event as a whole? Staff should not have to infer this while a line is waiting. Explain the intended check-in point and what to do if an attendee arrives at the wrong room or at a time that does not match their registration.
For a small team, assign responsibilities in advance. One person might greet attendees and help them find the right queue while another validates entry. At a smaller event, one person may do both, but the plan should still describe the steps: identify the session, validate the QR entry, and make sure the attendee’s arrival is recorded. Keep instructions short enough to use during a busy arrival period.
Prepare a practical fallback for cases staff cannot resolve immediately. Agree who can look up a registration or make a decision about an exception. Do not assume every QR issue has the same cause: the attendee may have the wrong session details, the registration may need checking, or the code may simply be difficult to present. Handle the person respectfully, verify the situation using your agreed process, and avoid admitting someone solely because the queue is building.
Event attendance supports organising events and sessions, registering attendees, validating entry from any device, and maintaining capacity, incident and access records. It may be useful when you want those parts of your event plan managed together rather than spread across separate lists.
Record attendance, access issues and incidents
Decide in advance what your team will record during check-in. At a minimum, make sure the process distinguishes expected attendees from people whose entry has been validated. If your event has multiple sessions, preserve enough detail to understand attendance by session rather than only at the event level.
Agree on how staff will note access issues. A brief, factual record can help the organiser follow up on a registration that could not be found, an attendee directed to the wrong session, or another exception. Record what happened and how it was handled, without adding assumptions. Give the team a clear point of contact for questions they cannot resolve at the door.
Keep the check-in routine consistent across staff and entry points. If one person marks an arrival in one way and another uses a different method, the final record may be hard to interpret. A short pre-event briefing can cover the steps, the session being checked, how to handle a failed validation, and where to report an incident.
There is also a useful distinction between a registration and an attendance record: a person on the list was expected, while a person recorded as checked in was present at the point your process captured. Keeping those ideas separate makes it easier to understand turnout later and avoids treating registrations as confirmed attendance.
Review attendance and capacity after each session
Once a session ends, compare the attendance record with the registrations and capacity plan. Note how many people were expected, how many were recorded as attending, and whether any access issues affected the count. If your process does not provide a reliable number for one of those measures, note that limitation rather than guessing.
Use the review to improve the next session, not to assign blame. A room that felt crowded, a slow check-in point, or several attendees arriving with unclear session details may point to a change in room planning, staffing, timing or attendee information. Write down a specific adjustment while the details are fresh.
After the event, review the pattern across all sessions. Which sessions had more demand, and where did attendance differ from registrations? Were transitions long enough? Could staff resolve QR or registration questions consistently? These observations can help you set more realistic capacities and make registration instructions clearer at your next event. Treat attendance figures as evidence for planning, while remembering that a record is only as useful as the process that created it.
Conclusion: make the process clear before doors open
Coordinating session capacity and QR check-in for a small event is mainly about connecting a few practical decisions: define each session, set its capacity, make registration easy to interpret, brief staff on validating entry, and record attendance and exceptions consistently. Review the results after each session so you can make timely adjustments and learn from the event.
If you need a straightforward way to organise sessions, registrations, QR entry and attendance records, explore Event attendance.