Settle the pack in advance
Agree which enquiry, booking, feedback and workload figures the meeting reads, so the pack is settled before anyone opens a panel.
Replace isolated dashboards with a review rhythm that explains what changed, why it matters and who owns the next step.
Hotel performance insights connect defined data points to a business question and decision. Instead of reporting every available metric, teams focus on guest-journey friction, direct-booking progress, response and follow-up signals that have a clear owner.
Every module or service needs a defined guest outcome, hotel owner and review signal.
Agree which enquiry, booking, feedback and workload figures the meeting reads, so the pack is settled before anyone opens a panel.
Each module keeps its own range control, so record the period every figure was read on and use the same one at the next review.
Carry each agreed action out with an owner and a date, then reopen it at the next review before anything new is added.

Replace isolated dashboards with a review rhythm that explains what changed, why it matters and who owns the next step.
Each capability is tied to a real guest decision, hotel owner and visible next action.
Read the CRM's pipeline stage drop-off, recorded lost reasons and weighted forecast on a three, six or twelve-month window.
The planner's Stats view computes the prior window automatically and shows it as a dashed series with a delta on each KPI tile.
The planner counts untracked completions separately and scores on-time rate only over tracked work, so the pack shows what it cannot measure.
Bring open task age buckets, completion rate and planned-versus-worked hours into the review, so staffing pressure sits beside commercial figures.
Per-survey analytics report average rating, NPS and per-question breakdowns on a seven, thirty or ninety-day view.
CRM list and deal views export as CSV or Excel, while planner Stats and review submissions export as CSV for an owner, asset manager or accountant.
A shared sequence makes ownership and handover easier to inspect.
Choose the few figures each role will be held to.
Build the pack from the panels those figures live in.
Work the agenda, agree owners and record due dates.
Start the next review with last month's actions.
Use these checks to compare options, document ownership and avoid a disconnected implementation.
Define what the owner or team needs to decide before selecting a dashboard, report or metric.
Agree sources, time windows, exclusions and ownership so teams interpret performance consistently.
Every recurring review should identify a responsible owner, due date and evidence needed for the next decision.
The panels show what was recorded against an enquiry, booking or task; they do not model which marketing effort caused a stay.
The work here is the agenda, the owner and the follow-up, while the panels themselves sit in the CRM, the planner and the review module.
Clear scope matters more than broad promises.
Start from the decisions the meeting has to make, then include only the panels that inform them. In practice that is usually pipeline stage drop-off, recorded lost reasons, guest feedback trend and outstanding work. Anything that has not changed a decision in three months can leave the pack.
You can see the source recorded on an enquiry when it was created, and how enquiries from each recorded source progressed to won or lost. That is a record, not a model. It does not account for guests who saw several touchpoints before enquiring, so it should not be read as proof that one channel caused a stay.
No. The PMS stays the system of record for rooms, rates, inventory and reservations, and rate strategy stays with your revenue tool or revenue manager. The reporting here covers the enquiry, booking request, feedback and task activity that runs inside the platform.
No. Each module keeps its own reporting surface, and their period controls differ: CRM reports run on a three, six or twelve-month window, the planner's Stats view offers its own ranges plus a custom From and To, and review analytics runs on seven, thirty or ninety days. The pack is assembled by a person from those panels, which is why agreeing the shortlist and recording the period matters.
Map the guest decision, current systems, team owner and smallest useful next step.