How to Set Up Emergency and Crisis Management in Hotels: A Guide to Fire, Earthquake, Evacuation, and Crisis Management

03:17.

The hotel's fire alarm is going off.

There is only one employee at the reception.

Most of the rooms are occupied.

A guest says:

“I smell smoke.”

The real question is no longer:

“Do we have a fire alarm system?”

The real questions are:

• Is the alarm real?
• Who will do the first check?
• Who will direct the guests?
• If evacuation is needed, who decides?
• Which exit will be used?
• How will we verify the rooms are empty?
• Who will call for emergency support?
• When will the manager be notified?
• Who will inform the guests?
• Who will record the incident timeline?
• Where will the guests be taken after evacuation?
• When can the hotel be used again?
• How will operations continue?

This is where:

Emergency Management

begins to differ from an ordinary security procedure.

Because in an emergency:

it matters as much that people know what to do as that the equipment exists.

The crisis management chain of a professional hotel can be roughly thought of like this:

Risk → Preparedness → Detection → Alarm → Immediate Life Safety → Emergency Response → Escalation → Crisis Management → Communication → Evacuation / Shelter / Operational Decision → Crisis Log → Stabilization → Recovery → Incident Report → Root Cause → CAPA → Lessons Learned → Updated Emergency Plan

The aim of emergency management:

is not to think about what to do once the crisis has started.

It is to determine, before the crisis begins, who will do what.

1. What Is Emergency Management?

Emergency management is:

the management system that ensures the protection of people,

the building,

operations

and critical systems during an extraordinary event.

For example, the following can fall within the scope of the emergency system:

• fire,
• earthquake,
• serious medical incident,
• major power outage,
• flooding,
• gas or technical hazard,
• serious security incident,
• evacuation,
• pool accident,
• missing child,
• natural disaster,
• extreme weather event.

However:

not every problem is an emergency, and not every emergency reaches crisis level.

This distinction is important.

2. Incident, Emergency, and Crisis Are Not the Same Thing

The three concepts can be confused with one another.

Incident

An event that occurs outside normal operations.

For example:

a guest falling in the lobby.

Emergency

A situation that requires rapid response and that can create serious risk to people, the building, or operations.

For example:

a fire starting in a room.

Crisis

A situation that normal operating structures struggle to manage on their own, requiring broad coordination and senior-level decisions.

For example:

the entire hotel being evacuated because of a fire.

So there is a structure that can escalate:

Incident → Emergency → Crisis

But not every Incident:

turns into a Crisis.

3. The Size of a Crisis Is Not Determined by the Name of the Event Alone

A “power outage” can be a small technical event.

But:

if the hotel is 100% full,

it is 2:00 a.m.,

the generator isn't working,

the electronic locks are affected,

a guest is in the elevator,

the CCTV system is down,

the event:

can turn into a serious crisis.

That is why it should be assessed using the logic of:

Crisis Severity = Event + Impact + Duration + Human Risk + Operational Capacity

4. The First Principle of Crisis Management: Life Safety

In an emergency, the first priority is not:

• revenue,
• the building,
• furniture,
• equipment,
• reservations.

The first priority should be:

Life Safety.

The basic order can be thought of as:

People → Immediate Hazard → Emergency Response → Property → Business Continuity

This ordering:

prevents wrong priorities during a crisis.

5. The Emergency Plan Isn't Written During the Event

One of the most dangerous approaches is the logic of:

“We'll figure it out if something happens.”

Because when a crisis begins:

• time is short,
• information is incomplete,
• stress is high,
• staff numbers may be limited,
• guests may panic.

That is why:

a significant part of the decisions:

should be designed in advance.

6. First Create an Emergency Risk Register

The emergencies the hotel may face can be identified.

For example:

One of the important variables here should be:

Preparedness.

Because the same risk:

can produce different outcomes in two different hotels.

7. What Is Emergency Preparedness?

The level of preparedness can be measured with these questions:

