Who is watching—and what happens next?
The most important rental question is not how many cameras are on the mast. It is who receives an event, what they can see, and what they are authorized to do.
Identify the actual monitoring provider.
A rental company may operate its own monitoring team or use a separate monitoring center. Do not assume the logo on the trailer identifies the people receiving its alarms. Ask for the monitoring organization’s name, the locations where operators work, and the rental company’s role in managing the service.
A U.S.-based or overseas team should be evaluated on clear service criteria. Location alone does not establish quality. Ask about training, communication, supervision, continuity, secure access to video, and familiarity with your site instructions.
- Who monitors the cameras, and can that arrangement change during the rental?
- What days and hours are covered? How are holidays and overtime handled?
- Who supervises operators and reviews missed or incorrectly handled events?
- Where is video accessed or stored, who can access it, and how long are incident records retained?
- How does the center maintain service during an internet, power, or staffing disruption?
- If a certification or accreditation is claimed, does it apply to the named center and this particular service?
“Live” can describe several different services.
| Service model | What to clarify | Important limitation |
|---|---|---|
| Event-triggered video monitoring | Which analytics or alarms bring video to an operator? What clips and live views are available? | An event must be generated and delivered before it can be reviewed through this workflow. |
| Scheduled remote patrols | Which cameras are reviewed, how often, and what happens between patrols? | Activity can occur between reviews. |
| Continuous human observation | Is sustained observation explicitly included? Which views are watched and how is coverage maintained? | People and camera views still have practical limitations. |
| Automated alerts or self-monitoring | Do messages go to your phone instead of an operator? Who is responsible for acting? | A notification alone does not provide a staffed response. |
Terms such as remote guarding, virtual guard, and remote guard service are not substitutes for a written scope. Ask the provider to describe an actual event from detection through closure.
Define the response before the first alarm.
- Detect: An agreed event occurs in a configured zone during monitored hours.
- Verify: An operator reviews available video and checks the site instructions.
- Deter where appropriate: The operator may use live talk-down or other approved measures.
- Escalate: Follow the agreed contact and dispatch procedure. Immediate threats may require a different sequence from routine trespassing.
- Document: Record actions, preserve available evidence, and report the incident.
This is an example workflow, not a promise that every provider follows it. Confirm when operators should contact you, request private security, or request law enforcement. A request for dispatch does not guarantee attendance or an arrival time. Ask how local response requirements and any needed permits are addressed.
Controlled sites allow clearer rules.
In a closed construction site or storage yard, a person entering a restricted zone after hours can be a clear reason to investigate. That still requires useful camera placement, correct schedules, stable power and connectivity, and updated instructions for legitimate exceptions.
Apartment parking lots are a harder problem.
Residents, guests, rideshare drivers, delivery workers, and maintenance staff may all legitimately use an apartment parking lot at night. A camera cannot establish criminal intent simply because someone is present. Clothing or appearance should not replace an observable event rule.
Ask what specifically merits review: crossing a restricted boundary, remaining in a defined location beyond an agreed time, or another behavior the proposed system can actually detect. Repeated access, occlusion by vehicles, lighting changes, and legitimate activity need to be part of the evaluation.
Ask for evidence behind behavior-analytics claims.
Some vendors offer unusual-activity or aggression-related analytics. Those labels can cover very different capabilities. Ask which exact behaviors and camera conditions the product supports; do not assume it can reliably recognize theft, fighting, or suspicious intent.
- Request a documented test using representative daytime and nighttime conditions.
- Define an event before testing, including its duration, zone, and threshold.
- Record both missed events and false alerts. Include busy periods and obstructed views.
- Ask how operator workload and event queues affect review and escalation.
- Agree on tuning, retesting, and who reviews performance after site conditions change.
A “detection rate” needs a denominator. Ask how many relevant test events occurred, how many were detected, and how many unrelated alerts were generated. A claim that nearly every reviewed alarm was valid does not establish how many incidents were missed. There is no universal detection percentage suitable for every site.
Separate technical outages from security incidents.
Who notices a disconnected camera, low battery, blocked view, or lost cellular signal? Does that create a service ticket, notify you, or prompt a technician? Ask for the outage notification procedure and any contingency protection. Good monitoring requires knowing when the system cannot see.
Before you sign
Obtain the named monitoring provider, covered hours, event definitions, response instructions, contact list, outage procedure, and reporting expectations in writing. Make sure the monitoring team receives the current site plan after every relocation.