How to deliver a paid online workshop

You've sold places for an online workshop. Your instructor knows the subject, the meeting link works, and the slides look good. Then you try the first exercise as a participant. You need to watch the demonstration, open a worksheet, find your own file and ask for help, all on one laptop. Suddenly, the delivery needs more thought.

To deliver a paid online workshop, plan how people will complete the promised task on their own devices, with enough practice and feedback to finish it. Prepare their setup before the session, separate teaching from technical support, and rehearse what happens when someone loses access or the instructor disconnects.

That's the difference your buyers will feel. They've set aside money and time to do something with your help. A smooth presentation is useful, but the workshop has to leave them able to repeat the work when you're no longer on the call.

We'll use a fictional example throughout: a two-hour online workshop where independent retailers build a simple stock reorder spreadsheet. There are 12 paid places, one instructor and one producer handling access and technical support. Attendees leave with a working file and know how to update it. Every quantity and timing in this example is a planning choice, not a benchmark or a customer result.

Start with the work people will finish

The first thing you want to do is describe what a participant actually completes. For our retailer workshop, that's a spreadsheet containing a small sample stock list, a reorder calculation and a check that changing sales changes the result. "Understand inventory management" would leave the instructor trying to cover a much wider subject.

Choose something people can finish with the time, starting knowledge and equipment you can reasonably expect. A beginner who hasn't used spreadsheet formulas needs a different lesson from someone who already manages several product lines. Put that starting point on the ticket page, along with the result and anything outside the session's scope.

Our example requires basic spreadsheet navigation. It doesn't teach accounting, advise on stock purchasing or connect to a retailer's ordering system. Attendees use supplied fictional product data so nobody has to expose their business records to the group. They can adapt the finished template privately afterwards.

Then work backwards. What must the instructor demonstrate? What will the participant try? What mistake would show that they haven't understood? What correction would help them continue? Those questions give you a teaching plan you can test, rather than a list of subjects you hope to get through.

Cornell's Center for Teaching Innovation describes active learning as applying ideas through tasks, discussion and problem solving, with timely feedback supporting the process. We're applying that teaching principle to a commercial workshop. It doesn't establish a particular ticket price, class size or completion rate.

If you're still deciding the wider offer, instructor arrangement and minimum bookings, use our paid workshop planning guide. Here, the delivery question is more specific. Can someone follow your lesson from their own desk and complete the promised work without the instructor standing beside them?

Choose the tools by testing the participant's route

You need a meeting service that supports the activities you've sold. Start with audio, screen sharing, captions, participant questions and whatever small group work the lesson requires. Check the actual account and settings you'll use, including session length and who can take over hosting. Don't assume a feature you've seen elsewhere is available in your booking.

Keep the number of tools down. In our example, the participant needs the meeting, their spreadsheet and a short instruction document. Adding a discussion board, polling app and separate submission portal would create more logins without helping them build the file. Use another tool when it solves a problem you can name.

Rehearse on the participant's likely setup. A laptop with one screen is a sensible starting point for our workshop. The instructor's two monitors can conceal an awkward task switch that everyone else will have to make. Try following the demonstration, moving to the spreadsheet and returning to the meeting without missing the next instruction.

Mobile access deserves an honest decision. Someone might be able to join the video call on a phone while still being unable to edit the worksheet comfortably. If the practical work requires a laptop, say so before purchase. Don't advertise participation on any device because the meeting itself opens on one.

For browser tools, check whether attendees need personal accounts or can use their existing work accounts. Workplaces may block outside sharing or installations. Google's file sharing documentation distinguishes viewing, commenting and editing permissions, and explains restrictions that can apply to work or school accounts. Test the permission people actually need for your exercise.

Give each attendee a private working copy where the task calls for one. A shared master that everyone can edit invites accidental changes and makes it harder to see who has completed their own work. Keep your demonstration file separate, name the files clearly and test how participants recover a clean copy.

Set a ticket limit around the feedback promise

An online room may admit far more people than you can teach well. Your useful capacity depends on how you see their work, how long corrections take and what support you've promised. A participant's camera tells you they're present. It usually won't tell you whether their spreadsheet formula is wrong.

If every buyer gets individual feedback, put that time into the plan. In our fictional workshop, the final check allows two minutes per attendee. With 12 attendees, that means 24 minutes reserved for those checks. The producer handles file access while the instructor checks one completed calculation from each person. These are modest checks of a defined task, not detailed business consultations.

Twenty attendees would require 40 minutes at the same allowance. You can't keep the same running order and promise simply because the meeting licence accepts more people. You'd need another suitably prepared instructor, a longer session or a different, clearly stated feedback offer.