• Is there an SOP?
• Is staff trained?
• Does the equipment work?
• Is the emergency contact list current?
• Is the chain of authority clear?
• Is there an evacuation plan?
• Is the assembly area clear?
• Has a drill been done?
• Does the night shift know what to do?
• Do critical systems have a backup?

Therefore:

Risk is not just the probability of an event; how prepared the organization is for it also determines the outcome.

8. How Is an Emergency Response Plan Built?

A separate:

Emergency Response Plan

can be prepared for each critical scenario.

The basic structure:

1. Trigger

What starts the procedure?

2. Immediate Action

What is done first?

3. Life Safety

What will be done to protect people?

4. Notification

Who will be notified?

5. Escalation

At what level will management step in?

6. External Support

Which outside agency or professional support may be needed?

7. Guest Communication

Who will inform the guests?

8. Operational Control

How will hotel operations be managed?

9. Documentation

What records will be opened?

10. Recovery

How do we return to normal operations?

This format:

ensures the different emergency SOPs are prepared with the same logic.

9. Crisis Levels Must Be Determined in Advance

A simple four-level structure can be used.

Level 1 — Local Incident

Single area or limited operational impact.

The normal shift can manage it.

Level 2 — Significant Incident

Manager intervention is needed.

There is guest or operational impact.

Level 3 — Major Emergency

Multiple departments,

senior management

and outside support are needed.

Level 4 — Crisis

There is risk to life safety,

wide evacuation,

serious legal or reputational risk,

a long operational interruption

or a major business continuity problem.

As the level rises:

Authority + Communication + Documentation + External Support

should rise too.

10. A Crisis Management Team Should Be Set Up

In major incidents, everyone trying to make decisions at once:

creates chaos.

That is why a:

Crisis Management Team — CMT

can be defined in advance.

For example:

Crisis Manager

Overall coordination and critical decisions.

Operations Lead

Operational implementation.

Safety / Security Lead

Safety of people and the area.

Technical Lead

The building and technical systems.

Guest Communication Lead

Guest communication.

External Communication Lead

Necessary external communication.

Crisis Log Owner / Scribe

Records the incident timeline.

In a small boutique hotel:

one person can take on more than one role.

But:

the roles needn't disappear.

11. What Should Crisis Management Look Like in a Boutique Hotel?

In a hotel with 10–20 rooms:

a separate crisis department isn't expected.

But these roles can still be assigned:

Duty Manager

→ crisis coordination.

Reception

→ guest communication and room information.

Technical

→ technical response.

Housekeeping

→ floor checks and help directing guests.

Designated Employee

→ Crisis Log.

In other words:

in a small hotel the organization is simplified; control doesn't disappear.

12. The Emergency Contact Chain Must Be Ready

During a crisis, this question should not be asked:

“Who had the manager's number?”

The list should be prepared in advance.

For example, depending on operational needs, you can list:

• Duty Manager,
• General Manager,
• Owner Representative,
• Technical Responsible,
• Security Responsible,
• necessary emergency services,
• critical technical services,
• critical suppliers.

The list should be:

current

and:

accessible.

13. Don't Trust a Single Digital List

In an emergency, the following can be affected:

• electricity,
• internet,
• computers,
• PMS,
• the phone system.

That is why:

suitable backup access methods should be planned:

for critical communication and procedure information.

The basic principle:

The Emergency System must be able to work even when normal systems are not working.

14. Fire Emergency Management

Fire:

is one of the most critical scenarios in hotel operations.

Because:

• it can be at night,
• guests may be asleep,
• the building may be unfamiliar,
• smoke can reduce visibility,
• evacuation may need to be fast.

A fire procedure:

cannot be only at the level of:

“Use the fire extinguisher.”

15. The Management Chain in a Fire Incident

Subject to the hotel's specific procedure and authorized safety plan, the operational structure can be designed as:

