What should the system let your team do?
A strong access control scope identifies each opening, how people enter and leave, who administers access and what happens when power, connectivity or an integration is unavailable.
Begin with the current problem: unmanaged keys, slow onboarding, missing audit records, inconsistent hours, difficult multi-site administration or doors that need repair. Then separate the security policy from the physical work. The controller, reader, credential and lock must be selected as a compatible door solution.
Create one line in the door schedule for every opening.
Record both sides of each door, its normal use and any existing hardware before pricing. A basic owner-approved schedule should include:
| Field | What to record | Why it matters |
|---|---|---|
| Door identity | Unique ID, building, floor, location, photo and floor-plan reference. | Aligns hardware, cabling, programming and test records. |
| Opening | Single/pair, frame and door material, swing, current lockset, closer, electrified components and door condition. | Determines whether proposed hardware can fit and function. |
| Use | Staff, public, guest, delivery or restricted area; expected traffic and operating hours. | Shapes credential, schedule and visitor workflow. |
| Interfaces | Reader location, door position, request-to-exit method, intercom, video and elevator or alarm connections if needed. | Exposes power, cable and programming dependencies. |
| Exceptions | Fire rating, accessible operation, existing automatic operator, landlord approval and field dimensions to verify. | Triggers qualified design and authority review. |
Photograph the strike area, hinge side, frame, existing power-transfer method and nearby controller location where access is permitted. Confirm who owns any door modification, patching, painting or work on rated assemblies.
Decide who gets access and who can change it.
For organizations with multiple properties, decide whether policies are centrally managed, locally delegated or both. The software choice should fit that operating model and the client’s identity-management requirements.
Document the technical dependencies before the quote.
Controller and power
Identify enclosure locations, available network and power, backup expectations, cable routes, spare capacity and who will configure the network.
Reader communication
Confirm supported reader/controller interfaces and credential technology. Where applicable, evaluate supervised, encrypted reader communication such as OSDP Secure Channel.
Cloud or on-premises
Compare remote administration, local behavior during outages, licensing, support responsibility, data ownership and existing platform integrations.
Connected systems
List required video events, intercom call flows, identity directory sync, visitor management, elevator control or building-specific integrations.
The Security Industry Association describes OSDP as a reader-to-controller protocol with bidirectional communication, supervision and Secure Channel capabilities. Its use still depends on product compatibility and how the system is configured. See source notes.
Plan egress, accessibility and fire interfaces at the right time.
Record who will coordinate with the door hardware supplier, design professional, fire alarm contractor, property management and permitting authority where required. Include what the door must do during a power loss, fire alarm condition and routine exit. Do not substitute a generic “fail safe” or “fail secure” statement for a complete opening review.
UL describes UL 294 as a standard for access control system units, but product certification alone does not approve a complete door arrangement for a particular facility. See source notes.
Agree on proof of operation before installation.
Store passwords, recovery codes and sensitive system settings through the customer’s secure credential process, separate from a broadly shared construction closeout folder.
Questions to resolve before a bid.
Can existing doors and locks be reused?
Often, but it requires an opening survey. Door condition, hardware compatibility, function, ratings, wiring path and the desired operating behavior determine whether reuse is practical.
Is a cloud access platform always the best choice?
No. Compare management model, existing hardware, network and outage requirements, integrations, licensing and the owner’s support capability before choosing an architecture.
Are mobile credentials enough for everyone?
Not necessarily. Some users may require cards, temporary credentials or another approved method. The plan should address device ownership, lost phones and visitors.
Who approves a maglock or electric strike?
The proposed locking arrangement should be reviewed for the specific door and adopted requirements by the appropriate qualified team and authority. A hardware part number by itself does not establish compliance.
Turn the survey into a scope that can be priced and tested.
Terapixels can assess commercial openings, coordinate access controllers, readers, credentials, door hardware, power, cabling, intercom and video dependencies, and define the project closeout. The final design and responsibilities should be confirmed door by door.
Technical source notes
- Security Industry Association, Open Supervised Device Protocol: reader-controller communication, supervision and Secure Channel overview.
- UL Solutions, Access Control System Testing and Certification: UL 294 overview.
- UL Solutions, Locking Configurations for Access and Egress Control: examples of application-specific locking arrangements.
- This planning checklist does not provide code or engineering approval for a particular door. Confirm local requirements and the final hardware schedule for each project.
Plan this with Terapixels.
Share your facility, existing systems and the decision you need to make. We will help identify the right scope and next step.
Discuss a project ↗