Work with the Schedule, Calendars and Blocked Dates

Use Cleaning Schedule for operational work and Calendar Management for reservations, availability, and blocked dates. Check both views when a unit must not accept or generate work for a period.

What you will accomplish

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

• Know the unit, start date, end date, and reason for the block.
• Confirm whether the block belongs in CleanOver or in the connected booking channel.
• 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: Choose the correct calendar

Open Calendar Management for reservation and availability changes. Use Cleaning Schedule when you are moving or reviewing work assignments.

Expected result: You are editing the system that owns the intended change.

Step 2: Find the unit and dates

Search for the unit and move to the correct month or week. Double-check the year when working far ahead.

Expected result: The complete blocked period is visible.

Step 3: Review existing reservations

Before adding a block, inspect any reservation, owner stay, or maintenance period touching the dates.

Expected result: The new block will not hide a real conflict.

Step 4: Add the block or reservation

Select the date range and use Add Reservation or the available block action. Enter a descriptive internal label and correct check-in/check-out boundaries.

Expected result: A clearly named calendar item covers the intended dates.

Step 5: Save and confirm the range

Verify the first and last blocked night after saving. Remember that checkout dates often behave as an end boundary rather than an occupied night.

Expected result: The visual bar matches the intended availability.

Step 6: Check connected channels

When a channel is connected, allow the sync to complete and verify the provider calendar if that provider is authoritative.

Expected result: CleanOver and the channel no longer disagree.

Step 7: Review generated jobs

Open Jobs and Cleaning Schedule around the block boundaries. Confirm required turnover or maintenance work still exists.

Expected result: The block did not remove a necessary operational job.

Step 8: Remove expired manual blocks

Review temporary blocks after the issue is resolved and remove only the exact obsolete record.

Expected result: Availability is reopened without affecting reservations.

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.