🔥 New · RM Copilot 2.0 - Voice mode is live

RevEvolve
Module 3 of 8 · Operations & Channels

Booking pace analysis that tells you which 3 dates matter today.

Real-time pace anomalies by date, segment, and channel - ranked by revenue impact. Built into the same platform as your forecast and pricing engine, so a pace alert comes with the recovery action attached.

Most pace reports are read once a week, scanned for red cells, and forgotten. The result: weekend pace problems get caught Friday morning when there's nothing left to do about them. RevEvolve treats pace differently. Anomaly detection runs against the forecast continuously - when actual pickup diverges materially from forecasted pickup at a given days-out interval, the date gets flagged. The morning briefing shows the 3 dates where action is warranted, with the recovery option attached. No more sea of red cells.

See Pace Alerts on Your Data - 30-Min DemoSee All 8 Platform Modules
  • 18 hrssaved per GM on revenue ops
  • Real-timepace anomaly detection
  • Ranked by $revenue impact, not variance %
  • +13.7%RevPAR lift in 10 days

Definition

What is booking pace in hotel revenue management?

Featured definition

Booking pace in hotel revenue management is the rate at which reservations are accumulating for a future stay date, measured in room-nights picked up at each days-out interval. Modern pace analysis compares actual pickup against a forecasted pickup curve in real time and flags dates where the variance signals an underlying demand or pricing problem worth acting on.

Ranked by revenue impact, not variance %.

A 30% pace shortfall on a Tuesday with 12 rooms left to sell shows red - dollar impact: $1,400. A 6% pace shortfall on a Saturday with 90 rooms compressed shows yellow or even green - dollar impact: $14,000. Operators acting on color-coded variance scan the wrong dates first.

RevEvolve ranks anomalies by projected revenue impact in dollars. Saturday's $14,000 problem surfaces above Tuesday's $1,400 problem, every time. The 3 dates that matter today are the 3 with the highest dollar impact - not the loudest red.

Pace without forecast is just a spreadsheet.

A spreadsheet showing “47 rooms picked up vs 52 same-day-last-year” is a comparison, not a pace alert - last year may have had different demand drivers, comp set position, or segment mix. The variance is unanalyzable without context.

RevEvolve compares actual pickup against the forecasted pickup curve from the AI Demand Forecasting module - which already accounts for events, comp set, segment mix, and historical pickup patterns. The variance is meaningful because the forecast is calibrated.

How the engine works

Inputs in, anomalies out - no sea of red cells.

Seven inputs, defensible outputs, real-time cadence, three reasons to trust the alert ranking.

01

Inputs - what the pace engine reads

  • AI Demand Forecast

    The forecasted pickup curve at each days-out interval. The single biggest input - pace anomalies are defined as variance against this curve, not against last year.

  • Real-time PMS booking state

    Current cumulative pickup for each future stay date. Updates within 90 seconds of each new booking, modification, or cancellation.

  • Cancellation patterns

    Historical cancellation rate by lead time and segment. Pace evaluation is net of expected cancellations, not gross pickup.

  • Segment mix

    Pace by segment (corporate, leisure, group, OTA, direct). A topline pace anomaly is rarely meaningful - segment-level pace anomalies are.

  • Channel mix

    Pace by channel. OTA pace ahead while direct pace lags = pricing or visibility problem on the direct booking surface.

  • Same-day-last-year baseline

    Secondary baseline for sanity-checking. Available in the dashboard but not the primary anomaly signal.

  • Pricing action log

    Recent rate changes for each date. Pace correlates rate moves to pickup changes - feeds the rate elasticity model in pricing.

02

Outputs - what the engine produces

  • Pace anomaly feed - chronological list of dates where actual pickup is materially diverging from forecast, ranked by projected revenue impact in dollars.
  • Pace curve by date - forecasted vs actual pickup for any selected stay date, at each days-out interval. Hover for variance and dollar impact.
  • Segment-level pace breakdown - reveals whether a topline pace problem is corporate-driven, leisure-driven, OTA-shifted, etc.
  • Channel-level pace breakdown - identifies OTA-vs-direct pace divergence and direct-booking visibility problems.
  • Recommended recovery actions - per-anomaly suggested response. Rate drop, restriction loosen, channel mix shift, OTA rate adjustment, or hold.
  • Pace audit log - every anomaly historically, the recovery action taken, and the actual outcome. Builds the playbook over time.
