Skip to content
Mizban
New experience guide

Operations coordinator — What remains unresolved?

Cases, ownership, rounds and verification.

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

ReportCaseOwnerRepair / supplyVerifyClose or reopen

Every issue has an owner and a next action.

  1. Case #104 • Sepidar, unit 302 • reported by the host • high priority • sample time 10:30. Actions and results stay with the case.
  2. Owner: maintenance. Next: start repair. Unit 302 stays out of service.
  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.

Periodic tasks with a clear scope

Tasks can cover all buildings, one building, all units, one unit or a facility. Each building's completion and verification are tracked independently.

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.

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.

Existing illustrated tutorialsTry the demo