Editorial dates are assigned for this collection; they do not represent original publication or author approval dates. The update date records this site revision.
FIELD PERSPECTIVE · 2 MIN READ
Developed from a public 1st Key LinkedIn discussion. Read the original company post ↗
List the dependencies
Map the credential reader to local controller, lock power, network, cloud service and administrator identity. Ask which functions require each connection and what the customer can operate locally.
Rehearse a controlled failure
Under an agreed test, observe authorized entry, exit, schedules, event storage and restoration after a network interruption. Life safety and safe egress remain governed by the approved design.
Document ownership
Provide roles, support contacts, backup administration and licensing records. Outage recovery works better when IT, facilities and the integrator know their responsibilities.
Working example: The scenario below is illustrative. It describes a practical design and review method, not a completed customer project or a guaranteed result.
A working scenario
A facility loses internet while employees arrive for an early shift. The decision is whether local controllers still honor cached credentials and what changes administrators can make.
The decision to make before buying
Document local versus cloud functions, credential cache, time schedules, reader-to-controller wiring, UPS runtime, and IT recovery contacts. Establish acceptable behavior for newly revoked or newly issued credentials during outage.
A useful acceptance test
Disconnect only within an approved maintenance window. Test allowed and denied entry, event buffering, door alarms, local power loss, reconnection, and synchronization against the design.
What the owner should receive
Keep a tested outage runbook, measured limits, admin escalation, manual procedure, and recovery checklist. Do not assume every product treats offline credentials the same way.
Bring this decision table to the site walk
Use these checks to assign responsibility and collect evidence for the actual facility. Record unresolved conditions before approving the final scope.
| Scenario | Question to prove |
|---|---|
| Internet unavailable | Which cached credentials still work? |
| Revocation during outage | When does each panel receive the change? |
| Controller power lost | What is the approved door and exit behavior? |
| Connectivity restored | Are buffered events replayed with correct time? |
Questions owners ask
Which promises require product-specific proof?
Offline credential behavior, buffer duration, revocation delay, local schedule and alarm delivery vary by controller and configuration. Ask for evidence on the exact deployed models and firmware.
How should staff operate during loss of connectivity?
Use a written site procedure identifying known limits, the support contact, temporary visitor handling, critical doors and recovery checks. Preserve approved egress behavior at all times.
Project conditions and responsibilities vary. Confirm the actual scope and test plan with the owner and project team.