The guide
What “mobile patrol” means in a California PPO context
In California, the only agency license that lawfully runs a drive-through patrol post is the BSIS Private Patrol Operator (PPO) — the same license that staffs a standing post, extended to a moving officer who carries the same BSIS guard registration as a stationary officer, the same Live Scan clearance, the same Power to Arrest training, and the same BSIS firearms permit when the route is armed. The mobile officer is accountable across multiple sites in the same shift, and the route is treated as a single post for documentation purposes — the dispatch roster, the post-orders pack, and the dashboard log all treat the route as one assignment owned by one PPO. Anything short of a PPO license — an unlicensed “security” operator running drive-through sweeps — falls outside California’s regulatory framework and exposes the client to civil and criminal liability on first incident.
Marked vehicles, uniforms, and the deterrence role
A marked patrol vehicle is the dominant deterrent for after-hours sites — a visible presence on the property line that the public, the staff arriving in the morning, and the would-be trespasser all read as “this site is being watched.” The California baseline is a clearly marked vehicle with an agency identifier, a light bar appropriate to the patrol posture, and an officer in a clearly identifiable uniform consistent with the agency’s PPO branding. Unmarked vehicles undercut the deterrent value and leave the officer’s authority ambiguous in the moment of an incident — the public doesn’t know whether to read the officer as a security presence, a police presence, or something else. On a mobile-patrol engagement, ask before signing what the vehicle baseline looks like and what the uniform baseline looks like; if the answer is vague, the vendor is telling you the deterrent value isn’t part of their scope.
GPS-stamped checkpoints and the audit trail
Every mobile sweep produces a contemporaneous log: a GPS ping at each checkpoint, a QR-code or NFC tag scan confirming the officer stopped at the right location, a timestamp, the officer’s identification, and a short narrative of conditions observed. The chain is what survives an insurance or regulator pull — not “the officer says they drove through,” but a verifiable record that the officer was at checkpoint 3 at 02:14, at checkpoint 4 at 02:27, and at checkpoint 5 at 02:41, with notes on each stop. A patrol report filed from memory hours later, or a “we drove through” summary without the GPS-and-tag evidence, doesn’t meet the audit standard. The dashboard on the client side should expose the same data as the dashboard on the agency side, so the client doesn’t have to request the log after the fact.
Randomized vs. scheduled routes
Two route cadences cover the bulk of California mobile-patrol engagements. A randomized routeruns on a randomized-night basis with the sweep time varying across a window (for example, 22:00 to 04:00) so a would-be trespasser can’t predict the officer’s arrival; this is the dominant deterrent pattern for after-hours sites on a low-incident baseline. A scheduled route runs on a fixed clock-time cadence — useful for sites with predictable receiving or outbound windows, where alignment between the officer’s arrival and the truck’s arrival closes the highest-value exposure. The brief usually drives which pattern fits: insurance-driven deterrent pull toward randomized; receiving-driven exposure pull toward scheduled. Often the right answer is a mix — randomized on weeknights, scheduled on receiving nights.
Multi-site portfolios and the dispatch-and-roster math
The math behind a multi-site mobile-patrol engagement is straightforward and worth asking the vendor about up front. Sites per route: how many sites a single officer covers per sweep without compromising checkpoint timing. Geographic radius: the drive-time distance a route covers, and whether adjacent sites can be folded into one sweep. On-roster officers per metro: the number of BSIS-licensed officers available in a given metro, since the roster size determines whether a backup officer can cover a callout. A vendor running one metro with a five-officer roster and a vendor running seven metros with a twenty-five-officer roster are very different engagements to price — ask explicitly which case your route is.
What dispatch needs to scope a quote
Five fields turn a brief around on the first call. The number of sites on the route. The frequency — sweeps per night, sweeps per week, or a receiving-aligned schedule. The check-in method — GPS ping, QR scan, NFC tag, or a mix. The site-size band — total square footage across the route, the number of access points the officer has to walk per sweep, and any outbuildings that need separate passes. The site address (or list of addresses) for the route, so dispatch can map the drive-time radius and fold adjacent properties into a single sweep. Five minutes on the phone produces a same-day number; a written scope with those five fields produces a same-day number plus a written quote you can hand the insurance carrier.
A note on this guide
Cadence and route math come from active California engagements and are a planning estimate, not a published contract. The mobile-patrol service page walks the warehouse-tilted allocation pattern in production, and the coverage page documents the seven-metro roster and the per-metro response-window bands. Confirm the specifics with dispatch before the first sweep.