How I Report No-Show and Walk Rates by Channel to Spot Risky Booking Sources

Let me tell you about the night that turned me into a no-show data nerd.

A hotelier I work with in Orlando called me at 9pm, furious. He had walked four guests that evening, paid for their rooms at a competitor down the road, comped breakfast, the whole apology package. Meanwhile, eleven rooms that were “booked” sat empty all night because the guests never showed. He had oversold by exactly the wrong amount, on exactly the wrong night, and it cost him real money on both ends.

His question was the right one: “Which bookings can I actually trust?”

He did not have an answer, because nobody at the property had ever split no-show and walk rates by where the booking came from. They tracked one blended no-show number for the whole hotel, which is about as useful as knowing your car gets “some” miles per gallon. So we built the report I am going to walk you through here. It is not glamorous. It is a spreadsheet. But it is one of the highest-leverage things an independent can do, and almost nobody does it.

Why a blended no-show number lies to you

Here is the trap. You look at your PMS, you see your overall no-show rate is, say, 6%, and you set your overbooking strategy around that. Feels responsible. Feels data-driven.

But that 6% is an average of channels that behave nothing alike. A guest who booked direct, gave you a credit card, got a confirmation email from your actual brand, and is excited about your specific property behaves very differently from a guest who booked through a third party on a non-refundable rate they barely remember purchasing, or a guest on a prepaid wholesale rate buried three layers deep in someone else’s package.

When you blend them, the reliable channels subsidize the flaky ones in your math, and you make overbooking decisions that are wrong for both. You overbook too aggressively on nights dominated by solid direct bookings (and walk people you should have kept), and not aggressively enough on nights stacked with flaky sources (and eat empty rooms).

This connects directly to the OTA story I bang on about constantly. OTA bookings are not just expensive at 15 to 25% commission. Some of them are also operationally riskier, and that risk is invisible until you measure it by channel. When you can show an owner that a channel is both costly and unreliable, the case for winning back more direct business gets a lot more concrete. I dug into the pure cost side over in the book-direct math post if you want the commission breakdown.

The two things I am actually measuring

Let me define terms, because people use “no-show” and “walk” loosely and it muddies the report.

• No-show: a guest with a confirmed reservation who never arrives and never cancels. The room sits empty, and depending on your policy you may or may not collect anything.
• Walk (or “walked”): a guest who does show up, but you have no room because you oversold, so you send them (and usually pay) to another property. A walk is your operational failure, not the guest’s.

These are different problems with different causes, but they are joined at the hip. No-shows are why we overbook in the first place. Walks are what happen when we overbook based on bad no-show assumptions. So I report them together, by channel, on the same sheet. You cannot fix the walk problem without understanding the no-show pattern that drove the overbooking.

I also track cancellations separately, especially late cancellations inside the penalty window, because a channel with a high late-cancel rate is a different kind of risk, more about your deposit policy than your front desk.

Pulling the raw data

You do not need fancy software for this. You need a reservation-level export, one row per reservation, with these fields:

• Reservation ID
• Arrival date
• Booking source or channel (this is the field everything hinges on)
• Rate plan or rate code
• Reservation status (honored, no-show, cancelled, walked)
• Room nights
• Net rate or revenue, if you can get it

Almost every PMS will give you arrival, status, and room nights. The field people fumble is channel, because properties tag sources inconsistently. You will see “Booking.com,” “BookingCom,” “BDC,” and “OTA-1” all meaning the same thing. Before you build anything, spend an hour standardizing your source values into clean buckets. I usually settle on something like: Direct (website), Direct (phone/walk-in), Brand/Loyalty, OTA, Wholesale/FIT, Group/Corporate, and GDS/Travel Agent. If your PMS source field is a mess, pull the channel from your channel manager instead, which tends to be cleaner.

This standardizing step is boring and it is also where most DIY attempts quietly fall apart. Garbage source tags in, garbage report out.

Building the buckets

Once you have a clean export, the math is simple counting. For each channel, over a defined window (I default to a rolling twelve months, then break it down by month), I calculate:

• No-show rate = no-show reservations divided by total arrivals expected for that channel
• Walk rate = walked guests divided by total honored arrivals for that channel
• Late-cancel rate = cancellations inside the penalty window divided by total bookings for that channel

A quick note on the walk rate denominator: walks are technically a property-level capacity event, not strictly a per-channel behavior. But I still attribute the walked guest to their booking channel, because over time it reveals which channels you end up walking most. If you consistently walk your direct guests to protect rooms for a flaky OTA allotment, that is a strategic own-goal worth seeing in black and white.

Here is what the core table looks like once it is populated. These numbers are illustrative, made up to show the shape of the thing, not real benchmarks:

