Preparation and acceptance criteria
A handover checklist is the formal verification step that sits between completing a physical installation and taking on day-to-day operational responsibility for a proximity system. In practice, it is the point where an integrator or internal project team confirms that everything the operations staff need to run, monitor and maintain the deployment has actually been delivered and accounted for.
For beacon networks, NFC installations and indoor navigation systems, the handover is not a single moment but a staged process. Hardware must be physically present and correctly placed. Configuration records must match what is actually broadcasting on-site. Access credentials for management platforms need to work for the people who will use them, not just the engineers who set them up. Any known issues, deviations from the original plan or temporary workarounds should be documented rather than discovered later by the operations team.
The checklist itself is a structured record of these confirmations. It does not replace as-built documentation, which describes the system in detail; instead, it verifies that the documentation exists, is accurate and has been received by the right people. A well-constructed handover checklist ties each item to a responsible individual and a sign-off date, creating a clear audit trail for when operational responsibility transferred.
What Belongs on the Checklist
The contents should reflect the specific deployment, but most proximity installations require verification across a consistent set of categories:
- Hardware inventory: Every beacon, NFC tag, QR label and fixture, matched against the procurement list and physically confirmed on-site.
- Placement verification: Confirmation that each device is in the agreed location, at the correct height and orientation, and secured according to the installation specification.
- Configuration records: Broadcast identifiers, advertising intervals, transmit power settings and firmware versions for each device, cross-referenced against the as-built documentation.
- Platform access: Login credentials, permission levels and API keys for any management console, content management system or analytics platform, tested by the operations team before sign-off.
- Known issues and deviations: A written record of any devices that could not be placed as planned, zones with reduced accuracy, or temporary configurations that need later attention.
- Training evidence: Confirmation that operational staff have received instruction on monitoring dashboards, content updates, battery replacement procedures and escalation contacts.
- Warranty and support details: Contract references, support hours, escalation paths and any exclusions that the operations team needs to know about.
From preparation to live testing
Retail Environments
In a retail deployment, the handover often coincides with a store opening or refit deadline, which creates pressure to sign off quickly. A practical approach is to split the checklist into two stages: a physical installation sign-off and a systems handover that follows once the management platform has been populated with the correct zones, campaigns and notification rules. This prevents the operations team from accepting responsibility for a system whose software configuration has not been verified in the live environment.
Store managers who will receive low-battery alerts or be asked to replace beacons need explicit, simple instructions included in the handover, not just a link to a technical manual. The checklist should confirm that these instructions exist, are specific to the store layout and have been reviewed by the person who will actually carry out the tasks.
Museums and Heritage Sites
Museum handovers frequently involve multiple stakeholders: the integrator, the venue's IT team, curatorial staff and front-of-house managers. The checklist needs to reflect which party is responsible for what. Curatorial staff may need sign-off that exhibit-linked content is correct and accessible, while facilities staff need confirmation of mounting methods, cable routes and any constraints on drilling or fixing to historic surfaces.
Where beacons or NFC tags are attached to movable exhibits or display cases that may be repositioned, the handover should explicitly note this and describe the process for updating placement records when items move. Leaving this assumption unstated is a common source of drift between the documented system and the physical reality.
Events and Temporary Installations
For event-based deployments, the handover checklist serves a dual purpose: confirming the installation is correct at the start of the event and providing a baseline for the decommissioning check at the end. Items specific to events include confirmation of temporary power supplies, the location of any network gateways or edge devices that are not part of the permanent venue infrastructure, and the agreed process for removing all hardware after the event closes.
Because event staff may not have been involved in the planning phase, the checklist should be written so that someone unfamiliar with the project can verify each item against what they see on-site.
Re-test, maintain and improve
Signing Off Without Physical Verification
The most frequent failing is accepting a handover based on paperwork alone. An integrator may submit a completed checklist stating that all 120 beacons are installed and configured, but if the operations team does not physically spot-check a representative sample, errors such as swapped identifiers, incorrect transmit power settings or devices mounted at the wrong height will only surface when the system fails to perform as expected. A reasonable approach is to verify at least 10 to 15 percent of devices on-site, selected across different zones and fixture types, before signing the handover.
Accepting Incomplete Access Credentials
Handovers sometimes include a single shared login for a management platform, with no individual accounts set up for the operations staff who will actually use it. This creates both a security concern and a practical problem when that single account is tied to the integrator's email address. The checklist should require that each operational user has logged into the platform independently, confirmed their permission level is appropriate and changed any temporary passwords before sign-off.
Omitting Known Limitations
Integrators may be reluctant to document areas where the system does not meet the original specification, such as zones where signal attenuation through a particular wall type reduces accuracy below the target, or areas where interference from existing Wi-Fi equipment affects beacon detection reliability. If these limitations are not recorded at handover, the operations team has no baseline for judging whether later performance issues are new problems or pre-existing conditions. The checklist should explicitly ask whether any zones or functions deviate from the agreed specification and require a written response, even if the answer is none.
Key Checks Before Signing
- Physically verify a sample of devices against the inventory and placement records.
- Confirm each operational user can log into all relevant platforms with their own credentials.
- Check that firmware versions recorded in the documentation match what is actually deployed.
- Verify that battery-level reporting is working for a sample of beacons in the management platform.
- Ensure any known deviations or temporary configurations are written down, not just mentioned verbally.
- Confirm that escalation contacts and support procedures are documented and understood by the operations team.
- Agree a process for updating the handover record if issues are discovered in the first weeks of operation.
A handover checklist is not a guarantee that nothing will go wrong after sign-off. It is a disciplined verification that the operations team has received what was agreed, understands the current state of the system including its limitations, and has the access and information needed to take responsibility. For ongoing operational procedures, including battery replacement schedules and routine monitoring, the next step is to refer to the operations and maintenance documentation that the handover confirms is now in the correct hands.
