What Happens When the Hotel General Manager Is Away

Some absences last barely a morning and yet reveal an entire hotel. The general manager leaves for a meeting, visits another property, attends to an obligation outside the hotel, or simply enjoys a day off. The doors continue to open, rooms continue to sell, breakfast does not stop, and guests rarely notice anything unusual. At first glance, everything operates normally. Yet during those hours, decisions begin to be made that say far more about the hotel’s health than several formal meetings.

I am referring to small, almost invisible decisions that will never appear in a report. Someone decides whether an incident requires immediate attention or can wait. Someone else decides whether to help an overstretched department or simply protect their own territory. A middle manager chooses between applying a rule literally or interpreting the guest’s needs. Decisions are also made about what information is shared, which mistakes are acknowledged, which behaviour is corrected, and which matters are best held back until the person with the final say returns.

Absence also changes the human climate. Some people let their guard down, speak more freely, and voice opinions they prefer to manage in the presence of management. Jokes, comments, accumulated complaints, rumours and corridor conversations emerge. At times, this is healthy relaxation. At others, a network of gossip, alliances and subtle challenges to authority surfaces—one that has long been influencing the operation. Hospitality has a peculiar acoustic: a sentence spoken near the back office can reach Reception before the lift does.

I have made the mistake of interpreting these situations in two overly simplistic ways. First, I thought that a team that rarely called me during an absence was necessarily autonomous. I later understood that silence can also mean concealment, resignation or fear of reporting a problem. At another stage, I mistook an abundance of calls for accountability, when some merely showed that we had conditioned people to ask permission to think. Between abandonment and micromanagement lies a far more demanding territory, where the team has authority, understands its boundaries and is accountable for the consequences.

That is why I no longer view the general manager’s absence as an interruption to hotel management, but as an operational culture test. It is not intended to discover who behaves well when the boss is away, nor should it become a trap to catch anyone off guard. It serves to assess whether the hotel retains judgement, discipline, honesty and the ability to coordinate when its most visible hierarchical reference point temporarily disappears. What matters is not that the team does exactly what I would have done, but that it can explain what it decided, what it protected and what it learned.

Absence does not create a different culture; it reveals it without make-up

Every hotel has two systems of governance. The first appears in the organisational chart, procedures, meetings and job descriptions. The second lives in everyday relationships. It determines who is truly heard, who can mobilise resources, which problems are considered legitimate, which departments receive support and which people have informal permission to challenge a decision. While management is present, the two systems may appear aligned. When management is absent, the gap between them becomes far more visible.

I have seen hotels where formal authority rested with one person and practical authority with another. The duty manager held the title, but it was a seasoned receptionist who resolved conflicts, knew the background to every incident and persuaded departments to cooperate. This could be a strength, because the hotel had distributed experience. It could also become a vulnerability if that influence had no boundaries, undermined managers or turned personal preferences into collective rules.

360° Hotel Intelligence

Stop managing isolated systems. Start managing the whole hotel.

HotelGEX connects guests, operations, Revenue, F&B, Groups & Events and Management into one intelligent hotel context — so every decision starts with a clearer picture.

See what your hotel could become

Discover HotelGEX →

✓ 30 days free · no commitment

One hotel. One context.

Customer 360 Revenue Intelligence Operations F&B Groups & Events

Start free trial →

The relevant question is not merely who is in charge when the general manager is absent. It is worth asking what kind of authority emerges. It may be authority based on knowledge, credibility and service to the whole. Or the most persistent person may prevail: the one who speaks loudest, monopolises information or uses their seniority as a kind of emotional shareholding in the hotel. The first strengthens the operation. The second creates dependency, defensive silence and decisions that are difficult to revisit.

During a brief absence, at least five types of decisions are made. Some affect the guest, others distribute work, others interpret standards, others manage information, and some protect internal reputations. This final category deserves particular attention. When an error occurs, the team decides whether its priority is to resolve it or to prove who was at fault. This seemingly human choice ultimately affects the hotel guest experience, because every minute spent defending territory delays the response the guest needs.

