Tickets & RSVP

Invites, registration & requirements to participate

Registration for a remote workshop is the first experience your participants have of you, and it sets the tone before they ever join the call.

Tickets and RSVP cover how people find out about the session, how they sign up, and what they agree to when they do. For a closed internal session that is a simple calendar invite. For an open or paid session it means a registration form, confirmation emails, and possibly access controls.

Online, registration does more than confirm attendance. It is the right moment to collect technical information, send joining instructions, set expectations about pre-work, and give participants what they need to arrive ready. A smooth registration process reduces the last-minute scramble that derails the first ten minutes of a remote session.

Requirements to participate are part of this card too: what device, what connection, what software, what account. Being clear about these upfront avoids discovering on the call that someone cannot access the tools you planned around.

Online, specificallyOnline registration is where you hand people their joining link, their tech requirements, and their first sense of how organised you are, so it does more work than a paper sign-in sheet ever did.

In a remote session

The same building block as it plays out online: how experienced facilitators tend to handle it when the room is a screen. Illustrations to react to, not rules to follow.

Confirm with everything they need

Good facilitators send the confirmation email with the video link, the tool links, and the technical requirements in one place, not spread across three separate messages sent days apart.

Ask what you actually need

They keep the registration form short, asking only for information the session genuinely needs: name, email, organisation, and any access or accommodation requirements. Long forms reduce sign-up rates.

Set tech requirements clearly

They state upfront what device, browser, and software participants need, and whether a camera or microphone is required. This prevents last-minute access failures.

Use registration to pace demand

For open sessions, a waitlist or limited capacity registration helps keep the group to a workable size, which is often smaller online than in a physical room.

Questions to plan around

Use these on your own or in a group. There are no right answers, only better conversations.

What information do you genuinely need from participants at registration, and what can you leave out?
Does the confirmation message give participants everything they need to join, including all links and technical requirements?
Are there requirements to participate, such as a specific device, software, or account, and have you communicated these before sign-up?
How will you handle participants who register but do not show up, or who try to join without registering?
What is the maximum group size this session design can handle, and does registration enforce that limit?

What trips people up online

Sending the video link in a separate email from the registration confirmation means someone always loses one of them.
Not stating technical requirements at registration means you find out on the call that someone cannot participate as planned.
Skipping a registration step for internal sessions is tempting but removes the moment to send joining instructions and pre-work in a natural, expected way.