When can a cleaning service issue be marked resolved?
Format: Article.
Mark an issue resolved only after the named reviewer checks the agreed fix. Record the outcome of any dispute too. A checked box, crew message, or photo can help the reviewer. None should take the place of that check.
Set the test for “resolved” before asking someone to close the issue. Missed trash, a locked room, and a disputed floor finish need different proof. A rule such as “photo attached” does not show whether the crew fixed the problem.
Match the closure test to the complaint
Keep the customer's own words, site, area, time, and proof they sent. Ask a supervisor to turn the concern into a clear task with a result they can check. Do not rewrite the complaint just to make it easier to close.
For example, “Meeting room still had waste after the evening visit” is not the same as “Crew did not attend.” The first describes an observation. The second assigns cause. The closure record should answer the observed problem without inventing an explanation.
ISSA describes its Cleaning Industry Management Standard, or CIMS, as a guide to how a cleaning company is run. It does not prescribe products or cleaning methods. [S02] The evidence ladder below is an editorial tool for supervision. It is not a CIMS assessment, a sanitation test, or a service guarantee.
Use an issue closure evidence ladder
| State | What the record establishes | What it does not establish |
|---|---|---|
| Issue received | Someone reported a specific concern | Cause, responsibility, or current condition |
| Corrective task assigned | A person owns a defined next action | That the action happened |
| Work reported finished | A crew member reports the task complete | Independent acceptance of the result |
| Evidence checked | Reviewer checked the required record or area | That unrelated areas or future shifts are satisfactory |
| Closure accepted | Person with authority accepted the agreed fix | Proof of sanitation or a bar to a later dispute |
Record the issue ID, agreed task, work report, proof link, reviewer, check time, and reason to close. If the contract calls for client sign-off, show that step. Do not assume every issue needs a client signature. Do not treat a quiet client as one who accepted the work.
A supervisor may need to visit the site for one check. A photo may be enough for another, limited check. The company must have qualified people set that rule. Do not pick the test just because a file is easy to get.
Keep access failures out of the resolved column
If the crew could not enter the room, record “blocked by access,” the attempt, and the contact asked to help. Do not close the issue as completed because the crew attended the site. An approved scope change can remove or replace a task, but its reason must remain visible.
A client may withdraw a request. Record that reason to close it. It does not mean the crew did the work. Keep accepted fixes, canceled requests, and work not done in separate groups. Do not add them into one count called successful work.
Hypothetical example: an image from the wrong room
A fictional client reports waste left in meeting room Cedar. The crew completes a corrective visit and uploads a clear image of an empty bin. The supervisor notices that the room label in the image is Maple.
The supervisor does not accuse the crew of poor work or accept the issue as resolved. The record moves to “evidence mismatch.” The crew lead checks the visit notes, confirms the wrong image was attached, and provides the correct room record. The original upload remains in the history with a correction note.
The reviewer checks Cedar against the agreed task and records sign-off. If the client later disputes the result, staff check the times of both reports. They may reopen the issue or link it to a new report. Keep the first sign-off. A later report does not prove the first check was false.
Give disputed results a clear path
Use a dispute note with two accounts: what the crew reported and what the client observed. Add the time of each, the exact area, and evidence links. Name a reviewer who can compare them and set a next check under the account's actual process.
If the proof cannot settle the dispute, say so. Use “result disputed; supervisor review due.” Do not say “resolved pending investigation.” That makes an open issue look closed. Call a review scheduled only when someone has set the time.
At the weekly review, keep separate counts of reopened issues, rejected proof, and tasks blocked by access. We propose these counts to help managers ask questions. They do not prove how well a crew worked. Check the reasons before judging the work.
Core Agentic can discuss a custom review tool that keeps these states clear. It is not a finished quality platform. Supervisors still inspect work, direct safe work, and control client messages. We would agree on access and any use of cloud services before use.
Book a Demo to discuss a closure process that shows what was actually checked.
Sources
These sources describe the named provider or framework. They do not establish a Core Agentic integration, customer result or certification.