What is a conference workshop?

A workshop is the format where the room’s limit is a hard number rather than a guideline. There are twenty seats, twenty sets of materials, and one facilitator who cannot usefully work with forty people.

In practice at an event

Because capacity is real, sign-up management becomes operational rather than administrative. Attendees reserve a place in advance, the limit is enforced, and a waitlist fills the gaps as people drop out — which they do, at rates high enough to matter.

Ninety minutes is the practical minimum for a workshop that does anything hands-on. The room usually needs a different layout from a talk, which means it needs its own room rather than a reset of a lecture space, and that constrains the venue.

What to look for

Ask whether capacity is enforced on the server. If it is enforced only in the app, two attendees tapping simultaneously will both be told they have the last place, and the resolution happens in front of the room.

Then ask whether waitlist promotion is automatic and whether the promoted attendee is told. A waitlist that depends on an organizer noticing a cancellation is not a waitlist.

Budget for drop-out when you set the limit. Pre-booked workshop places go unused at rates high enough to leave visible empty chairs, which is why the waitlist matters and why a rule for releasing unclaimed places five minutes in is worth agreeing in advance.

How event67 handles it

Workshop RSVPs carry a per-session capacity enforced server-side, with automatic waitlist promotion when a place is released. The organizer sets the limit in the console and sees the count as sign-ups run. Attendees reserve from the session screen in the app, and a promoted attendee is notified through the same deep-linked notification path as a schedule change.