Ask which functions survive, not whether the system has power

During a power outage, an entrance system may keep some functions and lose others. A battery-operated lock might still accept local entry while remote control is unavailable. A camera might remain powered but lose its recording destination. An intercom screen might illuminate while the separate door-release equipment is without power. These are possible arrangements, not promises about a particular installation. The useful planning question is what occupants can still do: enter, leave, answer a visitor, release a door, view a camera or retrieve a recording. Each function has its own chain of dependencies.

Distinguish a building power outage from loss of internet service and from failure of an individual power supply. They can happen separately or together. A system that performs well during an internet interruption may behave very differently when its local network switch stops. Likewise, a utility outage may leave some devices on backup power while others immediately go dark. Write down the expected result for each important function under each relevant condition. Where the result is unknown, treat it as a question for the installer and a planned verification rather than filling the gap with a general assumption about smart equipment.

Trace power and communication from each device

Create an equipment inventory beginning at the door and following the connections inward. Depending on the design, it may include a reader, lock, intercom station, controller, power supply, network switch, router, internet terminal and recording device. Identify the power source for each component and which backup, if any, supports it. Use equipment labels and existing documentation rather than opening live enclosures. Ask the installer to fill in concealed or uncertain relationships. Two devices installed beside each other may obtain power from entirely different places, so physical proximity is not evidence of shared backup coverage.

For each promised function, trace the full path. Remote visitor answering may require the door station, local network, internet connection, service platform and the recipient's phone to be available. Local credential acceptance may depend on a controller whose behavior during a connection loss is model-specific. Request confirmation of what information is stored locally and what requires an online service. Keep a simple dependency record with the equipment inventory. It helps expose partial protection, such as a backed-up controller serving a lock power supply that has no backup, before an actual outage reveals the missing link.

Understand lock power modes without assuming exit behavior

Allegion defines fail safe as unlocking without power and fail secure as locking without power. Those terms describe a hardware response, but applying them requires knowing the actual product, configuration and point at which power is lost. They do not by themselves describe the entire door assembly or every person's ability to leave. Mechanical operation, associated release equipment and the system design also matter. Ask the responsible professional to identify the installed hardware and document both entry behavior and intended exit operation for the relevant outage conditions.

Be precise about utility loss versus loss of power at the locking device. Backup equipment may continue powering a lock after the building supply fails, so its immediate state may differ from its state after backup energy is exhausted. Any required release interfaces must also be considered within the actual design. Owners should not disconnect release wiring, change lock modes or add backup arrangements to alter behavior by trial and error. The planning task is to understand and verify the intended sequence, with qualified assessment where door safety functions are involved. A reassuring product term is not a substitute for that sequence.

Battery-operated smart locks have a separate set of dependencies

A lock using its own batteries is not necessarily powered by the building supply. Schlage states that its residential electronic and smart locks remain functional during a building power outage, while communication-dependent features may be unavailable. That statement is specific to the products covered by its guidance and assumes the lock's own power remains available. It should not be extended to all electronic door hardware. For the installed model, identify which ordinary entry methods operate locally and which rely on other equipment. A phone application and the lock itself need not fail at the same moment.

Prepare for depleted lock batteries as a separate event. Follow the manufacturer's battery guidance and know the intended alternative entry method, if provided, before it is needed. Do not assume every smart lock has a physical key or the same external power feature. For a shared property, assign responsibility for warnings and replacement rather than relying on whoever happens to notice an alert. Confirm that authorized occupants understand the supported local operation. An outage plan that exists only inside an app unavailable during the outage is difficult to use when someone arrives at the entrance.

Intercom calling and door release may fail independently

An intercom's useful service is a sequence: the visitor initiates a call, the intended recipient receives it, communication occurs and an authorized release operates the correct entrance. Different stages may use different power sources or services. Ask what happens to each stage during the planned outage conditions. A station that still displays a picture does not establish that the release mechanism can operate. Equally, a functioning local release does not prove that remote visitors can reach someone. The plan should describe the remaining capability in terms that occupants can recognize without interpreting electrical diagrams.

For a business, consider who answers when the usual workstation, desk phone or network connection is unavailable. For a residence, consider whether every intended recipient depends on the same home router or phone service. A supported alternative recipient or local answering station may help in some designs, but its behavior must be confirmed for the chosen system. If calls will be unavailable, establish an approved visitor-handling procedure and who is responsible for it. Do not solve an unanswered-call problem by propping a controlled entrance open. The operational response should preserve the property's intended access arrangements.

Separate camera operation, viewing and recording

A surveillance system has several distinct outcomes: the camera captures a scene, a viewer receives live video, and a storage destination retains footage. Losing one does not automatically mean losing all three. Where the design supports local storage, internet loss may affect remote access differently from recording. AXIS Camera Station Edge, for example, supports offline live and recorded viewing, but offline mode must be enabled in advance for each Windows user while the site is online. During offline use, Axis calls for the client to share the devices' local subnet; the client, network, cameras and required storage still need power. This is a reason to check the installed configuration, not to assume all cameras record without internet or that local storage has already been enabled.

Ask where each camera's recording actually resides and what powers that destination. If a network recorder loses power while cameras remain active, the expected recording behavior needs confirmation. If storage is inside a camera, that camera still needs suitable power and the configured storage must be working. Include illumination in the discussion: an operating camera may show a much less useful scene when normal building lighting disappears. During verification, review an actual recording made under the planned condition rather than relying on a live image or an online indicator. The required outcome is usable retained footage, if that is the system's purpose.

Size backup around a complete useful function

