School and Campus Access Control: Gates, Doors, Visitors and Emergency Egress

School and campus access control must support daily movement, visitors and emergency arrangements without creating obstacles to escape. A campus can include public reception, teaching spaces, service areas and shared facilities with different schedules. NZ specifiers should coordinate the security design with the site's approved access, fire and evacuation arrangements.

Map campus boundaries and use periods

Identify gates, public entrances, staff areas and facilities used by external groups. Separate term-time, holiday and event schedules. Decide who owns permission changes for hired spaces and contractor visits. A single campus-wide unlock schedule may expose areas that are not in use. Keep the boundary plan and the opening schedule together so operational staff understand what changes when a period starts or ends.

Design visitor arrival and verification

Create a clear visitor route to the approved reception or answering point. Define who verifies a caller, authorises release and provides temporary access. A video call assists a decision but does not establish a complete visitor-management process. Confirm after-hours arrangements for community use. Avoid a shared permanent visitor code unless the approved operational requirement and control process specifically justify it.

Separate emergency actions

Evacuation, lockdown and routine securing are different actions. Have the responsible building and emergency-planning professionals define required behaviour for each opening and emergency condition. Do not assume a command to lock every door is appropriate or that it preserves escape. Document priority between fire interfaces, mechanical release and software commands. Test only under an approved coordinated procedure with the relevant specialists.

Preserve accessibility and escape

MBIE guidance on D1 access routes and C4 movement to a place of safety is relevant to the design review. Check reachable controls, opening method, clear routes and the approved exit path. A fail-safe label on a lock does not settle the complete door compliance question. Review the mechanical assembly and interfaces with the project team. Keep evidence of the agreed design and specialist acceptance.

Manage staff, contractors and shared users

Allocate permissions by role and area, with expiry for temporary access. Include staff movement between buildings and the people who maintain the system over school holidays. Confirm who removes access when employment or a contract ends. Test a revoked credential after it reaches each relevant controller. Avoid using access events as a guaranteed emergency occupancy list where unrecorded movement can occur.

Commission workflows rather than isolated doors

Test ordinary staff access, visitor assistance, community use and approved emergency modes. Check faults and recovery across buildings with separate networks or power supplies. Record operator permissions and the interface owner for each emergency action. Train staff in the approved procedures and keep a controlled change process. An installed system should support the campus's documented plan, not create a new unreviewed plan through software settings.

Apply the design to the actual project

Build a campus action matrix for routine access, visitor release, out-of-hours use and each approved emergency mode. Allocate an owner to every action and record the expected result for each affected opening. Review the matrix with the people responsible for fire, accessibility and evacuation arrangements. Do not import a generic lockdown template into controller programming without that review. Keep the approved design and software settings traceable to each other.

Use staged commissioning to avoid disrupting occupants or creating ambiguous emergency signals. Test ordinary permissions first, then perform specialist-approved emergency and recovery exercises under the agreed plan. Include more than one building where the system spans separate power or network paths. Confirm the answering and response arrangement for visitors outside staffed hours. Train designated staff in their actual operator role and retain a controlled procedure for holiday and community-use changes. A campus system needs a maintained operational plan as well as functioning readers and locks.

Separate security permissions from safe escape

Build permissions around roles and areas, then apply schedules and expiry dates. Give contractors time-limited access and allocate an owner to remove it. Use named operator accounts, restrict configuration rights and keep an audit trail of administrative changes. Test a valid credential, an expired credential and a credential without the required area permission. Include a revoked credential after synchronisation. Those tests reveal errors that a single successful presentation cannot show.

Entry control must be coordinated with the building's approved escape and accessibility arrangements. Do not treat a software unlock command as proof of acceptable emergency egress, and do not add an interlock that delays escape without the required design approval. Document the mechanical exit path, release devices and interfaces, with responsibility assigned to the relevant building professionals. New Zealand Building Code guidance on access routes and movement to a place of safety provides the starting point for the project's design review.

Commissioning acceptance checklist

Agree the expected result before testing. Use the installed configuration and retain evidence of each outcome, including a failure that must be corrected. The following checks supplement the exact manufacturer procedures and the approved project design.

Repeat affected checks after a material equipment, software or site change. Keep the test record with the as-built schedule so the next maintainer can understand which configuration passed and which assumptions still need review.

Equipment candidates and specification checks

These are relevant active catalogue candidates for a project review, rather than a universal recommendation or a promise of immediate stock. Use the full product page and current manufacturer information to confirm the supplied variant and its role in your design.

• RBH-IRC-2000 - RBH Integra32 2-Door Controller (UL Listed) includes Enclosure with 13.8VDC, 2A power supply. Confirm the exact supplied configuration, relevant interfaces and installation requirements before including it in the equipment schedule.
• RBH-BFR350 - Blueline Fingerprint Reader, PIN Keypad and Card Reader. Confirm the exact supplied configuration, relevant interfaces and installation requirements before including it in the equipment schedule.
• E12S - Akuvox Compact SIP Video Door Phone. Confirm the exact supplied configuration, relevant interfaces and installation requirements before including it in the equipment schedule.

Review the relevant Essential Security Supplies equipment range alongside the intended workflow. For further context, read our related installer guide.

Frequently asked questions

Is lockdown the same as evacuation release?

No. They are different emergency actions and need an approved opening-by-opening design.

Does a fail-safe lock prove an escape route complies?

No. The complete door assembly, release path and building design must be reviewed.

Can access logs guarantee a campus headcount?

No. Unrecorded exits, tailgating and outages can make logical events differ from actual occupancy.

Primary references and technical scope

Use the primary manufacturer or technical reference for the claims it covers. General design guidance does not replace the selected product's installation manual. Confirm current firmware, model variants and the approved project requirements before ordering or commissioning.

Get specification help from Essential Security Supplies

Send your site layout, equipment schedule, intended workflow and any existing model details to Essential Security Supplies for specification help and a project quotation. Identify the functions that must be demonstrated and the interfaces owned by other contractors. Our enquiry route supports a documented equipment review without publishing prices or assuming unverified compatibility.