vaayaa Inclusive Education
Hospitality risk assessment

Hotel Revenue and Yield Management Risk Assessment: Pricing, Booking and Payment Controls

A worked example of how a hotel revenue team finds, scores and controls risks to room income, pricing accuracy, guest data, staffing and safety, so that yield decisions do not create harm to guests or staff.

Updated November 2026 8 hazards assessed Review every 6 months Highest risk: Critical to Medium
See the Hotel Revenue and Yield Management course

Executive summary

This assessment shows how a mid-sized hotel revenue team can find, rate and control the risks that threaten room income, pricing accuracy, guest data, staff wellbeing and physical safety. Eight risks were chosen because they are plausible in everyday yield management, distribution and rooms operations. Guest data exposure is the highest inherent risk because its impact is serious and it is likely through phishing and spreadsheets. Rate and forecast errors, channel failures, overbooking, fatigue and facility faults also score High before controls. Most risks fall to Medium or Low once the existing and added controls are in place, and facility risk stays lower because closures are tracked. The first actions are rate floors and ceilings, multi-factor sign in, a written walk policy, and a link between room closures and the revenue system. The hotel is a teaching example, so every score illustrates method, not a real business.

Focus area
Hotel revenue and yield management
Setting
Rooms division of a mid-sized independent hotel with a revenue team, front office, sales office and facilities team
Method
Five by five likelihood and impact risk register

Scope

This assessment covers pricing, forecasting, distribution and reservations for a single mid-sized hotel, from rate setting and channel management to payments, guest data, staffing at peak demand and the safety of the rooms and facilities that are sold. Assumption: jurisdiction, property size, brand standards and the systems used are not specified, so they are treated as teaching assumptions. It does not cover investment decisions, legal advice or any real hotel.

Context

The hotel has a revenue manager, a director of rooms, a front office team, a sales office, a systems administrator and a facilities team. Rates are set in a revenue management system fed by historical bookings, competitor checks and forecasts for local events. Rooms are sold through the hotel website, online travel agencies, corporate contracts and the reservations desk, and card payments are taken at check in and check out. Each risk is scored before controls to show its natural level, then again after the existing controls and the additional controls proposed here.

Objectives, assets and stakeholders

The objective is to sell rooms at sound rates, keep bookings and payments accurate, protect guest and staff wellbeing, meet privacy and accessibility duties, and keep the trust of owners, guests and partners. The assets in scope are room inventory, rate and forecast data, the reservation and payment systems, guest profiles, staff rotas, plant and fire systems, and the hotel reputation. Stakeholders include guests, the revenue, front office, housekeeping and engineering teams, the general manager, owners, distribution partners, card processors and the relevant local authorities. Each risk has one owner role, and the revenue manager keeps the register current and reports to the general manager each month.

Risk matrix: before and after controls

Each cell shows hazard numbers placed by likelihood and impact. Compare the two grids to see how controls move each hazard.

Before controls

Inherent risk

Risk before controls: rows are likelihood from almost certain to rare, columns are impact from insignificant to catastrophic. Cells list hazard numbers.
1
Insignificant		 2
Minor		 3
Moderate		 4
Major		 5
Catastrophic
5 Almost certain
4 Likely Likelihood 4, impact 3, score 12, high: H02 Likelihood 4, impact 4, score 16, high: H01 Likelihood 4, impact 5, score 20, critical: H05
3 Possible Likelihood 3, impact 3, score 9, medium: H07 Likelihood 3, impact 4, score 12, high: H03 H04
2 Unlikely Likelihood 2, impact 4, score 8, medium: H06 Likelihood 2, impact 5, score 10, high: H08
1 Rare

After controls

Residual risk

Risk after controls: rows are likelihood from almost certain to rare, columns are impact from insignificant to catastrophic. Cells list hazard numbers.
1
Insignificant		 2
Minor		 3
Moderate		 4
Major		 5
Catastrophic
5 Almost certain
4 Likely
3 Possible Likelihood 3, impact 2, score 6, medium: H04
2 Unlikely Likelihood 2, impact 2, score 4, low: H06 H07 Likelihood 2, impact 3, score 6, medium: H01 H02 H03 Likelihood 2, impact 4, score 8, medium: H05
1 Rare Likelihood 1, impact 5, score 5, medium: H08
  • Low 1 to 4
  • Medium 5 to 9
  • High 10 to 16
  • Critical 17 to 25

Hazard register

A summary first, then the detail for each hazard.

