Who this is for
Chief commercial officer, group revenue office, group brand office, corporate systems team and the Suite Profit onboarding architect assigned to the portfolio. Property revenue managers and GMs sit downstream — they consume the governance the Command Centre publishes and can request exceptions, but they do not author group policy.
Prerequisites
- Every property in the portfolio connected to the Suite Profit operator console under corporate SSO.
- Portfolio brand register agreed with the group brand office — which brand each property belongs to.
- Corporate revenue office charter that defines who approves what: group revenue director, group commercial director, chief commercial officer.
- Multi-Property Command Centre entitlement live on the portfolio.
Step 1 — Author the master rate matrix
The master rate matrix defines reference BAR by room class, rate-plan skeleton (BAR, non-refundable, breakfast-included, corporate, long-stay), floor and ceiling logic expressed as formulas rather than absolute currency values, and compset-selection rules per brand. The group revenue director owns the matrix; the chief commercial officer signs off on quarterly changes. The Command Centre stores every version indefinitely; a governance-audit tab shows who changed what and when.
Step 2 — Per-brand multipliers
Absolute values are almost never correct at group level. Each brand receives a multiplier that reflects its market position:
- Multiplier — applied first to the master reference BAR. A premium heritage brand at 1.35, a select-service brand at 0.82.
- Voice modifier — attached to communication templates so brand tone flows through the guest experience automatically.
- Compset weighting — how heavily the brand tracks its own compset versus the group median.
Step 3 — Per-property overrides
Property overrides sit below brand multipliers in the precedence stack. The Command Centre resolves every setting through a five-layer stack, from lowest to highest priority: group default, brand default, regional cluster default (optional layer for portfolios with a Warsaw cluster and a Tricity cluster, for example), property override and date-range override. In the console any operator can hover a resolved value and see which layer produced it, which removes an entire class of governance disputes.
Step 4 — Master calendar for restrictions
The master calendar holds group-wide restrictions: minimum length of stay per season, closed-to-arrival windows around major maintenance projects, closed-to-departure on marquee sold-out weekends, and hold-back windows for corporate accounts. Restrictions inherit down the precedence stack the same way rates do. The calendar view shows every property in the portfolio in a heatmap so the group revenue office can see policy gaps at a glance.
Step 5 — Master package library
Packages — romance, family, spa, corporate, MICE, seasonal — are authored once in the master library and published to selected properties in one click. Each package carries a brand-eligibility filter, a rate-plan attachment, an ancillary inclusion list and a governance flag: Group-mandatory, Group-recommended or Property-optional. Property revenue managers cannot silently retire a group-mandatory package; they can only request an exception.
Step 6 — Approval workflow with the corporate revenue office
Every change above a threshold routes through a signed approval workflow. Default thresholds:
- Master BAR change > 3% — one-eyes approval by the group revenue director.
- Master BAR change > 8% — two-eyes approval by the group revenue director and chief commercial officer.
- New master package or restriction across more than five properties — approval by the group commercial director.
- Exception window for a local event — approval by the property revenue manager and the group revenue director on file.
Approvals are recorded in the governance-audit tab, mirrored to the corporate revenue office SharePoint and available to external auditors on request.
Estimated timeline
For a portfolio of three to fifteen properties, initial governance configuration runs six to nine weeks: two weeks of policy scoping with the corporate revenue office, two to three weeks of master matrix and master calendar authoring under group revenue office review, two weeks of per-brand and per-property override loading, and a two-week measured cutover during which property revenue managers shadow the Command Centre before it becomes the authoritative source.