A small cohort also makes it easier to notice someone who has gone quiet. It doesn't guarantee that you'll notice. Build a way for people to show progress privately, such as submitting the requested result or signalling that they need help. The instructor should know what those signals mean before the workshop starts.

Account for preparation and follow-up when reviewing the finances. An online event avoids some venue expenses, but the producer, rehearsal, resource preparation and promised feedback still cost time or money. Our workshop pricing guide helps you calculate the offer before extra support quietly absorbs what you expected to earn.

Tell buyers what participation will require

Your ticket page should explain the session as someone will experience it. For our example, tell buyers that they'll watch short demonstrations, complete exercises in their own spreadsheet and receive a brief check of their finished calculation. Explain whether they'll speak, share work with peers or use a camera, so there are no surprises.

State the date, start and finish time, and named time zone. International buyers shouldn't have to infer the zone from your location. Include a calendar invitation after booking and check that it displays correctly for the date of the session. Daylight saving changes can make a copied conversion wrong.

List the software, account, device and preparation requirements before payment. If an extra subscription, specialist material or download is necessary, disclose it and explain who supplies it. Our retailer workshop uses a supplied template and sample data; the attendee must have access to the specified spreadsheet software and a laptop that can run the meeting alongside it.

Be clear about access and attendance too. Explain when the joining instructions arrive, where people can ask for help, and what happens if they arrive late. If someone buys several places, find out whether each participant will receive their own instructions. An order confirmation sent to one buyer may leave their colleagues uninformed.

Describe the replay precisely if one is included. A recording of demonstrations is different from a recording of the whole session, and neither automatically replaces live feedback. Specify what people receive, when it arrives and how long they can access it. Only promise a replay when the instructor, recording setup and participant privacy arrangements support it.

Write cancellation, rescheduling and missed-session terms in plain language, with advice appropriate to the markets you serve. Technical requirements don't excuse you from delivering the advertised experience. If you change the platform or format after selling, assess what that means for buyers and communicate the practical options before the workshop.

Send preparation people can actually complete

Preparation works best when it removes a likely obstacle. Send instructions early enough for someone to try them and ask for help. In our example, the producer sends a setup email one week before the session and offers a short optional access check before the final reminder. Those timings are our choices for this cohort.

Ask attendees to open the practice file, make a copy, enter a sample value and save it. That's more useful than "Please familiarise yourself with the software." You learn whether the account and editing permissions work, and they arrive knowing where their file is. Keep the task short and explain how it helps them participate.

Here's a preparation message you can adapt. "Before our stock spreadsheet workshop, open the practice template and save your own copy. Enter any number in the test cell, then close and reopen the file to check it saved. You'll use that copy during the session. If you can't edit it, reply to this email before the workshop so our producer can help. The live exercises require a laptop; the meeting link alone will work on more devices."

Add the date, named time zone, expected preparation time and support contact around that message. Supply the actual links and specific steps for your chosen software. The template above is wording to adapt, not a substitute for checking the route on your own tools.

For ticket holder messages, Loopyah's attendee email tools connect your communication to the people holding tickets for the event. The live product distinguishes event updates from promotional offers when choosing recipients. You still need to write accurate setup instructions and provide the meeting and learning materials through your chosen services.

Keep one current instruction document. If you fix a broken step, update that document and tell anyone affected, rather than leaving different versions in several emails. Put the meeting access and recovery contact somewhere people can find without entering the meeting. A support instruction hidden inside the broken service won't help.

Make the materials usable while people work

A screen share is temporary. A participant looking at their own spreadsheet can miss the cell you've just selected. Give them a short set of written steps they can keep beside the task, and use the same names in the document and demonstration. "Open the practice file" should refer to one recognisable file.

Include a completed example and a way to check their result. For our stock calculation, the instructions name the sample inputs and the expected output. If someone gets a different result, they can tell the instructor which step they reached. Avoid making the worksheet so detailed that everyone spends the practice block searching through it.

W3C's accessible presentations guidance recommends accessible materials in advance, asking about accessibility requirements and describing relevant visual information. For an online workshop, that means checking the actual documents and meeting controls, then arranging the support people need. A general statement that everyone is welcome doesn't tell them whether they can participate.

Use readable headings and editable text rather than supplying instructions only as a picture or a protected document. Check keyboard navigation through the exercise and whether someone can follow without relying on colour. When demonstrating, say the field name and action aloud. "Change the reorder threshold cell to ten" is easier to follow than "Put it there."

Ask privately about support requirements and give people a direct response. Agree who handles an interpreter, captioning or an alternative format if requested, and test the arrangement during rehearsal. Don't wait until the opening minutes to find out that the captioner can't hear the instructor or the required file won't open.

