Record the subcontractor's reported outcome separately from the coordinator's completion decision. If access failed, parts are missing or another trade is needed, preserve the unresolved scope and next owner. Review the contractor charge against the agreed attendance and work evidence instead of treating an incoming invoice as proof of completion.
Understand the decision
A contractor may bill for a visit that established the cause but did not fix the issue. The occupant still needs a clear next step, while finance needs to understand the charge. The task structure should retain both the completed investigation and the remaining repair obligation.
Work through the requirements
- Capture the actual attendance outcome.
- Assign the unresolved work explicitly.
- Review charges against approved instructions.
| Record or decision | Why it matters |
|---|---|
| Attendance evidence | Explains work performed and limitations. |
| Outstanding action | Keeps remaining work owned and visible. |
| Invoice review | Connects charges to authorization and evidence. |
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
An invoice date and a task completion date may describe different events. Require a review of the actual outcome, preserve unfinished obligations and keep the occupant communication aligned with what has genuinely been resolved.
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 Property maintenance 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: helpdesk after-sales workflows ↗Odoo 19: field service materials and warehouse configuration ↗Odoo 19: project management ↗