How to run a paid virtual conference

Your keynote has finished, attendees are choosing their next sessions, and a speaker in another room has lost their microphone. Meanwhile, support has a buyer who paid for a workshop but can't enter it. This is where running a paid virtual conference becomes quite different from hosting a single online talk.

To run it well, organise delivery around the sessions happening at the same time. Give each room an accountable producer, make ticket access and capacity rules clear, and rehearse the transitions attendees and speakers will make. Then manage the conference against the programme you sold, including networking, sponsor commitments and replay delivery.

This guide focuses on that operational work. If you're still deciding whether the event should exist, our paid virtual event planning guide covers the offer and commercial foundations. Here, we'll use a fictional conference for independent training businesses to work through a programme with parallel sessions. The example arrangements are choices to test, rather than industry benchmarks.

Turn the programme into a delivery plan

The first thing you want to do is read the published programme as a series of things your team must deliver. A keynote needs someone to operate the feed. A workshop needs a facilitator, materials and a manageable group. A networking session needs introductions and a way to leave. List those responsibilities before counting how many people you need.

Our fictional conference has a shared opening, parallel sales and delivery tracks, a networking break, another parallel session block and a shared closing. Attendees choose the track that fits their business. That choice makes sense only if session descriptions explain the intended experience and assume a clear level of knowledge. Otherwise, people move between rooms trying to discover which talk they bought the ticket for.

Keep a delivery record for each session. Include its public title, room, start and finish, speaker, moderator, producer, access requirements, recording decision and materials. Add the speaker's private joining route separately. The programme page tells buyers where to go; the delivery record tells your staff what must happen and who is responsible.

Use that record to discover conflicting assignments. A guest cannot leave the main stage, join another room and begin a workshop at the same moment. A producer cannot test the next presenter while switching the current panel's screen share unless the setup supports that work. Resolve these collisions while you can still change the timetable.

Put one person in charge of the overall schedule. Room teams should know which decisions they can make themselves and which changes need approval. A moderator can shorten an introduction. Moving a session to a different time affects attendees, other speakers and support, so it needs a conference decision and an agreed way to communicate it.

Make parallel tracks worth the extra work

Two tracks let different buyers attend useful material at the same time, but they also create choices and missed sessions. Start with differences in what attendees need to learn. In our conference, a business owner preparing company proposals might choose the sales track, while an operations manager chooses delivery. Those are recognisable reasons to separate the sessions.

Avoid placing closely connected sessions opposite each other. If the proposal workshop requires the contract discussion, scheduling them together makes the programme harder to use. Ask people from the intended audience to choose their route through your draft timetable. When they repeatedly want both sessions in the same block, reconsider the pairing before adding recordings as an excuse.

Explain whether people can change tracks. An open conference might allow movement between presentation rooms while requiring a reservation for practical workshops. Publish that distinction wherever attendees choose sessions. A track preference collected during booking is not automatically a reserved workshop place, and a ticket for the whole conference doesn't necessarily promise unlimited access to every small group.

Keep shared moments where they help the programme. A common opening can explain the conference question and how tracks work. A closing discussion can compare what the groups learned. You don't need to bring everyone together after every session, especially if doing so consumes time attendees could use for a break or a useful conversation.

If your event mainly develops one question through a sequence of speakers, read our virtual summit guide. A single programme may be the better choice. Add parallel delivery when it solves an audience problem you can describe and when the ticket income can support the additional people and production work it creates.

Set session capacity and ticket access together

A room's technical capacity and the number of people it can serve well are different decisions. A presentation can support a larger audience than a workshop where everyone receives feedback. Ask the facilitator how participation will work, then set the practical limit. Check that your viewing provider and subscription can support both that limit and the overall conference.

For a fictional example, suppose you sell 120 conference passes and offer two workshops with 30 places each. That provides 60 workshop places, so you cannot promise every pass holder a workshop reservation. You could sell a clearly defined workshop add-on, offer another round, or make the limited availability explicit before purchase. These quantities are illustrative, not recommended capacities.

