When the Gate Won’t Open: A Safe Access-Incident Playbook for Self-Storage Managers

By Jared Mastroianni

• October 2, 2026
• 8
• Business Storage, Guides, Self Storage

Deck: A gate complaint can be a customer-specific access issue, a communications failure or a moving-equipment hazard. The manager’s job is to protect people, establish the boundary, preserve facts and make a controlled return-to-service decision.

Access incidents are managed at the property boundary: protect people, record the observed state and escalate technical work. AI-generated editorial image; not a documentary record of a facility, employee, customer, gate system or incident.

“My code worked yesterday, but the gate will not open” sounds like a simple service call. It is not yet a diagnosis.

The problem could be limited to one credential. It could affect an access schedule, keypad, communications link, vehicle detector, power supply or gate operator. The gate may have received an authorization signal without completing a safe movement. A customer may also be describing the wrong entrance, a closed access window or a condition outside the gate system entirely.

The manager’s first responsibility is not to guess correctly. It is to keep a customer-service problem from becoming a vehicle, pedestrian or equipment incident while the right facts are collected.

Protect the Movement Zone First

When a customer is waiting, pressure builds quickly. That is exactly when the boundary around the gate matters most.

Keep people out of the gate’s travel and entrapment areas. Do not ask a customer to walk through a vehicular gate, stand beside the moving assembly or hold a sensor. DASMA’s gate-operator guidance says pedestrians must use a separate entrance when the operator is for a vehicular gate.¹ Its property-owner checklist also calls for pedestrian access that does not bring a person into contact with the moving gate through its full travel.²

Stop normal cycling if there is visible damage, abnormal movement, an unusual sound, an exposed component, a failed safety device, a collision, a person inside the movement zone or any uncertainty about safe operation. Use the site’s approved restriction, emergency and escalation procedure. A manager should not defeat a sensor, reach into the mechanism, force the gate, open an electrical enclosure or improvise a release.

A powered gate is moving machinery, not a stubborn office door. UL Solutions identifies fire, electric shock, casualty and entrapment among the hazards addressed by UL 325 and emphasizes that safe use ultimately depends on correct product selection, installation, use and maintenance.³ ASTM’s active F2200-24 standard covers construction of automated vehicular gates and identifies UL 325 as the companion operator standard.⁴ Those standards do not turn a frontline manager into a gate technician. They reinforce the need for a clear operating boundary.

If someone is injured, trapped or in immediate danger, use emergency services and the site emergency plan. Customer access, asset security and equipment uptime remain important, but they do not outrank life safety.

Establish the Incident Boundary

Once the area is stable, answer four questions without entering a repair mode:

1. Who is affected? One customer, several customers, employees, vendors or everyone?
2. Which direction is affected? Entry, exit or both?
3. Which layer appears involved? Credential, schedule, reader or keypad, communications, power, gate movement or unknown?
4. What was directly observed? Indicator shown, sound heard, movement seen, time recorded and message displayed.

Use comparisons that are already authorized by site procedure. For example, a manager may check whether multiple valid users report the same symptom, whether the approved access hours are in effect, whether a normal status indicator is present or whether the same problem appears at both entry and exit. Do not create a new credential, change a schedule, reset hardware or operate a manual release merely to narrow the diagnosis unless that exact action is authorized and trained for the site.

DASMA’s remote-control troubleshooting guide notes that intermittent or nonresponsive operation can have several causes and directs users back to manufacturer instructions or a qualified dealer when the issue is not bounded.⁵ That is the useful lesson for facility operations: the same symptom can arise from different layers. Record the symptom; do not promote a guess into a fact.

Separate Authorization From Passage

An access system can say “granted” without proving that a vehicle passed through the gate. The keypad can accept an entry while the operator fails to move. The gate can open while the customer remains outside. A remote command can be sent without confirmation that the physical state changed.

Use separate states in the incident record:

• Credential state: valid, denied, expired, unknown or not checked.
• Command state: accepted, rejected, error, unknown or not checked.
• Gate state: open, closed, stopped, moving abnormally, damaged or unobserved.
• Passage state: completed, not completed, unknown or not applicable.
• Operating state: normal, restricted, held open under authorized procedure, out of service or awaiting qualified review.

This prevents a common closure error: “The code worked, so the incident is resolved.” A successful credential check is evidence about one layer. It is not evidence that the full access path worked safely.

Create One Controlling Record

Start one incident record before the details scatter across texts, calls and vendor messages. Give it an ID and capture the facility, exact gate, report time, reporter channel, affected direction, observed condition, safety boundary, temporary operating state, escalation owner and next review time.

