Most security companies spend an hour or more per client per week on the phone explaining what already happened. The property manager wants to know whether the lobby was staffed on Tuesday morning. The warehouse client asks whether the yard was walked overnight. The answers exist somewhere, in a sign-in sheet, a text message, or an officer's memory, and someone has to go and find them.
The call is not the problem. The call is a symptom of a reporting gap. When a client cannot see coverage for themselves, they ask. This article lays out a system for closing that gap so that the weekly call becomes a quarterly review.
Start with the three questions clients actually ask
Every client reporting conversation reduces to three questions.
- Was someone there? The client wants to know that a post was staffed for the hours they are paying for, and that the officer arrived on time.
- Did they do the work? For patrol contracts, the client wants evidence that rounds were walked and checkpoints were visited.
- What happened? When there was an incident, the client wants to know what it was, how it was handled, and what the officer recorded.
If your reporting answers these three questions without a phone call, you have solved most of the problem. Everything else is formatting.
Replace the sign-in sheet with arrival records
The sign-in sheet is where most coverage disputes begin. It is filled in by the person whose attendance it records, it can be completed at any time, and it lives at the site rather than in your office.
An arrival record from a security officer app solves all three issues. The officer checks in from their phone, the app compares the device location against a geofence drawn around the post, and the check-in is timestamped on the server. The record is created at the moment of arrival, by the system rather than the officer, and it is available to your operations team immediately.
For the client, the value is not the technology. The value is that "was someone there" has an answer with a timestamp attached. PostWatch produces exactly this record for every post, and the coverage map shows a client's posts with their current status.
Turn patrols into evidence
A patrol without evidence is a claim. Clients have learned to be sceptical of claims.
Checkpoint verification converts the patrol into a sequence of scans, each with a time and a location. NFC tags and QR codes both work; the comparison in NFC vs QR checkpoints for security patrols covers when to use each. What matters for client reporting is that the scans are retained and can be presented per site, per route, and per shift.
The most persuasive patrol evidence includes something the client can see. A checkpoint that prompts the officer to photograph a locked door or a clear fire exit gives the client a picture, not just a timestamp. Over a month, those pictures become a visual record of the condition of the site, which is often more valuable to the client than the patrol itself.
Structure incident reports so they can be shared
Incident reports written in email or text message cannot be shared cleanly with a client. They mix internal notes with client-facing facts, they lack required fields, and they are hard to find later.
A structured incident type with required fields, attached evidence, and an escalation chain produces a report that can be released to the client as it is. The operator reviews it, redacts anything internal, and releases it to the client portal. The client sees the incident with its evidence, the time it was escalated, and who acknowledged it.
The discipline here is release control. Clients should see incidents after an operator has reviewed them, not in real time as the officer types. Release control protects both the officer and the relationship.
Schedule the report so the client never has to ask
Once arrival records, patrol evidence, and incident reports are in one system, the weekly report becomes a scheduled export rather than a project.
A good weekly client report contains:
- Coverage rate for the week, with any gaps listed by post, date, and duration
- Patrol completion rate, with missed checkpoints listed
- Incidents released during the week, with links to the full reports
- Hours delivered against hours contracted
Deliver it on the same day at the same time, in PDF for the person who reads email and CSV for the person who builds spreadsheets. A report that arrives every Monday at 07:00 is a report the client stops asking for.
Give the client a portal, not a login to your system
Scheduled reports answer last week's questions. A client portal answers today's.
A portal should show the client their own posts only, with live status, patrol history, released incidents, and the SLA dashboard for their contract. It should carry your brand, because the client is buying from you, not from your software vendor. It should be read-only by default, with the option to let specific client users request additional coverage or comment on incidents.
A portal is not the same as giving the client access to your operations console. Clients should never see other clients' sites, officer personal details beyond what you choose to share, or your internal notes. ClientView is built around this separation.
Measure against the contract, not against perfection
Clients do not expect 100% coverage. They expect to know when coverage fell short and what you did about it. An SLA dashboard that shows 99.4% coverage against a 98% commitment is a stronger sales tool than a verbal assurance that everything is fine.
Define the SLA metrics in the contract, measure them in the platform, and show them to the client on the same dashboard you use internally. When the renewal conversation starts, open the dashboard. The conversation will be about scope, not about trust.
What changes when the calls stop
Operations directors who move their client reporting onto this system describe the same three results. The weekly status call becomes a monthly or quarterly review. Disputes about invoices drop, because every line links to an arrival record. And the operations team spends its time on the exceptions that need attention instead of reconstructing what already happened.
None of this requires more officers or more supervisors. It requires that the evidence of the work be captured at the moment the work is done, and that the client be able to see it without asking.