Detection → Alarm → Immediate Life Safety → Emergency Procedure → Notification → Evacuation if Required → External Emergency Support → Assembly → Accountability → Management Coordination → Guest Communication → Crisis Log → Recovery Decision → Incident Report

16. Why Are the First Minutes Critical in a Fire?

Staff:

should not hesitate about:

• how to activate the alarm,
• who to notify,
• how to start directing the evacuation,
• which areas not to enter,
• where to direct guests,
• how to call outside support.

The aim:

is not to read the procedure during a crisis, but to have learned it beforehand.

17. Staff Must Not Play the Hero

One of the most dangerous behaviors in an emergency:

is untrained staff:

trying to intervene by risking their own safety.

Especially in situations such as:

• fire,
• electricity,
• gas,
• a serious security incident,
• a dangerous technical failure,

staff should act only:

within their training, authority, and the limits of safe intervention.

18. How Is an Evacuation Plan Built?

An Evacuation Plan:

is not just a floor plan hung on the wall.

It must answer:

• what triggers the evacuation?
• who decides?
• which exits will be used?
• how will guests be directed?
• what are staff's duties?
• how will people who need special assistance be supported?
• where is the assembly area?
• how will it be checked who has been evacuated?
• what happens if someone is missing?
• who decides on return to the building?

Evacuation = not just leaving the building, but bringing people under safe control.

19. Why Is an Assembly Point Necessary?

The guests have left the building.

But:

everyone has scattered to different places.

In this case:

it may not be known who is safe.

That is why an:

Assembly Point

must be determined in advance.

The assembly area should be:

• at a suitable distance from the building,
• accessible,
• not creating new risk,
• as controlled as possible.

20. What Is Accountability in an Evacuation?

One of the most critical questions will be:

“Is everyone out?”

That is why the hotel should have an accessible information system on:

• current guests,
• staff,
• visitors,
• suppliers or other persons when relevant.

But:

untrained staff should not be sent back into a dangerous building to check on anyone.

Life Safety is still the priority.

21. Reception's Role During an Evacuation

Front Office:

is especially important.

Because it can access:

• PMS information,
• the room list,
• guest information,
• arrival/departure information.

However:

PMS may become inaccessible.

That is why:

an access method for the:

Emergency Guest List / Occupancy List

suited to the hotel's own structure should be considered.

22. After the Evacuation, the Second Problem Begins

The guests got out safely.

The crisis is not over.

Now these questions arise:

• where will they wait?
• what is the weather like?
• are there children?
• are there elderly guests?
• is anyone in need of medication?
• is access to luggage possible?
• what happens if the hotel can't be used?
• is a transfer needed?
• is alternative accommodation needed?

This is:

the transition from Emergency Response to Guest Recovery.

23. Why Is Earthquake Management Different for a Hotel?

An earthquake:

is different from a fire.

Because the event:

can affect, all at once:

• electricity,
• water,
• elevators,
• communications,
• the building,
• roads,
• outside support.

Also:

a significant share of guests:

may not know how the region behaves in an earthquake or the hotel's plan.

That is why:

earthquake management should be thought of separately as:

the moment of the event + after the event.

24. First Checks After an Earthquake

After the event, the priority can be:

People → Immediate Hazards → Building / Area Safety → Fire / Gas / Electrical Risk → Injuries → Communication → Operational Capability

Staff:

should not make structural safety decisions beyond their authority.

In doubtful cases:

professional assessment

may be needed.

25. After an Earthquake: “Is the Hotel Open?”

The building may be standing.

But this:

doesn't mean a return to normal operations is possible.

Things to check:

• physical safety,
• electricity,
• water,
• the fire system,
• elevators,
• gas,
• electronic locks,
• CCTV,
• internet,
• telephone,
• kitchen,
• pool,
• technical areas.

That is why:

the Recovery Decision is a management decision.

26. Aftershock Risk Management

After an earthquake:

even if the first event seems over:

the risk may continue.

In staff and guest communication:

