Assign Staff to a Job

Assign the right person by matching availability, skill, location, and the guest-ready deadline. CleanOver lets you assign from the job list or schedule board depending on how much context you need.

What you will accomplish

By the end of this guide, you will be able to complete a staff assignment from the correct CleanOver screen, understand the important checks before saving, and verify that the result is visible to the people who use it next.

Before you begin

• Confirm the job type, estimated duration, and next guest arrival.
• Review time off and specialized job authorization.
• Sign in to the Admin workspace and confirm you are in the correct business context.
• Use real operational dates and the property’s local timezone when the workflow includes time.

Step 1: Find the unassigned job

Open Jobs for the correct date and use Filters > Assigned Status > Unassigned. Confirm the unit and job type.

Expected result: The intended unassigned job is visible.

Step 2: Review the job requirements

Open the job detail and read access notes, checklist type, timing, and linked tickets before choosing a person.

Expected result: You know the skills and time window required.

Step 3: Check staff availability

Open Resource Planning or the schedule board and verify the worker is available, has capacity, and is already working in a practical area.

Expected result: The candidate can perform the work safely and on time.

Step 4: Choose the assignee

Use the assignee control on the job card or drag the card to the worker on the schedule. Select a team only when team-based dispatch is intended.

Expected result: The selected person or team appears on the job.

Step 5: Review warnings

Read overlap, authorization, or availability warnings. Choose another worker unless a documented operational exception has been approved.

Expected result: No unexplained warning remains.

Step 6: Save the assignment

Confirm the change and wait for the assignee to remain visible. Avoid making a second assignment while the first update is still saving.

Expected result: The assignment persists after refresh.

Step 7: Check the worker view

Confirm the job is visible to the worker and includes the correct instructions. For a new worker, test access before the shift starts.

Expected result: The assignee can open the job they are expected to complete.

Step 8: Communicate urgent changes

Send a direct operational notification when the job is same-day, reassigned, or time-critical.

Expected result: The worker is aware of the assignment, not just listed in the system.

How to confirm the workflow is complete

• Refresh the destination list or calendar and confirm the saved record appears only once.
• Check the unit, date, status, owner or assignee, and any linked record before leaving the page.
• Open the next downstream view mentioned in the guide and confirm it shows the same information.
• Record an internal note when the action corrects historical data or changes another person’s responsibility.

Common issues and what to do

The expected record is missing

Clear old filters, check the date and business context, then search by the most specific identifier available. If the data comes from a connected provider, check connection and mapping status before recreating it manually.

A button is disabled

Look for a required field, incomplete checklist item, missing permission, locked lifecycle status, or unresolved linked task. Complete the highlighted requirement instead of trying to bypass it.

The page shows different information after refresh

Another user or integration may have updated the record. Compare timestamps and the source system, then apply the correction in the system that owns the data.

You are unsure whether to continue

Stop before cancelling, overwriting, revoking, or issuing a financial document. Ask the workflow owner to confirm the intended outcome and add that decision to the internal record.

Best practices

• Use clear names that make sense to a new team member without extra context.
• Prefer the smallest safe scope for bulk actions, filters, permissions, and date ranges.
• Keep guest-facing communication separate from internal diagnostic notes.
• Verify a high-risk change in a second view before considering it finished.
• Update the source configuration when the same correction is needed repeatedly.