Reputation KPIs for a hotel general manager: what to watch weekly

A general manager does not run a hotel looking only at occupancy and ADR. Reputation is a financial asset, and like any asset, it needs indicators you review with rhythm. The problem is that most GMs look at one thing only: the star average on the OTAs. That number is the result, not the dashboard. Here are the KPIs a manager should read every week to govern reputation before reputation governs them.

Why reputation is a financial KPI, not a cosmetic one

Before the list, the compelling reason. The classic Cornell research, led by Chris Anderson at the Center for Hospitality Research, found that raising your online reputation by one point is associated with an increase of up to 1.42% in RevPAR, with a stronger effect on independent and midscale hotels. Translation for the GM: reputation is not makeup, it is revenue per available room. Measuring it badly costs real money.

1. Feedback volume: how many guests talk to you

The first KPI is not the score, it is how many people are rating you. Low volume means you decide blind, with a sample that represents nothing. High and growing volume means your thermometer is reliable. Review each week how many ratings you collected in situ. If the number is thin, your problem is not satisfaction, it is that you are not measuring it. Unlimited QR codes per point exist precisely to raise this number.

2. Trend of the average rating, week over week

Do not look at the historical total; it dilutes everything. Look at this week’s score against last week’s. The direction is the signal. A stable average that starts falling is an early alarm that gives you time to act. The GM who only sees the total learns of problems when they are already public and irreversible.

3. Service recovery rate and speed

This is the KPI that separates a reactive hotel from an excellent one. When a low rating arrives during the stay, how long do you take to address it? Measure two things: what percentage of low alerts you turned into a rescue, and how much time passes between alert and action. An immediate alert only matters if someone responds fast. An upset guest rescued in 20 minutes leaves happy; ignored, they leave to write the public review that costs you RevPAR.

4. Pending vs resolved incidents

Every complaint should have a visible life cycle: born pending, dies resolved. The KPI is your backlog. How many incidents are still open at the close of the week? A growing backlog is operational debt that sooner or later erupts into reviews. A backlog at zero means your team closes the loops. Review this the way you review the cash drawer: nothing stays open without a reason.

5. Ranking by area: where you win and where you lose

A global average hides that the room delights and the restaurant disappoints. The weekly KPI is the breakdown by area. Sort your spaces from best to worst rated and act on the tail. The advantage of a located QR is that this ranking builds itself, without you having to interpret comments by hand.

6. Ranking by employee: reputation has a face

The experience is produced by people. The rating ranking by employee tells you whom to recognize and whom to support. Use it carefully and with context, never as a whip, but use it. A GM who recognizes the best rated employee each week builds a culture where good service is seen and rewarded.

How to read them together: the Monday ritual

Isolated KPIs are data; together they are a story. Turn this into a fifteen minute weekly ritual:

• Volume: did we collect enough ratings to trust the rest?
• Trend: is the score up, down, or flat against last week?
• Recovery: how many low alerts did we rescue and how fast?
• Backlog: how many incidents are still open and why?
• Rankings: which area and which employee are rising, which need support?

That dashboard turns the manager from a spectator of the average into an operator of reputation. You stop reacting to the public autopsy and start governing the private diagnosis, every week, with numbers that translate directly into RevPAR.