The second you lay it out like this, the story jumps off the page. In this illustrative example, the direct and loyalty guests are rock solid, the OTA segment runs roughly three to four times the no-show rate of direct, and the wholesale segment is the wobbliest of all. That is a completely typical shape in my experience, even though your exact figures will differ.

A booking is not revenue until the guest sleeps in the bed. A report that treats a flaky reservation and a reliable one as equal is lying to you about how full you actually are.

Reading the report without overreacting

Now, the discipline part. A high no-show channel does not automatically mean “kill that channel.” I have watched owners get one look at the OTA row and want to torch the whole relationship, and that is the wrong lesson, and frankly not even possible to do cleanly. You are not going to fully escape the OTAs, and you should not want to, because they are genuine demand generators and a billboard for properties travelers have never heard of. The goal is a healthier mix and smarter operations, not a fantasy of firing them.

So here is how I actually use each row:

1. High no-show, high volume, decent net rate. Keep the channel, but tighten the terms. Push toward deposit or non-refundable rates on that source, and factor its real no-show rate into overbooking for nights it dominates. You overbook to the channel’s behavior, not to the house average.
2. High no-show, low volume, thin rate. This is your candidate for pruning or renegotiating. The juice may not be worth the operational squeeze.
3. Low no-show, high cost (hello, OTA). This is the one that makes the real strategic case. The guest is reliable, but you are paying 15 to 25% for the privilege. That is exactly the demand you want to learn to capture directly next time, which is the entire premise of our book-direct CRO work.
4. Low no-show, low cost (direct and loyalty). Protect these guests fiercely. When you have to walk someone, it should almost never be them. And every dollar you spend making your own site easier to find and book pays back double, because the guest is both cheaper and more reliable.

That fourth point is why I spend most of my professional life on getting independents found in search and AI answers. A direct guest is the best guest on this entire table, on both axes. If your own website is buried below the OTAs when people search your hotel by name, you are handing your most reliable potential bookings to your most expensive channel. I wrote a whole rant about that specific problem in why your hotel ranks below the OTAs for its own name, and the broader pattern in how OTAs quietly intercept your search demand.

Turning the report into decisions

A report nobody acts on is just a prettier spreadsheet. So I always pair the monthly numbers with a short decision list. After each run, I ask the property three questions:

• Overbooking: Given each channel’s real no-show rate, what is the right number of rooms to oversell on our next high-demand night? You can now build this bottom-up by channel instead of guessing off a blended average.
• Policy: Which channel’s late-cancel or no-show rate justifies tightening deposit or guarantee terms this quarter?
• Mix: Which reliable-but-expensive bookings are we getting that we should be working to convert into direct repeat business?

That third question is where measurement quietly turns into marketing strategy. When the data shows your loyalty and direct guests barely no-show, the business case for investing in being discoverable, in your Google Business Profile, in AI visibility across tools like ChatGPT, stops being abstract. You are not chasing rankings for vanity. You are chasing the cheapest, most reliable guests on your own report.

A few traps I have hit so you do not

Seasonality will fool you. A channel can look reliable in your shoulder season and fall apart during a big event week when bargain-hunters book three OTAs and show up at whichever is cheapest day-of. Always keep the rolling twelve-month view next to the monthly one.

Small samples lie. If a channel only had nine arrivals last month, one no-show is an 11% rate and means almost nothing. I gray out any cell under a sample threshold (I use 30 arrivals) so nobody makes a quarter-million-dollar overbooking call off a rounding error.

Status hygiene matters. If your front desk is sloppy about marking true no-shows versus late cancels versus walk-ins, your report inherits that sloppiness. Part of rolling this out is a quick front-desk standard on how reservations get closed out. The report is only as honest as the status field.

Do not confuse correlation with the channel’s fault. Sometimes a “bad” channel is really a bad rate plan you only sell through that channel. Slice by rate code too, and you will occasionally find the real culprit is a deeply discounted promo, not the source itself.

Why this is a competitive edge, honestly

Most independent hotels never build this. They run on a single blended no-show number and a gut feel about overbooking, and they leave money on the table at both ends, empty rooms from no-shows they did not anticipate, and walked guests from overselling they did not need to do.

When you can see reliability by channel, you make better overbooking calls, you set smarter deposit policies, and, most importantly to me, you get a clear-eyed view of which expensive channels are worth slowly weaning yourself off of in favor of direct demand you control. It reframes the whole OTA conversation from “they take a cut” to “here is exactly which guests cost more and show up less, and here is the plan to win more of the good ones back directly.” That is a much stronger position than a vague gripe about commissions.

If you want help connecting this kind of measurement to an actual plan for capturing more direct, reliable bookings, that is the work we do every day for independents. Take a look at how we approach reducing OTA dependence and winning back direct demand, or just book a call and bring your messiest reservation export. I genuinely enjoy this part. Let’s find out which of your channels you can actually trust.