Almost every city has one: a splashy announcement about free Wi-Fi downtown, a coverage map with a pleasing blue blob, a ribbon cutting. Then the quiet part arrives. The map never updates. The kiosk with the burnt-out screen sits behind the bus shelter. Nobody in the finance office remembers which line item pays for the backhaul.

Public Wi-Fi fails for boring reasons far more often than technical ones. The radios usually work. The planning around them does not. Here are the mistakes that show up again and again in municipal deployments, and what to do instead.

1. Calling it coverage when you mean a signal at three feet

Vendors quote coverage under ideal conditions: clear line of sight, no walls, no foliage, a handful of connected devices. Real streets have brick, tree canopy that vanishes in February and returns in June, idling buses, and a hundred phones in one park during a festival.

Before you promise anything, define what covered means in measurable terms. Something like: at least 10 Mbps down at a park bench on a busy Saturday, with 30 devices connected at once. Then test for it. Walk the routes with a laptop and a phone. Test at noon and again at 8 p.m. Test in winter, then test again after the trees leaf out. Keep the public map current, even when that means admitting to a gap.

2. Funding the build and hoping maintenance pays for itself

Capital budgets are exciting. Operating budgets are where projects die. A radio on a pole is not a one-time purchase; it is a small ongoing commitment with a known expiry date.

• Electricity and pole-attachment or meter fees
• Backhaul circuits, often the largest recurring cost
• Firmware updates and the eventual end-of-life replacement of every access point
• Spare parts, ladders, and the crew that climbs them
• Help desk capacity and a named owner inside the city
• Insurance, permits, and renewal of any lease agreements

Put the five-year operating figure in the same document as the construction figure, and make sure council sees both. If the project only works with one-time grant money, it will fail on schedule.

3. Publishing a privacy notice people cannot use

Public Wi-Fi is public infrastructure, and public infrastructure collects data whether you intend it to or not. Captive portals see device identifiers. Logs may hold timestamps and locations. Analytics vendors usually want more.

Collect only what you need to run the network. Hash or salt identifiers where possible, set a short retention period, and write the whole thing down in plain language. Put that notice on the splash page, not three clicks deep in the city website's legal section. Say who can see the data, how long you keep it, and how a resident can ask a question.

Two traps to avoid

First, do not require an email address or social login for basic access. A guest option removes friction and reduces the data you hold. Second, think hard about SMS one-time codes. If the network is aimed partly at people who may not have a mobile plan, an SMS gate locks out the exact residents you are trying to reach.

Privacy rules vary by jurisdiction and by what you log, so run your notice and retention plan past your city attorney or privacy counsel before launch.

4. Treating Wi-Fi as a digital divide program by itself

Connectivity is one layer of a stack. A hotspot does not help a household with no working laptop, no quiet place to use one, or nobody to help fill out an online benefits application. It does not help someone who needs to upload documents at 11 p.m. from home.

If closing gaps is the goal, pair the network with the other layers:

• Device lending through libraries and community organizations
• Digital navigator staff who sit with people and help finish a task
• Hours and locations that match real life, including evenings and weekends
• Materials and support in the languages people actually speak
• Some privacy for tasks involving personal documents or money

Measure what you actually care about, such as completed applications or job searches, not just the count of devices that connected.

5. Covering the neighborhoods that already have five bars

It is easier to install equipment where the fiber already runs, where political attention lives, and where the photo opportunity looks good. That usually means downtown plazas and tourist corridors. Meanwhile the apartment blocks on the edge of town, where need is highest, wait another budget cycle.

Be deliberate about site selection and be able to defend it. Rank candidate locations by need and foot traffic, not by convenience of installation. If a well-off district gets coverage first because the conduit is already there, say so publicly and publish the schedule for the rest.

6. Launching without metrics, feedback, or an exit plan

Vanity numbers are easy to produce and hard to learn from. Sessions and unique users tell you very little about whether the network is doing anything useful.

Track a smaller set of honest measures: peak concurrent devices, repeat usage by location, average throughput at busy times, help desk tickets per month, and a short resident survey once a year. Publish a one-page update quarterly, failures included.

Then decide in advance what would cause you to expand, repair, or shut down a site. A network nobody uses is not a neutral outcome. It is a recurring cost with a maintenance backlog attached.

A practical starting order

Start with the job, not the hardware. Write down what the network is for, who it serves, and what success looks like in a number you can measure.

1. Define the service level and test for it in real conditions.
2. Budget operations and replacement for at least five years.
3. Draft the privacy notice early, keep it short, and have counsel review it.
4. Pair connectivity with devices, staff, and usable hours.
5. Choose sites by need, and explain the choices publicly.
6. Publish regular, unflattering performance data.

None of that requires exotic technology. It requires treating public Wi-Fi as a service with a lifespan, a budget line, and residents on the other end. Cities that do end up with fewer dead kiosks and more people who can actually get online.

Photo: Antoni Shkraba / Pexels