There is no single British Standard that certifies an indoor navigation system as accurate, accessible and safe. A UK venue normally needs to consider several separate layers: inclusive access to the building, fire and safety signing, accessibility of the digital interface, the structure of indoor map data, and the measured performance of the positioning system. Treating one standard as a complete approval route creates false confidence.
Separate the physical environment from the digital service
The BS 8300 series is relevant to inclusive built environments. BS 8300-2 covers buildings, while BS 8300-1 addresses external environments and approaches. These standards can inform entrances, circulation routes, information, facilities and the usability of the physical environment. They do not certify the accuracy of Bluetooth, Wi-Fi or UWB positioning, and they do not replace testing with disabled users.
Fire and escape-route information is a separate safety layer. The BS 5499 series includes guidance on safety signs and escape-route signing. A digital route must not contradict approved fire signage, direct ordinary visitors through restricted emergency exits or obscure the venue's established evacuation arrangements. The fire strategy and responsible person's instructions take priority over a convenience route generated by an app.
The digital interface has its own accessibility requirements. WCAG 2.2 is the main technical reference for accessible web content, but compliance with a checklist is not the same as a usable indoor journey. Screen-reader labels, contrast and keyboard access matter; so do route timing, landmark wording, lift outages, changing noise levels and the availability of a human or physical fallback.
Use an indoor data model only when interoperability requires it
Indoor map standards are not interchangeable with building-access standards. OGC IndoorGML is specifically designed to represent indoor spaces and navigation networks. It can help when a project needs interoperable topology, connections between spaces or exchange between mapping and routing systems. Many smaller venues can operate with a simpler documented graph and do not need to implement a formal exchange standard.
ISO 20524-1 is sometimes cited in navigation discussions, but it concerns Geographic Data Files for intelligent transport systems and should not be presented as a general British indoor-navigation standard. Procurement documents should name the exact standard, edition and clause that applies, rather than using a broad phrase such as “ISO-compliant mapping”.
For radio performance, the controlling evidence is still the measured venue. No standard can establish that a beacon at a particular height and power setting will produce a dependable zone in a corridor filled with people, metal and changing displays. The acceptance plan should define test points, representative devices, route failures, accessible alternatives and re-test conditions after layout changes.
Turn standards into procurement evidence
- Ask what is being claimed. Is the supplier claiming conformance of the website, the building design, the map-data format, the signage or the positioning performance? These are different claims.
- Confirm the current edition. Standards are revised and withdrawn. Record the title, part, year and licensing route used for the project.
- Map each requirement to evidence. Request an accessibility test, route audit, fire-strategy review, map-schema sample or measured positioning report as appropriate.
- Do not accept a logo as proof. A supplier statement should identify the tested component, method, date, device set and limitations.
- Keep fallbacks independent. Static signs, staffed help and accessible route information should remain usable when the positioning service or visitor device fails.
Build a traceable evidence matrix
A useful procurement schedule names the requirement, the reference used, the evidence expected and the owner who accepts it. For example, inclusive circulation may be reviewed against the relevant BS 8300 part and an access audit; escape-route information against the approved fire strategy and relevant BS 5499 guidance; the web or app against WCAG 2.2 and assistive-technology testing; indoor topology against the project’s chosen map schema; and radio performance against a measured pilot.
This approach prevents a supplier from claiming broad “standards compliance” when only one component has been reviewed. It also exposes gaps early. A technically accessible app cannot repair an inaccessible physical route, and an accurate position estimate cannot make an unsafe or unavailable route acceptable. Each layer needs its own evidence, fallback and named decision-maker.
A defensible UK indoor-navigation specification therefore combines applicable building and signage guidance, accessible digital design, an appropriate map-data model and a site-specific acceptance test. Standards provide a common language; they do not remove the need for engineering judgement, user testing or operational ownership.
Before sign-off, record who verified each layer and when the evidence must be reviewed again. A version-controlled matrix is more useful than a general compliance statement because it lets the venue trace a route decision, map update or supplier claim back to the evidence that supported it.
