
Locks and controllers that enforce dated credentials locally, buffer entry records, survive power and signal loss, and sync when connectivity returns.
Many doors that most need access control sit where connectivity is worst: telecom shelters, remote utility sites, construction containers, agricultural stores, transit cabinets and the plant rooms of older buildings. An offline access control solution inverts the usual assumption that a door checks every credential against a server: locks and local controllers hold the schedule and credential set themselves, enforce dated codes and windows without a live link, buffer entry records, and synchronize when a connection is available. The design is explicit about what changes need a connection, how long credentials remain valid offline, and how a device that has been offline too long behaves. The telecom sites guide and construction guide cover the field conditions, while the cloud solution explains the online side this complements.
| Local decisions | Credentials and windows are enforced at the lock or controller, not by a distant server on every entry |
| Dated codes | Technician and visitor codes carry expiry dates, so access ends on schedule even without a connection |
| Buffered records | Entry events are stored on the device and synchronized when connectivity returns |
| Power resilience | Battery and power-loss behaviour is specified for doors without reliable mains or network |
| Stale-device rules | How an offline device behaves beyond its sync limit is defined rather than discovered |
| Physical rating | Outdoor and cabinet hardware is rated for weather, dust and tampering at the door |
| BOM shape | Offline locks and controllers by site, credential strategy, sync plan and field spares |
Sites with routine outages or no infrastructure choose local-schedule devices; connected urban doors may treat offline capability as an emergency fallback only.
| Dimension | Online-dependent locks | Offline-capable local schedules |
|---|---|---|
| Network outage | Door cannot decide or fails open | Normal dated credentials keep working |
| Remote sites | Impractical without infrastructure | Deployable to shelters and cabinets anywhere |
| Record capture | Events lost when offline | Buffered and reconciled on reconnect |
| Expiry | Dead codes require a live revoke | Codes expire on their own date at the lock |
| Maintenance | Depends on signal for updates | Syncs on technician visit or scheduled connection |
| Typical fit | Reliably connected urban doors | Telecom, utility, construction and field sites |
The shelter, cabinet or container door is the decision point; the controller choice depends on how often a sync will realistically occur.
| Opening | Typical door | Lock approach |
|---|---|---|
| Equipment shelter | Remote telecom or utility shelter door | Local-schedule lock with dated technician codes and weather seal |
| Street cabinet | Small metal roadside cabinet | Compact rated lock buffering events between service visits |
| Construction container | Site office or tool container | Award-dated codes valid for the project window |
| Plant / MEP room | Mechanical or electrical room offline patch | Controller holding schedules through building network gaps |
| Perimeter gate | Remote yard or energy-site gate | Offline-capable operator with battery and free-egress design |
| Service vault | Underground or shielded access point | High-seal hardware with long credential and battery life |
This example illustrates a typical configuration, not a specific customer project. Site count, visit frequency and climate drive the list.
| Component | Typical logic | Notes |
|---|---|---|
| Offline locks | Local-decision devices per shelter, cabinet or container | Dated credentials with defined offline validity |
| Controllers / sync | Gateway or portable sync strategy per site cluster | Reconciliation cadence matched to visit frequency |
| Power scope | Battery life and power-loss behaviour | Service intervals planned for remote travel distance |
| Stale-device policy | Maximum offline window and resulting door behaviour | Defined and documented before field deployment |
| Field spares | Sealed locks and batteries carried regionally | Swap by named technicians under the current MOQ policy |
The lock or a local controller holds the credential schedule — which dated codes and windows are valid — and evaluates every entry against that store at the door, so it grants the right technician and rejects an expired or unknown code with the network entirely absent. New credentials are provisioned ahead of a visit through a scheduled connection or a portable sync, and events are buffered on the device until they can reconcile. The design states the maximum offline window: after a defined period without sync, the device follows a chosen policy rather than behaving unpredictably. Choosing devices starts from how often someone will realistically visit or connect, not from the datasheet’s headline.
Offline credentials are issued with an end date and door scope, so a contractor code expires at the lock on the planned date even if no revocation message ever arrives, which is the core safeguard for field sites. Immediate revocation between syncs works only when a connection happens; for high-risk doors the offline validity window is kept short and paired with physical follow-up by a named technician. This is why sensitive field sites avoid issuing long-lived offline codes to rotating contractors and instead reissue per work order. The trade-off between convenience and revocation speed is made deliberately per door rather than left at default settings.
Each device timestamps and stores entry and tamper events in its local buffer and uploads them on the next scheduled connection or technician sync, where they reconcile into the central record for audit and incident review. Buffer capacity is specified against the longest realistic gap between visits, so a cabinet serviced quarterly is not chosen with a buffer sized for daily connections. Gaps or devices that have been offline beyond policy are flagged for investigation. Operations reports distinguish between real-time and reconciled-after-the-fact evidence so investigators understand what they are reading. The pilot cluster runs a full disconnect-and-reconnect cycle to confirm no events are duplicated or lost.
Offline locks are selected around battery life under the expected use and temperature, with service intervals matched to the cost and distance of reaching the site, because a battery change at a remote shelter is expensive. Low-battery state is reported at sync, and power-loss behaviour preserves both security and any required life-safety function; gates retain free egress regardless of power state. Where mains exists but is unreliable, controller power conditioning and backup are specified during the survey. Extremely remote or cold sites may prioritize ultra-low-power mechanical-code devices over electronic readers, a decision made per door rather than standardized across the estate.
The BOM lists each shelter, cabinet and container with its real connectivity and power conditions, the offline-capable lock or controller, sync method, maximum offline window and regional spares, with MOQ and lead time confirmed in writing per quotation. Teams pilot one route cluster through provisioning, a full offline period and reconciliation before scaling. Send the site list, measured signal conditions, technician visit frequency and climate, and the quote maps each line to a field architecture rather than connected-door pricing.
Send the site list, measured signal conditions and visit frequency — receive a field-architecture BOM with written MOQ and lead-time terms.
Discuss your project (RFQ)Project configurationsLast updated: October 31, 2026 · Reviewed by the Smart Lock Factory editorial team