Door Position Contacts Requirements Document Template
This door position contacts requirements template is a fill-in workbook for system integrators working with access-control engineers, installers, client representatives, and suppliers. It separates what a door position contact reports from what the controller and surrounding systems infer. It also records ownership when a state change is missed, a clock differs, a service becomes unavailable, or a field change is proposed. Complete one copy for each door or coherent door group, attach the approved drawings, and obtain sign-off before installation. Mark every unfilled field as pending, not applicable with a reason, or verified with evidence.
Direct answer. Condensed to the essential point, door position contacts requirements template turns a request into a decision record. door position contacts requirements template and door-position-contacts are the two parts of door position contacts requirements template most often skipped. A door position contacts requirements template traces one integration from lock to reader to record. door position contacts requirements template marks the handover point. door position contacts requirements template cannot be improvised there.
The phrase door position contacts requirements template is anchored in door position contacts requirements template. For the rest of this article it denotes the conditions and evidence that door position contacts requirements template sets out below. Nothing wider than that.
- Outline the interface — write down what hands over between lock, door and system at door position contacts requirements template
- Rehearse the handover — record the sequence that proves door-position-contacts works end to end
- Log the exchange — store the commissioning evidence with the file for control document
- For door position contacts requirements template, the order below is fixed and door position contacts is the reference point.
1. Control the document and door scope
Use one controlled workbook for each package. Repeat the document reference on every sheet and use the same door identifiers shown on the drawings, controller point schedule, and test records. The catalogue side of this is the smart door locks.
| Field | Fill-in entry |
|---|---|
| Document reference | |
| Project and site | |
| Package and door group | |
| Integration boundary | |
| Prepared by and role | |
| Technical reviewer | |
| Client approver | |
| Version, date, and distribution list |
Unresolved fields must have an owner and due date. A blank cell cannot be interpreted as “not required” during handover.
2. Build the door-by-door schedule
Record the physical opening before configuring the door monitoring interface. Identify the door, normal position, contact location shown on the drawing, controller channel, required event, and operator action. Use the same open closed state vocabulary throughout the drawings and configuration record.
| Door ID | Opening description | Normal open closed state | Contact location shown | Controller channel | Required event | Operator action | Test reference |
|---|---|---|---|---|---|---|---|
Describe what the contact is intended to detect rather than assuming that position proves why the door moved. A contact reports a state; it does not establish whether the door was held, pushed, propped, or obstructed. Treat those as separate requirements requiring another approved input or observation method.
Field conditions should be reconciled with the drawings before approval. The Office Smart Lock Site Survey and Smart Lock Retrofit Site Survey provide useful site-survey references, but the approved point schedule remains the controlling record.
3. Define what each signal means
Complete the door position contacts requirements template with explicit decisions rather than vendor terminology. The lock reports the state; the system decides what the state means.
| Decision question | Required entry | Boundary to preserve |
|---|---|---|
| What does the contact report? | Current open or closed state: | A state does not reveal the cause of the movement. |
| What creates an event? | Transition, source, debounce rule, and timestamp owner: | Do not label every transition as a forced-open event. |
| When is a door held open? | Configured duration, alarm, recipient, and reset rule: | The timer belongs to the controller or service, not the contact. |
| Is request to exit in scope? | Separate signal and interface details: | Request to exit reports operation from the escape side; it is not a release command. |
| What happens during power loss? | Local input behavior, controller behavior, and approved door state: | Position reporting and lock release behavior are separate decisions. |
| What happens when service is unavailable? | Local state, event handling, escalation, and recovery: | Do not substitute an assumed fail-safe or fail-secure outcome. |
Record the physical state separately from any access-control alarm. For example, an open state may trigger an operator notification, but the notification must not claim that an unauthorized entry occurred unless another approved source establishes that condition.
CONFIRM-WITH-LOCAL-EGRESS-AND-FIRE-AUTHORITY — Confirm the installed door’s release sequence, power-loss behavior, and interface responsibilities with the client’s approved authority and the local fire and egress reviewer.
4. Turn the contact into controller requirements
The controller requirements sheet defines the boundary between the physical contact, the controller, and the service that stores events. Complete one row for every configuration item rather than attaching a generic device diagram.
| Controller requirement | Fill-in decision or value |
|---|---|
| Input type and electrical limits | |
| Normally open or normally closed arrangement | |
| Supervision requirement, if applicable | |
| Configured debounce behavior | |
| Event source and event name | |
| Timestamp source and time zone | |
| Controller restart behavior | |
| Local event-memory limits | |
| Service-unavailable behavior | |
| Configuration owner and change record |
Treat the audit log and event memory as different records. The audit log is the retained event record with a time and source; event memory is the buffer used when the lock cannot reach the server. State explicitly whether buffered events transfer to the audit log after reconnection and how duplicates or gaps are identified.
CONFIRM-PER-SUPPLIER — Confirm on the dated product page for the specific SKU whether the selected lock exposes a door-position input and its electrical limits. If it does not, identify the separate contact, wiring arrangement, and controller channel. Do not transfer those assumptions to another SKU.
5. Assign the clock and control the data record
Choose one timestamp owner for each event type. The controller may create the event before service delivery, while another architecture may create it when the server receives a report; the workbook must identify which model applies and how the distinction remains visible.
| Data and timing decision | Fill-in entry |
|---|---|
| Event source and timestamp owner | |
| Time zone and clock source | |
| Synchronization check and fallback | |
| Event-ordering rule | |
| Event-to-identity linkage | |
| Audit-log retention location | |
| Event-memory capacity and transfer rule | |
| Authorized readers | |
| Reconciliation and gap review |
Door events linked to a person or credential can reveal movement through a space. Limit collection to the approved operational purpose, record who may read the records, and define how retention and export requests are handled.
CONFIRM-WITH-LOCAL-PRIVACY-LEAD — Confirm which door events, identities, access rights, and retention periods the client may collect in the operating region, and record the approved purpose, authorized readers, and review authority.
6. Specify the degraded modes
The offline case is the design, not the exception. Complete each row before commissioning. If a field is inapplicable, record the technical reason rather than leaving it blank.
| Failure scenario | Required local behavior | Event handling and alarm | Recovery owner |
|---|---|---|---|
| Contact or input fault | |||
| Controller restart | |||
| Network or server unavailable | |||
| Clock unavailable | |||
| Power removed | |||
| Wiring altered or disconnected |
Fail-safe / fail-secure describes the state a lock takes when power is removed. That choice belongs to the door’s role and the approved design, not to the contact wiring. Record position-reporting behavior, door release behavior, and alarm handling as separate fields so a change in one does not silently alter another.
flowchart TD
A["Contact reports open or closed"] --> B{"Controller accepts input"}
B -->|"Yes"| C["Apply configured debounce and timestamp"]
B -->|"No"| D["Raise input fault and apply fallback"]
C --> E{"Selected service available"}
E -->|"Yes"| F["Write event and apply access rule"]
E -->|"No"| G["Apply local degraded mode and preserve evidence"]
F --> H["Review exception and close work order"]
G --> H
It is worth pairing this with the smart lock motor durability. That is the same question door position contacts requirements template has to answer here.
7. Assign decision rights and the fix owner
Name an individual or role for each boundary. A boundary without an owner becomes a recurring dispute between the supplier, installer, integrator, and client.
| Role | Owns this decision or fix | Required evidence |
|---|---|---|
| System integrator | Requirement coordination and interface acceptance | Completed workbook and interface schedule |
| Contact installer | Physical installation, labeling, and wiring workmanship | Installation inspection and test evidence |
| Controller engineer | Input configuration, event generation, and local behavior | Configuration baseline and diagnostic record |
| Network or time owner | Connectivity, clock source, and recovery events | Connectivity and synchronization checks |
| Supplier | SKU-specific evidence and technical response | Dated product-page confirmation and written exceptions |
| Client approver | Operational rules, alarm actions, and acceptance | Signed decision and deviation record |
Use the Who Owns Door Position Contacts: Supplier, Integrator or Client to challenge unclear allocations. The Door Position Contacts for Smart Lock Projects: What Buyers Must Define First provides a separate scope check before detailed design begins.
8. Convert the requirements into door sensor testing
Door sensor testing must prove the agreed state and event behavior, not merely show that a magnet moves near a sensor. Record the configured threshold and timing evidence for every result.
| Test ID | Test action | Expected state and event | Evidence to retain | Result and retest owner |
|---|---|---|---|---|
| T01 | Establish the normal closed baseline | |||
| T02 | Open the door from the approved side | |||
| T03 | Close the door and wait for the configured transition | |||
| T04 | Hold the door beyond the approved duration | |||
| T05 | Apply a brief transition covered by the debounce rule | |||
| T06 | Restart the controller | |||
| T07 | Interrupt the selected service path | |||
| T08 | Remove and restore power, if approved for the test | |||
| T09 | Verify request-to-exit behavior if included in scope |
Use the Door Position Contacts: The Test Plan a Buyer Should Demand to expand the test conditions. Retain failed results as deviation records with an owner, corrective action, and approved retest date.
9. Assemble the handover package
Handover is a recorded transfer of operational responsibility. Store each artifact in the controlled repository identified below and link it to the affected door IDs.
| Handover artifact | Owner | Version or location | Approval or review |
|---|---|---|---|
| As-built door and contact drawings | |||
| Controller point schedule | |||
| Configuration baseline | |||
| Clock and event-data map | |||
| Completed test record | |||
| Alarm and escalation matrix | |||
| Open-deviation register | |||
| Training and support handover |
Document any later removal as a separate decommissioning operation, including the door identifier, service date, remaining access rights, and record-retention decision. The Documenting Door Position Contacts for Handover and Audit expands the handover evidence set.
10. Close evaluation with a signed evidence record
The workbook is ready for approval only when each check has an entry or a referenced approval.
- Door identifiers match the drawings and point schedule.
- State, event, and alarm meanings are unambiguous.
- The controller requirements and SKU evidence are dated.
- Clock ownership, data access, and retention are recorded.
- Every degraded mode has a behavior and owner.
- Privacy, egress, and fire-interface questions carry the required confirmations.
- Test results and deviations are attached.
- Handover artifacts have locations, versions, and approvers.
| Sign-off role | Name or reference | Date | Decision |
|---|---|---|---|
| Integrator | |||
| Access-control engineer | |||
| Client representative | |||
| Local reviewer, where required |
To move evaluation into procurement, attach the completed workbook to the request for quotation. Ask each candidate supplier to answer the dated product-page questions by SKU and return written exceptions. Do not accept a generic interoperability statement or equipment description in place of the completed signal, ownership, degraded-mode, and test fields.
The next step is to request a quote.