readiness for new developments,

safe areas,

the communication method

and the operating status should be clear.

Crisis management:

does not automatically end when the first shaking stops.

27. Major Power Outage

A power outage:

may not be a simple fault that the technical department manages alone.

It can affect:

• lighting,
• elevators,
• CCTV,
• electronic locks,
• POS,
• PMS,
• Wi-Fi,
• HVAC,
• water systems,
• the kitchen,
• guest communication.

That is why a:

Technical Incident

can very quickly become an:

Operational Crisis.

28. Power Outage Flow

Example:

Power Failure Detected → Emergency Lighting Check → Generator / Backup System → Elevator Check → Critical Security Systems → Technical Assessment → Management Notification → Guest Communication → Operational Impact Assessment → Recovery → Incident Report if Required

The critical point here:

is running technical response and guest communication at the same time.

29. Guests Can Be More Bothered by Uncertainty

The power went out.

Reception said:

“Technical is dealing with it.”

45 minutes passed.

No new information.

The guest:

may be bothered less by the problem itself than by:

the lack of information.

That is why in crisis communication:

an:

Update Cadence

can be set.

For example:

“There is currently no confirmed time for a fix. We will share new information within 20 minutes.”

This:

creates a sense of control.

30. Flooding Management

Flooding:

can create a chain reaction affecting:

• rooms,
• electricity,
• elevators,
• technical areas,
• storage,
• the building.

The basic operation can be:

Detect → Protect People → Source Control if Safe → Electrical Risk → Area Isolation → Technical Response → Guest / Room Impact → Management → Recovery → Incident Report → Root Cause → CAPA

31. Medical Emergency

A guest:

is experiencing a serious health problem.

The first question:

is not “Who will fill in the Incident Report?”

The first priority:

is starting the appropriate emergency assistance process.

Afterward come:

• area control,
• necessary support,
• management notification,
• guest privacy,
• the record.

The basic principle is the order:

Life Safety → Documentation

32. Privacy in Medical Incidents

A medical incident:

can create, among the hotel's other guests:

curiosity,

photos,

videos,

rumors.

Staff:

should not share information about the incident unnecessarily.

In particular:

the guest's identity,

health condition

and private information:

should be handled in a controlled way.

Crisis management is privacy management as much as it is safety.

33. Pool Emergencies

In hotels with a pool:

a separate scenario is needed.

Risks can be:

• falls,
• injuries,
• an emergency in the water,
• child safety,
• chemical risk,
• a technical equipment problem.

The pool SOP:

should not consist only of daily water checks.

In an emergency, the following should be defined:

• first reaction,
• area control,
• appropriate help,
• management,
• record,
• Root Cause.

34. The Missing Child Scenario

A missing child report:

is one of the incidents that can escalate very quickly.

In the first minutes, steps such as these can be important:

• accurate information,
• last seen location,
• clothing description,
• checking critical exits,
• CCTV support,
• staff coordination,
• management notification.

This incident:

may require, at the appropriate level, starting a:

Crisis Log.

35. Natural Disasters and Extreme Weather

Depending on the hotel's location, risks such as:

• earthquake,
• storm,
• heavy rainfall,
• flood,
• extreme heat,
• extreme cold

should be assessed.

Copying the same procedure:

to every hotel isn't right.

The Emergency Plan must be location-specific.

36. What Is Crisis Communication?

During a crisis:

as much as the right operation:

the right communication matters.

Because wrong information can increase:

• panic,
• complaints,
• reputational risk,
• operational confusion.

Crisis communication should answer these questions:

Who communicates?

To whom?

What information?

Through which channel?

How often?

37. The Single Voice Principle in a Crisis

If a manager says:

“The hotel will be open shortly.”

Reception says:

“It won't be open today.”

Technical says:

“It's not clear yet.”

the crisis grows.

That is why:

a One Source of Truth

should be established.

Verified information:

should be updated from a single center.

