Add and Organize Units

A unit is the operational home for reservations, jobs, checklists, access notes, rates, tickets, and forms. Create it carefully so every downstream module points to the same property.

What you will accomplish

By the end of this guide, you will be able to complete a CleanOver unit 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 the official address, unit number, timezone, check-in/out times, and operational alias.
• Check whether the unit already exists under another name.
• 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 Units

Go to Units > Units and search by address, unit number, or alias. Review inactive records as well as active ones before adding a duplicate.

Expected result: No existing unit represents the property.

Step 2: Create the unit

Select the add-unit action and enter a concise alias plus the complete address and unit number.

Expected result: The property can be uniquely identified in lists.

Step 3: Set location and timezone

Choose the correct region, building or unit group, and IANA timezone. Timezone accuracy affects reservations, schedules, messages, and check-ins.

Expected result: Dates and local times will be interpreted correctly.

Step 4: Add operational details

Enter check-in/out times, access guidance, parking, Wi-Fi, supply locations, and cleaning notes in their appropriate fields.

Expected result: Field staff can prepare without searching external messages.

Step 5: Set unit type and status

Choose rentable unit or common area and set the active status. Common areas should not appear in guest booking surfaces.

Expected result: The unit appears only in appropriate workflows.

Step 6: Organize with groups and tags

Assign the unit to the correct building, region, or operational group and add consistent tags used by filters.

Expected result: Coordinators can find the unit with normal filters.

Step 7: Attach forms and checklists

Create the relevant unit data form and verify the Clean, Audit, and Maintenance checklist cells.

Expected result: The unit has the required operating information and standards.

Step 8: Map the channel listing

If the unit is channel-managed, connect the exact external listing in Listing Mapping and verify a known reservation.

Expected result: Provider data flows to this unit, not a duplicate record.

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.