Deployment Planning Overview
Deploying Bluetooth beacons is a physical infrastructure project, not a software install. The hardware has to perform reliably inside a specific building, around specific materials, alongside existing radio systems, and under the control of operational staff who may not have been involved in the purchasing decision. Most deployments that underperform trace back to a disconnect between what was bought and what the environment actually requires.
A beacon deployment moves through distinct phases: site assessment, procurement, installation, commissioning, and handover to operations. Skipping or compressing any of these phases creates problems that surface later, usually as inconsistent detection, unexpected battery drain, or an asset register that nobody can reconcile with what is actually on the ceiling.
The planning phase itself — defining objectives, mapping zones, and deciding on placement strategy — is covered separately in our planning guide. This article addresses the full deployment lifecycle: what happens once you move from planning into execution, and what you need to get right at each stage to end up with a system that works in practice rather than only on paper.
Common deployment failures
- Procuring beacons based on advertised range rather than measured performance in the target environment.
- Installing without a documented placement plan, leading to inconsistent coverage and no way to replicate or adjust.
- Treating commissioning as a quick signal check rather than a systematic verification of zone boundaries under real-world conditions.
- Handing over to operations with no asset register, no maintenance schedule, and no clear escalation path for failures.
Site Survey and Assessment
The site survey establishes the physical and radio-frequency conditions the beacons will actually operate in. Without it, every subsequent decision — hardware choice, quantity, placement height, transmit power — is a guess.
Physical environment
Document the layout at a level of detail that matters for radio propagation. Note wall types and thicknesses: a single-skinned partition attenuates Bluetooth Low Energy (BLE) signals far less than a dense block wall or a glass partition with metallic film. Record ceiling types and heights, as these determine mounting method and whether beacons will be obstructed by ducting, lighting rigs, or signage. Identify metal surfaces, racking, and large reflective objects that will cause multipath interference — where the signal reaches the receiver via multiple reflected paths, distorting the received signal strength indicator (RSSI) readings that distance estimation relies on.
RF environment
Scan the 2.4 GHz band at the deployment site during normal operating hours. Look for Wi-Fi access points (particularly those on channel overlap with BLE advertising channels 37, 38, and 39), Bluetooth audio devices, microwave ovens in catering areas, and any industrial equipment emitting in the band. The presence of interference does not necessarily rule out beacons, but it changes the transmit power and placement strategy you will need. A site that appears quiet at 7am may be fundamentally different at midday.
Environmental conditions
Temperature extremes directly affect battery chemistry and, consequently, broadcast stability. Note areas subject to direct sunlight through rooflights, proximity to heating or cooling vents, and outdoor transition zones. Humidity and dust levels matter for enclosure selection. In heritage buildings, also document any conservation constraints on drilling, adhesive use, or visible cabling.
What to produce from the survey
The survey should result in a marked-up floor plan showing interference sources, material boundaries, mounting constraints, and environmental zones. This document drives both procurement and the detailed placement plan. Without it, installers will make ad hoc decisions that cannot be reviewed or corrected systematically.
Procurement and Hardware Selection
Hardware selection should follow from the site survey, not from a comparison table on a supplier's website. The specifications that matter in practice are often not the ones featured in marketing materials.
Specifications that actually matter
- Transmit power adjustability: The ability to reduce transmit power post-installation is essential for tuning zone boundaries without physically relocating beacons.
- Advertising interval range: A wider range gives more flexibility to trade off detection responsiveness against battery life after deployment.
- Enclosure rating: IP rating must match the actual environment, not a theoretical one. An IP67 rating is wasted money in a climate-controlled retail unit but essential in a covered external queue area.
- Battery type and access: Coin cells are common but fiddly to replace at height. Some form factors use AA or CR123A cells that are easier to handle. Consider whether the battery compartment requires a tool to open — this reduces tampering but slows maintenance.
- Mounting options: Check whether the beacon's form factor suits your ceiling or wall type. Adhesive-backed puck beacons are convenient but problematic on rough or porous surfaces. Some models offer threaded inserts for standard fixtures.
Quantity and spares
Order spares from the same manufacturing batch if possible. BLE beacons from different batches can exhibit minor variations in antenna performance that complicate calibration. A practical spare holding depends on your deployment scale and replacement lead time — the point is to decide this deliberately rather than discover at the first battery failure that you have no replacements.
Questions for suppliers
- Can the advertising interval and transmit power be configured over-the-air after installation, or only via a physical cable connection?
- What is the manufacturer's stated battery life at the specific interval and power level you intend to use, and is that figure based on a specific battery brand?
- Is the firmware field-updatable, and what happens to configuration during an update?
- What is the lead time for repeat orders of the exact same hardware revision?
Installation Process
Installation is where the deployment plan meets physical reality. The difference between a competent installation and a poor one is not usually dramatic at launch — beacons will broadcast from almost anywhere. The problems emerge weeks later as batteries drain unevenly, zones shift because a beacon was placed six inches off plan, or a maintenance team cannot identify which beacon is which.
Following the placement plan
Every beacon position should correspond to a documented point on the floor plan, with a recorded identifier, intended transmit power, advertising interval, and the zone it serves. Installers should not be making placement decisions in the moment. If a planned position is obstructed, the deviation should be documented and the impact on zone coverage assessed before the beacon is fixed in the alternative position.
Mounting method
Choose mounting methods appropriate to the surface and the expected maintenance interval. Adhesive pads are fast but make removal and replacement difficult without damaging the surface or the beacon. Cable ties through mounting points are secure and removable but may not suit all aesthetics. Mechanical fixings are the most reliable long-term option but require appropriate tools and access. Whatever method you choose, ensure it allows the beacon to be removed for battery replacement without destroying the fixture.
Physical labelling
Apply a physical label to each beacon that matches its entry in the asset register. The label should be legible from ground level if the beacon is ceiling-mounted, using text large enough to read with a torch on a stepladder. Do not rely solely on the beacon's MAC address or UUID being readable via a phone app — maintenance staff should not have to scan every beacon on a ceiling to find the one that needs attention.
Common installation errors
- Mounting beacons behind metal grilles, inside enclosed light fittings, or against large metal surfaces that block or distort the signal.
- Orienting beacons inconsistently (some vertical, some horizontal) in positions where antenna pattern matters — most puck beacons have a slightly directional radiation pattern.
- Installing at varying heights within the same zone, creating uneven detection boundaries.
- Failing to photograph each installed beacon against its surroundings for future reference.
Testing and Commissioning
Commissioning verifies that the installed system behaves as intended under real conditions. It is not a single walkthrough with a phone; it is a structured process that tests the specific things that will matter in operation.
Signal verification
At each beacon position, verify that the RSSI values at the expected zone boundaries match the calibration assumptions. Walk the boundary slowly with a logging device and record RSSI over time — a single reading is not reliable because of the natural fluctuation in BLE signals. If you have defined a zone entry threshold during planning, confirm that a device crossing that boundary consistently triggers detection within an acceptable time window.
Zone boundary testing
Test adjacent zones to confirm there is no significant overlap causing a device to be assigned to the wrong zone. Pay particular attention to corners, narrow corridors, and areas near the material boundaries identified in the site survey. If two zones share a beacon, verify that the zone-assignment logic in your software correctly weights the combined signals.
Interference testing under load
If the site survey identified potential interference sources, re-scan the RF environment with all beacons active. In venues with fluctuating occupancy, test during both quiet and busy periods if possible — the human body is a significant attenuator of 2.4 GHz signals, and a crowded space can behave very differently from an empty one.
When to adjust versus accept
Not every RSSI anomaly warrants repositioning a beacon. Minor fluctuations are inherent to BLE. The question is whether the observed behaviour would cause a meaningful error in your specific use case. A retail notification triggered a metre late is a different problem from an indoor navigation system placing a visitor in the wrong room. Set acceptance criteria before commissioning begins, tied to what your application actually requires.
Handover to Operations
The deployment is not complete when the last beacon is commissioned. If the operations team cannot maintain the system, it will degrade silently until it stops working — and nobody will notice until a visitor complains or an analytics report shows a sudden drop in detections.
Documentation package
Operations need a floor plan showing every beacon position with its identifier, a current asset register listing hardware model, firmware version, battery type, configured transmit power and advertising interval, installation date, and expected battery replacement date. They also need the commissioning records showing baseline RSSI values at key test points, so that future performance can be compared against a known-good state.
Monitoring setup
If your platform supports remote monitoring, ensure that alerts are configured for beacon disappearance (which usually indicates battery failure or physical removal) and for significant RSSI deviation from baseline (which can indicate physical displacement or new interference). Define who receives these alerts and what the response procedure is. An unmonitored beacon deployment is a deployment with an unknown expiry date.
Maintenance schedule
Agree a maintenance schedule based on the configured advertising interval and the manufacturer's battery life estimate, with an appropriate safety margin. Battery life estimates assume ideal conditions; real-world performance in variable temperatures or with slight firmware differences will differ. Schedule the first round of battery replacements earlier than the theoretical estimate suggests, and use the actual observed battery life to refine subsequent schedules.
Training and escalation
Ensure that at least two members of the operations team can physically identify, remove, replace the battery in, and re-verify a beacon without calling the original installer. Define an escalation path for issues that go beyond routine maintenance — firmware failures, unexplained RSSI changes, or hardware damage — and ensure the contact details for the integrator or manufacturer support line are documented and accessible.
The gap between "installed" and "operational" is where most deployments quietly fail. A thorough handover closes that gap by giving the operations team the information, tools, and confidence to keep the system working long after the installation crew has left the building.
