Hotel Room Inspection and Re-clean Workflow in TouteGestion
Hotel room inspection workflow with supervisor checklists, override controls, rejection reasons, immediate re-clean and separate hotel acceptance.
Why cleaning completion is not approval
The cleaner submits a room into Awaiting inspection. Supervisor Board treats that state as Waiting inspection and exposes an inspection action. This means the cleaner's statement that work is complete remains distinct from the supervisor's quality decision.
1. Cleaner submission has prerequisites
The cleaner cannot submit a room until every required cleaner checklist item is complete. Evidence count is also surfaced. If there are zero photos, TouteGestion warns the cleaner and requires explicit confirmation before allowing submission, while still permitting the workflow to continue.
2. TouteGestion loads a supervisor-specific checklist
When an inspection is opened, Supervisor Board requests the task checklist for phase=supervisor_inspection. The supervisor therefore reviews an inspection checklist rather than simply inheriting the cleaner's completion action as proof of quality.
3. Approval has a control for incomplete inspection items
If all required supervisor checklist items are checked, the supervisor can approve normally. If they are not all checked, approval requires an override reason. The approval request records the inspection checklist, supervisor notes and any override reason.
4. Rejection requires a reason
The implemented rejection choices include Bathroom issue, Bed issue, Dust found, Missing towels, Floor not clean, Amenities missing, Damage found, Guest item found and Other. If Other is selected, the supervisor enters the custom reason. A rejection cannot be submitted without a reason.
5. Rejection creates immediate re-clean
The rejection call sends assign_reclean_immediately=true. In the cleaner workspace, rejected tasks are deliberately classified as Re-clean required. The latest rejection reason, inspection notes and inspector information are surfaced so the cleaner can correct the failed quality point.
6. The cleaner starts the re-clean
A rejected room uses Start re-clean rather than being treated as a brand-new unrelated room. The same operational task continues through correction and resubmission, preserving the reason the first attempt failed.
7. Hotel acceptance follows supervisor quality control
The separate Acceptance screen lists pending acceptance records. Authorised hotel-side users—platform admin, hotel manager or receptionist in the current UI—can accept the room or raise a dispute with notes. Completed decisions remain visible in acceptance history.
Worked example
Room 508 reaches Awaiting inspection after its cleaner completes the required checklist. The supervisor opens inspection and checks the supervisor checklist. 'Bathroom floor' fails, so the supervisor selects Floor not clean and rejects. TouteGestion immediately returns the room to the re-clean workflow and the cleaner sees the rejection reason. After correction and resubmission, the supervisor approves. The hotel-side acceptance actor then either accepts the room or raises a dispute; that decision is stored separately from the supervisor inspection.
Review room operations in the live product workflow.
See how workload, cleaning, inspection, exceptions and acceptance work together.