Organize CHRM study around matching each revenue management concept to the business decision it supports: forecasting for availability, displacement analysis for group business, rate fences for segmentation, and duration controls for high-demand dates. Practice with paper scenarios where you must justify the tool choice, not just the calculation.
Why metric memorization alone breaks down on scenario questions
Each revenue metric exists to answer a specific management question. Study them as a map from decision to metric: profitability uses GOPPAR or TRevPAR, competitive position uses index metrics, and pricing decisions use segment-level demand data.
Start your preparation by drafting a two-column reference: on the left, a management decision (evaluate a group lead, judge market performance, set a discount, choose a distribution channel); on the right, the metric or analysis that informs it. Filling this table from your study materials forces you to articulate what each concept is for, which is the reasoning step that scenario-style questions test.
Then stress-test the map with mismatch cases. Ask what happens if you evaluate a food-and-beverage-heavy group booking using room RevPAR alone, or judge a soft-opening property using a RevPAR index before it has stabilized. Seeing why each tool fails outside its intended use cements the boundary conditions, which is far more durable than restating a formula definition.
- Metric: ADR, RevPAR — question: how well are rooms being sold?
- Metric: GOPPAR, TRevPAR — question: how much profit or total revenue does each available room generate?
- Metric: RevPAR index (RGI), ARI, MPI — question: how are we performing versus the competitive set?
- Analysis: displacement analysis — question: should we accept this group?
Forecasting demand: constrained versus unconstrained numbers
Unconstrained demand is the demand you could serve with unlimited rooms; constrained demand reflects your actual capacity and restrictions. Forecasts must separate the two, because capacity limits make raw booking pace misleading on high-demand dates.
In practice, a property that shows 100% occupancy did not necessarily capture all demand; some would-be guests were turned away. A useful study habit is to reconstruct both figures for a hypothetical week: take constrained occupancy by day, add an estimate of turned-away requests and ineligible stays, and label which nights are truly capacity-constrained. This exercise shows why the same 90% occupancy can mean a demand problem on Tuesday and a pricing opportunity on Saturday.
Forecast accuracy also has a purpose beyond prediction: it drives the controls you set. Compare two response rules — if unconstrained demand exceeds capacity, expect to apply minimum length-of-stay or closed-to-arrival restrictions; if demand is soft, expect discounting or channel-opening decisions. Linking each forecast reading to a named control turns forecasting from a passive number into a decision trigger you can narrate in a scenario answer.
Worked scenario: evaluating a group booking with displacement analysis
Displacement analysis compares group revenue against the transient revenue the group would displace, then adds ancillary contribution. Compare the group rate to ADR and you may reject business that would have increased total revenue.
Scenario: a 300-room hotel receives a request for 75 rooms on a Tuesday at $129. The constrained transient forecast for that night is 250 rooms at $185 ADR, well below the 300-room capacity. Group room revenue is 75 × $129 = $9,675. Accepting means 225 rooms remain for transient, so 25 forecast transient rooms are displaced, worth 25 × $185 = $4,625. Net room contribution is $9,675 − $4,625 = $5,050 before any group meeting or banquet revenue is added.
The plausible mistake is comparing rates directly: $129 against a $185 ADR looks like a clear rejection. The better decision runs the displacement arithmetic, notices that transient demand alone would leave 50 rooms unsold, and recognizes that only 25 rooms are genuinely contested. Because the group fills otherwise-unsold inventory and may carry food-and-beverage contribution, acceptance is the revenue-positive call. This is why group evaluation is a displacement question, not a rate-comparison question.
Rate fences and segmentation: justifying price differences to a guest
A rate fence is a rule that makes a discounted or premium rate available only to guests who meet a condition, such as advance purchase or refundability. Fences let prices differ by segment while protecting the full-rate business.
Study fences in two families: transaction fences (advance purchase, minimum stay, refundability, channel) and guest fences (membership, corporate status, group affiliation). For each fence, practice articulating the logic in one sentence: an advance-purchase fence trades flexibility for rate because the guest is committing early; a refundable fence justifies a higher rate because the property absorbs the risk of the room going unsold. A fence you cannot justify is a fence a guest can challenge.
Then connect fences to segmentation data. A fence only works if the segment it targets actually behaves as predicted — corporate guests booking late, leisure guests booking early. Build a one-page segment sheet for a hypothetical property listing each segment, its booking window, its price sensitivity, and the fence matching that behavior. In scenario questions, this lets you evaluate whether a proposed rate structure is internally consistent rather than merely whether each individual rate is plausible.
Worked scenario: duration control on a night with a sellout forecast
Duration controls such as minimum length of stay and closed-to-arrival manage which stays consume constrained nights. Evaluate a request by the opportunity cost of each night it uses, not by its nightly rate alone.
Scenario: a 140-room hotel forecasts a sellout for Saturday, with soft demand Friday and Sunday. Two requests arrive at the same $159 rate: guest A wants Saturday only; guest B wants Friday through Sunday, three nights at $159 each. Guest B's request totals $477 and consumes only one constrained night, while adding revenue on two nights that might otherwise go unsold. Guest A's request consumes the constrained night but leaves Friday and Sunday inventory exposed to soft demand.
The tempting mistake is treating both as interchangeable $159 bookings, or reflexively accepting the shorter stay to protect availability. The better decision weighs the whole stay against the constrained night's opportunity cost: if Saturday's remaining rooms will sell out regardless, guest B's three-night stay adds more total revenue for the same constrained-room cost. This is the reasoning behind minimum length of stay as a control, and why last-room decisions are stay-value decisions, not rate decisions.
Reading competitive performance with index metrics
Index metrics express your performance relative to a competitive set: occupancy (MPI), rate (ARI), and revenue per available room (RGI, often called RevPAR index). An index above 100 means you outperform the set on that measure.
The study skill here is reading combinations rather than single numbers. An RGI above 100 with an occupancy index below 100 indicates a rate-led position; the reverse suggests volume leadership at lower rates. Practice narrating what each combination implies and which lever it points to: a rate-led property defending rate integrity versus a volume-led property examining whether its rate gap is justified by its product or segment mix.
Add the classic follow-up question: why might strong index performance coexist with weak profit? Indexes measure room revenue only, so a property could win RGI while its mix skews to low-margin business, which is where GOPPAR and TRevPAR enter the picture. Working through these tensions — index versus absolute figures, revenue versus profit — trains the judgment that distinguishes a revenue manager from someone who merely reports numbers.
A four-week practice sequence and self-check rubric
Sequence preparation by decision, not by textbook chapter: metrics first, then forecasting, then group evaluation, then controls and competition. Close each week with one worked paper scenario scored against a rubric.
Week one: build the metric-to-decision map and compute ADR, occupancy, RevPAR, GOPPAR, and TRevPAR for a sample week until you can reconcile RevPAR two ways (room revenue ÷ available rooms, and ADR × occupancy). Week two: practice constrained versus unconstrained forecasting on the same dataset and flag which nights would trigger controls. Week three: run at least three displacement analyses with varying transient forecasts, including one where rejection is correct. Week four: design fences and duration controls, then read index combinations for a hypothetical competitive set.
Self-check rubric — score each item 1 (cannot yet), 2 (with notes), 3 (unaided): (1) compute and reconcile RevPAR; (2) explain the difference between constrained and unconstrained demand with an example; (3) complete a displacement analysis including ancillary reasoning; (4) justify a rate fence for each named segment; (5) choose between two same-rate requests using stay value. Treat 12–15 as a learning milestone showing fluency, not as a prediction of any exam outcome.
| Metric or tool | Question it answers | Use it when | Blind spot to watch |
|---|---|---|---|
| ADR | What is the average rate of rooms sold? | Assessing pricing on rooms actually sold | Ignores occupancy; can look strong in a sellout with heavy discounting hidden in mix |
| RevPAR | How productive is each available room? | Comparing rooms revenue across dates or properties | Room revenue only; ignores F&B and other profit centers |
| GOPPAR | How much profit does each available room generate? | Judging decisions with different cost and margin profiles | Harder to attribute; needs departmental cost data |
| RevPAR index (RGI) | Are we winning our fair share of revenue? | Benchmarking against the competitive set | Only as meaningful as the comp set definition |
| Displacement analysis | Should this group be accepted? | Evaluating group business against forecast transient demand | Depends entirely on forecast quality and ancillary estimates |
| Length-of-stay control | Which stays may consume this constrained night? | Sellout-forecast dates with mixed stay patterns | Can push away desirable multi-night revenue if set too bluntly |
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.