Inside a Real Sacramento Patrol Log: 7 Nights of Daily Activity Reports, Redacted

A defensible DAR contains eight fields on every tour entry: (1) unique tour ID assigned by the GPS platform, (2) officer name and BSIS guard card number, (3) tour start timestamp with GPS coordinates, (4) each checkpoint scanned with individual timestamp and photo, (5) tour end timestamp with GPS coordinates, (6) narrative notes on anything observed outside routine, (7) any incident report ID cross-referenced from the tour, (8) supervisor sign-off with timestamp. Anything less is not a defensible report — it will not hold up in an eviction dispute, insurance claim, or civil discovery.

Officer M.R. logged into Silvertrac at 21:47, arrived on site at 21:52, and completed the first tour at 22:14. Checkpoint scans hit: front gate, pool deck, mail room, back alley by carport 12, dumpster enclosure, laundry. Photo checkpoints all uploaded within 45 seconds of scan. Tour two 23:41, tour three 01:38, tour four 04:12. Narrative: 'All quiet. Two vehicles idling in visitor spots 8 and 9, verified as unit residents on curbside chat.' Shift closed 04:41, supervisor sign-off from D.V. at 06:15. Total DAR: 3 pages, 24 photos, tour compliance 100%.

Tour one uneventful. Tour two 23:52, at pool-deck checkpoint the officer observed two subjects in the pool area after posted hours (posted 22:00 close). Narrative reads: 'Two adult males, one described as approx 5'10" dark hoodie, one 6'0" light jacket. Politely asked to leave, confirmed non-residents (could not produce fob), left via front gate at 23:58 without incident. No property damage observed. Incident report SM-04-08-001 filed.' Photo of the pool deck (no subjects visible, per company privacy policy) attached. Property manager notified via email 00:12 with incident report link.

Tour one 21:58 uneventful. At 23:14 dispatch received an alarm from unit 2XX (redacted) via ADT central station. Officer M.R. diverted, arrived on-site 23:19 (dispatch-to-arrival 5 minutes), met ADT at unit, confirmed accidental trip by tenant returning from shift. Reset alarm, cleared scene 23:38. Returned to tour cycle, tour two started 23:52. Tour cycle preserved (4 tours completed by shift end). This is the pattern to look for — an incident occurred, was resolved, and the tour cadence was still met.

Four tours completed, no narratives beyond weather and one note about a burned-out light at carport 7 (maintenance ticket auto-filed to property manager). GPS photos on all 24 checkpoints. Shift closed 04:38, supervisor sign-off. This is what a normal night looks like — and 90% of nights on a well-patrolled property are exactly this. If you never see a routine DAR, the vendor is either padding narratives or not patrolling.

Friday cadence was pre-set at 5 tours per direction of property manager (weekend elevated). Officer completed 5 tours between 22:00 and 05:00. Tour three 01:12 documented three vehicles blocking fire lane at building B, tenants notified via posted vehicle notices per PM instruction. Tour four 03:15 documented one vehicle removed, two remained. Tour five 04:47 documented all three removed. This kind of chain-of-custody narrative is why the DAR matters — if a tenant later disputes the notice, the vendor can produce timestamped proof.

Tour two 23:34 the officer intercepted one adult subject climbing the perimeter fence between carports 4 and 5. Subject dropped back over the fence, fled south on the adjacent alley. Officer did not pursue (per post orders, no pursuit off property). Description logged, incident report SM-04-11-004 filed within 8 minutes, SPD non-emergency called at 23:41 (call log ID attached). SPD arrived 00:14 for report. Property manager notified 00:16. Perimeter check completed 00:33, no signs of successful entry. This is what a well-handled trespass looks like — no injuries, no lawsuit exposure, full documentation, coordination with SPD.

Four tours completed. Tour two 23:38 a tenant approached the officer at the mail room to report a suspicious vehicle observed earlier in the evening. Officer took the description, cross-referenced against the shift's photo record, could not confirm the vehicle at any checkpoint. Narrative: 'Tenant given non-emergency SPD number, offered elevated attention on next tour, no vehicle observed on tour three or four.' This is the kind of soft interaction that builds tenant trust and rarely gets billed but always matters for retention.

At the end of the week, the property manager receives a summary that consolidates every DAR into decision-useful information. Below is the actual summary format.

Watch your own DAR for these patterns and push back if you see them. Every one of these has appeared in DAR from national brands that later lost accounts to us:

• Tour narratives that read identically night after night (copy-paste)
• Checkpoint scans clustered at the same second of the same minute (someone scanning tags on a table, not on site)
• Photo timestamps that don't match GPS timestamps
• No supervisor sign-off, ever
• Incident reports referenced in DAR but never delivered to you
• Tour start and end GPS at the same lat/long (officer never actually drove the route)
• Weather narrative in every entry (padding)
• Officer name that changes every shift with no consistency

Every Monday, open the last seven nights of DAR. Verify: (a) tour count matches contract, (b) at least one photo per checkpoint per tour, (c) at least one narrative entry per night that is site-specific and not templated, (d) any incident reports referenced are attached and read them. Ten minutes a week catches every problem before it becomes a dispute. If your current vendor's DAR cannot survive this audit, that is the problem the DAR is telling you about.

Before you sign with any vendor, ask for three consecutive nights of sample DAR from an anonymized comparable account. A vendor who cannot produce a sample DAR from an existing account is telling you their existing accounts do not receive real DAR. We publish sample DAR to prospective clients under a mutual NDA — ask (530) 902-9390.