Indoor Map Software for Stadiums: A Buyer’s Guide for 2026

A stadium is the hardest building a map will ever be asked to work in. Sixty thousand people arrive within ninety minutes, through a steel and concrete shell, and almost all of them want one of five things: their seat, a toilet, food, an accessible route, or the way out. Signage was built for the first of those and handles none of the rest well.

This guide is written for the person who has to buy the software, not the person who writes the press release. Every number below comes from a government or standards source and carries a link to it. Where a number is only available from a vendor, it has been left out.

What is indoor map software for stadiums?

Indoor map software for stadiums is three parts working together: a digital model of the venue, a positioning engine that places a phone inside that model, and a routing engine that produces directions between two points in it. Analytics is a fourth part, built on the first three.

Buyers tend to evaluate the part they can see, which is the map graphic. The parts that decide whether the product survives a second season are the other two. A beautiful bowl rendering with a positioning engine that cannot tell deck two from deck three is worse than a static PDF, because the fan trusts it and then gets it wrong.

Ask which of those four a vendor builds and which they resell. The answer changes who you call at 19:45 on a match night.

Why does outdoor navigation stop working at the gate?

Because satellite positioning needs sky. The United States government’s own figure is that GPS-enabled smartphones are typically accurate to within a 4.9 metre radius under open sky, and that accuracy degrades near buildings, bridges and trees.

A stadium removes the open sky and adds the worst case of all three. Under a cantilevered roof, inside a concourse ringed with steel, the satellite fix either disappears or, worse, snaps to a plausible but wrong point outside the structure.

Then there is the second problem, which is that 4.9 metres would not be good enough even if you got it. A seating row is under a metre deep. Two concourse levels are stacked within ten metres of each other vertically. A circle of error wider than the thing you are trying to identify is not a location, it is a neighbourhood.

How accurate does the blue dot have to be?

Accurate enough to resolve the specific decision the fan is making, which is usually a choice between two nearby options rather than a coordinate. Precision in metres matters less than whether the dot lands on the correct side of a wall, a barrier or a deck.

The regulator has already done this arithmetic for a harder case. The Federal Communications Commission, in its 2015 Fourth Report and Order on indoor location accuracy benchmarks, set the vertical target for wireless 911 calls at plus or minus 3 metres, on the reasoning that this is roughly the height of a storey. Emergency responders need to know the floor. In a stadium, the floors are decks, and a dot on the wrong deck sends a family a full lap around the concourse in the wrong direction.

Vendor accuracy claims are difficult to compare because the test conditions behind them are rarely published, and a figure measured in an empty venue at 09:00 describes a building that does not exist on a match day. Insist on a live test in your own bowl, at capacity if you can arrange it, with the specific tasks above as the pass criteria.

How do the positioning methods compare?

Each method trades infrastructure you have to own and maintain against the conditions that break it. There is no method that is free of both, and the right choice depends on what already exists in the building.

Two things in that table are worth saying out loud. Crowds are not a footnote: a packed concourse is a wall of water, and water absorbs 2.4 GHz energy, which is why a system calibrated in an empty venue drifts when the venue fills. And access point moves are not rare. Your network team will relocate hardware for reasons that have nothing to do with your map, and if the positioning model is pinned to where the radios used to be, it quietly rots.

The maintenance question is arithmetic you can do yourself before any vendor conversation. Take the number of battery devices a design calls for, divide by the battery life in days, and that is your daily replacement rate forever. Five thousand beacons on an assumed eighteen-month battery is about nine swaps a day, every day, including match days and closed season. Nine a day. Whether that is acceptable depends on whether you already have a crew on site who can absorb it.

When is a beacon deployment still the right answer?

When you need certainty in a small, high-value area on a short timeline, and the venue gives the alternatives nothing to work with. Beacons are unfashionable and sometimes correct.

Three cases where they earn their keep. A premium hospitality floor where room-level certainty drives service, and the device count is in the dozens rather than the thousands. A back-of-house asset problem, where the thing being located is a tagged trolley or a defibrillator rather than a phone, and the tag can carry its own radio. And a brand-new build where cabling and anchors can be specified before the walls close, which makes ultra-wideband dramatically cheaper than retrofitting it later.

The case against beacons is not that they do not work. It is that a bowl-wide deployment hands you a permanent hardware estate with a daily failure rate, in a building that gets repainted, re-sponsored and re-fitted every close season. Anyone who tells you beacons are always wrong is selling you something, and so is anyone who tells you they are always right.

What accessibility law applies to a stadium’s map and app?

Both the building and the app are regulated, and the second one catches venues by surprise. The physical requirements have been settled for years. The digital requirements arrived recently and carry dates that have already passed.

On the physical side, the 2010 ADA Standards for Accessible Design scope wheelchair spaces in assembly areas by capacity. For venues of 5,001 seats and over, the table requires 36 spaces plus one for every additional 200 seats. Run that for a 60,000-seat stadium and you get 311 wheelchair spaces, which the same standard requires to be dispersed horizontally and vertically rather than grouped. Every one of them must sit on an accessible route.

That is a routing requirement disguised as a building code. A map that cannot produce a lift-and-ramp path to 311 dispersed locations is not describing your stadium.

