The operational tax hotel groups don’t realize they’re paying
Linda Girrbach
Hotel teams are overwhelmed not by strategy, but by repetitive daily tasks that quietly consume thousands of hours across portfolios. This hidden operational tax misuses expert time.
Across hotel groups, there is an ongoing conversation about automation. It usually revolves around AI, pricing sophistication, guest messaging, and personalization. Boards ask about it. Owners expect it. Vendors promote it.
Yet during a recent webinar with hotel leaders across regions, one theme surfaced repeatedly. Teams are not overwhelmed by strategy. They are overwhelmed by repetition. The quiet execution that keeps operations running every day is what consumes the most time.
This insight reflects what many operators acknowledge privately across portfolios. Innovation may capture attention, but repetition dominates reality.
Revenue managers build the same pickup reports every morning. Finance teams reconcile OTA commissions line by line. Operations staff manually route virtual credit cards. Guest profiles are cleaned, merged, and corrected. Rate codes are updated across multiple systems.
Individually, none of these tasks feel transformational.
Collectively, they form something far more serious.
And that is not work. That is tax on your operation.
What is an operational tax?
An operational tax is work that:
· - Must be done
· - Follows clear, repeatable rules
· - Is performed daily or weekly
· - Does not require strategic judgment
· - Scales linearly with the number of properties
It is not innovation or differentiation.
It is mechanical execution.
The reason it often goes unnoticed is simple. Per property, the time cost feels manageable. Thirty minutes here. An hour there. A few minutes per update. No single task appears significant enough to justify change.
But hotel groups do not operate one property. They operate ten, fifty, two hundred, or more.
That is where the math changes.
When small tasks become structural barriers
Consider rate code management. On its own, creating or updating a rate code may take only a few minutes. Multiply that by hundreds of properties and hundreds of updates per year across PMS, CRS, and channel systems.
- One large hotel group calculated the impact of automating this single workflow. The result was the equivalent of 312 working days saved per year.
- Not because the task was complex, but because the volume was high.
- This is the defining characteristic of operational tax. Small, repetitive tasks become structural barriers at scale. What feels like routine administration in one property becomes months of human effort across a group.
The same applies to daily pickup reporting. One hour per day per property becomes nearly a full month of labor per year. Multiply that across a portfolio and full time positions are effectively dedicated to extracting, formatting, and emailing data.
Not analysis. Not strategy.
At that point, the issue is no longer efficiency. It is operational design.
The misallocation of expertise
The deeper issue is not just time lost. It is expertise misused.
Commercial teams often spend 60 to 70 percent of their time on manual, repetitive tasks. That leaves only a fraction for strategic work such as interpreting market shifts, negotiating contracts, adjusting distribution mix, and anticipating demand changes.
As discussed during the session, your expertise lies in the decision, not the data gathering.
Pulling data from a PMS does not require expertise. Copying figures into a report does not require expertise. Reconciling spreadsheet line items does not require expertise.
Interpreting why RevPAR is declining despite strong occupancy does. Designing a pricing response does. Repositioning a property within a shifting competitive set does.
Workflow automation does not eliminate judgment. It protects it.
The illusion of progress
On the surface, the industry appears to be advancing rapidly.
Most hotel groups report using AI or automation in some form. Revenue Management Systems are widespread. Chatbots are common. Technology stacks continue to expand.
Yet adoption is not the same as transformation.
Trust in automation remains moderate. Many organizations are experimenting, but few are redesigning their operations around it. Only a small percentage have a company wide automation strategy led by senior leadership. A significant portion cannot clearly measure the return on automation investments.
Automating pricing decisions while leaving execution manual creates imbalance. Intelligent outputs still depend on fragile, human driven processes beneath them. Rate changes must still be loaded. Reports must still be compiled. Data must still be reconciled.
The visible layer modernizes. The operational backbone remains unchanged.
And the operational tax continues to accumulate.
Why it persists
If the math is so clear, why does operational tax continue?
Operational tax persists for structural reasons.
First, it is normalized. Every hotel has always done it this way. Tasks are embedded in routines and rarely questioned.
Second, responsibility is fragmented. Revenue automates revenue tasks. Finance optimizes finance workflows. Operations manages operations processes. Rarely does someone step back and assess the total human effort across the group.
Third, readiness varies. Effective automation requires documented processes, reliable data, system integration, and cross team alignment. Without these foundations, early attempts often fail and skepticism grows.
The challenge is rarely technological. It is organizational.
What removing the tax really means
Removing operational tax does not require a radical overhaul on day one. It starts with one repetitive, rule based workflow.
- A
daily report.
- A commission validation process.
- Virtual credit card routing.
- VIP tagging.
When one task runs automatically, reliably, and consistently, something shifts. Confidence increases. Time is freed. Teams see tangible impact.
The goal is not to automate everything.
The goal is to redesign how human expertise is applied.
Experts should make decisions, interpret context, negotiate relationships, and set strategy. Systems should execute predefined rules at scale, 24 hours a day, without fatigue or variation.
That distinction is where operational transformation begins.
A question worth asking
Hotel groups do not lack intelligence, technology, or talent. What they often lack is visibility into where their human effort is truly going.
Perhaps the most important question is not what should we automate next.
It is which work inside our organization should no longer exist at all.
Not because it is unimportant, but because it does not require expertise. When leaders begin to distinguish between decision making and data gathering, between strategic thinking and mechanical repetition, operational tax becomes visible.
And once it is visible, it becomes a choice.
For hotel groups looking to scale without exhausting their teams, that choice may be the most strategic one they make.