Incident report checklist

In cleaning and collection services, complaints come from every direction: the resident’s phone call, the building manager’s email, the council’s letter, the crew’s own report. When each one is noted in a notebook, a WhatsApp message or from memory, half get lost and the other half get no follow-up. The complainant calls again, and nobody knows whether it was resolved.

A structured incident report brings order to that chaos: every problem is logged with a reference, photo, location and owner, and does not close until there is evidence of a fix. That lets you respond to the complainant with facts and, above all, spot the points that fail again and again — the fly-tipping spot that reappears, the container that is always found burnt — to attack the cause and not just the symptom.

For whoever manages the contract, this record is also the defence with the client. Cleaning contracts and municipal concessions usually measure complaint response times; being able to show when the incident came in, who attended it and when it was closed is what backs up compliance and avoids penalties for supposedly unattended incidents.

How to use it with CaptaLog

Copy the template to your account and any team member raises the incident from their phone the moment it happens, even with no signal. Every report is stored with photo and location, assigned to an owner with a deadline, and is not considered closed until there is evidence of a fix. The history shows recurring hotspots and gives the council or the client a traceable report of complaints and response times.