On the digital side, the Department of Justice final rule on web and mobile app accessibility under ADA Title II adopted WCAG 2.1 Level AA, a W3C Recommendation published on 5 June 2018, as the technical standard for public entities. Compliance was due on 24 April 2026 for public entities serving a population of 50,000 or more, and is due on 26 April 2027 for smaller entities and special district governments. The first date has passed. If your stadium is owned by a city, a county, a transit authority or a public university, that rule reaches your venue app, including its map screens.

In the European Union, the European Accessibility Act brought consumer-facing e-commerce and ticketing services into scope from 28 June 2025.

What does Martyn’s Law require of a venue in the UK?

The Terrorism (Protection of Premises) Act 2025 requires qualifying premises to have public protection procedures covering evacuation, moving people to safety inside the building, lockdown, and communication with the people on site. The Act sets tiers by how many people may be present, and a stadium falls in the higher one.

The exact tier thresholds and the length of the implementation period are set by the Act and its guidance, and they are a question for your own legal team rather than a software vendor. What matters for this article is the shape of the duty rather than its numbers.

The connection to map software is the communication duty. A procedure that says “direct patrons to the nearest available exit” is a sentence until something can work out, per person, which exit that is. Software that already knows where a phone is and which routes are open is the mechanism, not the compliance. Do not let a vendor tell you a map makes you compliant with any of the four rows above. It does not. It makes some of them achievable.

What privacy rules cover location analytics on fans?

Indoor location data about identifiable people is regulated personal data in most of the markets a large venue sells tickets in, and the regulation attaches at a far coarser resolution than a stadium map operates at.

California is the clearest illustration. Under the California Civil Code definitions used by the CCPA, precise geolocation means data used to locate a consumer within a circle of radius 1,850 feet or less, and precise geolocation is treated as sensitive personal information. That radius is about 564 metres. Any indoor positioning worth deploying is two orders of magnitude inside it, so the question is never whether your analytics touches sensitive data. It does.

In Europe, the General Data Protection Regulation governs the processing, and Article 5(3) of the ePrivacy Directive governs access to information stored on the fan’s own device, which is a separate consent question from the one your ticketing terms cover.

Three practical consequences. Aggregate zone counts and individual traces are different products with different legal weight, so ask which one the analytics is built on. Consent for navigation is not consent for sponsorship measurement. And the answer to “who owns the data” should be your venue, in the contract, in writing.

What should the map be judged on after the first season?

On measurements you took before it went live, against the same measurements afterwards. Most of the revenue claims attached to indoor navigation cannot be audited, so the only credible number is one from your own venue.

Published, independently verifiable figures for per-capita spend uplift caused specifically by indoor wayfinding are scarce, and the ones circulating in vendor material usually have no methodology attached. Treat any number offered to you in a sales deck as a hypothesis about your building.

Four baselines are cheap to capture and worth having. Guest services contacts per thousand attendees, split by reason, because “where is section 304” is the one a map should delete. Median time from gate scan to first seat scan. Concession queue abandonment at the two stands your staff already know are badly signed. And the count of accessibility complaints per fixture, which is both a service measure and a legal exposure measure.

Capture those for three fixtures before launch. Without that, you will be arguing about whether the software worked using numbers that only exist after it was installed.

Which questions separate the vendors?

The questions about the second year, not the first. Any vendor can demonstrate a map; the differences show up in who maintains it after a renovation and what happens when the network changes underneath it.

Two more that do not fit in a table. Ask for the positioning engine’s behaviour at capacity, measured in your venue rather than described. And ask what the product does when positioning fails completely, because it will, and a map that degrades into clear static directions is a better product than one that shows a confident dot in the wrong place.

Bring your seating manifest, your floor plans and the three questions guest services answers most often. Book a scoping call and we will go through the bowl deck by deck, and say plainly which parts of this list your venue already clears and which would need work.

Frequently asked questions

Five questions that come up in nearly every stadium map evaluation.

Does indoor map software need its own app?

No, though an app gives the positioning engine more to work with. A mobile web map can show the venue, points of interest and static routes without any install, which suits one-off visitors. Continuous blue dot positioning generally needs the sensor and radio access that a native app has, so many venues publish both and accept that the web version offers less.

How often does the map data have to be updated?

At minimum, every time the venue physically changes, which for most stadiums means each close season plus any mid-season fit-out. Concession operators rotate, sponsors rename zones, and temporary structures appear for non-sport events. Agree the update route and its turnaround in the contract rather than the sales call, because stale map data is the most common reason fans stop trusting a venue app.

Does an indoor map make our venue ADA compliant?

No. Accessibility obligations sit on the building and on the digital service separately. The 2010 ADA Standards govern wheelchair spaces, dispersal and accessible routes in the physical venue, and the ADA Title II web rule applies WCAG 2.1 Level AA to apps and websites of covered public entities. A map can help you deliver accessible routing and must itself meet WCAG, but neither substitutes for the other.

Can the same system cover the car parks?

Usually yes, by handing off between satellite positioning outdoors and the indoor engine at the threshold. The handover is the part to test, because it happens exactly where a fan is most likely to give up and ask a steward. Walk the route from a parking bay to a seat during evaluation, and watch what the dot does in the gate tunnel.

What is the realistic deployment timeline?

For an existing stadium, plan in months rather than weeks, with the length driven by map data quality rather than software. If you hold accurate current floor plans and a clean seating manifest, the work is survey, calibration and testing. If your plans predate the last two refurbishments, the first phase is a drawing exercise, and that is the schedule risk worth naming early.