Revenuenaire
Hotel Revenue Management36 min read

Hotel Pickup Report: How to Read Booking Pace Correctly

A hotel pickup report tracks bookings minus cancellations by stay date. It covers the variance formula, group vs transient pace, and when a gap means act now.

Hotel Pickup Report: How to Read Booking Pace Correctly
In this article9 sections
  1. What Your Pickup Report Actually Shows
  2. The Real Pickup Variance Formula
  3. Reading Pace Against Last Year
  4. Group Pace vs Transient Pace
  5. Is Your Pace Falling Behind?
  6. When Should You Act on a Pace Swing?
  7. Pickup Reports Across Property Types
  8. Building a Pickup Report Without an RMS
  9. Frequently Asked Questions

Three weeks out from a slow Tuesday in March 2026, a 42-room boutique hotel was sitting at 61 percent occupancy on the books, nine points behind the same date in 2025. A manager watching only the occupancy number would have discounted that night on the spot. The pickup report told a different story: transient bookings for that date had accelerated for four straight days, while the prior year's pace had already flattened by the same point in its booking curve. The hotel held its rate. It closed the night at 94 percent, two points ahead of the prior year, at a higher average daily rate. The number that mattered was never the occupancy on the books. It was the rate of change behind it, and that rate of change is exactly what a pickup report is built to show.

What Your Pickup Report Actually Shows

A hotel pickup report shows how many rooms and how much revenue a property added to, or lost from, a future stay date between two points in time. It is a comparison of two on-the-books snapshots for the same future date, broken out by market segment.

It is a difference report, not a snapshot report, and that distinction is the first thing most operators get wrong when they start reading one. The change it measures is expressed in rooms, room nights, and revenue.

Every pickup report is built from the same three ingredients: a stay date, a snapshot date, and a prior snapshot date to compare against. The stay date is the night being sold, for example a Saturday six weeks from now. The snapshot date is today, when the report runs. The prior snapshot is whatever reference point the hotel chose, commonly yesterday for a daily pickup report or the same day last week for a weekly one. On the books, abbreviated OTB throughout this guide, refers to every confirmed reservation touching that stay date at the moment the snapshot was pulled, regardless of what channel it came through.

The table below shows a simplified version of what a daily pickup report looks like for a single future stay date, tracked across a five day window. In the portfolios we price, this is close to the minimum viable layout: date, rooms on the books, the change since the last snapshot, and revenue on the books, split by segment.

Snapshot DateRooms OTB (Transient)Rooms OTB (Group)Pickup (Rooms)Revenue OTB
Day 15820N/A (baseline)$14,210
Day 26120+3$14,890
Day 36318+2 / -2$15,020
Day 46818+5$16,340
Day 57022+2 / +4$17,780

Read that table correctly and a pattern appears that occupancy alone would hide. Transient rooms climbed every single day, a healthy and consistent pickup. Group rooms dropped by two on Day 3, a cancellation inside a block, then jumped by four on Day 5 as a new block confirmed. A property manager glancing only at total occupancy on Day 3 would have seen a flat or declining number and assumed demand was softening, when the transient curve was accelerating the whole time. This is why pace is read in segments first and only combined afterward, a rule that holds for a 20-room inn and a 400-room full-service property equally.

Most property management systems and revenue management systems generate some version of this report automatically, labeled pickup report, pace report, or booking performance report depending on the vendor. The structure barely changes across systems: a grid of stay dates down one axis, snapshot dates or comparison periods across the other, with rooms, ADR, and revenue populated in each cell. What differs enormously, and what determines whether the report is useful, is how disciplined the hotel is about pulling it on a fixed cadence and comparing it against a consistent baseline rather than whatever number happens to be easiest to find that day.

Cadence matters more than most independent operators assume. A daily pickup report, pulled at the same time every morning, is the right tool for the next 0 to 21 days, where booking activity is dense enough that a single day's change is meaningful. Beyond that window, daily noise starts to dominate the signal, and a weekly pickup report, comparing this Monday to last Monday, becomes the more reliable read. Running a daily report on a date 90 days out mostly produces zeros and the occasional single-room blip, which tells a revenue manager nothing and wastes the five minutes spent looking at it. Running a weekly report inside the 14-day window, conversely, is too coarse to catch a cancellation that needs same-day action. Matching the report's frequency to the booking window being examined is a small operational choice that saves hours a month once it is set correctly.

