How to use this hybrid event checklist
This checklist is grouped by area rather than by date, because hybrid events tend to fail in one area at a time: the upload runs short, the audio is muddy, the backup was never tested, or nobody knew who should make the call. Work through each group with the people responsible for it, and tick an item only once it has been tested, not just discussed.
It assumes a typical split of work. The venue supplies the room and often the internet line, a production or AV team runs cameras, the encoder and the streaming platform, and a network provider handles the connection, the separate networks and the backup. At EventWiFi our part is the network, described on our hybrid event internet page; lighting and sound can be delivered by partner AV specialists, coordinated by us with the network.
Hybrid event checklist: connection and upload
The connection is the slowest thing to change, so it comes first.
- The venue has confirmed its upload figure in writing, and whether other rooms or tenants share the line
- Upload needed is calculated: 10–20 Mbps per stream plus about 1.5 Mbps per remote presenter
- Headroom is included, at roughly 1.5–2× the stream bitrate
- Upload has been tested at the stream position, not in the venue office
- If a new service is needed, it's ordered; activation can take from a couple of business days to several weeks
- The venue allows outside network equipment, or its in-house supplier has agreed to what you need
- Guest WiFi is limited so it can't take the stream's share of the connection
- Recording uploads after sessions are planned separately from the live stream
Worked example: upload for a two-stream hybrid event
A conference streams its main room and one breakout, with three remote presenters joining by video call. Using the top of each range gives the planning figure.
| What's sending | Calculation | Upload to plan for |
|---|---|---|
| Main room stream, encoder set to 10 Mbps | 10 × 1.5 to 10 × 2 | 15–20 Mbps |
| Breakout room stream | Planning range per stream | 10–20 Mbps |
| Three remote presenters on a video call | 3 × 1.5 Mbps | 4.5 Mbps |
| In-room audience uploads | Photos, messages, cloud sync | Small, kept within the guest network's share |
| Session recordings sent after each block | File size ÷ time available | Planned separately; often larger than the live streams |
| Live-session planning total | 20 + 20 + 4.5 | About 45 Mbps of steady upload |
Steady means for the whole session, measured at the stream position, not one good result on a speed test. The guide to upload speed for live streaming covers stream settings in more depth.
Hybrid event checklist: encoder and network path
The encoder turns cameras and audio into the stream. Its path to the internet should be the most protected route on the site.
- The encoder connects by cable, not WiFi
- That cable goes to a production network separate from guest and staff WiFi
- The encoder position is marked on the floor plan, with power and a protected cable route
- Remote presenter and production control laptops are on the production network, cabled where possible
- The venue network doesn't block the services the streaming platform uses (test from the actual port)
- The stream has been sent to the real platform from that port, not just a speed-test site
- A spare cable and a spare switch port are ready at the production desk
Hybrid event checklist: audio for the remote audience
Remote viewers will put up with a soft picture far longer than poor sound, and most hybrid audio problems are planning problems.
- The stream takes its audio from the sound desk, not a camera microphone
- There's a separate stream mix if the room mix doesn't suit headphones
- Remote presenters hear the room without hearing themselves echoed back
- The room hears remote presenters clearly through the PA
- Audience questions are picked up by a microphone, not repeated from memory
- Levels have been checked by someone listening remotely on headphones
- Spare batteries for radio microphones are at the desk
- If lighting and sound need supplying, they're booked; see event lighting and sound
Hybrid event checklist: backup and failure plan
A backup only counts if it has been tested at the venue and everyone knows what happens when it's used. Our backup internet page explains the options.
- A second connection, often a 4G/5G router, is connected to a router that can switch to it
- Switchover has been tested by disconnecting the main line during rehearsal
- The team knows the stream may drop briefly during switchover, and how the encoder reconnects
- A lower stream bitrate is ready for the backup, since mobile upload is limited and site-dependent
- The session is also recorded locally, so a copy exists whatever the internet does
- A holding slide or message is ready for the remote audience
- One person is named to decide when to switch, pause or carry on
- Contact numbers for the venue, network and production leads are printed at the desk
Rehearsal: run the whole hybrid chain once
A rehearsal is the only test that covers everything at once. Plan it like a real session.
Book it at the same time of day
A building's shared line can be quiet in the evening and busy mid-morning. Rehearse at the hour you'll go live, on the event day or as close to it as the venue allows.
Stream to the real destination
Use a private or unlisted event on the actual platform, with someone watching from outside the venue.
Bring in a remote presenter
Have them join from where they'll really be, on the device they'll really use, and check they can hear the room and the room can hear them.
Pull the main connection
Disconnect the main line on purpose and watch what the stream, the encoder and the remote viewer see. Then reconnect.
Load the guest network
If you can, rehearse with staff or early attendees on the guest WiFi, so the production network is tested while something else is busy.
Confirm cues and calls
Walk through who says 'go', who handles the chat and who decides what happens when something fails.
Hybrid event roles: who does what on the day
Small hybrid events combine some of these roles and large ones split them further. What matters is that each has a name next to it.
| Role | Responsible for | Needs on the day |
|---|---|---|
| Event lead | Final decisions: hold, switch to backup, carry on | A view of the live stream and contact with every other role |
| Stream producer or operator | Encoder, platform, cameras, and starting and stopping the stream | A cabled production position and a screen showing the live output |
| Audio engineer | Room mix, stream mix and remote presenter audio | Headphones on the stream feed, not only the room speakers |
| Network contact | Connection, separate networks, backup and switchover | Access to the network equipment, and the support level agreed in the plan |
| Remote presenter host | Getting remote speakers connected, checked and on cue | A laptop on the production network and every presenter's contact details |
| Chat and Q&A moderator | The remote audience: questions, problems and links | A device on the staff WiFi and a way to pass questions to the stage |
| Venue contact | Rooms, power, access and the venue's own network | A phone number that answers during the event |
Write the names into the run sheet. An unassigned role becomes nobody's job at the worst possible moment.
Questions people ask
What do you need for a hybrid event?
A hybrid event needs an internet connection with enough steady upload, a production network separate from guest WiFi, a wired encoder, clean audio from the sound desk, a way for remote presenters to join and be heard, a tested backup connection, a full rehearsal and named people for each technical role. The connection and upload take longest to arrange.
How much upload speed does a hybrid event need?
Plan 10–20 Mbps of steady upload for each live stream, with headroom of roughly 1.5–2× the stream bitrate, plus about 1.5 Mbps for each remote presenter on a video call. Two streams and three remote presenters come to about 45 Mbps at the top of each range. Measure upload at the stream position.
What happens if the internet drops during a hybrid event?
If the internet drops during a hybrid event, the stream stops for remote viewers while the room carries on. A router with a tested backup connection can switch over, usually after a short interruption, and the encoder reconnects. A local recording keeps a full copy, and a holding message tells remote viewers what's happening while the team recovers.
When should you rehearse a hybrid event?
Rehearse a hybrid event at the venue, at the same time of day as the live sessions, on the event day or as close to it as the venue allows. Stream privately to the real platform, bring in a remote presenter, check audio on headphones, and disconnect the main line once to test the backup.
Who is responsible for the internet at a hybrid event?
Responsibility for hybrid event internet is usually shared. The venue supplies or approves the line, a network provider sets up the connection, separate networks and backup, and the production team runs the encoder and platform. Put a name against each part in the run sheet, so it's clear who acts when something goes wrong.
What are the most common hybrid event tech mistakes?
Common hybrid event tech mistakes are checking the venue's download speed but not its upload, running the encoder over guest WiFi, taking stream audio from a camera microphone, relying on a backup connection that was never tested, rehearsing at a quieter time of day than the event, and leaving nobody clearly in charge of deciding what to do when something fails.
Sources
Planning figures on this page are starting points. Every network is confirmed against the actual site.
