Stop Calling Every Site Open: Build a Facility Operating Mode Register

By Jared Mastroianni

• August 31, 2026
• 12
• Business Storage, Guides, Self Storage

A schedule says what a self-storage facility expects to offer. An operating mode says what the property can actually support now, who owns the next decision and when the state must be reviewed.

At 7:05 p.m., a self-storage dashboard can show a facility as open while the office is empty, customer gate access remains enabled, a remote team is answering calls and an elevator is unavailable. None of those facts is necessarily wrong. Together, however, they make “open” almost useless as an operating instruction.

The employee handling a call needs to know whether a move-in can be completed. The regional manager needs to know whether the property requires intervention. A vendor needs to know who can authorize entry. An automated workflow needs to know whether it may continue, route to a person or stop. A customer needs an accurate statement about the service that matters to that customer.

One binary field cannot carry all of that meaning.

A multi-location operator can close the gap with a facility operating mode register: a time-bounded record of how a property may operate now. The register does not replace office hours, access schedules, an incident record or an emergency plan. It joins those records into a usable operating statement.

Five Modes Are Usually Enough to Start

The first version should be small enough that a facility team can use it without a glossary. A practical starting vocabulary is:

1. Staffed normal: The office is staffed as planned, approved customer services are available and no material operating restriction is active.
2. Remote supported: No local employee is present, but named remote coverage is active for a defined set of services and escalations.
3. After-hours customer access: The office and staffed services are closed, while customer access remains available under the property’s approved schedule and restrictions.
4. Degraded operations: The facility remains partly operational, but at least one consequential service, system or area is restricted and the restriction has an owner.
5. Closed or restricted: Customer access or facility operations are suspended within a defined scope. The record must say whether the restriction applies to the entire property, one building, one service or one customer group.

These are authored operating categories, not industry standards. A portfolio can rename or subdivide them, but each mode needs a stable meaning. “Remote,” for example, should not mean both “a call center is available” and “all services can be delivered without local staff.”

A facility can also have more than one service state inside its current mode. During degraded operations, ground-floor access may remain available while an elevator-served area is restricted. The register should preserve that detail instead of flattening the whole property to open or closed.

A Mode Is Not a Schedule or an Alarm

Office hours describe an expected calendar. Access hours describe when an authorized customer is ordinarily permitted to enter. Service hours describe when a named service is offered through a named channel. Those schedules remain useful, but they do not prove that the expected service is available at this moment.

An alarm is also not an operating mode. A disconnected camera, missed opening check or door fault is evidence that may trigger a review. It does not automatically establish what the facility can support, which restrictions apply or who has authority to change the state.

The mode record is the controlled conclusion after those inputs are evaluated. It should say:

• which facility and scope the mode covers;
• when the mode became effective, including the local offset;
• who declared it and under what authority;
• what evidence triggered the change;
• which customer, office and rental services remain available;
• which systems or areas are restricted;
• who owns response and revalidation;
• what communications have been issued; and
• what evidence is required before normal operation returns.

RFC 3339 provides a widely used Internet timestamp format that includes a date, time and offset.¹ A value such as 2026-08-31T18:30:00-04:00 is more useful than “Monday evening,” but time syntax alone does not establish that the clock is accurate or that the person making the entry had authority.

Give Every Transition a Trigger and an Owner

Mode changes should be deliberate. A regional manager should not discover a degraded property by reading yesterday’s notes, and an automated system should not restore “normal” merely because one alarm cleared.

Define the trigger classes that can open a mode review. Typical self-storage examples include:

• a planned transition, such as the end of staffed office hours;
• a staffing transition, such as an approved remote-coverage period;
• a service condition, such as an elevator or access lane becoming unavailable;
• a safety or emergency condition governed by the property’s approved plan;
• a technology condition that limits monitoring, access administration or communications; and
• a management decision that restricts a service, area or customer activity.

For each trigger, identify who may declare the mode, who may expand a restriction and who may return the facility to normal. Those may be different roles. A remote support representative might record a customer report and route the condition, while only an authorized property or regional owner may change customer access.

FEMA’s Continuity Guidance Circular is broad public- and private-sector guidance for sustaining essential functions during disruption. It separates essential functions, dependencies, delegations of authority, communications, continuity records and reconstitution.² A private self-storage operator is not adopting a federal continuity program by using those ideas. The useful transfer is narrower: an operating state needs an owner, bounded authority, current information and a defined path back.

Treat “Degraded” as an Operating Decision

Degraded operation is where the register earns its place.

Without a controlled mode, teams tend to improvise one of two conclusions. The first is too optimistic: the property is open because the gate still moves. The second is too broad: the property is closed because one consequential component is unavailable. Both can misstate the actual operating boundary.

A degraded-mode record should answer five questions:

1. What remains available?
2. What is restricted?
3. Who is affected?
4. What temporary control is active?
5. When will the decision be reviewed again?

Consider a loading-area door that has been removed from service. The mode record might preserve customer access to unaffected areas, restrict the loading zone, identify the approved alternate route, assign the facility owner for local checks and set a revalidation time. It should not diagnose the equipment, declare it safe, authorize an untrained repair or predict a return time without evidence.

