Hotel WiFi: the guest-experience math no one runs

A hotel usually shops guest WiFi as a bandwidth line: how many megabits for the building, what the circuit costs, sign here. That framing hides where the money and the reviews actually move. In the J.D. Power 2025 North America Hotel Guest Satisfaction Index Study, connectivity is one of seven scored dimensions, and a single problem during a stay drops guest satisfaction 217 points, to 460 from 677 on a 1,000-point scale. WiFi that crawls at 8 p.m. is exactly that kind of problem. The question is not how big the pipe is. It is whether the guest in room 412 can get on and stay on.

Slow hotel WiFi is almost always a coverage problem, not a bandwidth problem

When guests say the WiFi is slow, the internet circuit almost always has headroom to spare. The bottleneck is the radio layer inside the building: too few access points, or access points fighting concrete floors, tile bathrooms, and mirror-backed walls that eat signal. In the last several hospitality reviews we ran, the property angriest about its WiFi had the most bandwidth per room on paper and the worst coverage in the guest towers. Buying a fatter circuit to fix that spends real money on the layer nobody was complaining about. The circuit is a monthly line you upsize with a phone call. The access-point count and cabling is capital you scope once, usually at renovation, and live with for years.

Size the guest network to occupied-room concurrency at peak, not to the building

The math no one runs is per-occupied-room concurrency, and it takes four inputs: occupied rooms at peak, devices per room, the share of those devices active at once in the evening, and a per-device throughput floor you promise to hold. Run that product, add a margin for meeting and public space, and you get a circuit that maps to what guests feel instead of a round number that looks safe on a proposal. A property that sizes to a headline building figure tends to overbuy the circuit and underbuild the access-point layer. The formula matters at renewal because it tells you which line to cut and which to protect: trim the oversized circuit, keep the access-point density.

That is where a buyer-side advisor earns the engagement. Buyer-side. Supplier-paid. Buyers pay zero. Compensation has zero weight in the Cardinal Index scoring. We size the network to your occupancy curve, price the circuit and the in-room layer as the two separate decisions they are, and read the managed-WiFi contract for the clause that usually gets missed: who owns the access points and cabling when the term ends. A bundled package can be the right answer when it takes capital and support headaches off your plate, and the wrong one when it names an aggregate circuit number, stays silent on per-device throughput, and hands the hardware back on the way out.

You cannot design the guest network to force people onto paid WiFi

Federal law bars a hotel from blocking guests' personal hotspots, including as a way to push them onto the paid network. The FCC's Enforcement Bureau put this in writing: intentional interference with personal Wi-Fi hot spots violates Section 333 of the Communications Act, and Marriott paid a $600,000 civil penalty after deploying a deauthentication protocol at a convention property to do exactly that. The advisory calls Wi-Fi "an essential on-ramp to the Internet." For a buyer, this is not trivia. Many managed-WiFi platforms ship with containment or rogue-suppression features that can deauthenticate nearby devices. That capability is a control you leave off on purpose and confirm in the contract, not a default you inherit.

Guest WiFi has to be walled off from the systems that touch card data

A hotel that runs cards has a cardholder data environment, and PCI DSS treats the guest wireless network as untrusted by default. The guest VLAN has to be isolated from the property-management and point-of-sale systems, with no routing between it and the network where card data lives. Do it well and you shrink your PCI scope, because a properly segmented guest network stays out of the assessment. Seamless authentication earns its place here: the Wi-Fi Alliance's Passpoint standard lets returning and loyalty guests connect automatically with WPA3 security instead of a captive portal, improving the experience without collapsing the wall between guest traffic and the systems you protect.

What to put in the RFP

Turn the above into six lines a vendor has to answer in writing before you sign:

• Throughput SLA per device, not an aggregate circuit number. Hold the vendor to what a single guest gets at peak.
• Access-point density target for guest floors, stated as a ratio and validated against your building materials, not a coverage promise.
• VLAN segmentation of guest traffic from the PMS and POS, with no inter-VLAN routing, so the guest network stays out of PCI scope.
• Seamless authentication such as Passpoint for returning and loyalty guests, with WPA3.
• No hotspot blocking. Confirm in writing that containment and deauthentication features are disabled, per FCC Section 333.
• Hardware ownership at term end. Name who keeps the access points and cabling when the contract closes.

This is the kind of scoping the Cardinal Method is built to run: separate the decisions the vendor has bundled, size the network to your own occupancy data, and hold the contract to the controls that regulators and card networks already require. Slow WiFi and a fat bill usually come from the same mistake, which is buying bandwidth to solve a problem that lives in the walls.