Four-Door Access Control Site Survey Checklist

Start with a Door-by-Door Inventory

A four-door access control project begins with a clear inventory of each entrance. Assign a stable identifier to every door and record its physical hardware: door type, frame, lock, hinges, and any existing access equipment. Note the door's function—main entrance, staff door, equipment room, or emergency exit—and who uses it.

Document the current mechanical condition. A door that binds, sags, or has a misaligned strike will cause problems regardless of the electronic system. Check that the lock operates smoothly and that the door closes fully without assistance. These details affect reader placement, lock selection, and user experience.

• Assign a unique ID to each door (e.g., D01, D02).
• Record door material, swing direction, and dimensions.
• Note existing lock type and its power requirements.
• Identify any fire-rated or emergency exit doors.

Map the User Workflow for Each Door

For each door, define who should have access and when. List user groups: employees, visitors, contractors, or residents. Determine the credential type—card, PIN, biometric, or mobile—and whether different doors require different credentials.

Specify the access decision flow. Where are permissions stored? Which component grants or denies access? For a four-door system, you may have a central controller managing all doors, or each door may have its own intelligence. Clarify this before selecting hardware.

Consider special cases: first-time visitors, after-hours access, temporary permissions, and emergency overrides. Write down the expected behavior for valid, invalid, and expired credentials. This becomes your test plan later.

• List user groups and their access levels per door.
• Identify the credential type(s) to be used.
• Define normal, denied, and emergency access scenarios.
• Document who administers permissions and how changes are made.

Inspect Wiring and Connectivity Paths

Survey the cable routes from each door to the controller location. Measure distances and note obstacles such as walls, ceilings, and existing conduits. Determine whether new cabling is needed or existing infrastructure can be reused.

Check the type of cable required for readers, locks, and sensors. For example, Wiegand readers typically use multi-conductor cable, while RS485 devices may use twisted pair. Confirm the maximum cable length for the chosen interface to avoid signal degradation.

If the system will use Power over Ethernet (PoE), verify that the network switch supports the required power budget for all connected devices. A network port alone does not guarantee PoE availability; check the switch specifications and per-port limits.

• Measure cable distances from each door to the controller.
• Identify existing conduits and potential obstacles.
• Confirm cable type and length limits for readers and locks.
• Check PoE switch capacity if PoE devices are planned.

Assess Power Requirements Separately

Do not assume that reader power and lock power are the same. Each component has its own supply requirements. Record the voltage and current needed for each reader, controller, and lock. For example, a reader may require 12V DC, while a magnetic lock may need 24V DC.

Check the relay contact rating of the controller or reader. A relay rated for 30V/1A does not mean the device itself should be powered at 30V. Keep supply and contact ratings separate in your documentation.

Plan for power backup. Decide which doors must remain operational during a power outage and what backup solution is needed—UPS, battery, or fail-safe/fail-secure lock behavior. Emergency exit requirements must be addressed with the building's fire safety plan.

• List power requirements for each device (voltage, current).
• Separate reader power from lock power in the design.
• Verify relay contact ratings for lock control.
• Define backup power strategy and fail-safe/fail-secure behavior.

Evaluate Environmental and User Conditions

Visit each door at different times of day to observe lighting, temperature, and traffic. For outdoor entrances, note exposure to rain, sun, and dust. These factors influence device selection and mounting.

Consider the user's approach. Is there enough space to present a credential? Is the reader at a comfortable height? For video intercoms or face recognition terminals, check camera angle, screen readability, and ambient noise.

Test with representative users if possible. Observe how they interact with the proposed location. A reader placed too high or too far from the door can cause frustration and delays.

• Record lighting conditions and temperature range at each door.
• Check for weather exposure and need for protective enclosures.
• Measure mounting height and approach space for readers.
• Observe user flow during peak times.

Document Network and Integration Points

Identify where the controller will be located and how it connects to the network. For a four-door system, a central controller may be installed in a wiring closet or IT room. Ensure there is adequate space, power, and network connectivity.

If the system integrates with other platforms—HR database, visitor management, or building automation—document the data exchange requirements. What information is sent, and in what format? Confirm compatibility with the host system before finalizing hardware.

Plan for future expansion. Will additional doors be added later? Choose a controller with spare capacity if needed. Also consider remote management capabilities and how firmware updates will be applied.

• Locate controller placement and network drops.
• List integration requirements with other systems.
• Check for spare capacity on the controller.
• Define remote access and maintenance procedures.

Create a Test and Acceptance Plan

Before installation, write down the acceptance criteria for each door. What must happen for the system to be considered working? Include tests for valid credentials, denied access, door forced open, and network failure.

Plan a pilot installation on one door first. Use the actual hardware and firmware that will be deployed. Test all scenarios and document the results. Only after the pilot passes should you proceed with the remaining doors.

Prepare a handover package that includes wiring diagrams, configuration settings, user manuals, and support contacts. Train the operators on daily use and troubleshooting. Schedule periodic reviews to ensure the system continues to meet requirements.

• Define acceptance criteria for each door.
• Pilot test one door before full rollout.
• Document all test results and configurations.
• Provide training and handover documentation to operators.