Skip to content
Centrov resources

Proof & client reporting

What to Include in a Cleaning or Security Client Report

A practical client reporting guide for cleaning and security companies, with sample reports, service evidence, exceptions and clear follow-up actions.

Centrov Editorial Team · · 8 min read

The practical answer

A useful client report connects the agreed service to the work recorded: where and when it happened, what was completed, what needs attention, and who owns the next action. Keep the summary short, support it with relevant evidence, and review it before sharing.

Start with the questions your client needs answered

A property manager does not need to reconstruct a night shift from a folder of photos or a stream of messages. They need to know whether the agreed work took place, whether anything changed, and whether a decision is waiting for them.

For an Ontario janitorial company, that might mean the evening cleaning was completed but one room was locked. For a security company, it might mean the patrol was completed and a door defect was passed to building management. Both reports should make the exception as easy to find as the completed work.

Agree on the audience, reporting period and delivery channel at the start of the contract. A daily service summary, a monthly review and a detailed incident report serve different purposes. Urgent issues still follow the agreed escalation procedure; they should not wait for the next routine report.

Include six things in every service summary

  1. Building and reporting period. Identify the job address, service date or date range, and the local time zone. Distinguish the time of the work from the time the report was written.
  2. Expected service. State the agreed visit, shift or task. Use the contract scope or post instructions as the reference, rather than an unrelated generic checklist.
  3. Recorded delivery. Explain what was completed and what evidence supports it. Label missing or unverified records clearly instead of filling the gaps with assumptions.
  4. Exceptions. Make incomplete work, access problems, failed checks and changes visible. Say what the team observed and how the issue affected the service.
  5. Next action. Name the responsible role, the agreed next step and its due time. Distinguish an action already taken from one that is only proposed.
  6. Review details. Identify the reviewer and review date. Keep a reference to the underlying record so the office can answer a question without rebuilding the history.

Lead with a short status and the exceptions. Put supporting details underneath. A client should be able to scan the summary and decide whether they need to act.

Cleaning example: show the tasks and the unfinished work

A cleaning client report should describe the areas and tasks serviced, any inspection findings, and anything that could not be completed. A clock-out confirms a recorded time event; it does not establish that every room met the agreed standard.

Sample evening cleaning summary

Fictional editorial example · Toronto office building · October 1, 2026 · All times Eastern

Planned service
Evening janitorial visit, 18:00–21:00: reception, shared washrooms, kitchen and meeting rooms.
Completed
Reception floors cleaned, washrooms serviced, kitchen surfaces cleaned and waste removed. Office review checked the task record and relevant photos.
Exception
Meeting room 204 was locked throughout the visit. Its scheduled cleaning remains incomplete.
Action taken
The team recorded the access issue and notified the office at 20:35.
Next action
Building management to confirm access arrangements by 15:00 on October 2. The cleaning supervisor will confirm the next available service window.
Review
Reviewed by the cleaning supervisor at 09:00 on October 2. Job record reference: CLEAN-EXAMPLE-01.

The locked room is the most useful part of this summary. It makes the service limitation explicit and gives building management a concrete action. Reporting only the completed checklist items would hide the part of the visit that still needs attention.

Security example: record observations and actions precisely

Security reports need a clear sequence: where the guard was, what was observed, when it happened and what action followed. Describe the actual checks performed. A completed patrol is not a guarantee that a building is safe or that no incident occurred outside the observed period.

Ontario’s security guard report-writing syllabus emphasizes factual, standardized reporting and confidentiality. Keep observations separate from assumptions about causes or motives.

Sample security patrol summary

Fictional editorial example · Ontario commercial building · October 1, 2026 · All times Eastern

Planned service
Exterior patrol and agreed entrance checks during the 22:00–22:30 visit window.
Recorded visit
Arrival recorded at 22:08 and departure at 22:24. The visit record lists the entrances and exterior areas checked.
Observation
At 22:12, the guard observed that the west service door did not latch when closed. A photograph documents the visible latch condition.
Action taken
The guard notified the duty supervisor at 22:14. The supervisor contacted the designated building representative at 22:18 using the agreed escalation procedure.
Next action
Building management to arrange a repair and confirm the interim access procedure. The security supervisor will track the issue until an outcome is recorded.
Review
Reviewed by the duty supervisor at 22:40. Related incident reference: SEC-EXAMPLE-01.

A routine client summary can refer to a restricted incident report without distributing every detail. Preserve the original notes and use the organization’s approved process for corrections and access. The summary complements the underlying incident record.

Use photos and timestamps to answer a specific question

Attach evidence because it explains a completed task or an exception. Give each photo enough context: building, area, date and what it demonstrates. A close-up without a location or explanation can create more questions than it answers.

A photo of a cleaned washroom supports a particular observation. It does not verify every task in the building. A recorded arrival supports attendance; it does not prove that the full patrol was completed. If location evidence is missing or unverified, say so.

Use the agreed photography rules for the building. Avoid capturing people, computer screens, access credentials or unrelated documents in routine service photos. If an incident requires sensitive evidence, handle it through the authorized incident process and audience.

Keep internal staff records separate from client reporting

Clients need service outcomes and relevant follow-up. Wage rates, medical absence reasons, private staff conversations and internal personnel decisions usually do not help them understand the delivered service. Review the audience before sharing names, contact information or incident details.

The Office of the Privacy Commissioner of Canada describes limiting collection and appropriate safeguards among the principles for handling personal information. Apply your organization’s privacy procedures to report content and access.

Keep client recipients current and use an approved delivery channel. A link or an attachment does not make a report suitable for everyone who receives it. Decide who is allowed to see the supporting evidence as well as the summary.

Review exceptions before publishing, then close the loop

Before sharing, check the building, reporting period and agreed service. Reconcile task records with actual delivery, look for missing evidence, and confirm that actions described as completed really happened. Make unresolved items visible and assign their follow-up.

On the next report, carry forward open issues with their current status. A door defect should not disappear because a new patrol took place. A room skipped for lack of access should not become completed merely because its next visit was scheduled.

For monthly reviews, summarize repeated issues by building and type. Report how many scheduled visits were completed and how many exceptions remain open, using consistent definitions. Avoid percentages that combine attendance, task completion and inspection quality into a single unexplained score.

How Centrov connects the service record

Centrov brings schedules, recorded time, checklists and supporting proof into the operational workflow. Its client portal presents service information alongside inspections, incidents and invoices so the office and client can refer to the same job.

For completed patrol and supervision visits, the office reviews the report before publishing the client snapshot and selected photos. Private staff conversations stay outside that client reporting path. The team still decides whether the record is complete, accurate and appropriate to share.

Use the sample outlines above to agree on the information your clients need. In a guided product walkthrough, we can show the current office, crew and client experiences for your cleaning or security operation.

Put the method to work

Walk through your cleaning or security operation with us →