Decide what the event is for
A virtual event takes time from both organizers and attendees, so begin with one concrete purpose. Typical aims include teaching a skill, answering questions from a community, introducing a project or simply giving members a reason to see each other. Write the aim in a sentence and describe the person you expect to attend. Every later choice, from length to format, should serve that sentence.
Also decide what a good outcome would look like. It might be that attendees leave with one practical idea, or that a certain number of questions get answered. Avoid vague goals such as “get lots of people”, since turnout is hard to predict and is influenced by many things outside your control.
Pick a format that matches the goal
The main formats differ in how much attendees take part:
- Presentation or webinar: one or a few speakers talk, with a question period. It is easier to run but can feel passive.
- Panel: several guests discuss prepared questions with a moderator. It needs a strong host to keep time.
- Workshop: attendees do something during the session. It works better with smaller groups.
- Informal meetup: open conversation with a loose structure, often in small breakout rooms.
Whether to run something live or record it is a trade-off covered in the article on live sessions. In short, live events allow questions and a feeling of presence, while recordings are easier to watch at a convenient moment. Many organizers do both: run the event live and share a recording afterward.
Choose the date, length and time of day
Shorter is usually safer. Attention tends to fade on a screen, so 45 to 60 minutes, with time for questions inside that, is a common and sensible range for a talk-style event. If you need longer, build in breaks.
When attendees live in different regions, no time suits everyone. Check how your chosen time converts for the main groups you expect, and think about offering a second session or a recording. The same awareness described in guidance about working across time zones applies here. Look at local holidays and avoid clashes with obvious competing events. Putting the date in everyone’s calendar early helps; many registration tools can send a calendar file, which fits with the way people use shared calendars.
Build a simple schedule
Write a run-of-show: a minute-by-minute outline of who speaks, who controls the slides, when questions are taken and who handles chat. A simple structure might be a welcome and housekeeping (five minutes), the main content, a question period and a closing with next steps. Leave a little slack, because things nearly always run over.
Assign roles even for small events:
- A host who opens, introduces and closes.
- A speaker or speakers.
- A technical helper who handles settings, recording and problems.
- A chat monitor who gathers questions and welcomes late arrivals.
One person can fill more than one role, but being host and technical helper together is stressful.
Set up registration carefully
Registration lets you estimate attendance and send reminders. Collect only what you need, usually a name and an email address. Say plainly how you will use the data and whether you will contact people afterward. If registrants will join an email list, make email consent explicit rather than assumed, and include a clear way to opt out. Where details are shared with a third party, say so.
Send a confirmation immediately, then a reminder a day before and another shortly before the start. Include the date and time with a time zone, the joining link and any materials needed. Expect that a good share of registrants may not attend; the proportion varies widely, so plan for uncertainty instead of relying on a particular figure.
Rehearse the technology
Most avoidable problems are technical. Run at least one rehearsal with all speakers on the actual setup they will use. Check:
- Audio first, since people tolerate weak video better than poor sound.
- Screen sharing and how slides look to attendees.
- Whether recording starts and where files are saved.
- How questions, polls and chat will work.
- A backup plan, such as a second host able to take over or a phone number for last-minute help.
Speakers should know how to behave if something fails. Many of the habits described for good video meetings, such as muting when not speaking and testing equipment ahead of time, carry over directly.
Plan for accessibility
Accessibility is easier to plan than to repair afterward. Consider:
- Live captions if your tool supports them, and a transcript afterward.
- Slides with large, high-contrast text, and descriptions of any important images.
- Sharing materials in advance so people can read at their own pace.
- Speaking plainly and avoiding unexplained jargon.
- Giving more than one way to ask questions, such as chat and spoken.
These steps also help people who join from noisy places, have slow connections or speak the language as a second one. The broader principles of web accessibility apply to the registration page as well.
Run the event calmly
Start on time but allow a short grace period for the joining link. Greet people as they arrive, state the agenda and say how to ask questions. Keep an eye on the clock, repeat questions before answering them and have the chat monitor flag anything that needs attention. If something goes wrong, acknowledge it briefly and carry on; audiences are generally forgiving of small glitches.
Hold to the same standards of online etiquette you would expect in person, and decide beforehand how you will handle disruptive attendees. Having the ability to remove someone and to restrict screen sharing is a sensible precaution.
Follow up promptly
Within a day or two, send thanks, the recording or summary if you promised one, links to materials and any answers to questions you ran out of time for. A short feedback form with a few clear questions helps you improve; well-chosen customer feedback methods and basic survey design principles apply. Review what you can learn from attendance and any data you have, keeping in mind that numbers rarely tell the full story.
Write down what worked and what did not while it is fresh. The next event will be easier for it.