Move Jobs Around the Schedule Board

Use the schedule board to rebalance work when availability, travel, or guest timing changes. Moving a job changes the operational plan, so verify the date, person, and arrival window before finishing.

What you will accomplish

By the end of this guide, you will be able to complete a moved schedule job 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 may be moved and is not already in progress.
• Check the next guest arrival and any fixed access window.
• 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: Open Cleaning Schedule

Choose the day or week containing the job. Use filters to narrow the board when many teams are visible.

Expected result: The correct job card and destination are visible.

Step 2: Read the job timing

Open or inspect the card and note checkout, next check-in, job duration, and current assignee. These times define the safe movement window.

Expected result: You understand the job’s scheduling constraints.

Step 3: Check the destination cleaner

Review the person’s existing route, availability, and required job authorization before moving the card.

Expected result: The destination has enough time and the correct skills.

Step 4: Drag the job to its new position

Move the card to the intended cleaner and time slot. If the interface shows a warning, stop and read it instead of forcing the move.

Expected result: The card appears in the proposed destination.

Step 5: Review conflicts

Look for overlap, excessive travel, time-off conflicts, or another job displaced by the move. Adjust the surrounding plan if needed.

Expected result: The board has no unresolved warning around the moved job.

Step 6: Save or confirm the change

Complete the confirmation step when shown. Avoid repeated dragging while the update is saving.

Expected result: The assignment remains after the board refreshes.

Step 7: Verify in Jobs

Open Jobs for the same date and locate the unit. Confirm the displayed assignee and job status match the schedule board.

Expected result: Both views show the same assignment.

Step 8: Notify affected staff

Tell the previous and new assignee when the move changes responsibility or start time.

Expected result: No worker is relying on an outdated schedule.

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.