Plan Cleaner Availability for the Week

Resource Planning shows when staff can work, are unavailable, or have time off. Keep it current before assigning jobs or running Auto Fill.

What you will accomplish

By the end of this guide, you will be able to complete a weekly availability plan 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

• Collect approved working hours, time off, and recurring availability.
• Open the week before jobs are finalized.
• 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 Resource Planning

Go to Team Management > Resource Planning and choose the target week. Confirm the displayed timezone and team scope.

Expected result: The board represents the correct week and people.

Step 2: Review the legend

Understand the colors for Available, Time Off, and Other. Do not assume an empty cell means available.

Expected result: You can interpret every existing block.

Step 3: Add normal availability

Select the worker and time range, choose Available, and set the hours. Use recurring weekday options for a stable weekly pattern.

Expected result: The worker’s normal hours are visible.

Step 4: Record time off

Add approved time off with the correct start and end. Include a brief internal reason only when policy permits.

Expected result: Dispatch will not treat the worker as available.

Step 5: Add exceptions

Use Other for training, meetings, or partial constraints that are neither working availability nor leave.

Expected result: Special constraints remain visible to planners.

Step 6: Check company and daily capacity

Review group limits and the worker’s existing workload. Availability is permission to schedule, not unlimited capacity.

Expected result: The plan is realistic for the number and duration of jobs.

Step 7: Compare with Cleaning Schedule

Open the same week on Cleaning Schedule and look for jobs outside available hours or conflicting with time off.

Expected result: Every assigned job fits the availability plan.

Step 8: Publish changes early

Save changes and notify the dispatcher when same-week availability changes after assignments were made.

Expected result: Operations can rebalance work before service is at risk.

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.