I recall an incident that occurred on a day when I was away from the hotel. A room could not be released on time because of a combination of a minor technical fault, a late check-out and incomplete communication between Housekeeping and Reception. No individual element was serious on its own. The problem grew because each department tried to prove that it had fulfilled its part. While messages were exchanged to reconstruct responsibilities, the guest continued waiting. The team had information, people and alternatives; what it lacked was a shared priority strong enough to stop the debate and resolve the stay first.

That episode taught me that autonomy does not mean allowing every department to decide only on its own matters. In a hotel, almost no relevant decision belongs entirely to one department. Compensation affects margins and perceptions of fairness. A late check-out can improve the stay while complicating room turnaround. Accepting a booking, offering an upgrade or extending a service can commit capacity that another team needs. True autonomy requires understanding these interdependencies and preventing local freedom from undermining the overall result.

This perspective connects with the need to turn Reception into a high-value decision-making centre. The front desk often absorbs the first pressure when a management reference point is absent, but it should not carry the hotel’s entire uncertainty alone. It needs up-to-date information, financial limits, available decision-makers and criteria for coordinating responses. Giving it authority without context is like handing over a master key without explaining which doors must not be opened.

I have also learned to observe which standards survive without supervision. Some teams maintain their level of detail because they see it as part of their professionalism. Others comply while they feel management is watching and relax their standards as soon as that gaze disappears. The difference is rarely corrected through more controls. It usually indicates that the standard is still experienced as an external demand rather than a commitment to the guest, the colleague and the property’s value proposition.

When the team lets its guard down, signs emerge that should be interpreted carefully. Not all are negative, and none should be judged out of context:

• The pace of work changes. A slight relaxation may be reasonable and even healthy. The problem arises when performance depended on the general manager’s visible pressure. If a task stops being done properly as soon as supervision disappears, the hotel does not have an internalised standard but conditioned behaviour.
• Exceptions multiply. Favours are granted, priorities are changed or procedures are ignored because it is assumed that no one will ask for an explanation. Some exceptions improve the guest experience. Others shift work to the next shift, consume inventory or create precedents that someone else will later have to manage.
• Information changes speed. Good news circulates quickly, while errors wait for management to return. This selective delay is dangerous. A problem reported early usually allows for alternatives; a problem concealed for hours arrives with fewer options and greater cost.
• Alternative authorities emerge. People without formal responsibility begin assigning tasks, reinterpreting decisions or blocking initiatives. Their influence can be valuable if it coordinates and protects the hotel. It should concern us when it uses privileged information, fear or personal affinities to build power.
• Departments negotiate with one another. This negotiation demonstrates maturity when it seeks the best outcome for the guest and the business. It becomes fragmentation when each area trades favours, withholds resources or accepts a concession today in the expectation of collecting on it tomorrow.
• The conversation becomes more candid. At times, absence creates space for the team to raise issues it had not found a way to present. This frankness may contain valuable information. If it only emerges beyond management’s reach, it is worth reviewing why the formal channel does not feel sufficiently safe or useful.

Gossip deserves specific reflection because it is often treated as a minor nuisance. In my experience, rumour is a rudimentary way of managing uncertainty. It emerges when people feel that a decision affects them but do not know its context, do not trust the official explanation, or believe that the real information circulates through other channels. The team fills the gaps with interpretations, and every interpretation incorporates interests, fears and personal histories.

That does not turn all gossip into legitimate criticism, nor does it require us to respond to every comment. Some rumours are used to wear down a person, protect privileges or block necessary change. There are also conversations that management labels as gossip in order to avoid hearing an uncomfortable reality. Distinguishing between the two requires maturity. I try to ask myself whether the comment contains a verifiable fact, an operational concern or merely an insinuation that cannot be tested.

A healthy team can criticise a decision without turning it into a campaign against the person who made it. It can disagree, ask for context and propose an alternative. A deteriorated team personalises every boundary, assigns motives and turns every mistake into material for internal circulation. The difference affects leadership in the hotel sector because it requires deciding how much space should be given to disagreement and where professional disloyalty begins.

Absence also reveals which behaviours have been tolerated for convenience. If someone belittles a colleague, ignores procedures or spreads sensitive information when management is away, the problem did not begin that day. There were probably earlier signs that no one wished to confront. The hotel simply used the silence of the office to reveal a cultural debt that had been accumulating for some time.

