Gateway Placement and Coverage: The Test Plan a Buyer Should Demand
Use this sheet as a contractual attachment to any smart-lock gateway proposal. It converts a placement assertion into a repeatable acceptance test. A buyer should receive the gateway placement and coverage test plan with the bid, not after equipment has been ordered or installed.
Direct answer. To put it plainly: gateway placement and coverage test plan has to hold for gateway placement and coverage test plan. gateway-placement-and-coverage has to hold at the same time. The sections below describe the order gateway placement and coverage test plan is settled in. A gateway placement and coverage test plan treats the handover as the unit of work. gateway placement and coverage test plan decides the interface. gateway placement and coverage test plan is operable on day one only if it does.
gateway placement and coverage test plan is used here in the sense given under gateway placement and coverage test plan. It is a working definition of gateway placement and coverage test plan that carries no regulatory weight. The buyer still has to check it against the dated product page.
- Draw the interface — write down what hands over between lock, door and system at gateway placement and coverage test plan
- Exercise the handover — record the sequence that proves gateway-placement-and-coverage works end to end
- Archive the record — store the commissioning evidence with the file for gp- issue instruction
- For gateway placement and coverage test plan, gateway placement and coverage is what each step has to answer to.
The sheet defines the evidence required from the survey, the tests that must use the final installation configuration, the outage cases that must be demonstrated, and the person who owns each correction. It is intended for the system integrator coordinating access control, networking, installation, and the client’s operating teams.
A floor plan, signal-prediction graphic, or model datasheet can support planning, but none substitutes for a documented test against the buyer’s designated doors and operating conditions. The Office Smart Lock Site Survey can support door and area preparation; this document defines what the buyer should demand before treating that survey as accepted.
GP-01 — Issue instruction and mandatory bid return
Add the following instruction to the request for proposal: “Each bidder shall return a completed gateway placement and coverage test plan with its technical response. Unanswered fields must carry a written explanation and an owner. A proposed threshold remains proposed until the buyer approves it.”
| Return item | Required bidder content | Acceptance evidence |
|---|---|---|
| Compliance matrix | Response to every clause, including exceptions | Signed or attributed revision |
| Placement proposal | Gateway position, enclosure, power, network path, and service access | Marked drawing and photographs |
| Survey method | Instruments, test points, setup, calibration controls, and recorded conditions | Method statement and sample record |
| Coverage test plan | Door-level method, pass threshold, retest rule, and test sequence | Completed test schedule |
| Outage matrix | Expected behavior and evidence for each degraded mode | Fault-injection record |
| Responsibility matrix | Named role and contact for every failure domain | Contract schedule |
| Handover package | As-built records, configuration evidence, exceptions, and maintenance inputs | Indexed electronic package |
The bidder must distinguish a committed design from a proposed option. “To be confirmed after survey” is acceptable only where the affected door, dependency, owner, and release date are recorded. A blanket exception covering unknown site conditions should be treated as an incomplete bid unless the buyer has accepted it in writing. The commercial end of this decision is the smart door locks.
The bidder shall also identify which evidence will be produced before installation, which will be produced at commissioning, and which will remain open after handover. This prevents a coverage problem from being carried into operation without a documented hold point or concession.
GP-02 — Scope boundary for the signal path
The gateway is one component in a larger path. It does not decide whether a person may enter, and coverage at the gateway does not prove that the controller, lock, credential, and server have completed the intended transaction. The bidder must document both directions of the path and the behavior when a message does not arrive.
| Layer | Contract question | Required evidence | Accountable role |
|---|---|---|---|
| Gateway and network | What path carries the relevant radio or network traffic? | Final placement, configuration, and path record | Supplier or integrator named in bid |
| Controller | Where is door state held, and which decision is made locally? | Controller configuration extract | Access-control integrator |
| Lock and credential | Which event is produced, and how does the installed combination respond? | Controlled point test | Supplier and access-control team |
| Service platform | Which event reaches the platform, and what happens if it cannot? | Timestamped transaction or written interface rule | Platform owner |
| Building services | Which other systems share the relevant space or network route? | Coordination record | Client or prime integrator |
Centralised and standalone are architectural choices, not interchangeable labels for local and cloud operation. The response must state where the lock state resides, which functions remain available without the server, and which failures cause a local denial. The lock reports the state; the system decides what the state means.
Local API and cloud API requirements must be separated. A buyer asking whether an event reaches the platform has a different acceptance question from one asking whether an access decision can be made at the door. For a retrofit, begin with the constraints identified in the Smart Lock Retrofit Site Survey, then trace each requirement through the complete path.
GP-03 — Design inputs required before testing
No coverage result is meaningful until the buyer and bidder use the same door list, operating conditions, and acceptance basis. The following inputs should be frozen or marked provisional before the survey:
| Input | Minimum content | Status treatment |
|---|---|---|
| Door schedule | Door identifier, area, access role, priority, and operating state | Freeze before baseline test |
| Survey drawings | Current plans, reflected layouts, and identified construction zones | Record revision and source |
| Proposed equipment | Gateway, controller, lock, credential, and candidate product references | Label each item proposed or approved |
| Physical environment | Wall, partition, door, enclosure, and nearby equipment observations | Include photographs |
| Power and network route | Intended supply source, route, interface, and service access | Mark unverified items |
| Existing radio environment | Nearby devices and systems relevant to the test area | Record observed conditions |
| Coverage threshold | The buyer-defined condition that every designated door must meet | No implied default |
| Degraded behavior | Required local, controlled, and failed states for each door role | Require approval before test |
| Test authority | Who witnesses, records, receives, and closes exceptions | Name roles and contacts |
If a bidder identifies a specific SKU, radio characteristics, port behavior, power requirements, and environmental limits must be confirmed on the dated product page for the specific SKU. A family-level value cannot be transferred to another model. Where an input remains unknown, the test plan must show which conclusion is blocked and who must supply the missing evidence.
GP-04 — Smart lock gateway site survey deliverable
The smart lock gateway site survey is a measured record, not a drawing exercise. It must connect each test point to a door identifier and each proposed gateway to a serviceable physical location. A predicted heat map without the instrument, setup, and point records does not demonstrate acceptance readiness.
The bidder shall return a survey package containing the survey date and responsible personnel; instrument identification and calibration status; all test-point coordinates or marked locations; measured observations; photographs; obstruction notes; candidate gateway positions; and a list of unresolved design changes. The bidder must also identify which observations came from a temporary setup and which came from production-equivalent equipment.
flowchart TD
A[Door schedule] --> B[Site survey]
B --> C[Candidate positions]
C --> D[Configure test unit]
D --> E[Run coverage and outage tests]
E --> F{Result accepted}
F -->|Yes| G[Issue evidence record]
F -->|No| H[Adjust and retest]
H --> D
G --> I[Release installation hold point]
| Survey record field | What it prevents |
|---|---|
| Test-point and door-ID cross-reference | A passing result with no assigned door |
| Equipment and configuration revision | A test performed with a different setup |
| Physical-condition notes | A later unexplained coverage change |
| Photograph index | Disputes about obstructions or access |
| Exception and owner list | An unidentified outstanding action |
A survey may recommend a placement, but it cannot waive the final acceptance test. Where relocation would affect power, cabling, enclosure, maintenance access, or a door’s physical operation, the bidder must identify the affected trade and obtain the required approval before installation.
GP-05 — Placement arrangements the bidder must compare
The gateway placement and coverage test plan must compare the physical arrangements available to the project rather than presenting one location without context. The comparison below is a decision aid, not a performance ranking. The bidder completes it using the survey evidence.
| Arrangement | Intended project condition | Evidence required | Hold or reject condition | Decision owner |
|---|---|---|---|---|
| Distributed local unit | Separate coverage zones with independent access needs | Door-level tests and a location for each unit | Coverage fails or the service path is unresolved | Access-control integrator |
| Shared enclosure | Equipment grouped in an accessible technical area | Enclosure survey and end-to-end tests | Required doors cannot meet the approved threshold | Client and integrator |
| Central shared unit | Common path for a defined area | Whole-area test matrix and interference test | Any protected door lacks an approved result | Buyer’s project authority |
| Hybrid arrangement | Different areas have materially different constraints | Separate evidence for each zone | Zone boundaries or responsibilities remain ambiguous | Named design authority |
A candidate location must have confirmed power, a confirmed network route, safe service access, and no unapproved structural or building-services work. These are entry conditions, not substitutes for radio and connectivity testing. A location also becomes a hold point if the physical arrangement obstructs required access, alters the approved door behavior, or leaves the equipment owner unidentified.
The buyer records the selected arrangement, rejected alternatives, reasons, and residual exceptions. A later change to the arrangement triggers the change-control process in GP-08; it does not rely on memory of the original survey.
GP-06 — Wireless coverage acceptance test
The wireless coverage acceptance test must use the proposed production gateway in its intended physical position and with the configuration intended for operation. Predictive results remain planning inputs. Acceptance comes from recorded observations at designated door locations under the buyer’s approved operating conditions.
| Test ID | Method | Pass criterion | Evidence |
|---|---|---|---|
| W-01 | Establish a site baseline at every designated test point | Result meets the buyer-approved threshold | Door-level measurement record |
| W-02 | Operate the selected gateway from its proposed position | Every linked designated door meets the threshold | Final placement record |
| W-03 | Repeat tests in the listed door and traffic states | Results remain within the approved acceptance condition | Test-state matrix |
| W-04 | Run the planned nearby-equipment condition | No designated door becomes an approved exception | Coordination and result record |
| W-05 | Repeat a defined subset to check repeatability | Repeated results meet the agreed condition | Repeat-test log |
| W-06 | Test after any approved physical or configuration change | Affected points remain within the acceptance condition | Change and retest record |
The buyer must state the acceptance threshold before comparing bids. If the bidder proposes a threshold, label it as proposed and identify the measurement method with which it is comparable. Do not allow a bidder to redefine the threshold after a failed test.
Each result record must contain the door identifier, test-point identifier, gateway identifier, physical location, configuration revision, operating condition, measured result, acceptance criterion, tester, timestamp, and disposition. An exception must state the affected door, likely cause, temporary arrangement, accountable owner, retest condition, and buyer disposition.
GP-07 — Lock connectivity test
A lock connectivity test proves more than a radio observation. It demonstrates that the final gateway, controller, lock, credential, and service path behave as the approved design expects. The bidder must identify whether a failed step belongs to association, policy exchange, event delivery, door response, or platform reporting.
| Test ID | Controlled action | Pass criterion | Required record |
|---|---|---|---|
| L-01 | Establish the intended lock and gateway path using final configuration | The path forms and retains the approved identity | Configuration and connection evidence |
| L-02 | Present a valid test credential | The response matches the approved access policy | Timestamped transaction |
| L-03 | Present a credential outside the test policy | The response matches the approved rejection behavior | Timestamped transaction |
| L-04 | Observe the controller-side and platform-side records | Both represent the same test event correctly | Reconciled event record |
| L-05 | Operate the controlled door under the approved test method | Door response matches the specified behavior | Door and controller record |
| L-06 | Restore service after the approved interruption sequence | Recovery and event state match the design | Restart and recovery log |
The credential is the item a person holds or presents; identity is the person or role behind it. Test records should identify both so a successful device test is not mistaken for proof of the correct person-to-door entitlement. Use dedicated test identities and remove them under the approved decommissioning process.
A product reference included in the test record must remain tied to the exact approved SKU. Radio reach, pairing behavior, and operating limits must be confirmed on the dated product page for the specific SKU rather than inferred from the gateway alone.
GP-08 — Interference, physical changes, and retesting
Coverage is an observed condition at a particular time. The buyer therefore needs defined triggers that reopen the test. The bidder should include any additional trigger required by the physical environment or installation sequence.
| Change or condition | Required response | Affected evidence |
|---|---|---|
| Partition, wall, door, or finish change | Review the location and retest affected points | Survey and W-series records |
| Gateway, lock, controller, or credential change | Verify configuration compatibility and rerun linked tests | Configuration baseline and L-series records |
| Nearby radio equipment added or relocated | Recreate the approved coexistence condition | W-04 record |
| Power or network route changed | Revalidate service availability and outage behavior | Commissioning and outage records |
| Gateway relocated | Repeat coverage and connectivity tests | New placement package |
| Door or furniture arrangement materially changed | Confirm the operating condition still represents the approved use | Survey update and affected test points |
The bidder must not close an open test point by substituting a nearby passing door. Coverage evidence transfers to another point only when the buyer approves the transfer and the physical and configuration conditions are demonstrably equivalent.
GP-09 — Outage and degraded-mode acceptance
For each door role, specify the approved fail-safe or fail-secure state and identify who approved it. That decision belongs to the door design and approval process, not to a generic product claim. The offline case is the design, not the exception.
| Scenario | Controlled method | Pass criterion | Evidence and owner |
|---|---|---|---|
| Upstream network unavailable | Interrupt the defined upstream path under the approved method | Local behavior and event handling match the door-specific design | Configuration, event record, and integration owner |
| Controller unavailable | Apply the approved controller-loss condition | Door response and credential handling match the stated degraded mode | Fault log and access-control owner |
| Service platform unavailable | Separate platform loss from local network loss | Local operations continue or fail exactly as the design states | Local transaction and platform-recovery record |
| Gateway restart or power interruption | Restore service through the approved sequence | Recovery, retained events, and door mapping match the design | Restart log and supplier owner |
| Radio path degraded | Reproduce the buyer-approved degraded condition | Each designated door has the approved result | Door-level test record |
| Partial communication failure | Interfere with one path component at a time | The system identifies the lost path and follows the fallback rule | Interface trace and named owner |
Do not accept “works offline” as a pass statement. The response must name the door, the component that failed, the local function that remained available, the event that was not delivered, and the recovery action. If a transaction moves from the server-side audit log to local event memory, preserve the distinction and demonstrate how the record is reconciled later.
The bidder and buyer should agree which tests are safe for the installed door and how they will be performed. The test method must not depend on an improvised release or bypass. Any exception receives a written buyer concession, an owner, and a retest condition before the installation hold point is released.
GP-10 — Clock, event, and record ownership
One authoritative clock must be identified for each event class. The bid response must state how controller, lock, gateway, and platform timestamps are aligned, what happens during clock loss, and which timestamp is used when reconciliation is required. Two unexplained clocks cannot support a reliable incident chronology.
| Record | Authoritative owner | Access and retention requirement | Export or reconciliation evidence |
|---|---|---|---|
| Door-access event | Named access-control owner | Define readers, purpose, and storage location | Sample export tied to a test identity |
| Local event memory | Named lock or controller owner | Define buffer boundary and recovery procedure | Before-and-after recovery test |
| Audit log | Named platform owner | Define access permissions and auditability | Permission test and sample record |
| Coverage result | Named integrator or supplier | Preserve test conditions and configuration revision | Signed door-level result set |
| Configuration baseline | Named configuration owner | Preserve approved and observed versions | Change log and file hash or equivalent control |
| Gateway commissioning record | Named commissioning owner | Retain with the access-control handover | Indexed handover package |
Audit log and event memory must not be treated as the same record. The audit log is an event record with a time and source; event memory is the buffer used when the lock cannot reach the server. The buyer must know which events exist in each place, how they are reconciled, and whether an outage leaves a visible gap.
CONFIRM-WITH-LOCAL-PRIVACY-ADVISOR: Confirm the records, purposes, access rights, retention periods, export recipients, and authority approvals allowed for the jurisdiction in which the system operates before commissioning.
This line remains with the completed record schedule. It identifies the approval needed; it does not substitute for the client’s local decision or the integrator’s documented configuration.
GP-11 — Gateway commissioning checklist
Use the gateway commissioning checklist to close physical, logical, and evidentiary gaps before the equipment enters normal service. The checklist is completed against the same identifiers used in the coverage and connectivity tests.
| Check | Required confirmation | Sign-off evidence |
|---|---|---|
| Identity and mapping | Gateway, controller, door, and physical location are correctly associated | Configuration extract and label photograph |
| Power and network | Intended supply and path are confirmed without an unresolved hold | Installer record |
| Configuration baseline | Hardware, software, and relevant settings are recorded | Approved configuration snapshot |
| Door credentials | Test identities work only where intended | Transaction and reconciliation record |
| Clock | Approved time source and recovery behavior are recorded | Clock comparison and recovery log |
| Coverage and connectivity | All required tests and dispositions are attached | Signed test package |
| Outage behavior | Every required degraded-mode case has a result | Outage matrix |
| Labels and service records | Equipment is identifiable and maintainable | Asset register and location schedule |
| Decommissioning plan | Removal, credential cancellation, and record disposal have owners | Approved offboarding procedure |
The Gateway Placement and Coverage Requirements Document Template can carry these requirements into the project’s formal document set. Its fields should point to the actual test records; an empty or future-tense field is not completed evidence.
Provisioning brings a device into service with its identity, door, and owner. Decommissioning is a separate recorded operation and must not be represented by an unchecked box on the commissioning sheet.
GP-12 — Property-specific application notes
A hotel deployment may organize the schedule by property area and room type, but the gateway test still identifies an exact door or approved location. The Gateway Placement and Coverage for a Hotel Property provides the property-specific decision context; it does not replace the door-level evidence in this sheet.
A multifamily or office portfolio may reuse a test template, but it cannot reuse a result. The Gateway Placement and Coverage for a Multifamily or Office Portfolio addresses portfolio-scale application. Each building, common area, and distinct physical arrangement still needs its own baseline and accepted exceptions.
For either case, record which parts of the evidence package may be standardized and which must be regenerated at the site. Reusing a drawing, configuration, or test point without confirming the site conditions is an open assumption, not an efficiency measure.
GP-13 — Access control integration handover package
The access control integration handover is the transfer of an operating and evidentiary package. The Documenting Gateway Placement and Coverage for Handover and Audit should be used to align the package with the client’s audit and maintenance requirements.
| Package item | Required content | Receiving owner |
|---|---|---|
| As-built placement | Final gateway locations, enclosures, routes, and photographs | Facilities and access-control owner |
| Door-to-gateway map | Permanent identifiers and controlled test-point references | Commissioning owner |
| Configuration baseline | Approved hardware, software, settings, and change record | Configuration owner |
| Test evidence | Coverage, connectivity, clock, and outage results | Acceptance authority |
| Exception register | Cause, owner, concession, retest condition, and closure evidence | Project manager |
| Event ownership | Clock, event sources, readers, retention, and recovery procedure | Platform and privacy owners |
| Maintenance procedure | Inspection access, known weak points, change triggers, and contact route | Service provider |
| Decommissioning procedure | Equipment removal, credential cancellation, and record handling | Client operations owner |
A handover list containing equipment locations is insufficient. The receiving team must be able to trace each accepted door result to the installed configuration, reproduce the test conditions, identify unresolved exceptions, and determine who acts when the condition changes.
GP-14 — Failure ownership and acceptance decisions
A boundary that is not drawn becomes a dispute after installation. Each bidder must insert the actual company, contact, and escalation route for every failure domain in the contract schedule. Generic labels such as “vendor” or “integrator” do not satisfy this clause.
| Failure domain | Required ownership entry | Closure evidence |
|---|---|---|
| Coverage shortfall or changed radio condition | Equipment supplier and survey owner | Corrected placement and passing retest |
| Lock or credential path failure | Approved product and integration owners | Transaction, configuration, and recovery evidence |
| Controller or interface failure | Access-control integrator | Controller log and agreed correction |
| Network path failure | Network service owner | Path record and outage retest |
| Server or platform failure | Platform owner | Recovery and event-reconciliation evidence |
| Configuration drift | Named configuration owner | Approved baseline and change record |
| Test disposition | Meaning | Buyer action |
|---|---|---|
| Accepted | Every mandatory criterion has passing evidence and no unapproved exception | Release the associated hold point |
| Conditionally accepted | A bounded exception has a documented concession, owner, and retest condition | Record the limitation and responsible party |
| Failed | A mandatory criterion lacks acceptable evidence or the result conflicts with the approved design | Correct and retest before acceptance |
Every closure record must identify the failed test, the revised condition, the retest result, and the person authorized to accept it. A supplier claim that another party owns the cause is not closure. The named accountable role remains responsible for coordinating the evidence until the buyer accepts the outcome.
It is worth pairing this with how to choose between smart lock technologies. That is the same question gateway placement and coverage test plan has to answer here.
GP-15 — Acceptance certificate and issue instruction
The final acceptance certificate should reference the immutable test package rather than summarize results from memory.
| Acceptance field | Buyer confirmation |
|---|---|
| Scope | Approved door schedule and coverage areas |
| Placement | Final locations and associated test-point identifiers |
| Coverage and connectivity | Accepted test records and exception dispositions |
| Degraded mode | Approved outage behavior and recovery evidence |
| Records and clock | Event ownership, synchronization method, and recovery procedure |
| Responsibility | Named owners and escalation routes |
| Handover | Indexed package received and access confirmed |
| Open items | Written concessions, deadlines, and retest conditions |
Attach this sheet to the request for proposal, issue it with the survey brief, and require the completed version with the technical bid. A comparison becomes meaningful only when bidders are proving the same door paths against the same acceptance basis. Close unresolved inputs before bid close; after award, convert every accepted location into an installation and commissioning obligation with named evidence.
A quote request turns the written requirement into something a supplier can price: request a quote.