Keep personal or business information out of public exercises unless sharing it is genuinely necessary and agreed. Our sample data lets participants learn the calculation without uploading real stock records. If a participant wants advice on their own figures, explain whether that's covered and use an appropriate private route rather than inviting a screen share of everything.

Give teaching and support separate owners

The instructor needs to follow the work and explain the corrections. The producer needs to admit attendees, resolve access problems, manage the meeting controls and watch the help requests. Those responsibilities happen at the same time. For our paid practical session, I'd budget for both roles before adding another activity to the lesson.

The producer doesn't have to be a second subject expert, but they need to know the exercises well enough to recognise a file problem. Agree which requests they can solve and which need the instructor. "I can't open my copy" goes to support. "My result changes in the wrong direction" needs teaching attention.

Use one visible help route inside the session, plus the external recovery contact. Tell attendees when to raise a hand, post a question or send a private message. Check what the meeting service supports and what participants can see. Don't invite confidential details into a chat that everyone can read or later download.

Give the producer a simple working record of unresolved requests, with the participant, problem and next action. They can tell the instructor that two people are stuck on the same formula without interrupting every explanation. Keep sensitive details out of the general running order and restrict access to the people who need them.

If you're teaching alone, simplify the offer until you can deliver it. Pretest access, reduce the cohort or remove tools that create extra support. You can also schedule a separate setup session. Selling personal feedback to a large group while planning to monitor every technical issue yourself is likely to disappoint someone.

Build the running order around practice and correction

Write the running order in minutes, including transitions. People need time to stop watching, open their file, try the instruction and return to the conversation. The instructor's preparation often hides those pauses because they already know where everything is. Your rehearsal should measure the participant's route.

Our fictional two-hour plan uses 10 minutes for orientation, 15 for demonstrations, 45 for guided practice, a 10-minute break, 10 for peer review, 24 for individual checks and six for saving work and explaining follow-up. That totals 120 minutes. Spread the demonstration and practice through the session rather than delivering all the explanations first.

This chart shows our invented running order, not a recommended percentage split for every workshop. It makes the tradeoff visible. If you add another 15 minutes of explanation, you have to take those minutes from somewhere or extend the advertised session. Decide which promised activity changes before you agree.

Demonstrate one useful step, let people try it and check the result before continuing. In the first practice block, participants copy the sample data. Next, they build the calculation. Later, they test it by changing an input. That sequence gives the instructor several chances to catch a misunderstanding before it affects the whole file.

The individual checks don't have to make everyone watch 12 similar conversations. Once the common teaching is complete, attendees can refine and save their files while the instructor checks each person's requested result through the agreed private route. Explain the order and expected wait, and have the producer direct people who need a fresh copy or missed a step.

Don't remove the break to recover a late start. People may have planned around it or need it to manage fatigue. Instead, cut an optional example or discussion you identified beforehand. Preserve the tasks needed to reach the advertised result, and tell the group what you've changed.

Make remote feedback specific enough to use

"Any questions?" often gets silence, especially when participants aren't sure what went wrong. Ask for something observable. "Enter the reorder result in the check field" lets the instructor see who needs help. Explain whether that response is private and give attendees another route if they can't use the field.

When correcting work, name the next action. "Select the formula cell and check which sales column it references" gives someone a place to start. "Your formula is wrong" doesn't. Let them make the correction and test it again. Doing every repair for them can leave a tidy file without the understanding they paid to gain.

For peer review, give people a small task they can judge. Our pairs compare a calculation against the supplied sample and explain one change they made. They aren't assessing each other's business decisions. The instructor remains responsible for teaching the correct method and resolving disputed answers.

If you use breakout rooms, test entry, return and help requests beforehand. Provide the task in writing before moving people, along with a completion signal and a way to stay in the main room if that's easier for them. The producer watches the room assignments while the instructor visits where teaching help is needed.

Some people will prefer to keep cameras off or avoid speaking publicly. Give them a way to submit work and receive the promised feedback. A camera requirement should have a clear teaching purpose and appear before purchase. Don't treat visible enthusiasm as the only evidence that someone is learning.

Rehearse the workshop with someone who hasn't built it

Run the real lesson with a trial participant who matches the starting ability you've advertised. Ask them to use an ordinary device, their own account and the instructions you've prepared. Watch where they hesitate. A colleague who helped create the spreadsheet may skip exactly the steps a paying beginner will find confusing.

Rehearse the producer's job too. Have the trial participant request help, join late, leave and reconnect. Check that the instructor can continue while support works through the problem. Test captions, screen sharing, file permissions and the route for submitting a result. Write down what failed and correct it before the full rehearsal.