The segment split in the table above is doing more work than it looks like. Transient pickup, driven by individual leisure and corporate travelers booking directly or through OTAs, tends to arrive close to the stay date and respond quickly to rate changes. Group pickup, driven by blocks booked months in advance, moves in large, infrequent steps tied to contract deadlines and attrition clauses rather than daily demand. Blending the two into a single occupancy number erases exactly the distinction a revenue manager needs to decide whether today's rate is still correct. A full breakdown of how those two patterns diverge, and what to do differently for each, follows in a later section of this guide.

Bottom line: A pickup report is a rooms-and-revenue delta between two OTB snapshots for the same stay date, and it only becomes decision-useful once transient and group pickup are read separately, on a cadence matched to how far out the stay date sits.

The Real Pickup Variance Formula

The pickup variance formula is Pickup equals Rooms OTB at Snapshot B minus Rooms OTB at Snapshot A, run for one stay date, with Pace Variance adding a second subtraction against the equivalent snapshot from last year. Everything else in a pickup report sits on top of that arithmetic.

The color coding, the dashboards, and the automated alerts in a PMS or RMS are a presentation layer, nothing more. Revenue managers who can do this arithmetic on paper read a vendor dashboard faster than those who only know how to glance at a colored cell, because they can tell when the dashboard itself is wrong.

Write the formula out in full and it has four components worth naming separately, because each one fails in a different way. Rooms Pickup equals New Reservations minus Cancellations minus No-Show Adjustments for the period between snapshots. Revenue Pickup equals New Revenue Booked minus Cancelled Revenue, which is not the same number as Rooms Pickup multiplied by the average rate, because new bookings and cancelled bookings rarely carry the same rate. Pace Variance equals Pickup This Year minus Pickup Last Year, measured at the identical number of days before the stay date, never the identical calendar date. ADR Pickup equals Revenue Pickup divided by Rooms Pickup, which tells a manager whether the rooms being added are helping or hurting the rate mix, independent of how many of them there are.

Here is a complete worked example using a 60-room independent hotel pricing a Friday night 30 days out. At the 30-day snapshot, the hotel had 24 rooms on the books at an average rate of $162, for $3,888 in revenue on the books. Seven days later, at the 23-day snapshot, the hotel had 33 rooms on the books at an average rate of $171, for $5,643 in revenue on the books.

Metric30-Day Snapshot23-Day SnapshotChange
Rooms OTB2433+9 rooms
Revenue OTB$3,888$5,643+$1,755
ADR OTB$162.00$171.00+$9.00
Occupancy OTB (of 60 rooms)40%55%+15 points

Rooms Pickup for the week is 9 rooms. Revenue Pickup is $1,755. ADR Pickup, the rate at which those 9 new rooms sold, is $1,755 divided by 9, or $195 per room, a full $33 above the ADR already on the books. That single number is the most useful figure in the whole table: it says the newest demand coming in is willing to pay more than the demand already booked, which is the single clearest signal a revenue manager can get that a rate increase on this date will not cost volume. Had ADR Pickup come in below the existing OTB rate, at say $140, the correct read would reverse entirely, suggesting the hotel is backfilling with discount-sensitive demand and should hold or lower rate rather than push it.

Carry the same numbers into RevPAR to see why pickup, not occupancy, is the number that should move a pricing decision. RevPAR OTB at the 30-day snapshot was $3,888 divided by 60 total rooms, or $64.80. At the 23-day snapshot it was $5,643 divided by 60, or $94.05. That is a $29.25 RevPAR gain in a single week from pickup alone, before a single rate change was made. Comparing that gain against the same 7-day window last year, if last year's RevPAR OTB moved from $58.00 to $71.00 over the equivalent snapshots, a gain of $13.00, this year is pacing $16.25 ahead of last year's pace on the same date. That gap, not the raw occupancy percentage, is the number worth presenting to an owner or reporting into a monthly pack.

The arithmetic holds at any property size, but the thresholds that matter shift with room count. On a 400-room property, a 9-room pickup in a week is noise; on the 60-room hotel in the example above, it is a 15-point occupancy swing and a legitimate pricing signal. Across the hotel accounts we manage, the rule of thumb is to size the "meaningful pickup" threshold at roughly 3 to 5 percent of total room count per week for transient business, and treat anything below that as within normal daily variance rather than a trend. A 20-room boutique property should expect single-room pickup days to look dramatic in percentage terms and should resist reacting to any one day in isolation; a 300-room property should do the opposite and treat even a modest percentage move as statistically real, because the sample size behind it is large enough to rule out noise.