03

Cadence - when pace updates

  • Real-time triggers

    Booking, cancellation, or modification → pace recomputes for the affected stay date within 90 seconds. Anomaly threshold re-evaluated.

  • Hourly triggers

    Anomaly ranking refresh - revenue impact recalculated against current rate, current forecast, and remaining inventory.

  • Daily triggers

    Morning briefing assembly. RM Copilot synthesizes the top 3 anomalies into the operator's daily briefing with recovery action prompts.

  • Weekly triggers

    Pace audit log roll-up - which anomalies were caught, which recovery actions were taken, what the outcome was. Feeds the recommended-action engine over time.

04

Why this is defensible - three structural reasons

  • Forecast-anchored, not last-year-anchored.

    Anomalies are defined against the calibrated forecast, which already accounts for the demand drivers shaping this year's pickup pattern. Last-year comparison is a sanity-check overlay only.

  • Ranked by dollar impact, not variance percentage.

    Operators don't have time to scan 90 dates of red and yellow. The 3 dates with the largest dollar impact get surfaced. Everything else stays in the dashboard for analyst review.

  • Recovery actions, not just alerts.

    An alert without an action is a homework assignment. RevEvolve attaches a recommended recovery - rate drop, channel shift, restriction loosen, or hold - to every anomaly. Copilot can execute on operator approval.

Operator use cases

Three scenarios where pace alerts ranked by $ impact change the day.

  • 01

    The Saturday pace lag you don't see in variance %.

    Setup

    It's Wednesday. Saturday's pace is 6% behind forecast - not a red flag in any traditional pace report. But Saturday is a 90-room compressed weekend. The 6% lag translates to ~5 unsold rooms at $389 ADR = $1,945 of unrealized RevPAR if pace doesn't recover.

    What pace analysis does

    Anomaly engine ranks Saturday at the top of the alert feed because the dollar impact is high, even though variance percentage is low. Recommended recovery: "OTA rate decrease 4% - comp set has room to absorb without parity break. Projected pickup recovery: 4 rooms over 72 hours." GM approves in the morning briefing. By Friday, pickup has recovered to forecast.

    What this replaces

    In a traditional variance-percentage pace report, Saturday's 6% shortfall sits under Tuesday's 30% red flag - even though Tuesday's dollar impact is $1,400 and Saturday's is $14,000. Operators scan the wrong dates first.

  • 02

    The segment mix shift hidden in topline pace.

    Setup

    Next Tuesday's topline pace looks fine - 1% above forecast. But the segment breakdown shows corporate pace is +18% while leisure is -22%. Total looks balanced. Underneath, the rate mix is shifting toward higher-rate corporate, which inflates ADR but doesn't reflect underlying demand.

    What pace analysis does

    Segment-level anomaly detection catches the divergence. Alert: "Tuesday corporate +18%, leisure -22%. Segment mix shift detected. Risk: corporate pickup may stall as remaining demand softens. Recommend hold, monitor closely." RM holds rates instead of pushing higher. Two days later, leisure pickup recovers as comp set rates harden. Tuesday closes near forecast with healthy segment mix preserved.

    What this replaces

    Topline-only pace reports miss segment mix shifts entirely. Operators see green and act on green - then watch RevPAR slip without any defensible explanation for ownership.

  • 03

    The cancellation wave caught in real time.

    Setup

    Thursday afternoon. A weather event in a feeder market causes 23 transient cancellations in 90 minutes for the upcoming weekend. Without intervention, weekend RevPAR will undershoot forecast by ~$18K.

    What pace analysis does

    Pace engine detects the cancellation cluster within 2 minutes. Two anomalies fire - Saturday and Sunday both flip from "on pace" to "high dollar impact." Recommended recovery for Saturday: "Drop OTA rate 12%, push same-week leisure promo, release 8 rooms held for Sunday group block." RM gets the alert by 2:47 PM, approves the multi-action recovery, and Saturday pickup recovers to within 4% of forecast - saving roughly $11K of the $18K projected shortfall.

    What this replaces

    Nightly-batch pace reports miss cancellation waves entirely. Operators discover the cluster Friday morning when there's no time left to recover anything.

The pace dashboard

