Access control during network outages: an acceptance checklist

Before accepting an access-control system for an office or factory, test what happens when connectivity fails. A successful door opening is not enough: establish which permissions are enforced, which updates cannot reach devices and how events are reconciled after recovery. This checklist proposes acceptance tests, not a claim that every device configuration has passed them.

Separate internet, local-network and power failures

An internet outage may leave a local server and devices connected. A device-to-server disconnection is a different test, and a power failure requires a separate assessment of controllers, locks and backup supplies. Record exactly which connection is interrupted. Agree a safe test window and recovery procedure; do not casually test emergency exits or critical operational doors.

Understand local decisions and revocation limits

Duall Master's offline-first architecture places access decisions at the device using synchronized data and rules. The server manages policy, synchronizes devices and aggregates events; it does not decide each access attempt. A disconnected device may still apply old permissions until it receives an update. Newly granted rights may also be unavailable. A saved server configuration is not proof of device delivery.

Test the following scenarios

• Previously synchronized valid permissions work at the correct door and schedule.
• An unauthorized test identity remains denied unless a separately approved safety mode applies.
• Stored schedules and expiry limits behave correctly with verified device time.
• Rights revoked during disconnection are tested before and after reconnection; document the actual exposure window.
• New permissions are checked at the disconnected door and again after synchronization.
• Allowed and denied test events are reconciled after recovery for missing or duplicate entries and incorrect timestamps.
• Internet-only failure is tested separately from device-to-server failure, including any externally dependent workflows.
• Recovery confirms connectivity, updated permissions and event reconciliation; power and life-safety tests remain a separate approved scope.

Make handover evidence operationally useful

Record device model, firmware, configuration, interruption point, timestamps, expected and observed behavior, evidence and the person signing off. Ask the supplier to document local event capacity, full-buffer behavior and synchronization confirmation for the chosen hardware. Set recovery targets before purchase rather than extrapolating from a small demonstration.

Duall Master is a building operations and security command platform with peer modules for Access Control, Visitor Management, Attendance, Parking, Video Management and Video Intercom. Passing one offline door test does not validate every connected workflow. Request a demonstration based on your site plan, network design and acceptance scenarios.