Summary of hazards with scores before and after controls
No.HazardBeforeAfterOwner
H01 Rate and forecast errors from poor demand data 16 High 6 Medium Revenue manager
H02 Booking channel and payment system failure 12 High 6 Medium Systems administrator
H03 Overbooking and guest relocation failures 12 High 6 Medium Front office manager
H04 Staff fatigue and understaffing at peak demand 12 High 6 Medium Human resources manager
H05 Breach of guest payment and personal data 20 Critical 8 Medium Data protection lead
H06 Accessibility and unequal treatment in offers 8 Medium 4 Low Accessibility lead
H07 Supplier disruption to revenue software and distribution 9 Medium 4 Low Procurement manager
H08 Fire, facility and equipment failure closing rooms 10 High 5 Medium Chief engineer
H01

Rate and forecast errors from poor demand data

Financial Before 16 After 6

Rates are set from stale forecasts, incomplete competitor data or wrong group pickup figures, so rooms are sold too cheaply or too dearly and revenue is lost.

Who or what is affected: Revenue team, owners and sales staff

Causes

Reliance on one forecasting model, manual entry of group data and pressure to meet budget.

Consequences

Lost revenue, discounting that damages rate integrity and poor investment decisions.

Existing controls

  • Rates are approved by the director of rooms before going live.
  • Forecasts are compared with actual occupancy each month.

Control gaps

Competitor data is checked by hand, and forecast accuracy is not recorded over time.

Additional controls

  • Prevent: Set rate floors and ceilings in the system and require approval for any change outside them.
  • Detect: Review pickup and pace reports weekly and flag forecasts that miss by more than an agreed margin.
Likelihood 4 x impact 4 before; 2 x 3 after Owner: Revenue manager Target: Within 45 days Early warning: Forecast variance above the agreed margin for two consecutive weeks.
H02

Booking channel and payment system failure

Technology and data Before 12 After 6

The reservation system, channel link or card payment terminal fails or is misconfigured, so bookings are duplicated, rates differ between channels or payments are not captured.

Who or what is affected: Guests, front office staff and distribution partners

Causes

Interface errors after software updates, shared login details and no separate test environment.

Consequences

Overselling, guest complaints, missed payments and card chargebacks.

Existing controls

  • Channel rates are checked each morning by the reservations team.
  • Payment terminals are serviced under a supplier contract.

Control gaps

The manual procedure has not been rehearsed, and parity checks run only on weekdays.

Additional controls

  • Prevent: Use a single rate source with rate parity checks and lock inventory limits on each channel.
  • Recover: Keep a manual booking and payment procedure in print and rehearse it twice a year.
Likelihood 4 x impact 3 before; 2 x 3 after Owner: Systems administrator Target: Within 30 days Early warning: Rate differences between channels found in more than one check per week.
H03

Overbooking and guest relocation failures

Reputational Before 12 After 6

Rooms are oversold without a clear walk policy, so arriving guests are moved to another property or left waiting, which causes complaints, refunds and lost goodwill.

Who or what is affected: Arriving guests, front desk staff and partner hotels

Causes

Forecast optimism, no-shows that are not predicted and late cancellations.

Consequences

Guest compensation, negative reviews and lost repeat business.

Existing controls

  • An overbooking limit is set by the revenue manager each season.
  • The front desk checks arrivals against the expected list each evening.

Control gaps

The walk policy is not shared with night staff, and partner rates are not agreed in advance.

Additional controls

  • Prevent: Set the overbooking limit from no-show history and review it every month.
  • Respond: Keep a written walk policy with a named partner property and a budget for guest compensation.
Likelihood 3 x impact 4 before; 2 x 3 after Owner: Front office manager Target: Within 30 days Early warning: Arrivals waiting more than 30 minutes for a room, or walked to another hotel in a month.
H04

Staff fatigue and understaffing at peak demand

People Before 12 After 6

Rooms and revenue teams are stretched during peak periods, with long shifts and few trained cover staff, so errors rise, breaks are missed and service slips.

Who or what is affected: Housekeeping, front office and revenue staff

Causes

Seasonal peaks, staff turnover and vacancies that take a long time to fill.

Consequences

Mistakes in rates and bookings, injury from fatigue and poor guest service.

Existing controls

  • The rota is planned four weeks ahead by department heads.
  • Overtime is recorded and reviewed monthly.

Control gaps

Fatigue is not assessed, and cover staff rarely have live system access.

Additional controls

  • Prevent: Set maximum consecutive shift and minimum rest rules, and cross train two cover staff per department.
  • Detect: Track overtime and sick absence each week against an agreed threshold.
Likelihood 3 x impact 4 before; 3 x 2 after Owner: Human resources manager Target: Within 60 days Early warning: Overtime above the agreed weekly hours for three or more staff in one week.
H05

Breach of guest payment and personal data

Legal and compliance Before 20 After 8

Guest profiles, identity details and card data held in the system or emailed to partners are accessed or leaked, exposing guests to fraud and the hotel to penalties and claims.