Decide what happens to unclaimed reservations. If you release a place after a stated arrival deadline, explain the deadline when people book. Have a staff member manage that decision rather than allowing a late buyer and a waiting attendee to argue over entry. Keep a record of any promised access that support needs to honour.

Test the different tickets against the actual conference access settings. A general pass, workshop add-on, sponsor guest and staff account may need different permissions. Check that a refund or cancellation removes the relevant access through your chosen process. Also test a company buying tickets for colleagues, because the payer's email may not identify the people attending.

Loopyah's ticketing tools support ticket types and release quantities, which helps you sell defined offers with controlled availability. The conferencing service still needs its own access configuration. Verify how those purchases become the right room permissions in your setup, and avoid assuming that creating a ticket type also reserves a seat inside another service.

Check what each extra room costs

Before confirming parallel delivery, ask suppliers to quote the actual session arrangement. Include room production, moderation, captioning where required, rehearsal and replay preparation. An extra room may change several bookings at once. Request the hours and responsibilities behind each quote so you can compare a simpler conference with the one you intend to sell.

For a fictional calculation, suppose the additional track costs $2,400 and each extra paid booking contributes $80 after the costs associated with that sale. You would need 30 additional bookings to cover that track's additional cost. This assumes the rest of the conference budget already works and excludes any expenses missing from those inputs. It isn't a recommended ticket price or a prediction of demand.

Ask what evidence supports those extra bookings. Existing buyers choosing between rooms won't necessarily generate extra revenue. The track may attract a distinct audience, support a higher priced offer or improve repeat purchase, but those are different commercial arguments. Describe the one you're relying on and check whether your sales evidence supports it before committing money.

Also budget for operational changes after launch. A popular workshop might justify another session, but the speaker, producer and accessibility arrangements must be available. Price the whole addition before promising it to buyers. If you cannot deliver another session responsibly, keep the original limit and explain the remaining offer accurately.

Staff each room and the conference separately

Start with the work that happens simultaneously. Each live room needs somebody accountable for the feed, speaker permissions, media and recording. Each discussion needs moderation. Attendee support needs access to bookings and the conference instructions. Someone also needs to watch the overall programme and make decisions when a problem affects more than one room.

On a smaller conference, a room producer may also manage written questions while a moderator hosts the conversation. Try that combination during rehearsal using the busiest session. If the producer stops monitoring sound to sort questions, the arrangement needs changing. Staffing should reflect the work you observe, rather than the smallest headcount that looks affordable on a spreadsheet.

Give staff a private communication route that remains available outside the live rooms. Use clear room names and identify who is speaking. A message saying the workshop speaker has disconnected should name the workshop and the producer handling it. Otherwise several people may interrupt their own sessions to investigate, while the affected room still waits for a decision.

Assign a deputy for the conference lead and a replacement route for each producer. This doesn't always require another person sitting idle. It does require someone who has the correct permissions, understands the room and can take over without borrowing the missing person's login. Check that taking over doesn't leave another essential responsibility uncovered.

Book the preparation and follow-up hours as well. Room setup, rehearsal, recording checks and incident reports are part of delivery. Agree when each person's responsibility ends and who receives unfinished tasks. A producer who signs off after the closing session may not be available to explain an incomplete recording the following morning unless you planned for it.

Write handovers that speakers can follow

A speaker handover begins before the audience sees it. Decide where the incoming presenter waits, who checks their sound and slides, and who tells them they are live. Keep their private access separate from the attendee route. An invited guest shouldn't have to find their own session through the public programme while the moderator fills time.

Send a brief that explains the session's audience, question and format, together with the joining instructions. Our conference speaker briefing guide covers the content detail. For delivery, add the producer's name, the communication route if joining fails, the agreed timing signals and what happens when the previous session runs late.