38. Separate Information from Estimates

Within the Crisis Log, you can separate:

Known

Verified information.

Unknown

What is not yet known.

Estimate

A guess.

Decision

The decision taken.

For example:

Known: Grid power is out.

Unknown: When will it return?

Estimate: The technical service expects 1–2 hours.

Decision: Guests will be updated every 30 minutes.

This distinction:

prevents estimates from spreading as if they were fact.

39. What Is a Crisis Log?

During a crisis:

events can develop very quickly.

An hour later, it can be hard to remember:

“What time did the first alarm come in?”

“Who made the evacuation decision?”

“When were the guests first informed?”

That is why a:

Crisis Log

is kept.

Crisis Log = the crisis timeline + decision record + communication memory.

40. The Difference Between a Crisis Log and an Incident Report

In short:

The Crisis Log is live.

The Incident Report is retrospective analysis.

41. Core Fields of a Crisis Log

For example:

This record:

is very valuable:

for post-incident analysis.

42. The Crisis Manager and the Scribe Should Be Separate

If the crisis manager:

tries at the same time to:

• make decisions,
• manage guests,
• make phone calls,
• write the incident record,

details can be lost.

That is why, where possible:

Crisis Manager

Makes decisions.

Crisis Log Owner / Scribe

Records decisions and events.

In a small hotel:

this role can be taken on by reception or another suitable employee.

43. Is a Crisis Room Necessary?

In a large hotel:

there can be a physical Crisis Room.

In a boutique hotel:

it may not be needed.

But a:

Crisis Command Point

can be designated.

Here the following are coordinated:

• communication,
• the incident list,
• guest information,
• technical status,
• outside support,
• decisions.

But the area:

must be safe from the incident itself.

44. Handover Is Even More Important in a Crisis

A crisis:

can last longer than one shift.

In this case:

the incoming manager:

should not have to collect information from scratch.

The handover should include:

• Current Situation
• Known
• Unknown
• Decisions
• Open Risks
• Guest Impact
• External Support
• Open Actions
• Next Update

The Crisis Log:

can be the primary source for this transition.

45. What Is Business Continuity?

Emergency management:

protects people.

Business Continuity:

tries to sustain the business's critical functions.

For example:

PMS isn't working.

But you must still know:

• who is staying?
• who is arriving?
• who is leaving?
• which rooms are occupied?
• how will payment be taken?

That is why:

critical processes can have:

Fallback Procedure

plans.

46. Identify the Hotel's Critical Functions

For example:

Life Safety

Tolerance for interruption is very low.

Guest Access

Critical.

Communication

Critical.

PMS / Room Status

High.

Payment

High.

Water

Critical.

Electricity

Critical.

Internet

High, depending on operations.

Breakfast

A short-term alternative can be created.

This exercise shows:

which systems need to be backed up.

47. Recovery Priority List

After a crisis:

it may not be possible to fix everything at once.

The priority:

Priority 1

Life Safety Systems.

Priority 2

Building Safety.

Priority 3

Guest Access and Basic Needs.

Priority 4

Critical Operations.

Priority 5

Full Guest Experience.

Priority 6

Normal Optimization.

This way, instead of:

“Let's fix everything right away,”

risk-based recovery is carried out.

48. Reopening the Hotel Is a Decision

The evacuation was carried out.

The fire was brought under control.

The guests are outside.

The decision:

“Everyone can go back to their rooms.”

should not be made automatically.

Re-entry:

should be done after the necessary safety assessments are completed,

through the authorized decision mechanism.

Because:

the end of the incident may not mean the end of the risk.

49. Guest Recovery After a Crisis

The crisis has closed operationally.

But the guest experience continues.

For example:

• the room can't be used,
• the guest couldn't sleep,
• they couldn't access their luggage,
• they missed a transfer,
• their schedule was disrupted.

In this case:

a Guest Recovery Plan is needed.

Options can be:

