Your Event Wi-Fi Is Not a Production Network

There is a dangerous moment at almost every large event: the venue is quiet, the crew is setting up, and the internet appears to be perfect.

Registration terminals are online. The production team is downloading last-minute presentations. The stream is stable. Somebody runs a speed test and gets a number everyone is happy with.

Then the doors open.

A few hundred or a few thousand additional phones arrive in the building and the network you tested at 8am is suddenly operating in a completely different environment.

A speed test isn't a network test

The number people tend to focus on is bandwidth. It matters, but it isn't the whole story. An event network also has to deal with congestion, access-point capacity, interference, roaming devices and hundreds of people trying to connect at roughly the same time.

A 500 Mbps internet connection can still provide a terrible experience if the wireless network between the delegates and that connection is badly designed.

This matters even more when operational systems share the same infrastructure as guests.

Check-in, badge printing, payment terminals, production laptops and livestream encoders should not be depending on the same public Wi-Fi that attendees are using to upload video from the keynote.

Separate production from convenience

Wherever possible, give critical event systems their own network.

For a livestream encoder, a wired connection is still preferable. For registration desks, wired connections or a dedicated operational wireless network remove a large and unnecessary variable.

Guest Wi-Fi can then do what guest Wi-Fi is supposed to do: provide internet access for attendees without also carrying the systems required to operate the event.

Ask the venue what is actually being supplied. "Wi-Fi included" tells you very little.

Useful questions include how many access points cover the event space, whether you can have dedicated SSIDs or VLANs, whether wired connections are available at registration and production positions, whether bandwidth is dedicated or shared, and what support is available during the event.

Have another route out

A backup only counts if it fails differently from the primary connection.

Two cables connected to the same venue switch are not much of a backup. Neither are two services that ultimately use the same building connection.

For important broadcasts, consider a secondary circuit or cellular connectivity from more than one network. The exact solution depends on the consequence of failure, but the principle is simple: don't discover your backup has the same point of failure while you're already off air.

Test when the building is busy

An empty venue is useful for checking configuration. It is a poor simulation of an event.

If the venue hosts regular events, ask what happens to wireless performance at full occupancy. For especially important shows, ask for network monitoring during the event rather than waiting for users to report that something feels slow.

And decide in advance what happens if connectivity disappears completely.

Can registration continue temporarily offline? Are essential lists available locally? Can video be recorded locally if a stream drops? Is there a phone number for the network engineer rather than a generic venue helpdesk?

Internet connectivity has become infrastructure in much the same way as power. Treating it as a convenience until something goes wrong is an increasingly expensive mistake.

The best event network is usually the one nobody notices. That takes rather more planning than running a speed test on setup day.