Where incident reports fall apart
A cleaner finishes a recurring Thursday visit and notices a hairline crack in a bathroom mirror that she does not remember seeing last week. She mentions it to her lead in the truck. Two days later, the client calls about the mirror and about a ring she thinks went missing from the nightstand. Nobody can say whether the crack was there before, and the only note about the ring is a text message that says "didn't see any jewelry."
That scene is an original illustration, not a TwoQM client and not a measured result. Nobody acted in bad faith. The problem is that the observation existed only in someone's memory, and the company had no shared record to check against.
TwoQM has already written about quality checklists with photo proof after recurring visits and about key and alarm code custody logs by property. Quality photos show the work was done. This article covers something different: what happens when a crew notices damage, causes damage, or finds or cannot find an item, and how that becomes a report the office and the client can both rely on.
The usual gaps look like this:
Verbal first, written never. A cleaner tells the lead, the lead tells the office, and by the time it reaches a manager the details have changed.
Photos on personal phones. The picture exists, but it lives in a camera roll that the office cannot search by property or date.
No "before" to compare. When a client reports damage, there is nothing showing the condition of that item on an earlier visit.
Lost and found by text thread. Found items are mentioned in a group chat, and nobody records where the item was left or who confirmed it with the client.
No owner for the follow-up. The report is filed, but nobody is responsible for contacting the client, deciding next steps, or closing it.
One report type, filed from the job
Start by giving crews one short report they can file from the visit itself, tied to the property and the job, not to a phone. Keep it to what a person can complete in a couple of minutes:
What kind of report. Pre-existing condition noticed, damage during the visit, item found, or item the client asked about.
Where. Property, room and the specific item or surface.
Photos. A wide shot that shows the room and a close shot of the item, taken before anything is moved or cleaned.
What happened, in plain words. What the cleaner saw or did, without guessing at cause or fault.
Who was there. The crew members on the visit, recorded automatically from the schedule.
The goal is to capture facts while they are fresh and attach them to the place they happened.
Pre-existing conditions are the most useful reports
The report that saves the most trouble is the one filed before anything goes wrong. When a crew notices a chip, stain, loose fixture or crack that was already there, a quick photo report marked "pre-existing" gives the office something to point to later. Over time, each property builds a short condition history that anyone on the team can review before a visit.
Lost and found needs a chain, not a chat
For found items, the report should record where the item was found, where it was left, and whether it was placed somewhere the client asked. For items a client asks about, the report records what the crew checked and where. Each item stays open until a person confirms with the client, and that confirmation is part of the record.
Your company's own policies decide what crews should and should not do with valuables. The report simply makes sure the steps are written down.
Route every report to a named owner
Each report should land in front of one person, usually an office manager or operations lead, with a status: new, client contacted, resolved, or closed. The owner decides whether to call the client, schedule a return visit, or involve the business owner. The client update is drafted and sent by a person, not triggered automatically by a cleaner's photo.
A short weekly list of open reports, grouped by property, keeps anything from sitting unanswered.
Where automation and AI help
Business automation fits this problem because the steps repeat: file the report from the job, attach it to the property, notify the owner, track the status, and flag reports that stay open too long. Where your scheduling and job tools allow it, the report can sit next to the visit record, as confirmed during scoping. If no off-the-shelf tool matches how your crews work, custom software can provide a simple mobile report form and property condition history.
AI integrations can turn a cleaner's short note into a clear summary for the office, suggest which report type applies, and draft an English or Spanish client message for the manager to review. AI does not decide who was at fault, does not tell a client whether anything will be paid for, and does not send anything on its own. A person reviews every report and every message.
Where to start this week
Pull the last five client complaints about damage or missing items. For each one, ask: Was there a photo from that visit? Was there a photo from an earlier visit? Who owned the follow-up, and is it written down anywhere? The gaps in those answers show where a simple report would help first.
TwoQM builds automation, custom software and AI-assisted workflows for cleaning companies. This article describes operations workflows, not legal or insurance advice; follow your own policies and any agreements with your clients. Pricing explains how business apps, systems and custom software are scoped.
Describe Your Incident Report Workflow · Explore business automation