Gateway Placement and Coverage Requirements Document Template
A gateway conversation can end in a guess: one party mounts the unit, another walks the floor with a phone, and the claim survives as a screenshot in an inbox. This gateway placement and coverage requirements template replaces the guess with a record — the doors in scope, what each candidate position must reach, and what the gateway is not asked to do.
Direct answer. For a system integrator the template is the boundary between what the client believes and what the installer can promise
What the template settles before anything is mounted
A gateway is a path between the hardware at the door and the controller holding the door's state. It is not a decision-maker: the lock reports the state and the system decides what the state means. The document says three things up front — which doors depend on which position, what covered means in the client's language, and which failures the gateway is not asked to absorb. Every commercial claim here has to be checked against the smart door locks.
The template also fixes vocabulary while it is cheap to fix. A door position contact reports open or closed, not why. A request to exit is the signal that an exit device was operated from the escape side, not a release command. Neither belongs in a gateway's scope.
The eight blocks the document contains
| Block | Content | Owner |
|---|---|---|
| Scope | Buildings, floors, doors in and out | Integrator |
| Door inventory | Door ID, role, credential type, surface | Integrator |
| Positions | Location, height, power, network drop | Installer |
| Coverage requirement | Doors to reach, threshold per door | Integrator |
| Interference | Masonry, plant, metal, neighbours | Integrator |
| Degraded mode and clock | What works when the path drops, time source | Client |
| Evidence and acceptance | Method, tester, form of record | Client |
| Change control | Triggers that reopen the survey | Integrator |
Every block carries one named owner. Blocks without an owner arrive unfinished at handover, with two parties each assuming the other did the work.
Filling the blocks in order
flowchart TD
A[Scope and door inventory agreed] --> B[Candidate positions surveyed]
B --> C[Coverage requirement written per position]
C --> D[Evidence plan and acceptance threshold set]
D --> E[Client walks the route with the installer]
E --> F[Document signed and issued for installation]
E --> B
F --> G[Change trigger reopens the survey]
The order is not decorative. The inventory comes first because a position only means something against a door list. The coverage requirement comes before the evidence plan, because a threshold written after the walk test gets written to fit the walk test. The client walks the route last, which turns a design record into an accepted one.
Candidate positions
| Candidate position | Resolves | Cannot resolve | Approval |
|---|---|---|---|
| Corridor ceiling over the door group | Short path to one floor's doors | Doors behind a core or plant room | Ceiling access |
| Electrical or comms room | Power and network in one place | Shielded doors | Facilities access |
| Local unit at the door group | One cluster, short path | Other floors or sites | None beyond survey |
| Raised floor or ceiling void | Open structure, cable routes | Solid or loaded slabs | Building survey |
Read the table as a decision rather than a menu. A position that solves a power problem but cannot reach a required door is not a candidate for that door set.
The coverage evidence the document requires
Coverage requirements are written per door, not per floor. For each door that depends on a position, the document names the threshold, the test method, the tester and the date, and records failures with a reason, not a note that the signal was weak. A route that passes once in an empty building is not evidence for a building with occupied floors.
Any published range or radio configuration quoted in the requirements has to come from the supplier for the exact unit considered: confirm on the dated product page for the specific SKU, and record the date the figure was taken.
CONFIRM-PER-SUPPLIER: Obtain a written statement from the supplier for the specific SKU before any coverage figure enters the requirements, the acceptance criteria or a tender response.
The offline case is the design, not the exception
Name the degraded mode in the document, not in the handover meeting. When the path from the gateway down is lost, state what still works: doors whose controllers hold state locally continue to apply cached credentials, and events sit in the controller's event memory until the link returns. If the honest answer for a door is that it stays locked when the path drops, the client approves that in writing.
Clock, records and the person who owns the fix
Who owns the clock: events from two sources with two clocks cannot be reconciled, so name the building's single time source and the party that keeps it. What is written down: say where the survey, the acceptance record and the change log live and who may read them, because a coverage claim nobody can retrieve is not a record. And which side owns the fix: assign the gateway, the network path, the controller and the platform to named parties with a first response and an escalation route.
Privacy, egress and the notes block
Two entries in the notes block are never drafted by the integrator alone.
CONFIRM-WITH-LOCAL-PRIVACY: Ask the local privacy adviser whether the device identity, location and telemetry attached to a gateway position counts as personal data in the operating jurisdiction, and what retention rule applies to the survey and acceptance records.
CONFIRM-WITH-LOCAL-EGRESS: Ask the local authority having jurisdiction over escape routes whether a proposed gateway position or its cabling obstructs an escape route or an alarm interface, and record the answer against that position.
Acceptance and change control
The signature block is one row per door position: door ID, position ID, test date, tester, result, notes, and the date the client accepted it. The change control block lists what reopens the survey — a tenancy change, new plant or a metal partition in the path, a controller moved, a change of radio configuration on the platform side — and names the person who may call a re-test.
Where the template sits in the chain
Issue the template with the survey, not after it. Pair it with the Office Smart Lock Site Survey or the Smart Lock Retrofit Site Survey so the door inventory and the coverage requirement arrive together. When a position fails its walk test, the recovery options are set out in Gateway Placement and Coverage Failure Patterns and How to Recover. When the client asks who carries a second position, the arguments sit in Who Owns Gateway Placement and Coverage: Supplier, Integrator or Client. The record that leaves the building belongs in the handover pack, covered in Clause Bank: Documenting Gateway Placement and Coverage for Handover and Audit.
Ask for the blank template first
Send the door inventory and the shortlisted positions, and we will return the blank gateway placement and coverage requirements template with the coverage requirement, evidence and acceptance blocks pre-marked for the units under evaluation, plus the confirmation points the installer should settle with the supplier before anything is ordered.
Close the loop with requesting a quote.