Four views operators use weekly.

  • 01

    Anomaly feed (default landing view)

    Chronological list of dates with material pace variance, ranked by projected revenue impact in dollars. Each item shows stay date, current variance ($ and %), recommended recovery action chip, and a one-click drill-down. The 3 highest-impact dates pin to the top - operators act here, not in the curve view.

  • 02

    Pace curve detail

    For any selected stay date: forecasted pickup overlaid with actual pickup, plotted across the days-out interval. Hover any point for variance and projected dollar impact. Toggle to view by segment, channel, or topline. Same-day-last-year overlay available as a secondary baseline.

  • 03

    Segment & channel breakdown

    Cuts the pace by segment (corporate, leisure, group, OTA, direct, government, SMERF) and by channel (direct, GDS, OTA-by-name, wholesale). Reveals mix shifts that hide in topline pace. Critical for high-mix urban and convention properties.

  • 04

    Pace audit log

    Every anomaly historically, what recovery action was taken, what the outcome was. Builds the playbook over time and gives ownership a defensible record of pace management. Asset managers use this for portfolio-level pace governance reviews.

Platform integration

Pace reads from forecasting + pricing - feeds 5 more modules.

In a stitched stack, your pace report runs nightly against a week-old forecast and produces alerts your pricing tool never sees. RevEvolve runs pace continuously against the live forecast, feeds the anomalies into pricing and channel decisions in the same cycle, and delivers the recovery action through Copilot.

Compared

How this compares to how you track pace today.

CapabilitySpreadsheet-basedOther RMSSingle Enterprise RMSRevEvolve
Anomaly baselineSame-day-last-year (manual)Same-day-last-year + budgetForecast (property-week)Forecast (date × segment × channel)
Update cadenceWeekly (manual rebuild)Nightly batchDaily batch + on-demandReal-time (90 sec on inventory change)
Ranking methodVariance percentageVariance % + color codesVariance percentageProjected dollar revenue impact
Segment cutLimited (manual)Topline + segmentTopline + segmentDate × segment × channel
Recovery actionsTribal knowledgeNot providedSuggested in advanced tierPer-anomaly recommendation
Audit logEmail chainLimitedAvailable - analyst-builtBuilt-in, ownership-ready
Cross-module recoveryN/AManual handoff to pricingManual handoffPricing + channel + reporting in one cycle
Pace recovery in the field

From 6 hours of pace scanning to 12 minutes of pace action.

A 22-property independent management company in the Midwest had two analysts spending roughly 30 hours combined per weekon pace scanning across the portfolio - opening each property's report, eyeballing variance, flagging dates for the RM director's review. After switching to RevEvolve's pace anomaly feed ranked by dollar impact, the same coverage took 12 minutes per property per day. Pace scanning effectively disappeared as a manual workflow.

  • 30 hr → 12 min

    Per property per day pace coverage

  • +13.7%

    RevPAR vs prior 30-day baseline

  • 22

    Properties on one anomaly feed

My analysts were spending half their week reading pace reports. Now they spend 12 minutes a day acting on the 3 dates RevEvolve surfaces, and the rest of their time on strategy. The dashboard view is still there if we want to dig in - but most days, the alert feed is enough.
RM Director22-property independent management company · Midwest US
Read the full case study

FAQ

Pace questions, answered honestly.

A traditional pace report runs nightly, shows variance vs same-day-last-year or budget, and color-codes dates by variance percentage. Operators have to scan the whole report and decide which dates matter. RevEvolve runs pace continuously against the live forecast, ranks anomalies by projected dollar revenue impact, and surfaces only the 3-5 dates where action is warranted - with a recommended recovery action attached. The result is operator action, not analyst homework.

Stop scanning. Start acting.

See pace alerts on your data.

We'll connect to a slice of your PMS history and run anomaly detection on your last 30 days. You'll see the 3 dates that should have been alerts but weren't - and what the recovery action would have been. Bring a weekend that went soft and we'll show you why.

See Pace Alerts - 30-Min DemoSee All 8 Platform Modules

Comparing pace tools? See the side-by-side at /compare/ - or run the 18 hrs/week savings on your portfolio at /roi-calculator/.

  • Real-time anomaly detection
  • Ranked by $ impact, not variance %
  • Recovery action per anomaly
  • Forecast-anchored variance
  • Audit log · ownership-ready