What do you need before you start measuring?
You need three things running before any number is meaningful.
First, your gate system must log every credential event with a timestamp. A gate access log records the credential used and the timestamp of each gate event, according to modSTORAGE. Without timestamps you cannot separate after-hours events from daytime ones.
Second, your intercom must store a record of each entry call. Video intercoms produce a date- and time-stamped photo or video record of each entry event stored to the cloud, according to ButterflyMX. That record lets you verify who used a credential without displaying the credential itself.
Third, you need a defined after-hours window. According to findboatstorage.com 2026 Boat & RV Storage Statistics, 63.3% of boat and RV storage facilities operate on restricted hours, typically 6:00 AM to 10:00 PM. Whatever your posted hours are, write them down as the boundary for your measurement.
Once those three things are in place, run this setup workflow before you start collecting data.
- Confirm your intercom log exports separately and includes call outcome, timestamp, and whether the call was answered or missed.
- Set your after-hours window in writing: the time gate access is permitted minus office hours, or whatever boundary your facility uses.
- Create a simple spreadsheet with one row per day and columns for each of the three measures below.
What are the three measures and how do you collect them?
Unresolved entry rate counts gate cycles where a second vehicle crossed without a corresponding credential event, divided by total after-hours gate cycles in the period. According to modSTORAGE, gate access systems can produce an unresolved entry record when a gate cycle is interrupted or when a second vehicle crosses without a corresponding credential event. Your denominator is total after-hours gate openings. Your numerator is the count of those flagged records. Export both from your gate system's event log.
Prop-open event count is a raw count, not a rate, because each event is already a discrete problem. Prop-open alerts are triggered when a gate is held open beyond a defined cycle time and are a documented feature of gate intercom systems, according to CellGate Watchman. Count them per week during your after-hours window. If your system lets you set the cycle-time threshold, document what that threshold is so your counts stay comparable month to month.
Identity-verification escalation rate counts calls or entry requests where the remote operator or your staff had to escalate beyond a routine credential check, divided by total after-hours intercom calls answered. Remote monitoring operators can answer intercom calls, verify the identity of the person requesting access, follow site-defined escalation procedures, and log the outcome as a distinct access event, according to Gazer Monitoring. Ask your monitoring provider to flag escalated calls in their log export, or create a simple category in your own call log.
What does a measurement checklist look like for a boat and RV storage yard?
- Define your after-hours window in writing before pulling any data.
- Confirm your gate log exports credential ID, event type, and timestamp on every row.
- Confirm your intercom log exports call outcome and timestamp on every row.
- Identify the field your gate system uses to flag unresolved entries or interrupted gate cycles.
- Confirm prop-open alerts are enabled and that the cycle-time threshold is documented.
- Confirm your monitoring provider logs escalation outcomes as a distinct event type.
- Store raw exports; do not overwrite them when you pull the next period.
Hypothetical example
Hypothetical example. After-hours is defined as 9:00 PM to 6:00 AM.
That is the raw count for the period, no denominator needed.
Of those, 6 were escalated because the person at the gate could not be matched to an active space.
None of those numbers are benchmarks. They are a baseline. The value is in watching them move month to month after you make a change, such as enabling AI video detection or adjusting your gate cycle time.
What are the common mistakes and edge cases?
The biggest mistake is treating the gate log as a complete picture. A gate access log records the credential and timestamp but does not confirm that only the credentialed person entered; video context is required to detect tailgating or shared-credential use, according to modSTORAGE. If you measure only gate events, you will undercount actual access problems.
A second mistake is mixing daytime and after-hours events in the same count. Tenant Inc. notes, citing Inside Self-Storage 2026, that roughly 20% of self-storage inquiries come in outside business hours, and current tenants add to after-hours gate activity because gate access hours typically extend past office hours at both ends of the day. If your gate access window is wider than your office hours, be precise about which window you are measuring.
A third mistake is escalating by reading out or confirming a gate code over the phone. According to Gazer Monitoring, the remote verification workflow separates identity verification from credential issuance, meaning the operator confirms who the person is without transmitting the credential. Build that separation into your escalation procedure before you start measuring escalation rate, or the measure will not reflect actual credential security.
AI video integrated with gate access control can detect after-hours activity, forced entry, or tailgating in real time and route verified video alarms to local law enforcement if escalation is needed, without requiring staff to share or read out gate codes, according to Coram.ai. If you add this capability mid-measurement period, start a new baseline rather than comparing across the change.
What should you do next?
- Pull your intercom log for the same period and confirm it includes call outcome and timestamp.
- Write down your after-hours window as a specific time range.
- Count unresolved entries, prop-open events, and escalated intercom calls for that period using the definitions above.
- Record those three numbers as your baseline before making any system changes.