Who or what is affected: Guests, staff and corporate clients

Causes

Phishing, shared accounts and personal data copied into spreadsheets for reporting.

Consequences

Fines, compensation claims, loss of guest trust and penalties from card scheme rules.

Existing controls

  • Full card numbers are held only by the payment processor, not on hotel systems.
  • Access to guest profiles is limited by job role.

Control gaps

Access logs are kept but never reviewed, and staff privacy training is given only once a year.

Additional controls

  • Prevent: Enable multi-factor sign in and remove stored card numbers from emails and spreadsheets.
  • Detect: Review access logs for bulk lookups and unusual devices each week.
  • Respond: Keep a written breach response plan with a named data protection lead and notification route.
Likelihood 4 x impact 5 before; 2 x 4 after Owner: Data protection lead Target: Within 30 days Early warning: Repeated bulk exports of guest records or access from an unknown device.
H06

Accessibility and unequal treatment in offers

Legal and compliance Before 8 After 4

Booking pages or rate packages are presented in a way that excludes guests with disabilities, or quotes are given less favorably to some groups, which can breach equality duties and harm reputation.

Who or what is affected: Guests with disabilities, families and group bookers

Causes

Booking pages built without accessibility testing and rates quoted by phone without a script.

Consequences

Complaints, legal challenge and reputational harm in local and online reviews.

Existing controls

  • Accessible room types are shown on the booking website.
  • Staff are told not to quote different rates by protected characteristic.

Control gaps

Accessible room data is incomplete, and no one checks it against the physical rooms.

Additional controls

  • Prevent: Test booking pages with assistive technology and publish full accessible room details.
  • Detect: Audit a sample of quotes each quarter for consistency and missing accessibility information.
Likelihood 2 x impact 4 before; 2 x 2 after Owner: Accessibility lead Target: Within 60 days Early warning: Complaints about booking pages or accessible room information in a quarter.
H07

Supplier disruption to revenue software and distribution

Supplier Before 9 After 4

The revenue management software, channel manager or online agency fails or changes terms, so rates cannot be updated and bookings stop flowing from key sales channels.

Who or what is affected: Revenue team, sales office and guests

Causes

Dependence on one supplier, price rises and weak data export terms in contracts.

Consequences

Lost bookings, rate errors and the cost of an emergency switch.

Existing controls

  • The supplier contract includes service levels for system uptime.
  • A second channel manager is listed but not yet connected.

Control gaps

Export of rate history has never been tested, and the backup supplier is not configured.

Additional controls

  • Prevent: Review supplier financial health and exit terms each year and confirm the hotel keeps full data export rights.
  • Respond: Document a manual rate update process and test the switch to the second supplier.
Likelihood 3 x impact 3 before; 2 x 2 after Owner: Procurement manager Target: Within 90 days Early warning: Supplier status update showing service failure or a notice of contract change.
H08

Fire, facility and equipment failure closing rooms

Safety Before 10 After 5

A fire alarm fault, water leak, lift failure or faulty boiler closes rooms or floors at short notice, so rooms cannot be sold, and guests, staff or contractors may be harmed.

Who or what is affected: Guests, staff and contractors

Causes

Ageing plant, delayed repairs and water damage from leaks that go unseen.

Consequences

Injury, closure of floors, lost revenue and action by fire or building authorities.

Existing controls

  • Fire alarms are tested weekly and serviced under contract.
  • A room closure procedure is held by the duty manager.

Control gaps

Room closures are not linked to the revenue system, so closed rooms may still be sold.

Additional controls

  • Prevent: Schedule planned maintenance for lifts, boilers and sprinklers and record every defect against the affected rooms.
  • Detect: Check leak and temperature sensors in plant rooms each day.
  • Respond: Keep a live list of out of order rooms and a relocation plan that updates the revenue system at once.
Likelihood 2 x impact 5 before; 1 x 5 after Owner: Chief engineer Target: Within 30 days Early warning: Repeated defects on the same plant item, or an alarm fault left open for more than one day.

Rating method and evaluation

Each risk is rated on two five-point scales. Likelihood runs from Rare to Almost certain, and impact runs from Insignificant to Severe. Multiplying the two gives a score from 1 to 25, which falls into one of four bands: Low from 1 to 4, Medium from 5 to 9, High from 10 to 16 and Critical from 17 to 25. Low risks are accepted and watched, Medium risks need routine controls with a named owner, High risks need senior attention and a dated plan, and Critical risks need immediate action and direct reporting to the general manager. Inherent risk is the score before any controls. Residual risk is the score after existing and added controls, and it must never be higher than the inherent score. Impact is judged on money lost, guest harm, legal exposure, time to recover and damage to trust, and a risk is not rated down simply because it has not yet happened. Ratings are challenged by the staff who do the work, by a second reviewer who was not involved in scoring, and whenever a warning indicator reaches its threshold.

