Who this is for
Chief commercial officer, group revenue director, brand revenue leads, corporate systems and the Suite Profit onboarding architect assigned to the portfolio. Property-level revenue managers are execution consumers of the decision matrix; they act inside the guardrails the group publishes.
Prerequisites
- Multi-Property Command Centre configured and the property roster loaded.
- Twelve months of Profitroom Suite pace, occupancy and ADR history available per property.
- Compset selection agreed per brand — five to twenty competitor properties per brand cluster.
- Corporate revenue charter that defines threshold-based approvals.
Step 1 — Author the group decision matrix
The Rate Intelligence Engine reads decisions from a single group-owned matrix rather than a per-property rule pile. The matrix expresses each pricing decision as a signed row: input signal, threshold, response, brand scope, property scope, effective window and approver. The group revenue director owns matrix authorship; the chief commercial officer signs off on quarterly publications. Every row is versioned and reversible.
Step 2 — Set target ADR bands per brand
Each brand carries an ADR band expressed in EUR net, converted to local currency at publish time. A premium heritage brand might sit in the €160-240 band on weekend leisure and €140-190 on mid-week corporate; a select-service brand in the €70-110 band year-round with a €130 shoulder ceiling on trade-fair weeks. Bands are the outer envelope: floors and ceilings live inside them and the engine never publishes outside the band without a signed exception.
Step 3 — Compression thresholds
Compression thresholds are how the portfolio decides to hold price versus flex it up. A typical set:
- Occupancy < 55% by D-30 — hold at the lower half of the band, activate weekend leisure promotion.
- Occupancy 55-80% by D-14 — mid-band with pace-linked adjustments.
- Occupancy > 80% by D-7 — push toward ceiling, close discounted rate plans.
- Compset compression > 85% for D+1 to D+3 — override to ceiling irrespective of own-pace.
Step 4 — Minimum length-of-stay defaults per season
Length-of-stay defaults live on the master calendar in the Multi-Property Command Centre and are consumed by the Rate Intelligence Engine as constraints. A high-summer coastal brand runs a 3-night MLOS on Fridays through Sundays and a 2-night MLOS on Christmas and Easter. A city business brand runs a 2-night MLOS on trade-fair weeks and no MLOS otherwise. Defaults are published per brand and inherited by every property in that brand.
Step 5 — Per-brand ceilings and exception windows
Ceilings prevent brand-integrity damage during compression events. A heritage brand ceiling of 2.2x reference BAR keeps ADR credible on peak weekends without publishing rates the guest will screenshot. Exception windows carve out local events — Impact CEE in Warsaw, Wianki in Kraków, MTP fair weeks in Poznań, the summer festival calendar in Sopot — during which the ceiling temporarily rises by a signed offset. Every exception window is approved by the group revenue director and, above 2.6x, by the chief commercial officer.
Step 6 — Audit-trail signature protocol
Every published row of the decision matrix carries a signature block: author, approver, effective from, effective to, digest hash and rollback pointer. The audit trail is exportable in a machine-readable form for the corporate revenue office and, on request, for external revenue audit or brand-parity reviews. When a property revenue manager requests an exception, the request itself becomes a signed row and joins the same audit trail.
Portfolio benchmarks
From Suite Profit's onboarding cohort of hotel-group portfolios on Profitroom Suite, we observe median RevPAR uplift in the +5.8% to +9.4% band after 120 days of the Rate Intelligence Engine operating under a signed group decision matrix, compared with the previous per-property status quo. Portfolios that also adopt the Multi-Property Command Centre master calendar in the same window see uplift closer to the top of that band.
Estimated timeline
For a portfolio of three to fifteen properties, initial rate-governance rollout runs eight to twelve weeks: two weeks of policy scoping with the corporate revenue office, three weeks of decision-matrix authoring and simulation across the property roster, two to three weeks of controlled publish waves with the group revenue director signing each wave, and a two-week measured window before the previous per-property rule stack is retired.