The weekly client report: what it should contain
The weekly report tells the client what they got this week and what changes next week, in six parts: a coverage summary, patrols, incidents and actions, trends, open issues and next week’s changes. It doesn’t repeat the daily shift reports; it summarises them, draws conclusions and asks for decisions. The provider’s supervisor or account manager writes it, not the guard.
Updated: 4 min read
What should a weekly security report contain?
Six parts: coverage, patrols, incidents and actions, trends, open issues and next week’s changes. Each part answers a question the client would ask.
- Coverage summary: were all shifts covered? How many hours were planned, how many were worked, and if a post was left uncovered, when and why.
- Patrols: how many were planned, how many were completed, which checkpoints were missed repeatedly.
- Incidents and actions: each incident in one line — time, what, what was done, whether it’s closed — linked to the full incident report.
- Trends: what is repeating or changing compared with previous weeks.
- Open issues: what’s pending, who owns it, by when.
- Next week’s changes: new staff, shift changes, events, works on site, changes to the post orders.
What does a weekly security report template look like?
A one-page summary at the top, the six parts in a fixed order below, and at the end the decisions needed from the client. The same format every week, so weeks can be compared.
- Header: site, week (from–to), author, date sent.
- Three-line summary: the state at a glance — “full coverage, 2 incidents (closed), 1 open issue for you”.
- Coverage: shifts planned / covered, gaps with cause, replacements.
- Patrols: completed / planned, missed checkpoints and the explanation.
- Incidents: a table — date, time, type, actions, status, reference.
- Site observations: faults, lighting, doors and locks that need the client.
- Trends: comparison with previous weeks, in two or three sentences.
- Open issues: issue — owner — deadline — status.
- Next week: what changes and what’s being prepared.
- Decisions for the client: what is waiting on you.
Agree the template and the day it’s sent in the contract. A report without a fixed format and date slowly becomes optional.
How is the weekly report different from the daily shift report?
The shift report records what happened on one shift; the weekly report interprets what they all mean together. One is a record, the other is management.
- Author: the guard writes the shift report; the supervisor or account manager writes the weekly one.
- Purpose: the shift report says “what happened”; the weekly says “what it means and what we’re doing”.
- Content: the weekly report doesn’t copy the daily ones; it sums them up in numbers and refers to them.
- Decisions: the weekly report ends in actions and asks the client for decisions.
Above the weekly report sits the monthly review against the security KPIs. The weekly report keeps issues alive between monthly meetings.
How do you write trends in a security report?
By comparing the week with previous weeks on the same measures and saying plainly what is changing. A trend is something that repeats, not a single event.
- The same measures every week: patrol completion, coverage gaps, incidents by type.
- Repetition: “the back door was found open three times in the last two weeks”.
- Time patterns: incidents clustering at one hour or day of the week.
- A checkpoint that’s often missed: a sign of a problem with the route, the checkpoint or the instructions.
- A proposal: every trend comes with a suggested action.
Don’t write trends from gut feeling. If patrol data comes from checkpoints and reports are timestamped, comparing with previous weeks is a measurement, not an opinion.
How are open issues tracked from week to week?
In a list carried from report to report, with an owner, a deadline and a status, until each issue is closed. An issue doesn’t drop out of the report just because a week has passed.
- Each issue has a number and keeps it until it’s closed.
- The owner is a person, not “the company”: the supervisor, the client’s technician, the building manager.
- Issues waiting on the client are marked separately, so they aren’t counted as the provider’s delay.
- Issues that stay open for several weeks go up to the monthly review.
OVIT brings patrols, incidents and reports together in the Guardly platform, so the client sees the same live picture as the operations team and the weekly report rests on it.
At a glance
- Six parts: coverage, patrols, incidents, trends, open issues, next week.
- A fixed template and send day, written into the contract.
- The weekly report interprets the shift reports; it doesn’t copy them.
- A trend is something that repeats, and every trend comes with a proposal.
- Open issues carry over with an owner and a deadline until they close.
Frequently asked questions
Who writes the weekly report to the client?
The provider’s supervisor or account manager, not the guard. They compile it from the week’s shift reports, patrols and incidents.
Do I need a weekly report if I already get a daily shift report?
Yes. The shift report says what happened on one shift; the weekly report shows trends, open issues and what’s changing, and asks you for decisions.
What do I do if the weekly report is the same every week?
Ask in writing for the week’s numbers and the open-issues list with owners and deadlines. If nothing changes, raise it at the monthly review.
Want us to look at your site?
Talk to the OVIT operations team — a real person answers.