Likelihood, impact and rating bands

Likelihood

  • 5 Almost certain: Expected to happen in most circumstances.
  • 4 Likely: Will probably happen in many circumstances.
  • 3 Possible: Could happen at some time.
  • 2 Unlikely: Not expected, but it could happen.
  • 1 Rare: Only in exceptional circumstances.

Impact

  • 1 Insignificant: No lasting effect. Handled within routine work.
  • 2 Minor: Small effect that is quickly corrected.
  • 3 Moderate: Noticeable effect that needs managed effort to correct.
  • 4 Major: Serious effect on people, delivery or reputation.
  • 5 Catastrophic: Severe or lasting effect that threatens the whole activity.

Bands (likelihood x impact)

  • Low (1 to 4): Accept and monitor.
  • Medium (5 to 9): Manage with routine controls.
  • High (10 to 16): Senior attention and a treatment plan.
  • Critical (17 to 25): Act first. Do not proceed until reduced.

Monitoring, escalation and review

Review this assessment every 6 months, and sooner when an indicator below reaches its threshold.

Early-warning indicators and escalation thresholds
Indicator to watchEscalate when
Forecast variance above the agreed margin for two consecutive weeks.Escalate to the revenue manager at once, and to the director of rooms if the variance persists for a month.
Rate differences between channels found during the morning check.Escalate to the systems administrator the same day, and freeze the affected channels until parity is restored.
Arrivals walked to another property in a single month.Escalate to the front office manager when more than two walks occur in a month, and to the general manager if the limit is breached again.
Overtime above agreed weekly hours for three or more staff in one week.Escalate to the human resources manager within two working days, and to the general manager if it continues for two weeks.
Repeated bulk exports of guest records or access from an unknown device.Escalate to the data protection lead at once, suspend the account, and inform the general manager within 24 hours.

Contingency arrangements

If a serious event occurs, such as a confirmed guest data breach, a full channel outage or a fire-related room closure, the duty manager informs the general manager and stops affected sales at once. The systems administrator isolates the affected system and restores data from the latest tested backup. The data protection lead leads the response and contacts the relevant authorities through the general manager where required. Guests are relocated under the walk policy, and staff receive clear instructions and support.

Prioritized action plan

  1. Set rate floors, ceilings and approval rules in the revenue system, owner revenue manager, within 45 days.
  2. Enable multi-factor sign in and remove stored card numbers from spreadsheets, owner data protection lead, within 30 days.
  3. Write and rehearse the overbooking walk policy with a partner property, owner front office manager, within 30 days.
  4. Link room closures to the revenue system and schedule plant maintenance, owner chief engineer, within 30 days.
  5. Agree shift limits and cross train cover staff in each department, owner human resources manager, within 60 days.

Conclusion

Sound yield management depends on steady habits: approved rate changes, a single rate source, a tested walk policy, tested backups, supervised access to guest data and maintained facilities. The highest scores sit with guest data, rate integrity and channel reliability, and each has actions that bring the residual score down. Keep the register under review on the stated cycle, and seek qualified advice for any real legal, privacy, safety or accessibility question.

Assumptions and limitations

Assumptions

  • The property is a single independently run hotel of around one hundred rooms that takes card payments through a third party processor.
  • Staff are trained in the property management system and use managed devices on a secure network.
  • Jurisdiction is not specified, so privacy, accessibility and consumer duties are described in general terms only.
  • Rate changes are approved by the director of rooms before they go live in the revenue system.

Limitations

  • The scores are examples for learning and do not describe any real hotel, market or guest group.
  • Pricing, data protection and accessibility rules differ by country and change over time, so specialist review is needed.
  • This is educational content and does not replace a formal site-specific assessment or licensed legal, financial or safety advice.

Related frameworks to study

  • Enterprise risk management with likelihood and impact scoring
  • Hierarchy of controls
  • Three lines model of risk ownership
  • Business continuity planning basics
  • Fire risk assessment process for guest accommodation

Hospitality Risk Assessment

China, India, United States, Indonesia, Pakistan, Nigeria, Brazil, Bangladesh, Russia, Japan, Mexico, Philippines, Vietnam, Egypt, Turkey, Germany, United Kingdom, France, Italy, Canada, South Korea, Australia, Spain.

For Learning Reference Only: This assessment demonstrates how risk assessment principles are applied in a practical setting, providing a useful reference for learning and understanding. Actual assessments may be adapted to suit specific site conditions and circumstances.

Keep learning

Study the subject behind this assessment.

Hotel Revenue and Yield Management course Read the best practices for this course

More Hospitality risk assessments

Hourly Active: 35,661 Learners