NIST Cybersecurity Framework 2.0 distinguishes continuous governance and monitoring from incident response and recovery. It also states that incidents are declared when adverse events meet defined criteria and that recovery actions are selected, scoped and prioritized.³ The framework addresses cybersecurity, including information technology, operational technology and related systems. It does not define facility operating modes. Its value here is the disciplined separation among a signal, a declared condition, a response and a verified recovery.

NIST SP 800-53 similarly separates contingency planning, incident handling, physical-access monitoring and recovery controls.⁴ That catalog is designed for security and privacy risk management, not as a self-storage rulebook. It reinforces one important design choice: a portfolio should not let a monitoring signal, response action and recovered state collapse into one field.

Emergency Plans Take Precedence

An operating-mode register is not an emergency action plan and should never be used to soften an emergency instruction.

Where Occupational Safety and Health Administration standard 29 CFR 1910.38 applies, an emergency action plan must address specified elements such as reporting an emergency, evacuation procedures, accounting for employees, duties for employees who remain for critical operations, and the roles employees may contact for more information.⁵ The standard also requires review when a covered employee’s responsibilities or the plan changes.

The mode register can point to the approved plan, record that the plan is active and state which ordinary operations are suspended. It should not paraphrase evacuation routes, rescue duties or other life-safety instructions into a dashboard row. Emergency services, local authorities and approved site plans control within their actual scope.

A Fictional Five-Site Review

Consider Eastline Storage Group, a fictional five-facility portfolio created only to demonstrate the method.

At fictional Eastline Harbor, the facility opens in staffed normal mode after the manager completes the approved opening checks. The mode record confirms staffed office service, scheduled customer access and a next review at the end of the staffed period. It does not certify every device or area as defect-free.

At fictional Eastline Grove, an approved manager absence activates remote supported mode. Customer access remains on its normal schedule. New in-person services are unavailable, a regional employee owns escalation and a named local verifier can inspect conditions that cannot be confirmed remotely. The mode does not imply that the remote team may perform every local task.

At fictional Eastline Junction, the office closes and the property changes to after-hours customer access. The transition is planned rather than incident-driven. A current access schedule, monitored-system state and after-hours response route are referenced in the record.

At fictional Eastline Orchard, an elevator report triggers degraded operations. The report is not treated as a technical diagnosis. Upper-level move-ins are held, unaffected access remains available, a qualified service route owns the equipment assessment and the regional operator must revalidate the mode at a stated time.

At fictional Eastline Bay, the approved emergency plan is activated and the property enters closed or restricted mode. The register points to the governing plan and records the suspension of ordinary services. It does not reproduce emergency instructions or claim the property is safe to reenter.

Every facility, event, role, timestamp, system condition and operating result in this example is fictional. No real modSTORAGE, Facily.ai, customer, property, employee, vendor or deployment is represented.

Put the Register Into the Daily Operating Rhythm

Start with one week of operating transitions, not a portfolio-wide software project.

First, define the five modes in plain language and list the services each mode ordinarily permits. Second, name the roles that may declare, restrict and release each mode. Third, create the register with one current row per facility and an append-only history of superseded rows. Fourth, test three common transitions: staffed to after-hours, staffed to remote supported and normal to degraded. Fifth, review whether customers, staff and central teams received the same usable message. Sixth, confirm that returning to normal required evidence rather than elapsed time alone.

Revalidation belongs in the mode record. A routine after-hours mode may expire at the next scheduled staffed opening. A degraded mode may require review every hour, every shift or after a named piece of evidence arrives. The interval is a local decision based on consequence and operating context, not an industry benchmark.

The practical register accompanying this article uses clear fields for facility, mode, authority, trigger, service state, restrictions, owner, communication, revalidation and return criteria. It includes one blank template and fictional teaching rows. It should be adapted to the operator’s actual plans, systems, authority and jurisdiction.

The goal is not another status dashboard. It is a controlled answer to a basic operating question: What can this facility support now, and who is responsible for the next decision?

Sources and notes

1. Internet Engineering Task Force, RFC 3339: Date and Time on the Internet: Timestamps, July 2002. It defines a timestamp syntax; it does not establish clock accuracy, record integrity or operating authority. ↩
2. Federal Emergency Management Agency, Continuity Guidance Circular: 2018 Continuity Guidance Circular (2024 Update). This is broad continuity guidance, not a self-storage safety plan, legal delegation, staffing rule or compliance standard. ↩
3. National Institute of Standards and Technology, The NIST Cybersecurity Framework (CSF) 2.0, February 2024. The framework addresses cybersecurity risk management; it does not validate the operating-mode method or establish facility practice. ↩
4. National Institute of Standards and Technology, SP 800-53 Rev. 5: Security and Privacy Controls for Information Systems and Organizations, including Release 5.2.0 dated August 27, 2025. The control catalog is flexible and tailorable; citation does not establish selection, implementation, effectiveness, compliance or certification. ↩
5. Occupational Safety and Health Administration, 29 CFR 1910.38: Emergency Action Plans. Applicability depends on the governing standard and workplace facts; the operating-mode register is not a substitute for an emergency action plan. ↩