Check the speaker's actual files and equipment. A rehearsal with a blank screen doesn't tell you whether their embedded video has sound or their financial example is readable. If the producer will operate slides, agree how the speaker requests changes. Keep a checked copy available where permissions allow, so a failed screen share doesn't remove the entire presentation.

Rehearse the end as carefully as the opening. The moderator needs to know how to close questions, tell attendees where materials will appear and direct them to the next session. The producer needs to stop or mark the recording correctly, remove the departing speaker's permissions where appropriate and prepare the next guest without exposing backstage conversation.

Use the same basic timing signals across rooms. Speakers can prepare for a warning and a final question if they know what those mean. Don't invent a different interruption style for each moderator. When the audience must move together, consistent endings matter more than allowing every session to continue until its speaker feels finished.

Help attendees move without missing the programme

Make one current programme page the source for session access and changes. Name rooms consistently across that page, reminders, support replies and moderator announcements. If the sales track is called Sales in one place and Business Growth elsewhere, attendees have to work out whether those labels mean the same room while a session is already beginning.

Include movement time in the timetable. People need to finish a discussion, choose their next session, open it and settle in. Measure that journey during rehearsal on the devices buyers will use. A move that takes staff moments with administrator access may involve another login or permission check for an attendee using a phone.

The W3C's draft guidance on accessible remote meetings recommends explaining how participants enter and leave breakout rooms, identifying help and providing alternatives for inaccessible controls. Apply that to the whole conference. Test the route between rooms with keyboard controls, check caption availability after moving and offer a support route that doesn't depend on using the failed control.

End sessions with practical directions. The moderator can name the next choices, explain the break and point attendees to the current programme. Leave those directions available in text too. Someone who has sound turned down or joins during the ending should still understand what happens next without asking the room producer privately.

Don't change links casually after reminders go out. When a change is necessary, update the programme source and tell affected attendees what changed. Loopyah's attendee email tools distinguish event updates for ticket holders from promotions for opted-in contacts. Use verified event communications for the joining information, and test that the conference service accepts the route you describe.

Make accessibility work across every session

An accessible main stage doesn't establish that your workshops or networking rooms work for the same attendees. Check the controls, materials and accommodations in every format you sell. A participant might follow a presentation comfortably and then lose access when a workshop depends on a shared board they cannot operate. Test those format changes before finalising the programme.

The W3C's accessible events checklist recommends asking about accessibility requirements, providing accessible materials and briefing presenters. Ask early through a clear contact route, explain what arrangements you can provide and follow up on specific needs. The answer may change your staffing or supplier booking, so leave time to act before the event.

Parallel sessions make captioning and interpretation a scheduling question too. Confirm which rooms need which services and whether the professionals involved can move between them. One captioner cannot independently cover simultaneous discussions. If attendees reserve sessions to secure an accommodation, explain that process and avoid unexpected timetable changes that make their chosen route impossible.

Give speakers concrete instructions. Describe the important information in a chart aloud, identify speakers during discussions and avoid explaining an exercise only through a screen share. Supply materials that people can read directly with their preferred tools. The moderator should repeat an audience question before the speaker answers, so everyone receives the same context.

Keep breaks usable. Tell people whether they can step away without losing a reserved place, and give them enough time to return through the actual access process. If an accommodation fails during a session, treat it as a delivery problem requiring attention. Record who was affected, what replacement support was offered and what remains unresolved afterwards.

Give networking a clear purpose and boundaries

Paid networking needs a reason for people to join and a structure they understand. For our training conference, you might group attendees around delivering company programmes or improving proposals. Ask a useful opening question, identify the facilitator and state the finish time. Buyers can then decide whether the conversation fits their needs without having to enter a room first.

Keep participation optional unless your ticket clearly depends on it. Let someone listen, contribute through text or leave a discussion without explaining themselves. A buyer attending between work commitments may value a short relevant conversation but have little interest in an automatic sequence of introductions. Choose the format around the audience's purpose and available time.

