Keeping Cleaning Records a Client Can See
Cleaning records only prove something if a client, owner or auditor can read them without you in the room. What to keep visible, what to keep internal.
A cleaning records file that only makes sense to the person who built it is an internal diary, not evidence. The test is simple: can a board member, an incoming contractor or an insurance adjuster open the file cold and understand what was checked, what was found and what was done about it?
Most property managers inherit the opposite. Photos sit on a supervisor's phone. Scores live in a spreadsheet only one person maintains. Deficiency emails are spread across three inboxes and a WhatsApp group. Ask for the last six months of cleaning performance and the honest answer is a reconstruction exercise.
Key takeaways
- A record is client-visible when a stranger can read it without you explaining it.
- Four readers matter: owners, tenants, insurers, and whoever replaces you.
- Publish one file per building per month, not a folder of everything.
- Every failed item needs a date, a score, a photo and a closure date.
- Keep pricing analysis, staff notes and negotiation history internal.
What makes a cleaning record client-visible?
A client-visible record is one that stands on its own: legible, attributable, dated and actionable. Four tests decide it, and a record either passes all four or it is not ready to leave the building.
- Legible. Written in the language of the contract, not the cleaner's shorthand. "Washroom 3, floors, Level 4 against target Level 2" beats "bathrooms bad".
- Attributable. Says who inspected and when, not just that an inspection happened.
- Dated. Carries the date of the observation and the date the finding closed.
- Actionable. Describes the condition and what changed, so a reader can judge whether the answer was adequate.
If a record fails the second reader test, it is not a record. It is a note.
Who actually reads cleaning records?
Four audiences, four different questions. Most record systems are built for the first and fail the rest.
| Reader | Question they are asking | What they need |
|---|---|---|
| Owner or board | Are we getting what we pay for? | Monthly area scores against target, trend, exceptions |
| Tenant or occupant | Why is my floor like this, and when will it be fixed? | Complaint reference, area, closure date |
| Insurer or adjuster | Was a hazard known, recorded and acted on? | Critical item failures with dates and corrective action |
| Incoming manager or vendor | What state is this building in? | Current condition baseline, open deficiencies, area targets |
The insurer and the incoming manager matter more than managers expect. A slip-and-fall claim or a change of contractor turns a routine file into a document that is read line by line.
What belongs in the visible record set
Keep the visible set deliberately small. Five record types cover almost every request you will get.
- Scored inspection reports per area, with the target level stated on the same page as the observed level.
- Photo pairs for anything below target — one context shot showing the area, one detail shot showing the condition. The photo evidence standard that makes an image usable is worth copying into your vendor's contract.
- A deficiency log with owner, due date, closure date and re-inspection result, generated the same way as deficiency tracking works on the contractor's side.
- The standard itself — the area list, the APPA target per area, the frequency, and any agreed exceptions.
- Compliance documents with expiry dates: insurance certificates, workers' compensation clearance, WHMIS training, site-specific orientations.
Two supporting items are optional but earn their place: a monthly complaint log with resolution dates, and a one-page monthly summary that states what changed since the last period.
What should stay internal
Not everything that happens belongs in a client-visible file, and mixing the two is the fastest way to make a whole record set unauditable.
- Pricing analysis. Unit rates, cost per square foot benchmarks and negotiation positions belong in the commercial file, not the quality file.
- Staff performance notes. Names and coaching records are employment information. Report the area result, not the individual.
- Speculation. "Looks like they are short-staffed" is a hypothesis. Record the condition and the count, and let the pattern speak.
- Unverified tenant claims. Log the complaint as a complaint until an inspection confirms it, then record the finding. The difference between a tenant report and an inspection finding is the difference between noise and evidence.
The anatomy of an entry that survives scrutiny
A record entry should read the same way whether it is reviewed next month or in a dispute three years later. The retention rules you set only matter if the entry is worth keeping, so build the entry properly first.
- Date and time of observation, not of data entry.
- Building, floor, room and item named the way the scope names them.
- Observed level against target level, on the five-point APPA cleanliness scale or whatever scale the contract specifies.
- Observer name and role.
- Photograph with a visible reference point.
- A note of condition in plain language — "soap scum on two of three partitions, bin overflowing".
- Action taken, by whom, and when.
- Re-inspection result and closure date.
The eighth line is the one that gets skipped. A record set with findings and no closures reads as a list of complaints, and a reader will conclude nothing is fixed.
How to publish without creating a job
Publication should take minutes, not an afternoon. Three habits do most of the work.
- One file per building per month. A single PDF, named
building-month-year, containing the summary page, the scored areas, the open and closed deficiencies, and the exception list. - One index. A shared folder with a predictable structure per year, so a reader can find March 2027 without asking.
- Publish on a fixed date. By the fifth working day of the following month, every month, whether or not anything went wrong. A pack that only appears after a complaint looks defensive.
For owners, the monthly pack can be the same document discussed in reporting the vendor's performance, trimmed to one page. Keeping one source avoids the classic mismatch where the owner's summary and the site file tell different stories.
Where cleaning records meet privacy rules
Photographs and logs collect personal information more often than managers intend: a tenant's name on a whiteboard, a unit number in frame, a cleaner's name on a schedule. In Canada, private-sector collection, use and retention of personal information is governed by the Personal Information Protection and Electronic Documents Act and by substantially similar provincial laws in some provinces.
Three practical rules reduce the exposure:
- Photograph the condition, not the people. Crop or re-shoot if an occupant is identifiable.
- Refer to areas, not occupants, in findings.
- Give the vendor a defined access window and a defined retention period, and remove access when the contract ends.
Not legal advice. Privacy obligations vary by province and by the type of building. Confirm specifics with your provincial regulator and your organisation's privacy officer.
What becomes visible changes vendor behaviour
The strongest argument for a client-visible record is not archival. It is behavioural.
When the contractor knows the same monthly pack goes to the owner, three things change. Deficiencies get closed before the pack is due rather than after a chase. Disagreements about a score get raised at the time, with a photo, instead of months later. And the vendor's own supervisor starts reporting the same way, because the format is now the shared language.
That is the mechanism behind cleaning contractor management: visibility sets the standard of proof for both sides. The vendor is not being audited harder. They are being audited consistently, and they can see the file you see.
Common mistakes that make records unreadable
- Folders instead of files. A shared drive with 400 loose photos is storage, not a record.
- Scores without targets. A Level 3 means nothing unless the reader knows Level 2 was required.
- Photos with no context. A close-up of a scuff proves a scuff, not a location.
- Deleting closed deficiencies. Closure history is the most persuasive part of the file.
- Changing the scale mid-year. If you move from pass/fail to a five-point scale in July, the trend line breaks and the year looks worse than it was.
- Letting the vendor write the record. Their report can be part of the pack, but it cannot be the whole pack if you are the one being asked to prove oversight.
Frequently asked questions
What counts as a cleaning record?
Any dated, attributable document that shows what was inspected, what was found and what was done. That includes scored inspection reports, photo sets, deficiency logs, complaint logs, the standard itself, and compliance documents such as insurance and training certificates.
How long should cleaning records be kept?
As a working rule, keep monthly packs and inspection reports for at least two years and keep the annual summaries and any critical item failures far longer. Confirm the period against your building's document policy and any insurer or lender requirement; retention is easier to defend when it is written down.
Should tenants be able to see cleaning records?
Tenants should be able to see the record that answers their complaint: the area, the finding, the action and the date. They do not need the full pack. Publishing a monthly summary in a common area or on a tenant portal handles most requests without releasing anything sensitive.
What if the contractor refuses to share their inspection data?
The contract should make the data yours. If it does not, ask for the reports as a condition of the next invoice cycle and start your own inspections in parallel. A vendor who will not share scoring data has told you something useful about the renewal conversation.
Do paper records still count?
Yes, if they are legible, dated, signed and stored where they can be retrieved within a day. In practice paper fails on retrieval and on photo attachment, which is why most managers move to digital inspection records that export a report.
Build it once, then reuse it
The file you build for one building becomes the template for the next. Same fields, same pack, same publication date, and the monthly assembly drops to under half an hour.
NeatScore records scored inspections with photos and notes, tracks deficiencies to closure, and exports a branded report you can hand to an owner without editing. Try it free for 14 days, or see pricing.