Bottom line: Pickup Variance is bookings added minus bookings cancelled between two identical snapshots, and the ADR on that pickup, not the room count alone, is what should decide whether a rate holds, rises, or falls.

Reading Pace Against Last Year

Reading pace against last year means comparing today's on-the-books position to the same point on last year's booking curve, not to the same calendar date. A Friday in 2026 and a Friday in 2025 rarely share a calendar date, and comparing the wrong two produces a pace number that looks wrong for reasons that have nothing to do with performance.

March 14 this year might fall on a Friday while March 14 last year fell on a Saturday. Lining those two dates up anyway will misstate pace on a predictable, fixable basis, not because the hotel's underlying demand changed.

The correction is day-of-week alignment, sometimes called a rolling STLY comparison, where "last year" means the same day of the week, the same number of weeks from a fixed anchor such as New Year's Day or the same position relative to a recurring event, rather than the identical date on the calendar. Most modern property management and hotel demand forecasting tools handle this automatically, but it is worth checking the setting rather than assuming it, because a system defaulting to calendar-date comparison will quietly misstate pace on every single date where the calendar has drifted, which by late in the year is almost every date.

Once the comparison date is correct, the second variable that determines how pace should be read is lead time, meaning how many days out from the stay date the snapshot is being taken. Demand does not arrive at a constant rate across the booking window. A typical independent hotel sees roughly 10 to 15 percent of final occupancy on the books at 60 days out, 30 to 40 percent by 30 days out, 55 to 70 percent by 14 days out, and the remaining share arriving inside the final two weeks, with the exact shape varying by market, season, and how much of the hotel's mix is corporate versus leisure. A corporate-heavy weekday hotel books later and faster near the date; a leisure-heavy weekend property books earlier and flattens out sooner. Neither pattern is wrong, but applying the other property type's expectations to your own booking curve is a reliable way to panic over a gap that is actually normal, or miss a gap that is not.

The table below shows how a pace gap at different lead times tends to resolve by the stay date, based on the pattern we see across the independent and boutique hotel accounts we manage. These are not universal constants, and a property with an unusually compressed booking window, common after a renovation reopening or in a destination market with high last-minute demand, will see different numbers. The value of the table is the shape of the relationship, not the exact percentages.

Pace Gap vs STLYAt 45 Days OutAt 21 Days OutAt 7 Days Out
0 to 5 points behindCloses without action in most casesCloses without action in most casesLikely to hold at close; low urgency
6 to 12 points behindWorth a rate or channel review within the weekAct now: review rate, OTA visibility, and comp set movementRarely recovers fully; manage expectations with ownership
13 to 20 points behindInvestigate immediately: check for a data or comp set issue firstMaterial risk to budget; consider a rate or promotion responseTreat as the likely final result; shift focus to displacement later in the year
Over 20 points behindUsually a data error, a group loss, or a market-wide event; confirm the cause before reactingNeeds an immediate, specific explanation, not a generic rate cutFinal outcome is largely set; focus on cost control for the date instead

The reason the table gets kinder as the lead time shortens from 45 to 7 days is not that smaller gaps matter less close to the date. It is the opposite: a 15-point gap at 45 days out has 45 days of remaining booking activity to close it, while the same 15-point gap at 7 days out has almost none, so the correct response shifts from "wait and monitor" to "this is close to the final number, plan around it." Treating every gap, at every lead time, with the same urgency is one of the most common mistakes independent operators make, and it leads to either chronic overreaction in the early window or complacency in the window where action still has time to work.

A related and frequently skipped step is checking whether a gap is a demand problem or a constrained demand problem before touching rate. If a date is already closed to arrival on one channel, or a room type has sold out while others remain available, the pickup report will show a slowdown that has nothing to do with weakening demand and everything to do with inventory that was not opened up. Unconstraining demand, meaning estimating what would have sold if availability had not been restricted, is the step that keeps a revenue manager from lowering rate into a date that was actually selling out, just not visibly.

Bottom line: A pace gap means something different depending on how many days remain before the stay date, and a gap should never be read without first confirming the comparison period is aligned by day-of-week and that the shortfall is not an availability restriction masquerading as weak demand.

Group Pace vs Transient Pace

Group pace and transient pace are tracked on the same pickup report but move on completely different timelines, and reading them as one blended number is the fastest way to misdiagnose a date. Transient pace moves daily; group pace moves in large, infrequent steps tied to contract milestones.

