What must be ready before the work starts
Planning a timeline for a proximity deployment means scheduling physical work, not just software delivery. Unlike a purely digital rollout, installing beacons, NFC tags, and indoor navigation infrastructure binds you to hardware lead times, contractor availability, and the operational hours of a physical venue. A schedule that looks manageable on a Gantt chart often collapses when the facilities team confirms you can only access the trading floor between midnight and 05:00.
A robust milestone plan separates the project into distinct, verifiable phases: procurement, site survey, physical installation, radio calibration, integration testing, and go-live. The critical error at this stage is treating "hardware delivered" as the same milestone as "hardware installed, powered on, and calibrated against the receiving app". They are separate states, and the gap between them is where deployments stall.
Milestones should be tied to physical realities and measurable outcomes. "Complete beacon placement" is vague. "All 40 beacons mounted at specified coordinates, firmware verified, and RSSI readings logged at three test points per zone" is a milestone you can actually sign off.
Execute the plan in the real venue
Retail environments
In retail, installation must almost always happen outside trading hours. Overnight or Sunday shifts are standard, which immediately restricts your available working hours and may introduce overtime costs for the installation crew. If the deployment coincides with a shopfit or refit, your timeline becomes subordinate to the main contractor's programme. Beacons cannot be calibrated until the final shelving and display units are in place, as these physical structures alter Bluetooth signal propagation. Your milestone plan must include a dependency check: if the shopfitter delays the fixture installation by a week, the calibration milestone shifts accordingly.
Museums and heritage venues
Museum timelines are typically dictated by exhibition changeovers. Beacons and NFC tags need to be installed alongside display cases, not weeks after the public are already viewing the exhibits. This requires close coordination with the exhibition design and installation team. Furthermore, heritage buildings often impose restrictions on drilling, adhesive use, or cabling, which means your procurement milestone must include approval of mounting methods by the venue's conservation officer. Calibration in a museum must account for the density of visitors on opening day; a space that calibrates perfectly when empty may behave differently when crowded, so the testing milestone should ideally include a soft-open phase.
Events and temporary venues
Event deployments operate on highly compressed timelines. Hardware often needs to be configured, tested, and labelled off-site, then shipped to the venue for deployment within a rigid 24-to-48-hour build window. There is no scope for delayed shipments or discovering incompatible firmware on-site. The milestone plan for an event must include a pre-build verification stage and a dedicated teardown and asset recovery phase. Hardware left behind after an event is a direct financial loss, so "asset recovery complete" must be a formal milestone with a sign-off process.
Acceptance evidence and rollback
Common mistakes
- Underestimating calibration time: Walking a floor to tune RSSI values and verify zone boundaries takes hours per floor, not minutes. Scheduling an hour for calibration in a 5,000-square-metre venue is unrealistic.
- Ignoring firmware preparation: Assuming beacons arrive ready to deploy is a frequent mistake. If hardware requires a firmware update to support your required broadcasting interval or power settings, flashing dozens of units adds days to the schedule.
- Decoupling installation from integration: Physically sticking a beacon to a wall is quick. Verifying that the receiving app actually registers that beacon at the expected distance, with the correct identifier, takes far longer. Scheduling installation and integration testing on the same day invites failure.
Limitations
You cannot compress the physics of radio signals. If on-site testing reveals severe interference from existing Wi-Fi access points or metal cladding, you need time to reposition hardware, adjust transmit power, or order additional units. These are not software bugs that a developer can patch overnight; they are physical constraints that require revisiting the site. Additionally, venue access is a hard boundary. If the operations manager revokes access during a busy trading period, your timeline stops entirely until access is restored.
Key checks before finalising the schedule
- Hardware lead times: Has the supplier confirmed current stock levels and a written dispatch date, rather than a general estimate?
- Site access windows: Are the exact dates and hours documented and approved by the venue's operations or facilities team?
- Platform readiness: Is the receiving app, CMS, or dashboard capable of ingesting live beacon data before the installation crew arrives on-site?
- Mounting approvals: Have the chosen adhesives, screws, or fixtures been approved for the specific wall or surface materials?
- Buffer allocation: Does the schedule contain explicit buffer time for interference troubleshooting and re-calibration, or does it assume perfect radio conditions?