Brief facilitators to help the discussion progress. They should invite quieter participants, interrupt someone who turns the room into a sales pitch and prevent the conversation from requiring confidential information. Our training group could discuss how they define delivery scope without naming clients or revealing contract values. Suggest that boundary at the start rather than waiting for a problem.

Set a contact exchange policy. Let attendees choose whether to share their details with another participant. Keep private conversations and the attendee directory subject to the permissions you advertised. A networking ticket shouldn't quietly become permission for every participant or sponsor to download everyone's contact information and begin sending commercial messages.

Plan for groups that don't work. The facilitator might combine sparsely attended rooms when the subjects are compatible, while leaving a clearly labelled option for people who prefer to stay. Give support a route for behaviour complaints outside the discussion itself. The organiser still has responsibility for the environment when attendees meet without a stage host present.

Deliver sponsor benefits without taking over the programme

Map each sponsor commitment to a specific place and person. A sponsor demonstration needs a host, a room, access instructions and an agreed recording decision. A mention during the opening needs approved wording. Record those obligations alongside the editorial sessions so the team can deliver what you sold without trying to reconstruct the agreement during the conference.

Label commercial activity clearly in the programme. Tell buyers whether a session is a sponsored demonstration, an optional product discussion or an independently moderated presentation. Keep the promised educational session useful on its own. A sponsor's request to extend their introduction should not reduce the workshop time paying attendees expected, even when the sponsor contributed substantial revenue.

Agree what evidence you can provide afterwards. That might include delivery screenshots, a record of the scheduled mention and aggregate participation information that the conferencing service actually supplies. Check how the service defines attendance before using it in a report. An opened page, a room entry and someone watching the whole session describe different things.

For UK operations, the ICO's data sharing guidance recommends planning responsibilities before sharing personal information with another organisation. Its guidance is under review following legislative changes. Check the rules applying to your event, agree any permitted sponsor data use and explain optional contact requests to attendees before collecting the information.

Don't promise information your systems cannot substantiate. Ticket purchases show commercial bookings; they don't establish which online sessions those buyers watched. Keep ticket reports and conferencing reports separate until you have verified a supported way to connect them. Your sponsor agreement should reflect the evidence you can responsibly deliver, with the method agreed before the event.

Rehearse the whole conference under pressure

Individual speaker checks are necessary, but they don't show whether the conference works when several rooms operate together. Rehearse a complete session block with the intended staff, permissions and communications. Have testers buy or receive the appropriate test access through your supported process, enter as attendees and move between the rooms while producers prepare the next speakers.

Use the busiest transition. In our fictional conference, that might be the keynote ending while workshop guests arrive and support deals with access questions. Give the team the same files and timing signals they will use live. Check what the audience hears while producers speak privately, and review the recording to see whether those conversations leaked into it.

Introduce problems deliberately. Ask one speaker to disconnect, make a workshop reach its agreed capacity and have a tester arrive with the wrong email. Staff should follow the intended response without receiving fresh instructions from the organiser. If everyone asks the conference lead what to do, identify which decision or permission was missing and repeat that part.

Test a room failure separately from a provider failure. A replacement room within the same service may resolve a broken configuration but remain unavailable during a wider outage. Check whether your alternative preserves ticket access, captions and recording. If it can't, decide which part of the programme can continue and what you will tell the people affected.

Finish rehearsal with a short list of unresolved conditions, each assigned to someone and given a deadline. Repeat the failed steps after changes. A new access setting can fix the workshop and accidentally block speaker entry, so test the connected journeys as well. Confirm readiness using evidence that the current version works, rather than the fact that rehearsal happened.

Run incidents without disrupting unaffected rooms