A group block can sit perfectly flat for six weeks and still be exactly on track, because its pickup is tied to a cutoff date and a contract, not to daily demand. A transient curve behaving the same way would be a genuine warning sign.

A group block is booked against a contract, not a live rate shop, and that contract carries its own pickup logic: an initial block size, a cutoff date after which unsold rooms release back to general inventory, and an attrition clause specifying the minimum percentage of the block the group must honor or pay for regardless of actual pickup. Reading group pace correctly means tracking the block's own pickup against its own cutoff, separately from how transient demand for the same dates is moving, and only combining the two once the cutoff has passed and the released rooms are back in general inventory.

Here is a worked example. A 120-room hotel books a corporate group block of 50 rooms for a Tuesday through Thursday citywide event, 9 months out, with an 80 percent attrition clause and a cutoff 30 days before arrival. At the 90-day mark, the group has picked up 22 of the 50 rooms, which looks alarming if judged against a transient curve, but is normal for a group block that typically does not pick up in earnest until 45 to 60 days out. By the 45-day mark, pickup reaches 34 rooms. At the 30-day cutoff, the group has picked up 38 rooms against the 50-room block.

MetricValue
Contracted block size50 rooms
Attrition threshold (80%)40 rooms
Rooms picked up at cutoff38 rooms
Rooms short of attrition floor2 rooms
Attrition rate charged (example ADR $185)2 × $185 = $370
Rooms released to general inventory12 rooms (50 minus 38)

Two things happen at cutoff that a transient-only read of the pickup report would miss entirely. First, because pickup landed at 38 against an 80 percent attrition floor of 40 rooms, the group falls 2 rooms short and the attrition clause applies, generating $370 in attrition revenue at the contracted rate regardless of whether those rooms ever sell. Second, 12 rooms release back into general inventory 30 days before arrival, a meaningful transient opportunity that only exists because the cutoff passed. A revenue manager who was not tracking the group block's own pace against its own cutoff would miss the exact day those 12 rooms became sellable at the (usually higher) transient rate, and the pickup report for the surrounding transient dates would show a sudden, confusing jump in available inventory with no explanation attached.

This is also where group attrition strategy and pure pickup reading intersect. A group pace report that only tracks rooms picked up against block size, without also tracking the attrition floor and the cutoff date, cannot tell a revenue manager whether a slow-looking block is actually on track or genuinely at risk. The 22-of-50 pickup at 90 days out and the 38-of-50 pickup at cutoff are both "pace," but only one of them, measured against the right milestone, tells the hotel anything actionable.

Displacement is the second concept that only shows up once group and transient pace are read together. If transient demand for those same three nights is strong enough that the hotel could have sold the group's 50 rooms to individual travelers at a higher average rate, the group contract may be display quietly costing the hotel money even while it "paces normally" against its own block target. Checking group pace in isolation answers whether the group is honoring its contract. Checking it against concurrent transient pace answers the more important question of whether the hotel should have taken that group at all, a comparison worth running before, not after, a renewal conversation with a repeat group client.

In the hotel accounts we manage, the properties that get the most value from this split are not the large convention hotels, which usually have dedicated group sales systems already doing this tracking, but 40 to 150 room independent and boutique properties that take occasional group business without a dedicated sales department. Those are exactly the properties where a single blended occupancy number is most likely to hide a block quietly falling short of attrition, or transient demand being displaced by a group rate that looked attractive nine months ago and looks expensive now.

Bottom line: Track group pickup against its own cutoff and attrition floor, track transient pickup against the daily booking curve, and only read them as one occupancy number after the group's cutoff has passed and released rooms are back in general inventory.

Is Your Pace Falling Behind?

Your pace is genuinely falling behind when transient pickup has slowed for three or more consecutive snapshots relative to the same point on last year's booking curve, after ruling out a comparison error, a data gap, or a one-time event in either year's base. A single slow snapshot is not evidence of anything on its own.

Most pace alarms that reach an owner's inbox should be resolved before they ever get there, simply by checking whether the gap reflects real demand weakening or an artifact of how the comparison itself was built.

Start with the exceptions, because they are more common than genuine demand softness and far faster to rule out. A citywide event, a festival, or a large group that booked last year and did not rebook this year will make this year look weak by comparison even if underlying transient demand is flat or growing, because last year's base included a one-time spike that this year's base does not. A renovation, a temporary room-count reduction, or a brand standard change that affected last year's inventory will distort the comparison in the other direction. A rate parity violation on a major OTA, where a third party is quietly undercutting the hotel's own rate, can suppress this year's pickup on that one channel while the hotel's own booking engine shows nothing wrong. A booking engine outage, even a short one, can erase a day or two of what should have been pickup and make the following snapshot look like a spike that is really just delayed demand catching up.