Preserve only information necessary for the response. Do not put a customer’s full access code, payment detail, lock status, unit inventory or other sensitive record into a general incident note. If an authorized system lookup is needed, record the result and governing record reference rather than copying unnecessary personal data.

Photographs can document visible damage or lane conditions when policy permits and the frame excludes people, access data and security-sensitive details. Save relevant operator messages and vendor ticket numbers. Record the device time zone. If a later review is needed, “Friday morning” is weaker than an exact timestamp tied to the facility.

The record should also preserve what was not done: no repeated cycling, no bypass, no schedule change, no manual release or no technical inspection. Those boundaries help the next person understand the condition without reconstructing it from silence.

Make a Bounded Customer Promise

Customers need a clear next step, not a speculative diagnosis.

Use an approved message that states what is known, the current operating boundary and the next update time. For example: “The west vehicle gate is currently out of normal service. Please remain clear of the gate. We have escalated the issue and will provide the next update by 10:30 a.m.”

Do not say the gate is safe, repaired or about to reopen without the evidence and authority to support that statement. Do not blame the customer’s code, a vendor, weather, power or software until the governing evidence establishes the cause. If an approved alternate entrance exists, confirm that it is actually available, safe for the intended traffic and authorized for use before directing anyone there.

A callback time is a commitment to communicate, not a promise that the equipment will be repaired by then. That distinction protects trust when the repair timeline remains uncertain.

Escalate With a Useful Handoff

“The gate is broken” is not a complete vendor handoff. Provide the asset ID or exact location, first-known time, direction affected, directly observed behavior, visible condition, current operating state, safety boundary, recent work if verified, and the best on-site contact.

If servicing could expose an employee to unexpected startup or stored energy, OSHA’s hazardous-energy standard requires the employer to use its established energy-control program and applicable procedures, with authorized, trained employees performing covered work.⁶ A manager who is not authorized for that work should protect the boundary and wait for the qualified owner. Calling a technician is not evidence that the equipment is isolated, repaired or safe to return.

Keep three vendor states separate:

• Dispatched: The request was accepted for routing.
• Work reported complete: The technician says the assigned work was performed.
• Returned to service: The required repair evidence, safe test, site readback and operating approval are complete.

Close the Incident in Two Decisions

Technical readiness and operational release are related, but they are not identical.

The technical owner may confirm that work was completed and required safety functions were tested under the manufacturer’s procedure. The facility owner must still verify the correct operating state, remove temporary controls through the approved process, update customer messaging and confirm that entry and exit work as intended.

DASMA’s property-owner checklist says not to repair or adjust gate systems yourself and directs repairs and adjustments to a trained gate-systems technician.² Its emergency-access guidance places emergency arrangements under local authority requirements and says damaged systems that cannot be operated through the defined emergency means should be held open until repairs are complete.⁷ Site-specific instructions, the manufacturer, the qualified gate professional and the authority having jurisdiction govern the actual response; this article does not replace them.

After service is restored, review the incident as a system problem. OSHA’s incident-investigation guidance recommends preserving and documenting the scene, collecting information, determining root causes and implementing corrective actions. It also warns against stopping at blame or immediate behavior.⁸

Ask what allowed the failure to reach the customer: a missed preventive check, expired contact list, unclear after-hours ownership, untested backup, stale access schedule, repeated intermittent fault or a procedure no one could execute safely. Assign the corrective action and its due date separately from the closed customer incident.

A Fictional Shift Example

The following example is entirely fictional. It does not describe a real facility, customer, vendor, gate system or incident.

At fictional Juniper Square Storage, a customer reports at 9:12 a.m. that the east entry keypad accepts a code but the slide gate does not move. The manager keeps the customer clear, observes the gate from outside the travel zone and sees no movement. A second authorized test allowed by site procedure produces the same bounded result. The manager does not cycle the gate again.

The record shows: credential accepted, command result unknown, gate closed, passage not completed and east entry out of service. The manager confirms that the approved west vehicle entrance is available before directing traffic, posts the approved restriction message, opens a vendor ticket and commits to a 10:00 a.m. customer update. No code, schedule or safety device is changed.

The vendor later reports a repair. The manager does not close the incident on that statement alone. The authorized technical test is documented, the site verifies both normal entry and exit, the temporary notice is removed, and the operating owner records the return-to-service time. A separate corrective action is opened to review why the initial alert did not reach the manager before the customer call.

That is the operating standard: protect first, describe precisely, escalate cleanly and reopen on evidence.