Hotel Revenue Manager Role SOP / Operating Playbook

Model Role SOP / Operating Playbook: Hotel Revenue Management

Credential field: Professional Certificate in Hotel Revenue Management
Document type: Evidence-derived model operating playbook for local adaptation
Evidence geography and date: U.S.-workplace hotel revenue-management openings current on 2 October 2026
Author: MTF Institute Research Team
Reviewed by: MTF Institute
Prepared: 2 October 2026

Model for adaptation. This is a learner-facing example of an operating rhythm, not an employer policy, an authorization to change live rates, a universal hotel standard, or a legal compliance manual. Replace every [LOCAL ...] field with the employing hotel's approved rules, system names, roles and data definitions before use. The vacancy research report describes the bounded 65-opening sample and its 61-role operational sensitivity. The separate current-changes article provides dated market and product context; it is not a source of employer authority.

Purpose, scope and boundaries

The purpose of a hotel revenue-management workflow is to convert observed demand, booking pace, rate, room inventory, segment and distribution evidence into a documented commercial decision, carry out only the actions the role is authorized to take, and verify what happened. The work product is a forecast, rate or inventory recommendation, approved control change, channel correction, group-business assessment, revenue-meeting decision record, or performance explanation that another team member can use.

This model covers guest-room revenue and directly related group, meeting-space and channel decisions when the local role owns or supports them. Some U.S. postings also include reservations supervision, ecommerce, food and beverage, casino or other resort streams; those additions are role-specific and must not be silently imported into an ordinary hotel-room SOP. Four senior progression roles in the research set were kept outside the 61-role operational sensitivity. Assistant roles may prepare analysis and recommend changes while an assigned director owns final control. The Hilton assistant manager supports pricing decisions; the Grand Hyatt San Francisco director has wider strategy and inventory duties. Neither posting defines authority at every hotel.

The role must use [LOCAL APPROVAL MATRIX] for rate, restriction, group quote, overbooking, budget, refund, promotion and system-access decisions. A missing approval rule is an exception to resolve, not permission to act. This playbook never assumes that a revenue manager can commit group contracts, override an automated pricing system, change a channel connection, approve a budget or share confidential guest/owner data without authorization.

Roles, interfaces and inputs

The revenue-management owner collects and interprets commercial evidence and maintains the decision record. Depending on the local structure this may be a property manager, cluster/area manager, director, assistant or approved shared-services analyst. The decision approver is the person named in [LOCAL APPROVAL MATRIX]. Sales and Catering provide leads, group requests, account terms and event-space constraints. Reservations and Front Office confirm room availability, room-type mappings, pickup, cancellations, group blocks and guest-facing implications. Finance confirms budget and profitability definitions. Marketing and Ecommerce coordinate offers, direct-booking and channel campaigns. Distribution or system administrators own connectivity, rate loading or technical correction where designated. General Manager, ownership and corporate revenue leadership receive recommendations or approve decisions according to local authority. The interfaces listed here are source-derived examples, not a universal org chart.

The minimum inputs for a dated review are:

• the stay-date range, room type and property or approved portfolio in scope;
• reservations on the books, recent pickup, cancellations, lead time and remaining sellable inventory from authorized PMS/CRS/RMS sources;
• the current approved forecast and its assumptions, plus actual occupancy, ADR, RevPAR and relevant benchmark information where licensed;
• segment, channel and group-block views using local definitions, including rate fences, restrictions, allotments, parity and cost of distribution where available;
• the local event and demand calendar, competitor observations and known operational constraints; and
• the previous decision log, its owner, effective date and observed outcome.

Write [LOCAL SOURCE SYSTEM], [LOCAL DATA OWNER], [LOCAL METRIC DEFINITION] and [LOCAL REFRESH TIME] beside each input. Never paste guest-level personal data into a general meeting pack or an unapproved AI tool. If an input is stale, conflicting or missing, label it rather than filling it with a guessed zero.

Trigger-to-close workflow

Run this sequence when the scheduled review, a material booking change, a group request, a rate or channel exception, a forecast revision, or another locally approved trigger calls for action. It is a model sequence; local employer policy controls thresholds and permissions.