Once those are checked and ruled out, the following mistakes are the ones we see most often working against independent and boutique hotels specifically, and each one is avoidable with a five-minute process change.

  • Comparing calendar dates instead of day-of-week-aligned dates, which makes every comparison look wrong by a predictable, fixable amount rather than reflecting real performance.
  • Reacting to a single snapshot instead of a trend across three or more snapshots, which turns ordinary day-to-day booking noise into a false alarm or a false reassurance.
  • Blending group and transient pickup into one occupancy number, which hides a transient slowdown behind a group block that is simply following its own, unrelated contract timeline.
  • Ignoring ADR Pickup and reacting to room count alone, which can lead to holding or raising a rate on dates where the only demand coming in is price-sensitive, or cutting a rate on dates where new demand is already paying more than the rooms already on the books.
  • Not unconstraining for availability restrictions, which makes a sold-out room type or a closed channel look like weak demand instead of successful demand that ran out of inventory to sell.
  • Using last year's final pickup instead of last year's pace at the same lead time, which compares an unfinished number against a finished one and will almost always show the current year "behind," regardless of actual performance.

The decision process that avoids most of these mistakes is short enough to run in under ten minutes once it is a habit: confirm the comparison is day-of-week aligned, confirm the trend holds across at least three snapshots rather than one, split the read by segment before combining it, check ADR Pickup alongside Rooms Pickup, and ask whether any channel or room type hit a sell-out or closure that would mask real demand. A revenue manager who runs those five checks before reacting to a pace number will catch the majority of false alarms before they turn into an unnecessary rate cut or an unnecessary promotion.

There is a genuine edge case worth naming directly: a market-wide demand shift, such as a major employer leaving town, an airline cutting a route, or a competitive new-build opening nearby, will produce a pace gap that is real, persistent, and will not close on its own no matter how carefully the comparison is built. The signal that distinguishes this from a temporary slowdown is duration and breadth: a market-wide shift shows up across most date ranges and most segments simultaneously, not on one isolated Tuesday, and it does not improve as the booking window shortens the way a normal gap does. When a gap shows that pattern, the correct response moves from pace monitoring to a full repricing of the comp set position and, often, a conversation about long-term positioning rather than a short-term rate tweak.

Bottom line: Before treating a pace gap as a real demand problem, rule out comparison errors, segment blending, and availability restrictions; a gap that survives all three checks and persists across multiple snapshots is the one worth acting on.

When Should You Act on a Pace Swing?

You should act on a pace swing once it has persisted across at least three consecutive snapshots, survived the comparison and segment checks covered earlier, and sits outside the normal variance band for that lead time. Acting earlier risks chasing noise with a rate change.

Acting later carries the opposite risk: reacting to a problem that has already become the final outcome, rather than one a rate or distribution change could still influence while there was still time left on the booking window.

Setting this up properly is not a one-day task, and treating it like one is why so many independent hotels either abandon pickup reporting within a month or run it so loosely that it never produces a usable signal. A realistic rollout looks like this. In the first week, pull the hotel's actual booking curve from the prior 12 months, by segment, to establish what normal pickup at each lead time actually looks like for this specific property rather than assuming an industry-average curve applies. In the second week, set the comparison baseline to day-of-week-aligned STLY and confirm the property management system or spreadsheet is pulling it that way by spot-checking three dates by hand. In the third week, set variance thresholds by lead time, using a table similar to the one earlier in this guide as a starting point, and assign who reviews the report and on what cadence: daily inside 21 days, weekly beyond that. In the fourth week, run the full cycle for the first time with a real decision attached, meaning at least one date actually gets a rate or distribution change based on what the pickup report showed, not just a note in a spreadsheet.

Action thresholds should be written down, not held in one person's head, because the entire value of a pace report is lost the moment the response to it depends on who happens to be on shift. A simple version that works for most independent and boutique properties: inside 21 days, a transient pace gap beyond 10 points triggers a same-day review of rate and OTA visibility; between 21 and 45 days, a gap beyond 15 points triggers a review within 48 hours; beyond 45 days, a gap is logged and monitored but does not trigger an automatic rate change, because the sample size at that lead time is usually too small to act on with confidence. These numbers should be tuned to the property's own booking curve rather than copied directly, but having any written threshold beats having none, because it removes the guesswork about whether today's gap crosses the line.