• a room change,
• alternative accommodation,
• transfer support,
• an appropriate gesture or service,
• compensation depending on the state of operations,
• follow-up communication.

The decision here:

should be made according to the impact of the incident and the hotel's Service Recovery policy.

50. The Post-Crisis Incident Report

When the crisis ends:

the Crisis Log is closed.

But the analysis is only beginning.

The Incident Report can examine topics such as:

• the description of the incident,
• timeline,
• first response,
• decisions,
• communication,
• guest impact,
• staff impact,
• physical damage,
• operational impact,
• evidence,
• SOP compliance.

Then come:

Root Cause

and:

CAPA.

51. Root Cause: It's Not “An Earthquake Happened”

An earthquake:

can be the source of the event.

But it is not the root cause of system problems.

For example:

the emergency lighting didn't work during the earthquake.

The root cause:

is not that an earthquake happened.

You should ask:

• had maintenance been done?
• was there a test plan?
• was battery life being tracked?
• was the fault already known?
• was a CAPA open?

This:

separates the event we can't control from the system weakness we can.

52. Crisis CAPA

A post-crisis CAPA:

can be of different types.

Physical

Door, lighting, equipment.

Technical

Generator, CCTV, fire system.

Procedural

SOP change.

Training

Staff training.

Communication

Escalation Chain change.

Organizational

Change in authority and duties.

CAPEX

New investment.

This way:

the crisis becomes data that improves the business.

53. What Is an After Action Review?

After a serious incident, an:

After Action Review — AAR

can be held.

Four simple questions:

1. What did we expect to happen?

2. What actually happened?

3. Why was there a difference?

4. What will we change next time?

The aim of this meeting:

is not to find someone to blame but to improve the system.

54. Lessons Learned Must Be Recorded

Otherwise:

a crisis happens.

Everyone learns a lot.

Six months pass.

Staff change.

The knowledge is lost.

That is why a:

Lessons Learned Register

can be kept.

For example:

This:

turns crisis experience into institutional knowledge.

55. Don't Trust a Crisis Plan Without Drills

A document may say:

“Housekeeping checks the floors.”

In the drill:

Housekeeping:

may ask, “Who checks which floor?”

This is why drills are necessary.

A drill tests the system, not the people.

56. Which Drills Can Be Done?

Depending on the hotel's risk profile, scenarios such as:

• fire,
• evacuation,
• earthquake,
• medical incident,
• power outage,
• missing child,
• serious security incident

can be considered.

Not every drill:

has to be full-scale.

57. Tabletop Exercise

For example, management is told:

“It's 02:30. An earthquake has occurred. The power is out. A guest was injured on the stairs. The elevator isn't working. The hotel is 90% full. What do you do in the first 10 minutes?”

The team:

lays out its decisions.

This exercise can reveal:

• gaps in authority,
• communication problems,
• SOP shortcomings,
• resource needs.

58. Drill Evaluation Form

After a drill:

Then:

a CAPA is opened.

A drill:

is done not to take photos for the file, but to find the gaps.

59. Emergency KPIs

For example:

Emergency Count

Total emergencies.

Response Time

Time to first response.

Notification Time

Time to notify management.

Evacuation Time

Evacuation duration.

Accountability Time

Time to check people's status.

Drill Completion Rate

Completion rate of planned drills.

Training Completion

Completion rate of emergency training.

Crisis Log Completion

Rate of Crisis Log use in serious incidents.

CAPA Closure

Closure rate of opened actions.

60. The Most Important KPI Is Not Always “Speed”

An evacuation:

can be very fast.

But:

if a guest was forgotten:

it isn't good.

Similarly:

the response is fast.

But:

the wrong procedure was applied.

That is why:

Speed + Safety + Accuracy + Communication + Accountability

should be assessed together.

61. Emergency Readiness Score

Management:

can build a simple readiness score.

For example:

The aim:

is not perfect math.

But:

to make the readiness gaps visible.

62. Pre-Season Crisis Readiness Review

