Establish the baseline and success evidence
Proximity technology projects sit at the intersection of physical infrastructure, radio frequency (RF) physics, privacy law and operational logistics. A common error is treating a beacon or indoor navigation deployment as a standard IT networking task. While network connectivity is required for backend systems, the skills needed to make proximity technology reliable in a real-world venue are quite different from those used to manage Wi-Fi access points or servers.
The required competencies fall into four distinct areas, rarely found in a single person.
RF and Spatial Understanding
Someone on the project team needs a practical grasp of how Bluetooth Low Energy (BLE) signals behave in physical spaces. This means understanding that Received Signal Strength Indicator (RSSI) values fluctuate based on human bodies, metal racking, glass partitions and stock movement. The skill here is not theoretical physics, but the ability to read an RSSI scatter plot, recognise multipath interference, and translate a marketing zone requirement—such as "trigger when a visitor is near the entrance"—into a viable physical placement and calibration plan.
Hardware Operations and Inventory Management
Proximity hardware is dispersed, battery-powered and often hidden from plain sight. The project requires skills in physical asset tracking: labelling beacons or NFC tags logically, maintaining an asset register that maps hardware IDs to physical locations, and monitoring battery life based on advertising intervals and transmit power settings. When a beacon goes offline, the team needs the operational discipline to locate it, replace the battery or unit, and update the register without disrupting the wider deployment.
Privacy and Data Governance
Under current UK guidance, including the ICO’s expectations around location data, privacy cannot be delegated entirely to a legal review at the end of a project. The team needs someone who understands how to design consent flows, what constitutes personal data in the context of MAC address randomisation, and how to apply data minimisation at the point of collection. This skill involves knowing when a system is tracking aggregated device counts versus identifying repeat visitors, and setting appropriate data retention limits.
Zone Logic and Content Triggering
Defining where a notification should fire requires spatial logic. If a museum wants information to appear at an exhibit, the skill lies in setting the trigger zone so it does not fire at the previous exhibit or miss the visitor entirely. This requires balancing beacon density, transmit power and the filtering logic applied to the RSSI readings, rather than simply placing a beacon on a wall and hoping for the best.
Turn the requirement into a controlled plan
The mix of skills shifts depending on the environment and the use case.
In a retail setting, the primary challenge is often defining zones around competing stimuli—tills, promotional ends, and entrances. The team needs skills in translating footfall patterns into static beacon placements that remain accurate even when staff move display units. The operational skill of rapidly re-calibrating or relocating a beacon when a floor plan changes is critical.
For museums and galleries, the emphasis moves to precision and content alignment. The spatial logic skills must account for tightly packed exhibits where zones overlap. The team also needs the operational rigour to ensure that when an exhibit is moved, the corresponding beacon zone, trigger logic and asset register are updated in sync. Accessibility considerations also require someone who understands how to align digital wayfinding triggers with physical accessibility routes, rather than assuming a straight-line path.
At temporary events, the skills tilt heavily towards rapid deployment and fault-finding. The team must be capable of testing a temporary beacon network under peak RF congestion—where hundreds of attendees are actively using Bluetooth devices—and adjusting transmit power or advertising intervals on the day to maintain a stable signal. The hardware inventory skill is also tested, as beacons must be collected, checked for damage, and re-registered for the next event.
Across all these scenarios, there is a recurring need for a "translator" role: someone who can take a requirement from a marketing or operations manager and convert it into the technical parameters—power level, advertising interval, placement height, RSSI threshold—that an installer can actually execute.
Evidence for scaling or stopping
Assuming standard IT skills cover BLE
Staff proficient in standard IT infrastructure often expect predictable, cable-based reliability. BLE is inherently probabilistic. A common mistake is deploying hardware without anyone on the team who understands why a signal reading jumps by 10 dBm when a person walks past. If no one can interpret RSSI behaviour, the team will struggle to calibrate zones effectively.
Treating privacy as a compliance afterthought
Building the entire trigger and notification architecture before consulting privacy guidance leads to expensive rework. The skill gap here is failing to recognise that privacy constraints dictate technical choices—such as whether you can use device tracking for analytics or must rely on opt-in app interactions.
Neglecting long-term maintenance skills
Pilots often succeed because the integrator is on-site managing the hardware. Once handed over, the venue’s team must possess the skills to read battery telemetry, interpret offline alerts, and physically locate a specific beacon in a ceiling void. If these operational skills are absent, battery failures go unnoticed and the deployment degrades silently.
Key checks for your project team
- RF interpretation: Can someone on the team explain why two beacons placed symmetrically might report different RSSI values to the same phone, and adjust for it?
- Calibration methodology: Is there a clear process for measuring the environment before fixing beacons in place, rather than relying on manufacturer-stated range figures?
- Privacy by design: Does the team know exactly what data is being collected, whether it is personal data under UK GDPR, and where the deletion controls sit?
- Asset traceability: If a beacon is reported stolen or faulty, can the team trace its hardware ID to a physical location and a replacement battery size within minutes?
- Zone validation: Is there a documented method for testing trigger boundaries with real devices, rather than assuming a three-metre radius on a floor plan translates to a three-metre trigger zone in practice?
Assessing these skills early prevents the scenario where the hardware is purchased and installed, but the team lacks the practical capability to keep it calibrated, compliant and functional.