Measuring whether the pickup reporting process is actually working is a separate, ongoing task from running the report itself, and it is the step most hotels skip entirely. The cleanest measure is forecast accuracy: compare the occupancy the pace report implied at 14 days out against what actually happened at the stay date, across a rolling set of dates, and track the average error. A property that is reading pace correctly should see that error shrink over several months as the team calibrates its own variance thresholds to the hotel's real booking curve rather than a generic one. This connects directly to the broader forecasting discipline covered in our guide to building a hotel revenue budget, since a pickup reporting process that is not improving forecast accuracy over time is not actually earning the ten or fifteen minutes a day it costs to run.

A second, simpler measure that owners tend to respond to even without a formal accuracy calculation: count how many times per month the pace report flagged a date early enough that a rate or distribution change actually moved the outcome, versus how many times the flag arrived too late to matter. A process that is mostly generating late flags is a reporting process, not a revenue management process, and the fix is almost always to shorten the review cadence inside the 21-day window rather than to abandon pickup reporting altogether.

Ownership of the daily review matters more than most independent operators assume when they first set this up. An owner-operator running the front desk, housekeeping, and sales for a 30-room property genuinely does not have fifteen minutes a day to spare for pace review once the property is full of other fires, and a pickup process that depends on finding that time consistently will quietly stop happening within a few months, long before anyone formally decides to abandon it. The properties that keep the discipline going long-term are the ones that either assign the review to a specific person with no other morning fire to put out first, or outsource the review entirely to someone whose only job that morning is reading pace and deciding what, if anything, needs to change.

Bottom line: Act on a pace gap once it clears a written, lead-time-specific threshold across multiple snapshots, and track forecast accuracy over time to confirm the thresholds themselves are actually calibrated to the property, not just copied from a generic guide.

Pickup Reports Across Property Types

Pickup reports run on the same formula at every property type, but the thresholds, cadence, and booking curve shape that make the formula useful change between a boutique inn, a full-service branded hotel, an extended-stay property, and a seasonal resort. Applying one property's normal variance to another invites a false alarm or a missed problem.

A small independent or boutique hotel, typically under 60 rooms, will see the noisiest-looking pickup reports of any property type in percentage terms, simply because one or two rooms move the occupancy percentage by one to two points. The fix is not a different formula; it is wider variance bands and a firm rule against reacting to single-day movement, paired with closer attention to ADR Pickup, which carries more signal than room count at this scale because the sample size per room is so much larger relative to total inventory.

A full-service branded hotel, usually 150 rooms or more, has the opposite problem: enough volume that daily pickup is statistically meaningful, but a far more complex segment mix, with corporate negotiated rates, group and catering business, wholesale allotments, and loyalty redemptions all pacing on different timelines inside the same report. These properties typically already run pickup reporting through a dedicated revenue management system, and the value an independent consultant adds is less about building the report and more about making sure the thresholds across each segment are reviewed and tightened as conditions change, rather than left at whatever default the system shipped with.

Extended-stay properties change the pickup math in a way that is easy to miss: because length of stay often runs 7, 14, or 30 nights rather than 1 or 2, a single new reservation can move revenue on the books by several thousand dollars while moving the headline occupancy percentage for any single night only slightly, since that one guest occupies the room across many stay dates simultaneously. Reading an extended-stay pickup report by room-night pickup rather than by reservation count, and tracking average length of stay alongside ADR Pickup, gives a far more accurate read than treating it like a transient hotel with a longer average stay bolted on.

Seasonal resort and destination properties see the most compressed booking windows of any category, with a meaningful share of peak-season demand arriving inside the final two to three weeks, driven by weather forecasts, flight pricing, and last-minute leisure decisions rather than advance planning. A resort revenue manager who applies the lead-time thresholds built for a corporate-heavy urban hotel will constantly see "alarming" gaps at 45 and 30 days out that are completely normal for that property's own booking curve, and will miss the narrower window, often just the final 10 to 14 days, where this property's pace actually does predict the final outcome.

Urban business hotels add one more wrinkle worth tracking separately inside the same pickup report: weekday and weekend pace frequently move in opposite directions in the same week, with corporate transient demand driving midweek pickup and leisure demand driving weekend pickup. Blending a Tuesday night and a Saturday night into one weekly pace number hides the fact that one is accelerating and the other is softening, which is a different problem from the group-versus-transient blending covered earlier but follows the identical logic: segment first, combine second.