It is also worth remembering that indicators can conceal these dynamics. A shift may end with every task closed while leaving exhaustion, conflict and deferred problems behind it. Apparently excellent productivity may have been achieved by transferring the burden to another department. I have already examined how KPIs can produce the wrong behaviour; during a management absence, that risk increases because people tend to protect what they know they will be evaluated on.

That is why I distrust two overly comfortable interpretations. The first claims that, if the hotel does not call, everything is under control. The second assumes that any decision different from mine demonstrates poor judgement. A mature team may find a better solution than the one I would have chosen. What I need to know is whether it protected safety, the guest’s dignity, commercial consistency, future workload and hotel profitability. The method may vary; the principles it protects should not.

Designing an absence that teaches without becoming a trap

A useful absence begins before walking out the door. If the team does not know who is taking on coordination, what financial limits apply and which situations require escalation, we are not assessing autonomy. We are leaving a vacuum and hoping someone will fill it. Prior clarity prevents the most dominant person from appropriating the space and ensures responsibility falls to someone with legitimacy, information and the ability to act.

I do not recommend announcing every absence as a test. That would produce a temporary performance and increase anxiety. Nor do I advise deliberately disappearing in the hope of uncovering hidden behaviour. Management should not organise small corporate espionage operations. In addition to eroding trust, this practice produces unreliable information: people who feel watched learn to conceal better, not necessarily to work better.

I prefer to build what I call an Absence Decision Map. It is a brief document and, above all, a recurring conversation. It does not seek to anticipate every possible incident—an optimistic proposition in Hospitality, where a coffee machine can trigger a diplomatic crisis before eight in the morning. Its purpose is to offer reference points for thinking when the specific situation does not appear in any manual.

The map should answer six questions:

• What the team can decide without authorisation. Here I include compensation within a limit, task reorganisation, reversible operational changes and responses needed to protect the guest. Authority must be sufficient to resolve matters, not a symbolic authorisation that requires every step to be confirmed.
• Which decisions require consultation. These are those with significant financial impact, effects across several departments, contractual risk, reputational exposure or the potential to create a precedent. Consulting does not mean passing the problem upwards; the person consulting must provide context, options and a recommendation.
• Which decisions cannot wait. Safety, health, child protection, privacy, serious conflicts, critical failures and incidents with the potential to spread require action and communication. Fear of disturbing management must never delay a necessary response.
• Which principles are non-negotiable. Guest dignity, team safety, the truthfulness of information and the fulfilment of commitments must guide the decision even when the specific solution is uncomfortable or carries an immediate cost.
• What must be documented. Decisions with subsequent consequences require a clear note on facts, alternatives, people informed and pending actions. Documentation is not intended to manufacture a personal defence, but to allow the next shift to continue without having to reconstruct the entire story.
• Who coordinates interdependencies. The hotel needs someone capable of seeing the whole picture, even if they are not a specialist in every department. Their responsibility is to prevent a good local solution from creating three problems elsewhere in the operation.

This framework should be practised through real situations. In follow-up meetings, I use cases that have already occurred and ask what we would have done if the person with the greatest authority had not been available. A serious complaint, a payment discrepancy, an out-of-order room, aggressive behaviour or a capacity issue are useful exercises. It is also worth practising commercial decisions, because hotel revenue management and operations intersect more often than our organisational charts admit.

In these exercises, I do not seek a perfect answer. I observe the reasoning. I want to know what information the team asks for, which risks it identifies, who is affected and how it distinguishes what is urgent from what is merely noisy. I also pay attention to what no one mentions. If everyone talks about compensation and no one mentions the guest’s emotional recovery, one dimension is missing. If everyone wants to satisfy the customer and no one calculates the capacity being committed, another is missing.

There are decisions the team must learn to refuse. Autonomy does not mean saying yes more quickly. At times, it requires maintaining a boundary in the face of an unreasonable request, protecting an employee or avoiding an impossible promise. The judgement developed around guests a hotel should not accept at any price must also be available when management is not present. Otherwise, boundaries exist only while someone with sufficient seniority is there to defend them.

After every significant absence, I hold a brief review. I avoid beginning by asking whether there were any problems, because the most likely response is a reassuring “everything was fine”. I prefer more specific questions: which decision created the greatest doubt, what information was missing, which matter was delayed, where there was disagreement and what should be clearer before the next occasion. That is how the learning buried by a generic question emerges.