On the day, each room producer should confirm readiness with the conference lead before admitting the audience. Check the incoming speaker, programme timing, captions, media and recording status. Support should know which rooms are opening and where unresolved access cases stand. This gives the lead a useful picture of delivery without interrupting every moderator for an update.

When a problem happens, identify its scope first. A speaker microphone failure in one workshop doesn't require stopping the other track. Let that moderator follow the rehearsed response while the lead considers any programme consequences. Keep internal messages factual, with the affected session, current action and the decision needed. Avoid guesses about what caused the fault.

Tell attendees what they need to know while you investigate. Explain whether they should remain in the room, use another route or expect an update at a stated time. Don't promise restoration before someone has verified it. If the session must move, update the current programme and brief support before sending buyers in several different directions.

Keep an incident record as delivery continues. Note when the interruption began, which ticket benefits were affected, the recovery action and whether buyers could participate afterwards. A replay may help someone catch missed content, but it may not replace a paid live feedback session. Consider the actual ticket promise and applicable terms when deciding the remedy.

Give unresolved cases an owner before staff sign off. A buyer who reported missing access needs a response even if the conference later ran smoothly. Combine the support record with production evidence, explain the outcome plainly and carry out any agreed remedy. Closing the event room doesn't finish your responsibility for what you sold.

Decide when the whole programme should wait

Agree how much disruption justifies changing the conference schedule. A delayed workshop may continue independently when attendees can still reach their next session. If both tracks require the same closing speaker, however, moving one room can affect everybody. The conference lead needs the current situation in each room before deciding whether to delay that shared session.

Tell moderators what to protect when time runs short. For our training workshop, the worked proposal discussion may be essential while a long introduction is optional. Agree that priority with the speaker beforehand. Cutting the exercise buyers paid to complete while preserving every biography would make the session finish on time at the expense of its value.

Use breaks as planned recovery time only when attendees still receive a usable break. Don't quietly consume the entire interval to accommodate an overrun. If the session needs more time, offer a clearly announced continuation or change the schedule through the agreed process. People in the other track should receive the same current information.

After a material change, check access rules and recordings too. A moved workshop can conflict with a reservation elsewhere, and an automatic recording may end at the original time. Support needs to know which buyers face that conflict and what option you are offering them. Verify the replacement arrangement before telling everyone that the issue is resolved.

Release replays and close the commercial result

Treat replay release as another delivery stage with its own checks. Confirm which sessions were recorded successfully and whether each file contains the intended audio, slides and discussion. Check the session names against the programme. With parallel tracks, files can easily receive the wrong label, leaving buyers looking for material that appears to be missing.

Verify permissions before distributing anything beyond the agreed audience. The US Copyright Office's Copyright Basics explains that copyright can control reproduction and distribution. Keep your speaker agreements specific about paid replays, transcripts, edited clips and later promotion. Permission to appear live doesn't establish that every slide, recording or audience contribution can be reused commercially.

Review captions before release. The W3C's captions guidance explains that automatic captions need accuracy checks and often editing. Give particular attention to speaker names, specialist terms and figures that change the meaning of the example. Check playback with captions enabled, and confirm that the promised materials remain accessible alongside the recording.

Send buyers a clear library guide with the access deadline and any missing sessions explained. Then reconcile actual ticket revenue, sponsor income, refunds and delivery costs, including staff follow-up hours. Review session attendance using verified conferencing evidence, separately from bookings. Ask whether the tracks justified their extra costs and whether reserved workshops delivered what buyers expected.

Ask feedback respondents which track they used and whether they changed rooms. That context helps you distinguish a confusing timetable from a weak session. Keep unanswered support complaints in the review even when the buyer doesn't complete your feedback form.

Before opening sales again, decide which changes the next edition requires. You may keep both tracks, repeat an oversubscribed workshop or simplify the programme so fewer rooms operate together. Base that choice on buyer experience and the commercial result. Update the delivery plan while your team still remembers what happened, then price the conference you can reliably run.