Seasonality changes the shape of the booking curve itself, not just the segment mix, and the variance thresholds built for one season rarely transfer cleanly to another. A shoulder-season date typically has a longer, flatter curve, with a larger share of final occupancy arriving early and little drama in the final two weeks. A peak-season date in a high-demand destination often does the opposite, holding back a meaningful share of its eventual occupancy for a compressed, weather- and last-minute-driven rush inside the final ten days. Applying a shoulder-season threshold table to a peak-season date, or the reverse, is one of the more common seasonal mistakes independent operators make, and it is worth rebuilding the threshold table at least twice a year, once for the slow season and once for peak, rather than running one fixed set of numbers year round.

Short-term rental and Airbnb operators track a conceptually similar metric, usually framed around booking window and comp set and booking pace data rather than the hotel industry's pickup report terminology, and the same core lesson applies on both sides of the business: the rate of change in bookings on the books predicts the outcome far better than the occupancy level at any single point in time. AirDNA's own comp set glossary entry is a useful reference for operators moving between the two vocabularies.

Bottom line: Build pickup report thresholds from the specific property's own booking curve and segment mix, because a boutique hotel, a branded full-service property, an extended-stay hotel, and a seasonal resort each generate a differently shaped curve that the same generic variance band will misread.

Building a Pickup Report Without an RMS

You can build a usable hotel pickup report without a revenue management system using nothing more than a daily PMS export and a spreadsheet, as long as the structure stays consistent and the snapshot is pulled at the same time every day. Most independent and boutique hotels run exactly this setup for years.

A dedicated RMS only becomes worth the cost once segment and channel complexity outgrow a spreadsheet, and a disciplined manual version often outperforms an automated system that nobody is actually reading on a given morning.

The minimum viable spreadsheet has one row per stay date and one column block per snapshot date, with each block recording rooms OTB, revenue OTB, and ADR OTB, split by transient and group. The export needed to populate it is almost always available from the PMS as a "rooms on the books by arrival date" or "future bookings" report, which every major PMS platform produces in some form even without an RMS layer on top. Pulling that export at the same time each morning, before the front desk starts processing same-day arrivals, keeps every snapshot comparable to the last.

ColumnWhat It CapturesSource
Stay DateThe night being measuredFixed, does not change
Snapshot DateWhen the export was pulledToday's date, same time daily
Rooms OTB, TransientConfirmed individual reservationsPMS future bookings export, filtered by segment code
Rooms OTB, GroupConfirmed rooms tied to a group blockPMS future bookings export, filtered by block code
Revenue OTBTotal room revenue across both segmentsSum of room rate times nights, from the same export
Pickup (Rooms)This snapshot minus the prior snapshotCalculated column, not pulled directly
STLY PaceSame calculation from the day-of-week-aligned date last yearArchived export from the same lead time last year

The column that trips up most first-time builds is STLY Pace, because it requires having archived last year's export at the matching lead time, not just last year's final numbers. A hotel starting this process from zero will not have that archive yet, and the honest fix is to start saving every daily export now, build the comparison forward, and accept that the first three to six months of pickup reporting will be pickup-only, without a reliable pace comparison, until a full booking cycle of archived snapshots exists. Hotels that skip this step and instead compare against last year's final occupancy, rather than last year's pace at the same lead time, end up with exactly the misleading comparison described earlier in this guide, just from a different cause.

Formulas in the spreadsheet stay deliberately simple: Rooms Pickup is a single subtraction between two columns, ADR OTB is Revenue OTB divided by Rooms OTB, and ADR Pickup is the change in Revenue OTB divided by the change in Rooms OTB across the same two snapshots. None of this requires anything beyond basic spreadsheet functions, and resisting the urge to build something more elaborate than that is usually the right call for a property under 80 rooms, where the complexity of a full RMS implementation would cost more in setup and training time than it would save in pricing precision.

The point at which a spreadsheet stops being the right tool is usually volume and segment complexity, not room count alone. A 50-room hotel with one segment and one channel can run this process cleanly for years. A 50-room hotel with a complex mix of corporate negotiated rates, wholesale allotments, three or four OTAs, and recurring group business will often hit the practical ceiling of a manual spreadsheet well before it hits any meaningful room-count threshold, simply because the number of segment-and-channel combinations to track daily grows faster than the spreadsheet can stay manageable by hand.

