What event guest WiFi is for
Guest WiFi is a courtesy, and a busy one. At a conference it lets delegates read the agenda and answer email; at a gala it carries photos to social media; at a festival it might be the only usable connection once mobile networks congest. It's also the network most likely to be overloaded, the one with the least trusted devices on it, and the one whose password ends up everywhere.
So the design goal has two sides. Guest WiFi should be easy to find, easy to join and fast enough for what guests actually do. And it should have no way to affect anything else: not the stream, not the payment terminals, not staff laptops. Every practice below serves one of those two goals, and they're the same two goals behind our event guest WiFi setups.
Choosing the event WiFi name
The name is the first thing guests see, so it should be impossible to get wrong.
Match the event
Use the event or brand name guests will recognise, so they don't pick the venue's network or a neighbour's by mistake.
Keep it short
Short names are easier to spot in a long list, and easier to type on the occasional device that needs it typed.
One guest name only
A single guest network name across every access point lets phones move between them without rejoining.
Keep other networks out of the way
Staff, payment and camera networks shouldn't look like guest options or carry names that describe what they carry.
Avoid confusing characters
Leave out symbols, accents and look-alike characters such as a capital I and a lower-case l.
Open WiFi, password or sign-in page: the trade-offs
Three common ways to let guests on, and what each one means in practice.
| Approach | Joining | Protection over the air | Watch out for |
|---|---|---|---|
| Open network, no password | Easiest | Often unencrypted between device and access point | Anyone nearby can join, including people outside the event |
| Shared password on signage | Easy, one step | Encrypted over the air, with everyone sharing the password | The password spreads, so treat it as public |
| Sign-in page before access | An extra step some devices handle badly | Depends on the network behind it | Sessions that expire, plus privacy and Spam Act obligations if details are collected |
Whichever approach you choose, guest isolation and a separate guest network do the real protective work.
Per-device limits keep guest WiFi fair
Without limits, one guest uploading a phone's photo library or streaming video in high definition can take a share of the connection meant for dozens. A per-device limit caps each guest device's speed so the network stays usable for everyone. Guests browsing, messaging and posting photos won't notice it; the guest backing up a laptop will, and that's the point.
Do the arithmetic for the guest network as a whole. Three hundred guests at about one device each, using around 0.5 Mbps when active, need 300 × 0.5 = 150 Mbps at the busiest moment. Give the guest network that share of the connection, cap each device at a sensible multiple of everyday use, and leave the rest for staff, the stream and payments. Access points follow the same count: 300 devices ÷ about 50 per access point = 6.
Guest WiFi signage checklist
Most guest WiFi complaints are really signage problems.
- WiFi name and password in large, plain type, identical on every sign
- Signs at the entry, registration, bars, seating areas and on screens between sessions
- A QR code that joins the network, beside the typed details for anyone who prefers them
- The password on lanyards, table cards or the event app if you have one
- No staff, payment or camera network details on any sign or handout
- A line telling guests where to go if they can't connect
- Type and contrast readable from a few metres away, and in low light for evening events
Setting up event guest WiFi
Five steps, done before the first guest arrives.
Put guests on their own network
Guest WiFi gets its own VLAN, with no route to staff, payment or camera networks; see separate WiFi networks for events.
Turn on guest isolation
Guest devices can reach the internet but not each other, which stops casual snooping and device-to-device problems.
Set the guest share and per-device limits
Cap the guest network's share of the connection and each device's speed, protecting staff, streams and payments.
Size the access points for guests
Plan about one device per public attendee and about 50 devices per access point, placed where guests gather.
Test as a guest
Join from a phone using only the signage, and time how long it takes from reading the sign to loading a page.
Common event guest WiFi mistakes
Each of these turns up regularly, and each is easy to avoid with a little planning.
Guests and staff on one network
The most common and most damaging. A crowded guest network then slows staff, and guests can see devices they shouldn't. Event WiFi security covers the risks.
A name close to the venue's own network
Two networks with similar names split guests between them and send some to whichever is struggling.
Changing the password mid-event
Every device already joined drops off at once and the signage becomes wrong. Change it after the event instead.
No per-device limit
A handful of heavy users can take the share meant for everyone else, usually at the busiest moment.
Too few access points where guests gather
Bars, foyers and seating areas concentrate phones. How many access points you need shows how to count them.
Questions people ask
What should I name my event WiFi?
Name event WiFi after the event or brand guests will recognise, keep it short, and use one guest name across every access point. Avoid names close to the venue's own network, symbols and look-alike characters. Give staff, payment and camera networks names that don't look like guest options or describe what they carry.
Should event WiFi have a password?
A password shown on signage is usually a sensible middle ground: easy for guests to join, encrypted over the air, and it keeps passers-by off. Treat it as public once printed. An open network is the easiest to join but often unencrypted over the air. Either way, guest isolation and a separate guest network do the real protecting.
Is public WiFi at events safe?
Public WiFi at events is as safe as its design. A guest network on its own VLAN, with guest isolation turned on and no route to staff, payment or camera networks, limits what anyone on it can reach. Guests should still use apps and websites that encrypt their connections, and organisers should never put payments or staff systems on the guest network.
How do I stop guests using all the event bandwidth?
Set a share of the connection for the guest network and a per-device speed limit at the router. Guests browsing and messaging won't notice, but a few heavy users can no longer crowd out everyone else. Staff, streams and payments sit on their own networks with their own share, so a busy guest network can't slow them down.
Can I collect email addresses through event WiFi?
You can ask for them, but if you plan to send marketing, Australia's Spam Act rules apply: consent, identifying yourself and offering an unsubscribe. Make marketing consent a clear, separate choice rather than assuming a WiFi sign-in implies it. The ACMA's guidance on avoiding spam explains the requirements, and it's worth getting advice if you're unsure.
Where should I put the WiFi password at an event?
Put the WiFi name and password where guests look first: the entry, registration desk, bars, seating areas and screens between sessions, plus lanyards or table cards if you use them. A QR code beside the typed details speeds things up. Keep staff and payment network details off every sign and handout.
Sources
Planning figures on this page are starting points. Every network is confirmed against the actual site.