The review should also include the calls received. If the team consulted too often, I do not reprimand it for calling; I investigate why it did not feel authorised to decide. Experience may be lacking, but so may financial limits, precedents or support. If it did not call about an important matter, I ask what led it to think the matter could wait. In both cases, the conversation should improve the system rather than merely assess behaviour.

I find it useful to classify decisions made during an absence into four groups. Confident and autonomous decisions confirm that judgement is maturing. Correct but unnecessarily escalated decisions signal dependency. Reasonable decisions made with insufficient information reveal access or communication failures. Concealed or glossed-over decisions require a deeper conversation about trust and accountability.

The most delicate category is the last one. An error reported honestly can usually be coached. A consciously hidden decision raises a different problem because it breaks the possibility of learning and correcting in time. Transparency must protect those who report in good faith, but it cannot become automatic amnesty for repeated negligence. Trust and professional accountability must coexist; separating them leaves the hotel trapped between fear and permissiveness.

It is also worth observing informal conversations without attempting to control every word. I do not need the team to speak positively about every decision I make. That would be unrealistic and, frankly, rather boring. I do expect disagreements not to destroy authority, disclose confidential information or deliberately undermine other people. The freedom to express fatigue or disagreement does not include the right to poison every shift with cynicism.

When rumour persists, my first response is to reduce the uncertainty feeding it. I explain what can be explained, acknowledge what has not yet been decided and avoid filling the gap with false certainty. If malicious behaviour exists, I address it directly with facts and consequences. A general meeting about “the importance of positive communication” rarely corrects someone who already knows perfectly well what they are doing; it usually makes those with no involvement uncomfortable.

Middle managers play a decisive role because they are the ones who turn absence into continuity or confusion. They need visible authority, but also the ability to receive disagreement without feeling challenged. A manager who interprets every question as insubordination drives conversations into the corridor. Another who avoids all tension allows informal influences to govern the shift. Preparing managers means teaching them to decide, explain, listen, correct and close.

Management selection itself influences this design. A person may accumulate many years of experience while having always built operations dependent on their presence. That is why, when assessing experience for a General Manager role, I consider it essential to ask which decisions their teams learned to make, what happened during their absences and how many capabilities remained after they left. The most valuable authority leaves judgement behind it.

To apply this approach without bureaucratising the hotel, I recommend a simple sequence. First, record over several weeks which decisions reach the office and which could be resolved at another level. Then define boundaries according to impact, reversibility and risk. Next, practise real cases with shift managers. Finally, review absences as a source of learning. The objective is not to eliminate all consultations, but to ensure that every consultation is of higher quality and every autonomous decision more considered.

I must also accept an uncomfortable part of the process. If I want a team that decides, I will have to live with solutions that do not reproduce my style exactly. Correcting every difference teaches that autonomy is decorative. I intervene when principles are breached, risks are ignored or important commitments are harmed. When the outcome is reasonable and the learning is sound, I try not to turn my personal preference into a universal rule.

The general manager’s absence should leave a residue of authority: understood priorities, clear boundaries, people able to coordinate and sufficient trust to tell the truth. If discipline, cooperation and judgement disappear when the door closes, management’s presence was sustaining an appearance. A strong hotel does not need to pretend that the general manager is dispensable; it needs to demonstrate that their work has built capability in others.

My advice is to begin by observing an ordinary absence, without announcing any experiment. Review which decisions were unnecessarily escalated, which were left pending and what conversations emerged afterwards. Do not look for culprits on the first reading. Look for patterns. An isolated call may be prudent; twenty calls about similar matters reveal a poorly designed authority boundary.

Then speak with the team from a position of demanding curiosity. Ask what it needed in order to decide better, but also ask what responsibility it avoided taking. Listen to rumours as signals without automatically granting them the status of truth. Reinforce those who coordinate without seeking the spotlight, communicate errors in time and protect the whole even when no one appears to be watching.

Finally, measure your management work by something more ambitious than the visible order maintained while you are present. Observe the quality of the decisions that remain when you leave. That is where it becomes clear whether you have built obedience, dependency or judgement. And in Hospitality, where the hotel never stops operating simply because someone important is away, shared judgement ultimately becomes one of the most discreet and profitable forms of leadership.