It is Monday morning and a revenue manager has three browser tabs open: one for the PMS export, one for last year’s spreadsheet, and one for the rate shop. She copies last night’s on-the-books numbers into a tracker, subtracts Friday’s totals, and calls the difference pickup. By the time the report reaches the GM, it is already a few hours old, and if the PMS export failed to load for one property in the portfolio, nobody notices until the weekly call.
This is the exact process Docyt was built to remove. Not the revenue manager’s judgment, and not the pricing strategy built on top of the numbers, but the manual assembly work that happens before anyone even gets to look at pace. Here is how Docyt’s AI does it.
What On-the-Books and Pickup Data Actually Mean
On-the-books (OTB) is the running total of confirmed reservations a property holds for a future date, expressed in room nights, ADR, and revenue. Pickup is the change in that total between two points in time, and pace compares current pickup to the same period last year or to budget.
A pickup report is not a forecast. It measures what has already happened, the raw pace data a forecast gets built from. The forecast itself layers historical booking curves, known events, and market judgment on top of that pickup data. Confusing the two is a common mistake, and it starts with a data problem: the pickup number itself is often less reliable than it looks.
Where Manual Pickup Tracking Breaks Down
A single-property revenue manager can usually manage a manual pickup process, even if it eats an hour every morning. The cracks show at scale, and they show in ways that quietly distort the number before anyone starts forecasting from it:
- PMS exports have to be pulled property by property, each on its own schedule, format, and login.
- Segment-level detail (corporate, OTA, group, transient) often has to be reconstructed by hand from a raw reservation list.
- The revenue figures tied to that pickup, ADR, room revenue, RevPAR, are only correct if the underlying revenue has already been reconciled against deposits and folio postings. Untracked comps, late OTA payouts, and misposted rates all distort OTB dollars before anyone opens a forecasting spreadsheet.
- Comparing pace across ten or thirty properties means normalizing ten or thirty separate spreadsheets into one view before anyone can spot which properties are falling behind.
This is the quiet failure mode behind a lot of missed forecasts. The pace analysis is done correctly. The number it started with was already off.
How Docyt's AI Automates On-the-Books Pickup Data
Docyt’s AI removes the manual assembly work underneath the pickup report, so the data feeding a hotel’s forecast is accurate and current the moment someone looks at it. It does this in four specific ways.
- Continuous Revenue Reconciliation, Not a Month-End Catch-Up
Docyt’s Precision AI reconciles revenue against PMS, POS, OTA payouts, merchant deposits, and bank feeds continuously, not at month-end. That means the OTB dollar figures behind a pickup number reflect revenue that has actually been verified, rather than revenue still sitting in an unreconciled queue.
- Automatic Segment Performance Tracking
Docyt’s segment performance tracking breaks revenue and booking activity out by guest type automatically, so a revenue manager can see whether a strong pickup week is coming from direct bookings, group blocks, or OTA channels without rebuilding a segmentation spreadsheet by hand. This is the same real-time discipline behind Docyt’s approach to hotel budgeting and forecasting, where live data replaces static, backward-looking projections.
- Portfolio-Wide Pace Comparisons in One View
For portfolios, Docyt consolidates OTB and pickup data across every property into a single view, so comparing pace at one hotel against another does not require normalizing ten separate exports first. A GM or owner can see which properties are pacing ahead of last year and which need attention, on the same day, in the same format.
- Revenue Leakage Detection Before It Reaches the Forecast
Docyt flags revenue leakage, such as untracked comps, missed postings, and rate errors, before those small discrepancies compound into a distorted OTB figure. For a closer look at how that discipline plays out across a portfolio, see our revenue leakage audit checklist. The result is a forecasting foundation that reflects what is actually happening at the property, not what a delayed or partially reconciled export suggests is happening.
From Clean Pickup Data to a Forecast You Can Trust
None of this replaces the revenue manager. Pricing decisions, event calendars, and market judgment still belong to the people who know the property and its competitive set. What changes is the starting point. Instead of building a forecast on top of a number that took an hour to assemble and might already be wrong, the forecast starts from OTB and pickup data that has been reconciled and segmented automatically, every day, across every property.
For hospitality groups managing multiple properties, this consistency matters as much for daily decision-making as it does for forecasting itself. Learn more about how our hospitality accounting platform keeps revenue data accurate across every hotel in a portfolio.
The Broader Industry Context
Pickup and pace remain foundational metrics in hotel revenue management education, with industry bodies like HSMAI continuing to define and teach them as core building blocks of a forecasting process (HSMAI Academy). At the market level, benchmarking providers have extended forward-looking booking and pickup data into competitive-set comparisons, giving operators a way to see how their pace stacks up against their local market rather than only against their own history (CoStar/STR). Both point to the same conclusion: pickup and pace are not going away as forecasting fundamentals. What is changing is how much manual effort it takes to get clean, current data in front of the people making pricing and staffing decisions.
Summary Overview:
- On-the-books (OTB) data is the running total of confirmed reservations for a future date. Pickup is the change in that total between two report dates, and it is the raw material a forecast is built from, not the forecast itself.
- Manual pickup tracking, built from PMS exports stitched together in spreadsheets, is slow, error-prone, and breaks down across a multi-property portfolio.
- Pickup data is only as reliable as the revenue data behind it. Untracked comps, rate misposts, and reconciliation lag distort OTB numbers before anyone builds a forecast on top of them.
- Docyt’s Precision AI continuously reconciles revenue against PMS, POS, OTA payouts, merchant deposits, and bank feeds, so OTB dollar figures reflect verified revenue, not an unreconciled queue.
- Docyt’s segment performance tracking and Daily Flash Revenue Report break pickup activity down by guest type automatically, without a manual segmentation rebuild.
- Docyt consolidates OTB and pickup data across every property in a portfolio into one view, and flags revenue leakage before it distorts the numbers feeding a forecast.
See How Docyt Automates Pickup Data in Action
If your Monday morning pickup report starts with pulling exports from three different systems, the problem is not your revenue management strategy. It is the data pipeline underneath it.
Schedule time with a Docyt expert to see how Docyt’s AI keeps on-the-books and pickup data accurate and current across your portfolio.
