Hotel Operations: Auditing Staff Workarounds to Fix Inefficiencies
Hotel executives can uncover core system flaws and avoid software purchases by auditing unofficial spreadsheets, group chats, and hidden routines.
The short answer
Hotel teams routinely create informal spreadsheets and chat groups when official software fails them. Auditing these workarounds allows operators to resolve operational bottlenecks without buying additional technology.
The short version
- Hotel staff build shadow IT workarounds when official systems fail real-life workflows or deliver incomplete data.
- Mikhail Volodin recommends interviewing new employees two to four weeks after onboarding to catch clumsy procedures.
- Manuel Kuckenberger advises questioning workaround creators directly to expose broken departmental handoffs.
Hotel executives can fix property operations by auditing staff workarounds to discover where official systems fail front-line teams. Tracking informal spreadsheets, messaging chats, and manual reports exposes broken departmental handoffs, improper software settings, and training gaps, allowing operators to correct underlying problems without spending money on additional technology platforms.
What Are Operational Workarounds in Hotels?
Operational workarounds represent an unofficial second operating model that runs parallel to documented standard operating procedures and hotel software systems [1]. While management defines workflows and responsibilities through official documentation, staff members frequently bypass these structures to complete daily tasks [1]. Examples include tracking guest requests on paper sticky notes, maintaining custom spreadsheets when operational software is difficult to use, rebuilding monthly reports by hand, and starting unofficial instant message groups so departments communicate quickly [1].
These improvised solutions emerge because official tools create friction during daily shifts [1]. Over time, seasoned staff teach these extra steps to incoming team members as standard practice, turning temporary fixes into regular routines [1]. As Lodging Magazine reported, although single workarounds appear harmless, the accumulated lost minutes undermine profitability and degrade guest service quality across the property [1].

Why Should Hoteliers Conduct a Shadow IT Audit?
Hoteliers should run a Shadow IT audit to pinpoint every unapproved tool and spreadsheet operating inside the building, revealing why employees abandoned official software in the first place [1]. Mikhail Volodin, a hotel tech and OTA specialist within HotelMinder’s Lobby community, advises that the objective of this audit is not to punish workers or instantly wipe out their tools [1]. Instead, the exercise uncovers the root cause driving staff behavior [1].
As outlined by Lodging Magazine, informal tools indicate that operational software mismatches the physical workflow, system settings remain misconfigured, or onboarding failed to teach staff the correct methods [1]. By treating these employee-created shortcuts as an operational roadmap, management pinpoints structural breakdowns without purchasing extra software products [1].
What Questions Uncover the Source of Broken Handoffs?
Management can identify the source of broken handoffs by interviewing the staff members who built the improvised systems [1]. Manuel Kuckenberger, an operations consultant known as the hotel tech fixer in HotelMinder's Lobby community, advises asking department heads to identify one recurring shortcut and the broken departmental handoff tied to it [1].

Operators should then interview the staff members responsible for creating the detour using targeted operational questions [1]:
- What problem were they trying to solve [1]?
- What happens when they follow the official process instead [1]?
- Where does information get lost or delayed [1]?
- What would make the extra step unnecessary [1]?
Staff feedback often exposes systemic gaps across property boundaries [1]. An unofficial front-desk spreadsheet frequently indicates that another department fails to transmit critical guest details reliably [1]. A manual report proves that built-in property management reports omit necessary data [1]. Similarly, cross-department messaging groups confirm that automated operational alerts do not reach staff fast enough [1].
When Do Inefficient Workarounds Become Invisible to Teams?
Workarounds become invisible when tenured staff pass informal steps down through multiple generations of new hires until no worker remembers the original purpose of the workaround [1]. When an employee trains a colleague who subsequently onboard recruits, the operational band-aid hardens into accepted company tradition [1].

To combat this institutional blindness, Volodin recommends interviewing new employees two to four weeks following onboarding [1]. During this window, fresh personnel still spot friction that tenured staff overlook [1]. Managers should ask new hires which daily tasks feel clumsy, which steps repeat needlessly, and which procedures seem completely unnecessary to capture unvarnished feedback [1].
How Do Hoteliers Evaluate Workarounds Before Buying New Software?
Hoteliers evaluate workarounds using six operational lenses to determine whether existing property tools can solve the problem before spending capital on outside vendors [1]. Rather than purchasing new systems immediately, leadership evaluates each workaround against technical and procedural checks [1].
| Evaluation Lens | Core Operational Question | Root Cause Identified |
|---|---|---|
| Capability | Can technology you already own perform the task [1]? | Unused platform features [1] |
| Configuration | Has that functionality been configured correctly [1]? | Improper software setup [1] |
| Connectivity | Does information effectively move between systems and departments [1]? | Integration or sync gaps [1] |
| Competency | Do employees know how to use the intended workflow [1]? | Inadequate employee training [1] |
| Complexity | Is the process itself unnecessarily complicated [1]? | Convoluted SOP steps [1] |
| Coverage | Is there genuinely a capability your current stack cannot provide [1]? | Missing technical features [1] |
As Volodin notes through Lodging Magazine, properties should only invest in new technology when a structured review confirms an authentic coverage void that current platforms cannot resolve [1]. Highly profitable hotels succeed not because their initial procedures run flawlessly, but because leadership captures frontline breakdowns before quick fixes turn into permanent operating procedures [1].
Reported by
This article was written from the following reporting. Follow the links for the original coverage.
- [1]How to Fix Hotel Operations by Auditing Staff Workarounds— Lodging Magazine
Frequently asked
+What is a shadow IT audit in a hotel?
A shadow IT audit is an operational review that catalogs unofficial spreadsheets, paper notes, and messaging channels used by hotel staff. The review identifies why employees created alternate tools instead of following official workflows.
+Why do hotel employees create operational workarounds?
Employees build workarounds when official technology is difficult to access, standard reports omit critical data, software configurations are incorrect, or cross-department handoffs fail to deliver guest information on time.
+When should managers question new hires about hotel procedures?
Managers should interview new hires two to four weeks after onboarding. During this window, employees still notice clumsy procedures, repeated steps, and unnecessary tasks before these inefficiencies become normalized habits.
+What are the six lenses used to evaluate hotel workarounds?
The six operational lenses are capability, configuration, connectivity, competency, complexity, and coverage. They determine whether a breakdown stems from training, system setup, or a true technological gap.
+Should hotels immediately eliminate employee workarounds?
No, hotels should not immediately eliminate workarounds. Management should first understand the problem the staff member was trying to solve, as workarounds highlight underlying operational and technical deficiencies.
Keep reading
Our reporting
More in operations

