Business Intelligence for Travel & Hospitality: RevPAR, Channel Mix, and Guest Analytics

A hotel group's BI team builds RevPAR dashboards. The VP of Revenue reviews and finds the dashboard's RevPAR differs from what STR (Smith Travel Research) reports. The reasons are familiar at every hotel group that builds BI without hospitality discipline: the dashboard calculates RevPAR using room revenue from the PMS; STR uses a specific revenue definition that includes or excludes certain items. The dashboard counts available rooms as physical inventory; STR adjusts for out-of-order rooms differently. The comp set definition in the dashboard doesn't match the STR STAR report comp set. ADR calculation handles day-use rooms and complimentary rooms differently. Each difference is small. Together they mean the dashboard can't be used in the monthly STR review — which is the industry-standard benchmarking conversation every hotel GM and revenue manager has.

Hospitality BI done right encodes the STR methodology and the hotel group's internal KPI definitions correctly from day one. RevPAR using STR-aligned revenue definition and room count methodology. ADR with day-use, complimentary, and house-use treatment matching the group's policy. Occupancy with out-of-order treatment. Channel mix with OTA commission impact on net revenue — showing not just gross channel contribution but net-of-commission contribution that affects GOPPAR. TRevPAR including F&B, spa, activities, and other revenue. Guest segmentation by value tier, loyalty status, and booking channel. All sourced from the PMS (Opera, Mews, Cloudbeds), CRS, channel manager, and F&B/POS with reconciliation to the night audit. Done this way, BI serves revenue management, operations, and ownership reporting. Done generically, the STR review reveals the mismatch every month.