Inspection reports and client evidence

Every completed inspection produces a report: each item, its result, the photos, the time, and who ran it. You read it to confirm the work met the standard, and use it as evidence when a client asks what happened at a location. The report is stronger than a standalone checkbox because it carries the context behind the answer.

What is in an inspection report?

The report is the record of one inspection run: every item with its pass or fail result, every photo pinned to its item, the location, the time it was run, and who ran it. Any issue found can show as a linked work order, so the report also points to what was handled, not just what was wrong. Read it top to bottom and you can see the condition recorded at that location at that time.

How do I read the report?

Open the inspection from the location or from Inspections and scan the results. Failed and flagged items surface first, so you see problems before you read past the clean items. Tap any item to see its photo and notes. Where an issue became a work order, follow the link to see whether it is still open or already closed out. The report is built to scan in seconds: green means it met the standard, a flag means it needs a look, a linked work order means it is being handled.

How does this defend my SLA?

The report is your evidence when a client questions whether the work happened. An SLA is a promise about what gets done and when; an inspection report shows what your team recorded during the service window. When a client says “the lobby was not cleaned Tuesday,” you open Tuesday’s inspection and review the photos and notes for that location. A checkbox gives a quick answer. A report gives the context behind it.

How do I share client-ready evidence?

Use the inspection report as the source when a client needs evidence. If sharing is enabled on your account, share the report from the record. If your workflow uses exports or screenshots, send the same inspection details without rewriting them in a separate document. Either way, the client sees the evidence in a form they can read at a glance.

Why is this stronger than just a checkbox?

Most tools stop at “the cleaner said it was done.” CleanLog records the condition: photos, notes, location, time, and the person who ran the inspection. A checkbox proves someone tapped a screen. The report shows what they saw. For a cleaning contractor, that record backs up the SLA conversation and helps settle client questions before they turn into disputes. See how inspections fit the rest of the product in all features and what plan includes them in pricing.

Where to go next

If an inspection surfaced something to fix, track it in creating a work order. To change what an inspection checks, edit the template in building an inspection checklist.