Use the actual network and equipment planned for delivery. Our guide to testing internet before streaming an event covers checking the connection and backup. For a workshop, also test the participant actions alongside the broadcast. An instructor can have good video while the exercise file remains inaccessible.

Agree what the producer does if the instructor disconnects. They should keep the meeting running where the service supports it, tell participants what's happening and direct them to a prepared task they can complete independently. Set a realistic point for deciding whether you can resume or need to reschedule the remaining work.

A backup meeting needs more than a saved link. Test its account, permissions and participant route, and decide who sends it through the external contact channel. Moving everyone may take longer than restoring the original service. Choose the response based on the failure you've rehearsed rather than assuming a switch will be instant.

Prepare a recovery note the producer can send without composing it during a failure. It should name the problem, the next task and when another update will arrive. For example, "Our instructor has lost their connection. Please save your file and work through the sample check in the instructions. Our producer is staying in this meeting and will update you shortly. If you also lose access, use the support contact in your preparation email." Replace "shortly" with a specific update time when the incident happens.

Distinguish an individual interruption from a group failure. If one attendee disconnects, the producer can help them return and identify the step they missed. If the whole group loses the exercise file, continuing the demonstration may create more catching up later. Pause, restore access and confirm that people can resume before moving on.

For our spreadsheet example, keep a downloadable practice file available as an alternative only if you've tested it in the software attendees have. That fallback changes the sharing process, so rehearse how the instructor will check results. A replacement that opens but removes the promised feedback hasn't fully solved the delivery problem. Record unresolved attendees for follow-up, with a named person responsible for contacting them.

Protect access without making paid attendees struggle

Keep the joining details within the ticket holder communication you've chosen, and use the meeting's available access controls. Check admission, participant screen sharing and host permissions before the day. A public joining link can bring in someone who hasn't booked or someone who disrupts the group.

The UK's National Cyber Security Centre provides guidance on securing online meetings, including considering meeting settings and controlling who can join. Apply those decisions to your actual service. Security arrangements should also leave the producer able to help a legitimate attendee whose display name differs from their booking.

Explain the recording arrangement at booking and again before recording begins. For our example, only the instructor's prepared demonstrations are recorded separately. Peer rooms, private checks and participant questions aren't included in the replay. Verify that your setup actually follows that plan, rather than trusting a recording setting you haven't tested.

W3C's audio and video accessibility guidance explains captions, transcripts and descriptions of relevant visual information. Prepare the replay accordingly and check what your audience needs. An automatic transcript can contain errors in formulas or technical terms, so review the instructions people will rely on to repeat the exercise.

Keep the promised replay access separate from your marketing use. Someone agreeing to attend a recorded workshop hasn't necessarily agreed to appear in an advertisement. Agree permissions for instructor materials and any participant contributions before reusing them, and establish who answers questions about recording access or removal.

Open with the instructions people need now

Open access early enough for the producer to resolve routine joining problems before teaching starts. Our example uses a short arrival period outside the advertised two-hour workshop. Tell buyers when access opens and when teaching begins so an early tech check doesn't become an unexpected requirement.

At the start, show where the materials are, explain the help route and describe the finished task. Confirm that people can edit their own file. Give late arrivals a written catch-up route and let the producer help them; repeating every opening instruction to the whole group takes practice time away from everyone else.

Here's an opening you can adapt. "Today you'll build and test your stock reorder file using the sample data. Keep your own spreadsheet open beside the meeting. If you can't access the file, message our producer through the help route shown here. If a calculation doesn't make sense, raise your hand so the instructor can help. We'll check your result before we finish, and you'll keep the template afterwards."

Then start the first task. A long introduction to the organiser, instructor biography and housekeeping can consume the attention you need for practice. Say enough to establish who is responsible and how the session works, and introduce further instructions when people need them.

Follow through on unfinished work and promised support

Before closing, ask everyone to save their file and locate it again. Check the specific result you've promised, rather than just asking whether they enjoyed the session. If someone hasn't finished, identify why and tell them the agreed next step. Don't let a private support request disappear when the meeting ends.

Send the resources and any promised replay on the date you gave attendees. Include corrections to the written instructions if the live session exposed an error. Explain exactly what follow-up support includes and when it ends. If you offered one brief review of the completed exercise, keep that promise without accidentally offering unlimited consulting.

Review delivery with the instructor and producer while the problems are still clear. Record which setup steps failed, which exercises took longer and how many people completed the intended task. Treat those figures as information about this session. A small cohort doesn't establish a universal completion benchmark.

Finally, compare actual delivery costs and hours with the plan, including extra support and refunds. If participants needed more help than expected, revise the preparation, scope or staffing before you sell the next date. Start with the point where people got stuck. Fixing that specific step gives the next cohort a better chance of leaving with work they can use.