How to Run an Online Workshop: Planning Canvas and Checklist

An online workshop should leave participants with something they can make, practise, or decide. If the only plan is "talk for an hour and take questions," the session can feel busy without helping anyone finish the job.

This guide gives you a practical way to run an online workshop: define the participant outcome, work backward through the activity and event handoffs, then rehearse the exceptions. It includes a copyable operations canvas, a fictional educator example, and a checklist for the attendee path.

1. Define the output and scope

Start with one sentence that finishes this prompt: By the end of the workshop, each participant will... The answer might be a draft, a rehearsal, a decision, a worked calculation, or a short plan. Keep it observable. "Understand launch emails" is hard to test; "leave with a first launch email and one revision" gives the session a clear job.

Write down four boundaries before you choose a platform:

• Output: what participants should make or practise.
• Prerequisites: what they need to know, bring, or complete first.
• Materials: the document, example, data, or account they will use.
• Out of scope: the useful topics you will leave for another session.

These boundaries help you decide whether you need a workshop at all. If participants only need to watch a demonstration, a webinar may be a better fit. If you are still weighing those formats, the webinar versus workshop comparison lays out the distinction.

2. Use a copyable workshop operations canvas

The canvas turns a teaching idea into an operating plan. Copy it into your planning document and add rows for each meaningful activity. The columns force the handoffs into the open, including the parts that belong to a live-room provider rather than to your event platform.

Do not treat the time column as a universal formula. Give each activity enough room for participants to do the work and receive the feedback you promised. A short rehearsal will tell you more than an industry rule about the ideal runtime.

3. Fill the canvas with a fictional educator example

Imagine Maya, an educator helping first-time course creators write a launch email. Her workshop promise is: leave with one launch email draft, one peer revision, and a next-send decision. The example below is hypothetical. It shows how the handoffs fit together; it does not report a measured completion rate.

Notice what the example does not claim. HeySummit does not assess the email or provide a built-in writing coach. The educator chooses the exercise tool and the evidence. The event setup only needs to make the promise, access path, reminders, and follow-up clear.

4. Build the attendee path

A good workshop plan can still fail if people cannot find the promise, prepare, or join. MIT Solve's virtual-event guidance treats goals, platform selection, room ownership, and follow-up as planning decisions. Walk the path as an attendee before you invite anyone:

1. Event page: state the output, who it is for, what to bring, and what the session does not cover.
2. Registration: ask only questions that change the session or the support you provide. If you need a topic, role, or accessibility request, explain why. The event registration question matrix can help you choose a small, useful set.
3. Access: distinguish a free registration from a paid ticket or other access rule. The attendee should know what the confirmation unlocks.
4. Preparation: send the materials, pre-work, join details, time-zone information, and a contact route. Custom event emails can carry these reminders when the setup supports them.
5. Test: complete the journey with a test address. Check the confirmation, the join link, the document permissions, and the route for a late attendee.

Keep payment and checkout details proportionate to the article. If the workshop is paid, the paid webinar guide covers ticketing, access, and replay decisions in more detail. The same principle applies here: the attendee should understand the exchange before the session begins.

5. Rehearse delivery and failure paths

Rehearsal is where the plan meets the real room. Run the core activity with the exact files, links, roles, and provider settings you intend to use. Ask a colleague to join as a participant and try the help route.

• Check microphone, camera, screen sharing, chat, captions, and recording settings with the chosen delivery provider.
• Give the producer a written run of show: welcome, instructions, work time, time checks, feedback, and close.
• Decide how a late arrival gets the context without stopping the group.
• Prepare a no-breakout and no-shared-document path. A downloadable prompt and typed response can keep the exercise moving.
• Set a rule for missing pre-work. Let people catch up without making prepared participants wait.
• Decide who answers access questions and what happens if the provider room drops.
• Use the W3C event accessibility checklist to review platform choice, preparation, and descriptions of visual information. Do not imply that a particular platform is certified accessible.

Keep the boundary between systems explicit. HeySummit can coordinate event pages, registration, ticket access, and attendee messages. The provider you connect for delivery determines the live room, collaboration controls, captions, breakout behaviour, and any whiteboard or assessment tools. Verify those capabilities in the current provider plan before you promise them.

6. Close the learning loop

End by showing participants what happens to the work they made. Ask them to choose the next action, submit a short reflection, or name the decision they will make after the session. If you collect a document or form response, tell them who can see it and how long it will be kept.

Recording and participant work deserve a separate decision. Explain whether you will record, who will receive the recording, whether participant names or contributions may appear, and how someone can ask a question privately. Get the consent and access wording you need for your situation rather than assuming one rule applies everywhere.

Measure only what the systems actually capture. Attendance, submitted work, feedback responses, or follow-up actions can be useful evidence when you define them in advance. Do not turn a workshop plan into a promise of learning gains or revenue results.

7. Connect the event handoffs to HeySummit

Once the canvas is clear, HeySummit can hold the public event journey around the live exercise. Its one-off workshops workflow is a sensible place to evaluate event pages, registration, ticket or access rules, attendee communications, and the delivery integration that fits your session.

Use the product for the handoffs it owns: explain the outcome on the event page, collect the information that changes the experience, give each attendee the right access, and send preparation and follow-up messages. Use the connected video or collaboration provider for the live room and its tools. The video and streaming integrations overview is the right place to check the current connection options.

If your workshop depends on assessment, collaborative editing, breakout facilitation, or a specialist classroom, keep that tool in the plan and make the boundary visible to participants. An event platform can reduce the registration and access work without replacing every teaching tool.

When the canvas, attendee path, and failure plan agree, you have a workshop you can run and improve. Start with the result participants need, then make every system and person responsible for helping them reach it.