Keep the missed or disputed service linked to the original visit and record the actual cause before deciding the remedy. Assign a supervisor to review access failure, incomplete work or a reported quality issue. Preserve any corrective attendance separately so the business can see its cost and apply the agreed customer treatment.
Understand the decision
A site may be inaccessible even though the team arrived, while another visit produces a complaint about one area. These cases need different responses. The workflow should show the customer's unresolved concern, the supervisor's decision and the next action without automatically charging for a corrective clean.
Work through the requirements
- Classify the service exception accurately.
- Record the supervisor's agreed remedy.
- Link corrective work to its original visit.
| Record or decision | Why it matters |
|---|---|
| Exception report | Preserves the missed or disputed outcome. |
| Remedy decision | Defines the reviewed customer response. |
| Corrective attendance | Tracks additional operational effort. |
What would a passing test show?
Use these hypothetical cases in a demonstration. Mark the evidence you have reviewed, then download the checklist. Selections stay in this tab.
Watch for this failure
Deleting a missed visit or replacing it with a fresh task hides the original obligation. Preserve the exception and remedy together so supervisors can investigate repeated issues and finance can explain any resulting adjustment.
Continue the evaluation
This example defines what to verify, rather than promising a particular Odoo feature. Keep a record of the demonstrated result, configuration, unresolved gaps and person who accepts it.
Read the wider implementation guideBring your workflow to the conversation.
Discuss requirements for Cleaning service businesses in a business needs review. Start with your current systems, the handoff that fails and the result you need to prove.
Sources & scope
The linked product documentation is a starting point for validating your chosen version, edition, apps and hosting. The scenarios and acceptance criteria are editorial planning guidance, not customer case studies or a guarantee of built-in functionality. See how this library is prepared.
Odoo 19: project management ↗Odoo 19: timesheet configuration and recording ↗Odoo 19: helpdesk after-sales workflows ↗