Choose priorities before selecting backup equipment. A property might prioritize the intended entry operation and one entrance camera, while accepting that a reception monitor will be unavailable. Another may need visitor communication throughout an outage. The designer should translate those priorities into a complete list of required loads and dependencies. An uninterruptible power supply, or UPS, can only support the equipment actually connected and suitable for it. Identify the battery-backed outlets on the selected model: some UPS units also have surge-only outlets that provide no power during an outage. Record which output serves each critical component rather than assuming every connected device has backup. A power supply's internal backup may cover a different set of devices. The labels backup and UPS do not establish identical behavior or coverage.

Ask the designer to document the selected equipment, operating demand, supported connections and required duration for the chosen function. For Power over Ethernet devices, include the equipment supplying that power as part of the assessment. Avoid simply adding together camera labels while overlooking the recorder and network equipment. Also consider what happens at transfer, when multiple devices start and when backup is nearly exhausted. If a generator forms part of the building design, coordination with the responsible electrical professional is needed; it should not be assumed to eliminate every interruption or support every security circuit.

Treat runtime as a maintained capability

Backup duration depends on the selected equipment and its actual load, battery condition and operating environment. Schneider Electric's APC guidance explains that increasing load reduces available runtime and that battery aging and temperature affect performance. A displayed estimate or an old commissioning result is therefore not a permanent promise. Ask which assumptions support the proposed duration and how it will be checked using the manufacturer's procedures. Adding equipment after installation should trigger a review of the backup assessment, even when the extra device appears small compared with the overall system.

Assign responsibility for battery alerts, inspection records and replacement planning. Record when backup equipment and batteries were installed and which devices they support. Do not use repeated deep discharge as a casual test method; APC warns that unnecessary runtime calibrations can shorten battery life. A professional maintenance plan should choose appropriate checks for the model and operational need. Include recharge in the outage plan as well. After one interruption, a second outage may occur before backup energy has fully recovered. Staff need to know when the system has returned to normal power but has not yet regained its intended reserve.

Give occupants a workable offline procedure

Technical backup is only part of continuity. Decide who checks the entrance, who receives fault notifications and who can provide authorized assistance if the normal entry method is unavailable. Keep the procedure accessible in a form that does not depend entirely on the affected network. Describe supported entry methods, the contact role and how visitors are handled. Avoid including secret credentials in a broadly circulated notice. In a multi-occupant building, instructions should be understandable to someone who has never seen the equipment cabinet and is arriving after the outage has already begun.

Consider different times and users. The person normally at reception may be absent in the evening, a delivery may arrive during a transition, or an occupant may have difficulty using the alternative method. Work through these circumstances with the people responsible for the property before finalizing the plan. Temporary staffing or an authorized escort procedure may be appropriate for some sites. Any response must preserve the intended exit arrangements and avoid improvised modifications to hardware. A useful plan explains who takes action and when, rather than telling occupants only that backup power has been installed.

Verify the design through a managed outage exercise

Arrange any outage exercise with the professionals responsible for the affected systems and the property's authorized representative. Define which condition will be simulated, what services will be interrupted and how normal operation will be restored. Tests affecting door release, safety interfaces or electrical equipment require the relevant qualified coordination. Owners should not create an outage by pulling unfamiliar wires or switching off an unidentified circuit. The aim is a controlled demonstration of the documented design, with occupants informed and an agreed response if observed behavior differs from the expectation.

During the exercise, record the actual tasks that succeed: intended entry, exit operation, visitor calls, authorized release, live viewing and newly recorded footage where applicable. Test internet loss separately from utility loss when the scope calls for both, because they answer different questions. Observe notifications and whether the right person receives them. A brief transfer test does not establish the full runtime; any duration assessment should follow an appropriate plan. Document deviations plainly, including a feature that never worked during the exercise. An incomplete result should lead to a defined correction rather than a general statement that the backup passed.

A hypothetical outage with partial protection

Imagine a small property whose owner believes the entire entrance system is protected because the network cabinet has a UPS. During a professionally managed exercise, the cameras and recorder remain available, but the intercom stops calling. The equipment inventory reveals that an essential intercom component receives power outside the protected cabinet. Meanwhile, the door hardware follows its documented behavior, and the intended exit operation is separately verified. This is a hypothetical example of a missing dependency, not a prediction that intercoms use a separate supply or that any particular lock will behave the same way.

The owner and designer can now make an informed choice: support the missing intercom dependency with an appropriate design, or formally accept the interruption and provide a workable visitor procedure. If backup coverage changes, the complete load and duration assessment needs updating. The next exercise should confirm the revised call sequence as well as the functions that previously worked. This example shows why a powered cabinet is an incomplete acceptance criterion. The useful result is a documented set of services that remain available, with clearly understood limits and responsibilities for those that do not.

Plan recovery as carefully as the loss of power

When utility power returns, confirm that the devices and services have actually recovered. Equipment may restart at different times, and a lighted screen is not proof that every connection has re-established. Check intended door operation, visitor calls and authorized release, then verify current camera views and new recordings. Review the relevant logs for the interruption and any remaining faults. If recordings contain a gap, document it accurately rather than assuming footage will appear later. Recovery should be judged by the restored user tasks, just as backup was judged by the tasks it maintained.

Update the outage record with what failed, what remained available, the observed duration and any action taken. Confirm backup charging or other recovery status through the supported interface and assign unresolved alerts to a responsible person. Retain the inventory, expected behavior and exercise results together so a future equipment change can be assessed against them. A new router, power supply, camera or door component may alter a previously understood dependency. Review the plan when those changes occur and after real outages reveal new information. The objective is an entrance system whose behavior is known before people must depend on it in the dark.