Katarina Railko has spent her career at the intersection of hotels, travel, and live events, where volatile demand and tight timelines sharpened her instinct for pricing with precision. She treats on-the-books data like a living pulse—one that connects curiosity at the top of the funnel to what actually lands in the reservation grid. Today she blends forward-looking market signals with disciplined OTB benchmarking to help commercial teams move faster, price smarter, and make every room night count.
To start, how do you define on-the-books (OTB) versus business on books (BOB) in practical terms, and which specific metrics—occupancy, ADR, RevPAR—do you track daily to make it actionable?
OTB and BOB are interchangeable in practice: both describe the confirmed room revenue and reservations already secured for future dates. I think of it as the clearest, real-time snapshot of what’s truly converting, not just who’s browsing. Daily, I review occupancy by stay date, ADR by segment and channel, and RevPAR to ensure rate and volume are moving together, not at odds. I also layer in pick-up by day, week, or month view because OTB is dynamic—cancellations and new bookings constantly reshape the picture. Finally, I align those OTB snapshots with forward-looking demand indicators to see whether we’re pacing ahead, behind, or right on trend for the dates that matter.
When using OTB as a budgeting baseline, how do you translate gaps into concrete rate moves, promotions, or inventory shifts? Can you walk through an example week showing targets, variances, and adjustments?
I start with budget targets by stay date and compare them to our current OTB to quantify the gap in rooms and revenue. Then I assess booking pace—how much pick-up we’ve had day by day—and whether rate evolution has helped or hindered momentum. If a midweek pattern underperforms while weekends hold, I avoid blanket discounting and instead adjust midweek fences, add a targeted value add, or reallocate inventory to channels that convert that segment best. Over a week, I’ll revisit each date in a day, week, or month view, check how pick-up reacts to changes within 24–48 hours, and either double down on what’s working or revert if the market doesn’t respond. Throughout, I keep the focus on maintaining ADR discipline where demand is stable, while using tactical nudges on true need nights.
Many teams compare current OTB to same dates last year. How do you separate true demand changes from calendar shifts, events, or compset strategy changes, and what safeguards keep comparisons fair?
I normalize first: align by weekday pattern, major events, and seasonal cadence so we’re not mistaking a calendar shift for a demand swing. Then I compare our OTB trend to market OTB at the city or compset level to see if the whole market is up or down. If the market is steady but we’re lagging, I dig into channel and segment mix to find the displacement—did we lose a corporate block, or did we opt out of a promotion the market embraced? My guardrails include always pairing OTB versus last year with forward-looking market insights and daily pick-up momentum, so we don’t anchor on a single benchmark. That helps us flag when compset tactics, not demand, are moving the goalposts.
Booking pace and daily pick-up can swing quickly. How do you structure a pace report that shows momentum by segment and channel, and what thresholds trigger pricing changes or stay restrictions?
My pace report starts with daily pick-up compared to a trailing average, split by segment and channel, so we see where momentum truly lives. I include lead-time curves to link how far out bookings come in for each segment, and a simple day, week, or month view to scan for acceleration or stalls. When a segment’s pick-up surges relative to its recent trend, I tighten fences or minimum length-of-stay on peak dates; when it lags, I open value adds or targeted offers on need dates. I don’t set fixed numeric thresholds in stone—I watch for meaningful deviations from normal pace and confirm with market OTB to decide whether to push rate, protect inventory, or stimulate demand. The goal is to act early, with precision, before the curve gets away from us.
How do you analyze the correlation between rate evolution and occupancy? Which graphs or metrics (e.g., elasticity, price-relative-to-compset) reveal whether you should push ADR, chase occupancy, or recalibrate value?
I overlay rate evolution with booking pace and occupancy for the same stay dates to spot where price increases slowed or accelerated pick-up. A simple rate-versus-pace graph, aligned with segment mix, shows whether a higher ADR coincided with stronger conversion or if we hit resistance. I also look at our position relative to the market OTB—if competitors hold stronger occupancy at similar or higher rates, our issue is likely value perception, not pricing power. Plotting these trends in a daily timeline helps me choose between pushing ADR, chasing occupancy, or adjusting the offer. When rate and occupancy move together in a healthy way, you can almost feel it—steady daily pick-up, minimal cancellations, and a calm reservation inbox.
When occupancy lags despite competitive pricing, how do you diagnose misaligned value perception versus weak demand? What step-by-step tests—content, packaging, fences, channel mix—help pinpoint the issue?
First, I check market OTB to confirm if the whole city is soft; if it is, it’s weak demand, and we protect rate while stimulating selectively. If the market is healthy, I test value perception: refresh content and photos, sharpen room descriptions, and clarify inclusions to ensure the offer pops. Next, I pilot packaging—small perks, clear benefits—on the channels with proven conversion, and compare daily pick-up to the previous day or week. If pace improves, value was the gap; if not, I revisit fences and channel mix, opening or tightening by stay date and length-of-stay. Throughout, I watch cancellations and pick-up momentum daily, because misaligned perception shows up as clicks with no conversion, while weak demand is quieter—fewer searches and subdued market OTB.
For need dates, what’s your playbook to stimulate pick-up without diluting ADR? Which levers—length-of-stay, targeted discounts, opaque channels, perks—work best, and how do you time them?
I start with length-of-stay tools to improve yield without shouting “discount,” like a third-night benefit or selective minimums around shoulder nights. Then I deploy targeted offers to segments that historically book those dates, using value adds or perks before I touch base rate. If the gap persists, I’ll use opaque or closed-user channels on a limited allocation, keeping parity intact elsewhere. Timing-wise, I check daily pick-up and forward-looking interest; if market OTB hints at a late surge, I hold rate and let pace build, but if signals are flat, I activate the plan earlier. The art is keeping the room feeling worth it—tangible value, smart fences, and measured visibility.
How do you fold group bookings, wash, and cancellations into your OTB view? What buffers or overbooking strategies do you use by segment, and how do you monitor displacement costs in real time?
I segment OTB by transient versus group and track wash patterns by event type so I can forecast realistic conversion. For groups, I hold thoughtful buffers on inventory and monitor daily pick-up to right-size blocks as arrival approaches; for transient, I balance overbooking on high-confidence dates where historic cancellations justify it. Displacement is managed by weighing the transient OTB forecast and market OTB—if transient demand is building, I price group space accordingly or release rooms sooner. Daily, I watch cancellations and pick-up alongside rate evolution to ensure we’re not crowding out higher-yield opportunities. It’s a continual recalibration, guided by how the OTB snapshot moves each day.
Forward-looking market insights can show strong top-of-funnel interest. How do you connect those signals to your OTB to forecast conversion, and what early indicators suggest a pricing window is opening?
I link forward-looking search and interest patterns to our OTB by stay date and lead time, watching for a lift in daily pick-up that confirms intent is turning into bookings. If market OTB starts to rise at the city level while our pace follows, I test small price increases and check for steady or improving conversion. An opening pricing window feels like this: consistent day-over-day pick-up, low cancellations, and compset rates edging up without stalling demand. I also monitor segment-specific momentum—if a channel leads the surge, I protect inventory there and refine fences to capture the most profitable mix. The key is acting while the window is forming, not after it’s obvious to everyone.
When benchmarking market OTB at the city or compset level, which comparisons matter most—pace versus rate, segment mix, channel mix—and how do you avoid chasing misleading outliers?
I prioritize pace versus rate first, because it shows whether competitors are buying occupancy with discounts or commanding it with value. Then I compare segment and channel mix to see who’s converting which demand pockets—corporate, leisure, direct, or third party. To avoid outliers, I look for patterns sustained over multiple days and validate against the broader city-level OTB. Single-day spikes can mislead; I want to see a steady pick-up momentum with rates holding or climbing. When the market’s story and our OTB align, I move; when they diverge, I probe deeper before changing course.
What’s your framework for daily versus weekly reviews of OTB, pick-up, and rate competitiveness? Who sits in the room, what dashboards do you use, and what decisions must be made on the spot?
Daily, it’s a tight stand-up with revenue, reservations, and distribution to scan OTB shifts, pick-up, cancellations, and any rate moves that need immediate action. Weekly, I bring in sales and marketing to align on broader trends, market OTB, and upcoming events and conferences. I use dashboards that visualize OTB in a day, week, or month view, overlaying rate evolution, segment mix, and city-level benchmarks so we can spot need dates and pricing windows at a glance. On the spot, we decide on rate changes, inventory allocation, fences, group block adjustments, and targeted promotions. The discipline is simple: fast daily tweaks, deeper weekly strategy, always tied back to how the OTB is moving.
How do you use AI/ML occupancy forecasts alongside historical OTB? Which inputs (seasonality, events, lead-time curves) most improve accuracy, and how do you validate or override model outputs?
I pair AI/ML forecasts with our historical OTB to get a forward-looking view that learns from past seasonality and real-time pick-up. Inputs that lift accuracy include seasonality, events, lead-time curves by segment, and current booking trends at the market level. I validate with backtesting—comparing forecasts to realized OTB—and by checking if daily pick-up and cancellations are behaving as the model expects. When they diverge, I override with human context, especially around unique events or shifts in compset strategy. The best results come when the model flags the signal and the team applies judgment.
Distribution can make or break conversion on high-demand days. How do you decide when to shift inventory across channels, change parity rules, or add fences, and which metrics confirm it worked?
I shift inventory when market OTB strengthens and our daily pick-up concentrates in channels with strong conversion, protecting direct and top-performing partners. Parity stays tight on public rates, while I use fences and closed-user groups for finely targeted value without eroding the broader perception. Success shows up as steady or rising ADR with consistent pick-up and manageable cancellations, not just a spike in volume. I also watch city-level OTB to ensure we’re not underexposed where demand is flowing. If rate holds and the inbox stays calm—few parity complaints, healthy conversion—we’ve struck the right balance.
In a resource-constrained team, how do you automate OTB ingestion, visualization, and alerting from the PMS? What are your must-have fields, and how do you ensure data hygiene and consistent definitions?
I automate a daily pull from the PMS into a dashboard that visualizes OTB by stay date and lead time, with alerts for unusual pick-up or cancellations. Must-have fields include arrival and stay dates, room type, rate code, segment, channel, lead time, ADR, status, and cancellation terms, all mapped to consistent definitions. I keep a single glossary so occupancy, ADR, and RevPAR mean the same thing across reports, and I audit mappings regularly to prevent drift. Views by day, week, or month help us move from a quick scan to deeper analysis without building multiple reports. Clean data is the quiet work that makes fast decisions possible.
What is your forecast for OTB’s role in hotel pricing and revenue management?
OTB will stay the heartbeat of pricing because it shows what’s real—confirmed bookings and revenue—while forward-looking market insights tell us what’s likely. As tools mature, more teams will benchmark against market OTB at the city level in real time, and blend AI/ML forecasts with human judgment for sharper decisions. I expect broader adoption as platforms serving tens of thousands of hotels in well over a hundred countries continue to centralize real-time data, streamline benchmarking, and surface precise opportunities. The winners will be the teams that make OTB accessible daily, align quickly across functions, and pair discipline with curiosity. Do you have any advice for our readers? Build a simple daily ritual: review OTB by stay date, scan pick-up by segment and channel, check market OTB, and make one concrete decision you can measure tomorrow—small, consistent moves beat sporadic overhauls every time.