1. Define the decision. Record the property, stay dates, segment/channel, affected rooms and the question to be answered. Identify whether the requested output is an analysis, recommendation, approval request, implementation or verification. Name the accountable decision owner from [LOCAL APPROVAL MATRIX].
2. Check the evidence. Record data extraction time and reconcile the relevant PMS/CRS/RMS and channel views. Compare rooms on the books, pickup, cancellations and inventory with the prior forecast. Mark any unverified search-interest or competitor signal as context rather than booked demand. If the data disagree, record the discrepancy, its owner and the next check before making a consequential rate or inventory change.
3. Build a focused comparison. Show current position, a plausible action and at least one reasonable alternative. State the expected effect on room nights, ADR, RevPAR, segment mix, net channel contribution or group displacement as applicable. Do not convert a supplier claim or a generic benchmark into a property outcome. Separate observed facts, assumptions and local policy constraints.
4. Recommend or approve within authority. Document the recommendation, effective stay dates, rate/room types, restriction or channel, expected benefit, downside and reversal condition. Send it to [LOCAL APPROVER] where required. An assistant or analyst records the approver's decision rather than acting as the approver. A declined proposal remains in the log with the reason and review date.
5. Implement the approved action. Use [LOCAL APPROVED SYSTEM] and the named execution owner. Confirm room-type and channel mapping, rate floor/ceiling, parity rule, group block and guest-facing terms before saving. Coordinate with Reservations, Front Office, Sales or Distribution when a handoff is needed. Record who executed the change and when; never assume that saving it in one system reached every booking surface.
6. Verify and close. Check the intended public/direct/OTA/GDS or internal channel view where permitted, then review pickup or exposure at [LOCAL REVIEW INTERVAL]. Record actual-versus-expected effect, exceptions and whether to retain, reverse or escalate. Close only when the approved output, verification evidence and next owner are visible in the decision log.

The Wolseley property director posting supports segment pricing, channel and group-quote decisions; the Aimbridge regional posting names forecasting, group mix and third-party distribution. These postings support the types of work, not one universal approval chain or numeric trigger.

Daily, weekly, monthly and event-driven cadence

Daily exception review: Check yesterday's performance and the next relevant stay dates for unusual pickup, cancellations, sellout risk, room-type availability, rate loading, group cutoffs and channel display. Prioritize exceptions, identify the data owner, and document a short recommendation or approved correction. A daily review may be a brief check rather than a full strategy meeting. The TPG property revenue-manager posting includes day-to-day yield and weekly forecasting; its Front Office and payroll duties are separately coded as non-core.

Weekly commercial review: Reconcile the rolling forecast with on-the-books rooms, pickup and need periods. Prepare a concise meeting pack with prior action outcomes, segment and channel mix, rate/inventory exceptions, group opportunities and explicit decisions sought. In the meeting, distinguish information from proposed action, record owner and approval, and issue notes that can be checked later. The Mandarin Oriental Boston mixed role prepares a commercial strategy pack; that source does not make every manager the chair.

Monthly performance and forecast review: Compare actual occupancy, ADR, RevPAR and room revenue with budget, prior forecast and relevant market context. Explain the variance by room nights, rate, segment, channel or one-off event rather than merely reporting a percentage. Record revised assumptions, risk ranges and proposed controls. Share owner or corporate commentary only with authorized recipients. Annual budget work is a separate assigned process and does not imply final budget approval.

Event-driven review: A group RFP, citywide event, changed flight/event demand, new competitor action, channel mapping failure, overbooking risk, system recommendation outside local bounds or major cancellation can trigger a focused assessment. Use the trigger-to-close sequence above, the local approval threshold and an explicit follow-up time. A marketplace search surge is not a booking surge; verify the hotel reservation signal before changing the forecast or price.

Decision, handoff and escalation record

Use one row per material decision or exception. The fields below are a reusable blank template; they are not a claim that any employer uses this exact form.

Escalate when data are materially inconsistent; the proposed change exceeds [LOCAL RATE OR INVENTORY LIMIT]; room-type, rate or channel mapping is uncertain; a group request exceeds [LOCAL GROUP APPROVAL RULE]; guest, contract or regulatory terms may be affected; or the assigned approver/system owner is not identifiable. The accepted vacancy sample explicitly states escalation in only 4 of 65 ads, so these are prudent model questions, not claims about universal hotel policy. Use local rules to name the actual escalation route.