Why Hotels Need More Than Another Dashboard to Turn Operational Data Into Timely Action

A dashboard can be beautifully designed, updated in real time and still have almost no impact on the operation. Information is not a decision. A decision is not execution. And none of it matters if the guest in room 614 still has no hot water while twelve green KPIs glow happily on a screen downstairs.
By Marty McDaniel, CHA, CEO of The Northstar Companies - 9.29.2026

Hotels have never suffered from a shortage of reports. We have reports about revenue, labor, guest scores, maintenance, sales, breakfast, channel mix and — on a good day — a report explaining why another report is wrong. Technology has made those reports faster and prettier. Occupancy. ADR. RevPAR. Pickup. Pace. Overtime. Service tickets. Energy use. We can put almost anything on a dashboard now. That is progress. It is also where the trouble starts.

A dashboard can be beautifully designed, updated in real time and still have almost no impact on the operation. Information is not a decision. A decision is not execution. And none of it matters if the guest in room 614 still has no hot water while twelve green KPIs glow happily on a screen downstairs.

A 2026 survey of hotel owners and operators illustrates the gap. Ninety-one percent of respondents said they still rely on some level of manual reporting. Only 11% reported a fully integrated technology stack, and just 15% were very confident in the accuracy and timeliness of their operational data. That is not primarily an AI problem. It is an operating-system problem.

A dashboard is a display, not a decision system

The operator does not wake up needing a dashboard. The operator wakes up needing answers. What changed? Why did it change? Does it matter? Who owns the response? What happens next? If the technology cannot help the team move through those questions, the hotel has reporting, not intelligence. I have sat in enough morning meetings to know the difference.

A report that tells me labor was high yesterday is interesting. A signal at 11 a.m. that tells me today’s schedule is about to go high — while I can still change it — is useful. For years, hospitality technology has been purchased department by department. Revenue has its systems. Front office has its systems. Housekeeping, engineering, finance, sales, F&B and guest engagement have theirs. Each tool may do its job well, yet the GM is left to reconcile the hotel across multiple screens, exports and definitions. At some point, the general manager becomes the integration layer. That is not a technology strategy.

Start with exceptions, not averages

Most hotel managers do not need a wall of green metrics confirming that yesterday was normal. They need to know what moved outside an expected range and whether it deserves attention. Housekeeping hours per occupied room jumped. A premium room type is being sold without its normal premium. Guest-service tickets are clustering around one floor. Overtime is appearing before the weekend arrives. Breakfast check average is stable but labor hours are not. The same piece of equipment is generating its fourth maintenance call.

Those are operating exceptions. Good technology should surface them early, attach context and reduce the time required to decide whether they are noise or a real problem. That is different from saying, “Here are 47 KPIs.” The operator’s scarce resource is not data. It is attention.

One definition of truth matters more than one screen

The industry spends a great deal of time talking about a single source of truth. In practice, hotels will continue using multiple systems. The more important goal is a single definition of truth. If finance calculates labor productivity one way, operations another way and ownership a third way, integration alone will not solve the argument.

The same is true for occupancy, out-of-order rooms, ancillary revenue, channel cost and forecast variance. That work is not glamorous. Nobody has ever cut a ribbon for a clean data dictionary. But trust begins there. A manager who has been burned by three conflicting reports will ignore the fourth, no matter how much AI is sprinkled on top.

The value of data has an expiration date

Hotel operations run by shift and by day. Timing matters as much as accuracy. A labor overage discovered at month-end is an accounting fact. The same overage identified at 11 a.m., while the schedule can still be changed, is an operating tool. A guest-satisfaction trend reported after 30 surveys is interesting. A cluster of similar service failures identified while the affected guests are still in house is actionable. I think of it as a window of usefulness. The closer the signal gets to the moment when a manager can still change the outcome, the more valuable the data becomes. After the window closes, the dashboard becomes an autopsy report. Accurate, perhaps. Helpful for learning, yes. Not much use to the guest who already checked out.

AI can be a terrific bloodhound. It is not the hotel manager.

Artificial intelligence is being embedded across hotel technology, and much of that work is promising. AI can identify patterns faster than a person, summarize large volumes of information, flag anomalies, suggest causes and prioritize work. But AI does not make bad definitions good. It does not make stale data current. It does not create accountability where none exists.

If a hotel’s underlying data is fragmented or unreliable, an AI layer can produce a faster, more confident version of the wrong answer. The most useful application of AI in operations is not replacing the operator. It is acting like a very fast bloodhound: find the trail, surface the issue, narrow the search. Then let someone who understands the building make the call. Hotels remain physical places full of people, equipment, judgment and trade-offs. The software does not have to explain to the wedding party why one elevator is down. The operator does.

Design technology around the operating rhythm

Hotels already have an operating cadence: morning stand-up, daily revenue call, housekeeping boards, engineering rounds, weekly labor review, sales strategy and monthly financial review. Technology should fit those moments instead of asking the operation to invent new rituals for the software.

For the morning meeting, the system should surface overnight exceptions, unresolved guest issues, staffing pressure, out-of-order rooms, arrivals needing attention and commercial changes large enough to affect the day. For the weekly revenue meeting, it should connect pickup and pricing to channel cost, segment mix and operating consequences. For the monthly review, it should show not only that a variance occurred, but whether the same issue appeared earlier and whether anyone acted on it. This is also where the P&L belongs in the conversation.

The P&L is essential, but it is a lagging indicator. Pace, pickup, booking-window shifts, overtime, maintenance work-order age, out-of-order rooms and recurring guest complaints often move first. The monthly statement should confirm the operating story, not reveal it for the first time.

Close the loop or stop pretending it is intelligence

This is the part most dashboards miss. A useful operating system should not stop when it identifies a problem. If overtime is above threshold, who received the exception? What action was assigned? Was the schedule changed? Did the metric improve? If guest complaints are rising around HVAC, was a work order created? Was the recurring root cause identified? Did the rooms return to service? Without that loop, hotels can become remarkably sophisticated at observing themselves. I have no objection to a beautiful dashboard. I object to admiring one while the same problem appears three mornings in a row.

The operator’s technology test

Before adding another system, I would ask six questions: Does it eliminate a manual step? Does it reconcile data the team currently argues about? Does it surface an exception sooner? Does it identify an owner? Can action be taken from the same workflow? Can we tell whether the action worked? If the answer is no, the technology may still be useful, but it is probably not transforming the operation. Hotel operators do not need to know everything happening in the building every second. They need to know what matters now, why it matters and who is doing something about it.

The future of hotel technology will certainly include better dashboards, more automation and more AI. But the winning systems will be the ones that disappear into the work: fewer reconciliations, fewer screens, fewer late surprises and clearer decisions. Because the dashboard is not the operation. The operation is what happens next — usually before lunch.

Marty McDaniel, CHA, is a second-generation hotelier with 38 years of senior hospitality leadership experience spanning hotel and resort operations, multi-property leadership, development, renovations, revenue strategy, turnarounds and advisory work. He is Chairman & CEO of The Northstar Companies. Northstar brings operational leadership, market intelligence and proprietary decision technology to hospitality assets facing performance pressure, transition, distress or opportunity. He has previously contributed to Hotel Business, Lodging and Hotel Management.

Are you an industry thought leader with a point of view on hotel technology that you would like to share with our readers? If so, we invite you to review our editorial guidelines and submit your article for publishing consideration.