Especially for seasonal hotels, before opening, you can check:

People

Has staff been trained?

Procedures

Are the Emergency SOPs current?

Systems

Do the fire system, CCTV, generator, and locks work?

Contacts

Are the lists current?

Evacuation

Are the exits and assembly area ready?

Drills

Has a drill been done?

Documentation

Are the forms ready?

63. End-of-Season Lessons Learned Review

At the end of the season, you should ask:

• which Incidents occurred?
• which Near Misses recurred?
• which Emergencies occurred?
• which SOPs didn't work?
• which equipment was inadequate?
• which CAPAs stayed open?
• what investment is needed next season?

This:

ties security data to next year's budget.

64. 20 Big Mistakes in Crisis Management

1. The thought “Nothing will happen to us.”

2. Not preparing an Emergency Plan

3. Copying the plan from the internet

4. Not adapting it to the hotel's real risks

5. Not training staff

6. Forgetting the night shift

7. Not defining the chain of authority

8. Everyone making decisions at once

9. Not keeping the emergency contact list current

10. Depending on a single digital system

11. Thinking the evacuation plan is just a floor plan

12. Not determining an assembly area

13. Not planning Accountability

14. Forgetting guest communication

15. Sharing unverified information

16. Not keeping a Crisis Log

17. Not doing drills

18. Not analyzing once the crisis is over

19. Opening a CAPA but not closing it

20. Not carrying Lessons Learned into the budget and SOPs

The common thread in these mistakes:

crisis management being left to reaction instead of preparation.

65. 15 Decision Gates for Emergency Management

Decision Gate 1

Are the hotel's critical emergencies defined?

Decision Gate 2

Is there an SOP for each critical scenario?

Decision Gate 3

Are Emergency Severity levels defined?

Decision Gate 4

Is the Crisis Manager clear?

Decision Gate 5

Does the night shift know who to call?

Decision Gate 6

Is the Emergency Contact List current?

Decision Gate 7

Is the evacuation plan workable?

Decision Gate 8

Is the Assembly Point clear?

Decision Gate 9

Is there an Accountability method?

Decision Gate 10

Has backup for critical systems been considered?

Decision Gate 11

Is Crisis Communication authority clear?

Decision Gate 12

Has a Crisis Log Owner been designated?

Decision Gate 13

Are drills being done?

Decision Gate 14

Do drills and incidents produce CAPAs?

Decision Gate 15

Is Lessons Learned carried into investment and SOP decisions?

If most of these questions are answered:

“No,”

then:

the hotel may have emergency equipment, but it does not yet have an emergency management system.

66. A Minimum Crisis Management File for a Boutique Hotel

Even for a small hotel, the minimum structure:

1. Emergency Risk Register
2. Emergency Risk Matrix
3. Crisis Severity Matrix
4. Crisis Organization Chart
5. Emergency Contact List
6. Communication Chain
7. Fire Emergency SOP
8. Evacuation SOP
9. Earthquake SOP
10. Medical Emergency SOP
11. Power Failure SOP
12. Water Failure / Flood SOP
13. Gas / Technical Emergency SOP
14. Pool Emergency SOP
15. Security Emergency SOP
16. Lost Child SOP
17. Assembly Point Plan
18. Accountability Procedure
19. Guest Communication Templates
20. Crisis Log
21. Incident Report
22. Root Cause Form
23. CAPA Log
24. Drill Plan
25. Drill Evaluation Form
26. Training Register
27. Lessons Learned Register
28. Emergency KPI Dashboard
29. Recovery Checklist
30. Crisis Readiness Checklist

can be set up.

This file:

should be not a forgotten folder opened in an emergency, but a living system in regular use.

67. The Full Cycle of Hotel Crisis Management

A professional system:

