How to onboard the next property

Practical guide for adding another property to an existing organization in hotel-portal.

Overview

After your first property is live or structurally ready, the next important operator task is often onboarding another property in the same organization.

The goal is not to repeat registration. The goal is to reuse the same organization workspace and follow the property onboarding sequence again.

When to add another property

You should onboard another property in the same organization when:

the hotel belongs to the same company or chain workspace
the same operations team should manage it in the same environment
you want one portfolio view across multiple hotels

You should not create a whole new organization unless the business boundary is actually different.

Recommended sequence

For each new property, use this order:

open the onboarding lane
create the new property draft
complete the property profile
build rooms and rates
load inventory
configure PMS or import setup
review readiness

The workflow should feel familiar and repeatable after the first property.

What should already be reused

By the time you onboard the next property, the organization-level basics should already exist, such as:

workspace/company identity
operator access
portfolio context

That means the work should focus on the property itself, not on rebuilding the entire workspace.

What to watch for

When onboarding the next property, pay attention to:

correct property name and address
correct room and rate structure for that hotel
correct PMS mapping identifiers
inventory loading for the right property

This is especially important when teams manage multiple hotels in the same workspace.

Use Ask AI to move faster

Useful prompts for multi-property rollout:

"Help me onboard the next property in this organization"
"What should I copy from the first property and what should I not copy?"
"What is missing before this new property can go live?"