Maintenance — Which repair needs me?

Receive work, repair, record the result and request verification.

This page explains the proposed experience using educational data; it does not connect to or change the operational application.

Every issue has an owner and a next action.

1. Owner: maintenance. Next: start repair. Unit 302 stays out of service.
2. Start and complete the sample repair
3. Repair completed, awaiting coordinator verification. The unit is not ready yet.
4. Repair verified. The case is closed and the unit is ready.
5. Case reopened. Maintenance must resolve the issue again.

Only the information each role needs.

Guests see their own stay. Procurement does not need guest identity or payments. Hosts see necessary check-in and building information. Disciplinary decisions are not a default coordinator responsibility.