Archiving matters as much as building the report in the first place, and it is the step most independent hotels drop first once the daily routine gets busy. Keeping a dated copy of every export, even just saved as a new spreadsheet tab or a new file named for the snapshot date, is what makes next year's STLY comparison possible at all. A hotel that started archiving at the beginning of 2026 can, by the same point in 2027, compare any future date's pace against the identical lead time with no extra work beyond pulling the matching archived file. A hotel that has not archived is stuck rebuilding history from whatever the PMS retains natively, which is often far less granular than a daily snapshot and sometimes does not go back far enough to be useful at all.

Bottom line: A spreadsheet built from a daily PMS export, pulled at a consistent time and archived every day, can run a fully functional pickup and pace process for most independent hotels, and the real constraint on when to upgrade to a dedicated system is segment and channel complexity, not room count alone.

Frequently Asked Questions

What is a hotel pickup report?

A hotel pickup report is a comparison of rooms and revenue on the books for a future stay date between two points in time, showing how much new business was added or lost since the last check. It is the single clearest early-warning tool a hotel has for whether a date is tracking ahead of, even with, or behind plan before the stay date actually arrives.

How often should I run a pickup report?

Run it daily for any stay date inside 21 days, where booking activity is dense enough for a single day's change to be meaningful, and weekly for stay dates beyond that, where daily movement is mostly noise. Matching the cadence to the lead time, rather than running one fixed schedule for every date, is what keeps the report useful instead of overwhelming.

What is the difference between pickup and pace?

Pickup is the raw change in rooms or revenue between two snapshots; pace is that same change compared against the equivalent snapshot from last year, at the same point in the booking curve. Pickup tells you what happened this week. Pace tells you whether what happened this week is ahead of, behind, or in line with the trend that actually predicts the outcome.

Why does my pickup report disagree with my PMS dashboard?

The most common causes are a calendar-date comparison instead of a day-of-week-aligned one, a snapshot pulled at a different time of day than the baseline, or group and transient business being blended in one system and split in the other. Before assuming either number is wrong, confirm both reports are comparing the same stay date against the same type of prior snapshot.

How far out should I compare pace to last year?

Compare at the same number of days before the stay date in both years, not the same calendar date, and read the gap differently depending on that lead time: a double-digit gap at 45 days out carries far less certainty than the same gap at 7 days out, because far more booking activity remains to close it at the longer lead time.

Is negative pickup always bad?

No. Negative pickup, meaning more cancellations than new bookings in a period, can reflect a group block releasing unsold rooms at cutoff, a seasonal cancellation wave that happens every year on a predictable date, or a channel cleanup removing duplicate reservations. Negative pickup is only a genuine warning sign when it is unexplained, persistent across several snapshots, and concentrated in transient rather than group business.

Can a pickup report predict final occupancy?

It can estimate it, not guarantee it, by combining current pace against last year's pace at the same lead time with the property's own historical booking curve for that day of week and season. The estimate gets more reliable the closer the stay date gets, which is exactly why pickup reports are read with more weight on recent snapshots than on numbers from 60 or 90 days out.

What does outsourced revenue management cost for an independent hotel?

Most outsourced revenue management engagements for independent and boutique hotels run as a monthly retainer, scaled to room count and segment complexity, with no long-term lock-in. A hotel under roughly 30 rooms with a simple transient mix can often manage pickup reporting internally; a property with group business or multiple channels usually sees the retainer pay for itself within a quarter.

Conclusion

A pickup report only earns its place in a hotel's routine when someone reads it against the right comparison, by the right segment, on a cadence matched to how far out the stay date sits, and actually changes a rate or distribution decision because of what it shows. The formula is simple; the discipline around reading it correctly, every day, for months, is where almost every independent hotel's process actually breaks down. A spreadsheet built on the structure in this guide, reviewed on a fixed schedule with written thresholds, will outperform an expensive system nobody looks at, and it will do so from week one rather than after a long setup and training cycle. If pace numbers in your own property are confusing more often than they are clarifying, talk to a revenue strategist about building a process that turns pickup data into pricing decisions instead of just another report nobody acts on.

ShareLinkedInXFacebook

Written by

Revenuenaire Expert

The Revenuenaire revenue management team: hotel and short-term rental pricing specialists writing practical, data-backed guidance on dynamic pricing, OTA optimization and revenue strategy.

Keep reading

Related articles

All insights
Put the insights to work

Ready to unlock more revenue?

Talk to a revenue manager about your property, or book a one-time pricing strategy session.