Single property first · portfolio capable

Expand the operating record without redesigning the decision.

The active property remains the primary workspace. This surface proves the next step: capture or import additional property records, compare the same governed fields, and preserve each property’s decision and approval context.

Import property JSON Return to property workspace No action taken.

Portfolio rollup

Comparable properties, visible caveats

0 properties

Forecast revenue$0Sum of captured property forecasts

Forecast GOP$0Current owner economics

Available rooms0After out-of-order inventory

Approval coverage0%Approved or approved with conditions

Property comparison

One data contract across every property

Imported and captured values remain attributable to their source record.

Property	Profile	Rooms	Occupancy	RevPAR	GOPPAR	Facilities	Approval	Updated
Capture the active property or import a record to begin.

Expansion boundary

What changes as multi-property operations grow

IdentityOrganization and property membership

Add named users, property membership, role assignments, and separation of duties to the existing server-verified access layer.

DataProperty-scoped tenant isolation

Partition encrypted records, evidence, audit events, and exports by organization and property as customer portfolios are added.

GovernancePolicy and approval enforcement

Enforce who may view, edit, approve, override, export, or write memory at property and portfolio levels.

IntegrationRepeatable hotel data contracts

Use the same property schema for PMS, CRS, RMS, POS, labor, finance, engineering, and benchmarking feeds.