User journeys and spatial data requirements
The core purpose of photographing and mapping installed beacons is to create a reliable visual and spatial record that lets someone who was not present during installation find, identify, and maintain each device. This is distinct from as-built documentation, which captures the complete installed system including cabling, power, network connections and integration points. Photographing and mapping focuses specifically on where each beacon sits in physical space and what its immediate surroundings look like.
A beacon map is not a floor plan with dots. It is a referenced record that ties each beacon's identifier — UUID, major and minor values, or a manufacturer-assigned ID — to a specific point in the venue, supported by photographs that show the mounting context. Without this, a maintenance visit to replace a battery or troubleshoot a signal issue becomes a search exercise, particularly in venues with dozens or hundreds of devices.
The relationship between the map and the asset register matters. The asset register holds the device identity, firmware version, battery type and replacement schedule. The map tells you where to find the device that matches that record. Both need to use the same identifier system, or the link breaks the first time a label peels off or a battery cover is removed.
Photographs serve three practical functions. First, they confirm the beacon is where the map says it is. Second, they show the mounting method and any hardware used, which matters when a different team handles battery replacement. Third, they capture the immediate environment — ceiling type, nearby metalwork, shelving, signage — which is directly relevant when diagnosing signal problems later.
Build the map around real movement
Photography Standards
Useful beacon photographs share several characteristics. They show the beacon clearly enough to read any physical label. They include enough surrounding context that a maintainer can orient themselves — a ceiling tile pattern, a wall junction, a fixture. They are taken from a consistent distance and angle, typically straight on or from slightly below for ceiling-mounted units.
Two photographs per beacon are usually sufficient: one close enough to read the label or housing markings, and one wider shot showing the beacon in its spatial context. Avoid photographing only the beacon with no background, as this removes the reference information that makes the image useful on a maintenance visit.
For venues where beacons are mounted at height, a photograph taken during installation with a pole-mounted camera or from a ladder is more useful than one taken later from floor level with a phone zoomed in. The installation team has the access and the context; the maintenance team may not.
Mapping Approaches
The most practical mapping method for most UK deployments is an annotated floor plan. Start with an existing venue plan — a fire exit plan, a CAD drawing, or a simple measured sketch — and overlay beacon positions using a consistent symbol. Number or letter each position and cross-reference it to the beacon identifier and the photograph file names.
For multi-floor venues, each floor needs its own map with a clear floor identifier. Stairwells and lift shafts are common points of confusion; mark which floor's map covers each vertical transition zone.
Coordinate-based mapping using survey tools or laser measures is appropriate for large venues or where the map needs to feed directly into an indoor navigation platform. In most retail, museum and event contexts, the additional precision is not justified by the cost and time, and an annotated floor plan with photograph references provides what maintenance teams actually need.
Use Cases
In retail environments, beacons are often mounted above specific product bays or at entrance points. Photographs here need to capture the bay number or department signage alongside the beacon, because retail layouts change and the photograph may be the only record of what the beacon was positioned to serve.
Museums present a different challenge. Beacons may be mounted near exhibits, on display cases, or on ceiling tracks. The photograph needs to show which exhibit the beacon serves, because exhibit locations change during gallery refreshes. A beacon mapped to "Gallery 3, position 7" is less useful than one mapped to "Gallery 3, near the Roman coin case, east wall."
For events, the mapping and photography exercise has a compressed timeline. Beacons may be installed over one or two days and removed after the event. The map and photographs serve a different purpose here: they verify that the deployment matches the planned layout before the venue opens to attendees, and they provide a record for post-event analysis of which zones had coverage issues.
Warehouses and industrial spaces often have repetitive environments — long aisles, identical racking. Photographs must include aisle numbers, bay markers or other fixed references, because without them, every aisle photograph looks the same.
File Organisation
A consistent file naming convention prevents the map from becoming disconnected from the photographs. A practical approach is to use the beacon identifier as the file name prefix, followed by a descriptor: [BeaconID]_close.jpg and [BeaconID]_context.jpg. Store photographs in a folder structure that mirrors the venue's floor or zone structure, not in a single flat directory.
Validation, versioning and change control
Photographing Without Context
The most frequent error is taking photographs that show only the beacon housing with no surrounding reference. This makes the photograph nearly useless for a maintenance visit. The person holding the phone needs to see enough of the ceiling, wall or fixture to locate the beacon in a space that may look uniform from below.
Failing to Capture Mounting Details
If a beacon is attached with cable ties to a ceiling grid, screwed to a wall bracket, or stuck with adhesive to a glass panel, the photograph should show this. When a different team arrives to replace the battery, they need to know what tools to bring and what mounting method to preserve. A photograph that shows only the beacon face hides this information.
Maps That Drift From Reality
Beacons get moved. A fixture is relocated, a ceiling tile is replaced and the beacon is reattached in a slightly different position, or a device is temporarily removed for testing and put back nearby. If the map is not updated when this happens, it becomes a record of where beacons used to be, not where they are. The map needs a version date and a process for updating it when physical changes occur.
Inconsistent Identifiers
If the asset register uses the manufacturer's MAC address, the map uses a handwritten label number, and the photographs are named with an internal ID, the three records cannot be reliably cross-referenced. Agree on a single identifier system before starting the photography and mapping exercise, and use it consistently across all records.
Privacy in Public Spaces
Photographing in retail stores, museums and event venues means photographing spaces where members of the public may be present. Avoid capturing identifiable images of visitors or staff in beacon photographs. If a photograph inadvertently includes a person, consider whether it needs to be retaken before it is stored in the deployment record. This is a practical operational consideration — consult current UK guidance on privacy and photography in public venues for specific obligations.
Not Photographing at Installation Time
Deferring photography to a later visit is a common planning error. The installation team has the ladder, the access, and the immediate knowledge of which beacon is which. Returning later to photograph means arranging access again, and the context of why each beacon was placed in that specific position may no longer be clear.
Key Checks Before Considering the Map Complete
- Every beacon on the asset register appears on the map and has at least one photograph.
- Every position on the map references a beacon identifier.
- Photograph file names match the identifiers used on the map and in the register.
- The map has a date, a version number, and a clear indication of which floor or zone it covers.
- At least one person who was not involved in the installation can use the map and photographs to locate a specific beacon without additional guidance.