Risk Assessment → Emergency Scenario → Preparedness → SOP → Role & Authority → Training → Equipment → Drill → Detection → Life Safety → Emergency Response → Notification → Escalation → Crisis Management Team → Evacuation / Shelter / Operational Decision → Guest Communication → Crisis Log → Stabilization → Business Continuity → Recovery → Incident Report → Root Cause → CAPA → After Action Review → Lessons Learned → SOP / Training / Equipment / CAPEX Update → New Preparedness Level

If this cycle is closing:

the hotel becomes better prepared after every crisis.

68. How Should the Investor Look at Crisis Management?

The investor's job:

is not to know every emergency procedure by heart.

But they should know the answers to these questions:

People

Does my team know what to do?

Systems

Is the critical equipment working?

Organization

Who makes decisions in a crisis?

Communication

Who informs guests and management?

Evacuation

Can we get people out safely?

Continuity

If one of the critical systems goes down, do we have an alternative?

Learning

Are we really learning from incidents?

Investment

Are we making the necessary investment against known risks?

Because:

crisis management is not only the operations manager's risk management, it is the asset owner's as well.

69. Crisis Management Is Not a Cost Item

A generator,

emergency lighting,

a fire system,

backup communications,

staff training,

drills,

CCTV,

access control

can look like costs at first glance.

But:

the real question:

is not “What does this cost?”

but:

“What could the risk cost if this control isn't there?”

Because a serious crisis:

may not create only physical damage.

It can also create:

• operational loss,
• revenue loss,
• loss of guest trust,
• reputational loss,
• a long closure,
• legal and financial consequences.

70. The Strongest Indicator of Crisis Management

A hotel's crisis management quality:

is not measured by the quality of the emergency plan on the wall.

The real test is this:

At 03:00, with management not at the hotel, when a newly started night employee receives an alarm, do they know their first three moves?

If the answer is:

yes,

then:

the system has started to reach the field.

If the answer is:

“They'd probably call the manager,”

then:

the system still depends on individuals.

Conclusion: When the Crisis Begins, It Is Too Late to Prepare

The biggest mistake in crisis management:

is seeing a crisis as:

a rare, extraordinary event and

postponing preparation.

Because:

a fire,

an earthquake,

a serious medical incident,

a major power outage,

flooding

or a serious security incident:

may not happen every day.

But when it does happen:

it tests the entire hotel management system at once.

Staff,

SOPs,

communication,

technical infrastructure,

leadership,

security,

guest relations

and management:

are all tested at the same time.

That is why strong crisis management:

doesn't begin during the crisis.

It begins much earlier.

You define the risks.

You build the scenarios.

You write the SOPs.

You set the authorities.

You train the staff.

You run drills.

You test the equipment.

You build the communication chain.

Then, when the event occurs:

You protect Life Safety.

You bring in the right people.

You inform the guests.

You keep a Crisis Log.

You stabilize operations.

You manage Recovery.

And after the crisis is over:

You prepare the Incident Report.

You investigate the Root Cause.

You open a CAPA.

You draw out Lessons Learned.

You change the SOPs.

You invest if necessary.

In this way:

the crisis stops being merely an event survived; it becomes institutional learning that makes the business more resilient.

A well-managed hotel:

doesn't manage security by saying “I hope nothing happens.”

It says:

“We did everything we could to prevent it. But if it does happen, we know what to do from the first minute to the return to normal.”

The real:

Emergency & Crisis Management

system is exactly this.

Hotel Investment Guide — Volume V

This article is based on the Security and Emergency Management approach I cover in Hotel Investment Guide — Volume V: Operations.

In Volume V, crisis and emergency management is treated within a holistic operating system together with:

• risk assessment,
• Emergency SOPs,
• fire,
• evacuation,
• earthquake,
• medical incidents,
• technical emergencies,
• pool safety,
• crisis organization,
• Crisis Communication,
• Emergency Contact Chain,
• Crisis Log,
• Incident Report,
• Near Miss,
• Root Cause,
• CAPA,
• drills,
• Lessons Learned,
• KPIs and Management Review.