This fictional example covers a one-day pottery workshop for up to twenty-four participants. The organiser needs two start times, equal capacity, and a simple way for people to release a place. The board coordinates registration only; payment and detailed participant communication happen elsewhere.
The workshop and its two choices
The board is titled “Saturday pottery workshop.” Its description gives the venue, date, two-hour duration, and a note that payment instructions arrive separately. Slots are “Morning — 10:00” and “Afternoon — 14:00,” each with twelve places.
Capacity matches the room and equipment
The studio has twelve wheels, so the organiser does not create extra places. The public link is tested in a private browser window before sharing. The organiser keeps the management URL in a private planning document.
A participant chooses and later changes a session
Nora signs up for the morning option and saves her private link. When travel plans change, she moves to the afternoon session herself. The morning capacity returns immediately and no organiser edits a spreadsheet.
The organiser reviews the board before the workshop
The organiser checks filled places, closes registration at the announced deadline, and contacts participants through the established channel. Roster shows names and choices but does not verify attendance, send reminders, collect fees, or export a calendar.