Why Room Inspection May Show a Different Completing User (MOP 2.0)

Why Room Inspection May Show a Different Completing User (MOP 2.0)

This article explains why the user shown as completing a Room Inspection task may differ from the user originally assigned to the task.

MOP records the user who completes a task—not necessarily the user to whom the task was originally assigned. This logic applies across Room Inspection and other task workflows and is part of MOP’s legacy task-completion design.

What Is Happening

In some cases, users may notice that:
  1. A Room Inspection task is assigned to one user (for example, a Room Attendant)
  2. The task appears as completed by a different user in Room Inspection views or reports
This behavior is functioning as designed.



How Task Completion Is Logged

MOP records and displays the user who completes the task, not the assigned user.
  1. If the assigned user starts and finishes the task, that user is recorded
  2. If the user who completes the task is different from the user it was assigned to, the completing user is the one who is recorded
This applies consistently across Room Inspection views, task history, and reporting.

Expected User Flow

The expected workflow is that:
  1. The assigned Room Attendant starts the room task
  2. The same user completes the task
This ensures accountability and accurate performance tracking.

Why a Different User May Complete the Task

MOP allows higher-level users (such as supervisors or managers) to complete tasks on behalf of others.
This behavior:
  1. Is intentional
  2. Exists due to legacy system logic
  3. Applies system-wide to all task types, not just Room Inspections
When this occurs, MOP correctly logs the user who performed the completion action.

Still Need Help With This Topic?

Ask Yourself:
  1. Was the task completed by a supervisor or manager instead of the assigned user?
  2. Did someone complete the task on behalf of the Room Attendant?
  3. Am I reviewing the Completed By field rather than the Assigned To field?
  4. Does this behavior occur with other task types?

Support May Ask You:
  1. Who was the task originally assigned to?
  2. Who completed the task?
  3. What role does the completing user have?
  4. Does this happen consistently or only in certain scenarios?

    • Related Articles

    • Housekeeping Task Lifecycle (MOP 2.0)

      Housekeeping tasks are a critical part of daily hotel operations, directly impacting room readiness, guest satisfaction, and internal coordination. In MOP 2.0, housekeeping tasks follow a structured lifecycle that provides real-time visibility into ...

    • MOP 2.0 Dashboard Overview

      The MOP 2.0 Dashboard is your control centre for tasks, room status, and operational workflows. From the left‐hand menu, you can access your tasks, team tasks, reports, and real-time updates — all based on your role’s privileges. Below you’ll find ...

    • Deactivate a User (MOP 2.0)

      In MOP, you cannot delete a user account entirely—but you can deactivate it to prevent further access. Follow the steps below to safely deactivate a user. Step-by-Step Instructions Path: Administration > Identity Management > Users Tip: If you want ...

    • Report Suspicious Activity (MOP 2.0)

      Report Suspicious Activity allows hotel staff to discreetly document and escalate potential security concerns directly within MOP. Submissions create a dedicated alert task, notify the appropriate team members, and ensure incidents are tracked, ...

    • Download Safety Alerts Report (MOP 2.0)

      The Download Safety Alerts Report feature allows authorized users to export a complete CSV file of safety-related alert activity. The report includes both active and archived alerts—specifically DND Alerts and Suspicious Activity—and is designed to ...