For a stretch of my career I was the person who made these reports. On the overnight shift at Alohilani, I ran the audit, tied out the numbers, and left the package for whoever opened in the morning. Now I am usually the one reading it, coffee in hand, before the first arrival walks in. Being on both sides taught me something simple. The night audit report is not paperwork the auditor generates to prove they did their job. It is a briefing, and a manager who reads it well walks onto the floor already knowing how the day is going to go.

The trouble is that the report can look like an intimidating wall of figures if no one has shown you where to look. Most new supervisors flip past it and wait for problems to find them at the desk. That is backward. Everything you need to run the morning well is sitting in that package before the lobby fills, if you know the order to read it in and what each number is actually telling you. This is the guided tour I give my own team.

What the report is, and where it comes from

The night audit report is the output of the daily close. Sometime in the small hours, the auditor posts room and tax, balances the day's charges and payments, and rolls the business date forward. The package that lands on the manager's desk is the snapshot of the property at that moment of rollover. If you want the mechanics of how that close actually happens, I walk through the whole overnight process in how night audit actually works. Here I want to focus on the other side of it, which is reading the thing after it is done.

The key mindset is that the report describes a frozen moment. It is true as of the rollover, not as of right now. Guests have checked out since, walkins may have arrived, housekeeping has been working the floors. So you read the report to understand the shape of the day, then you cross-check it against what is live in the PMS before you act on anything time-sensitive. Treat it as your starting map, not your live position.

The night audit report is not a record of last night. It is the briefing for this morning, if you know how to read it.

What is actually in the package?

Before the order matters, it helps to know the pieces, because a night audit package is not one report but a stack, and PMS systems name them differently. Whether you are reading it out of Opera or Lightspeed, most packages contain the same working parts, and knowing what each is for keeps you from drowning in pages you do not need this morning.

ReportWhat it tells youWatch for
Manager's flash or daily revenue summaryThe one-page headline: occupancy, room revenue, ADR, and the day's totals.Leadership reads this first, so you should too.
Occupancy and house countRooms sold, arrivals due, departures expected.The frame that sets the pressure for the whole day.
Room revenue and ADRWhat the rooms brought in and what the average sold room went for.A full house at a soft rate is not the win it looks like.
Room status discrepancy reportEvery place the PMS and the physical room disagree.Each one is a potential bad checkin if left unsettled.
High-balance or credit-limit reportFolios climbing toward or past the authorized amount on the card.The accounts that quietly become a write-off if no one acts.
In-house, arrivals, and departures listsWho is here, who is coming, who is leaving.The detail you staff and prioritize against.

You do not read all of these with equal weight every morning. You triage them, in a set order, so the pages that change your next hour get your attention and the rest are there when you need them.

Read it in the right order

The single biggest mistake is reading the report top to bottom as printed. The order that matters to a rooms manager is not the order the system spits it out. I read for the same four things every morning, in the same sequence, because each one sets up the next.

  1. House count and occupancyHow full the house is and the arrival and departure pressure on the day.
  2. Room revenue and ADRHow well the house sold, not just how full it was.
  3. Discrepancy and status reportsWhere the PMS and the physical rooms disagree.
  4. High-balance and credit reportThe folios climbing past their authorization.

First, the house count and occupancy

Start with how full the house is. The occupancy figure and the house count tell you how many rooms were sold, how many are arriving, and how many are departing today. This is the frame for everything else. A ninety percent house with a heavy arrivals list is a completely different morning from a sixty percent house winding down after a group checkout. Before I read a single revenue number, I want to know the pressure the day is under, because that decides how I staff the desk and how hard housekeeping has to push to turn rooms. If you want to go deeper on that one number, I break it down in the systems that run a modern hotel and the reports that feed it.

Second, room revenue and ADR

Once I know how full we were, I want to know how well we sold. Room revenue tells me the total the rooms brought in. Average daily rate, the ADR, tells me what the average sold room went for. Together they separate a good night from a merely busy one. A full house at a soft rate is not the win it looks like at first glance, and a slightly emptier house at a strong rate can be the better result. Reading these two side by side is how you tell whether the property made money or just made beds. It is also the number a general manager will ask you about first, so you want to have already seen it.

Third, the discrepancy and status reports

Now I go looking for trouble, and the discrepancy report is where it hides. A room status discrepancy is any place where the PMS and physical reality disagree. A room the system shows occupied that housekeeping found empty. A room shown vacant that clearly has someone in it. These are not clerical curiosities. Each one is a potential bad checkin, a skip that was never caught, or a room you might sell that is not actually available. I read this section slowly, because a discrepancy ignored at seven in the morning becomes a guest standing in the lobby with a key to an occupied room at three in the afternoon.

Fourth, the high-balance and credit report

Last, I check the money at risk. The high-balance report flags folios where the charges are climbing toward or past the authorized amount on the card. These are the accounts that can quietly become a write-off if no one acts. The morning is the time to catch them, put a fresh authorization in place, or have a quiet conversation before the balance gets away from you. Nobody enjoys this part, but a manager who skips it is choosing to find out about the problem at checkout, when it is far harder to fix.

A five minute read, in practice

Here is what that order looks like on an actual morning, so it stops being abstract. I sit down with the package and a coffee before I talk to anyone. Occupancy first: say it reads eighty-eight percent tonight with forty arrivals and thirty departures. That tells me the desk will have an overlap in the early afternoon and housekeeping has to turn thirty rooms into forty arrivals, so turns are tight and I will want the early arrivals blocked and prioritized. Revenue next: ADR held, so it was a genuinely strong night, not just a full one, and I have my answer ready when the GM asks.

Then the discrepancy report: four rooms flagged, two of them the routine lag of status not yet updated, but one showing occupied that departed yesterday, which smells like a skip or a missed checkout, and one out of order with no note. Those two get a person assigned to confirm them physically in the first hour. Last, the high-balance report: two folios over authorization, one a long stay that simply needs a fresh swipe, one a group master I want to look at before it grows. Five minutes, four sections, and I walk onto the floor with a short list of moves instead of a vague sense of dread. That is the whole point of reading in order.

What the discrepancies are really telling you

I want to linger on discrepancies, because they are the part of the report that most directly protects the guest experience. Every discrepancy is a small disagreement between systems that a human now has to settle. The auditor flags them because the machine cannot resolve them on its own.

Room status discrepancy. Any place the PMS and the physical room disagree, such as a room shown occupied that housekeeping found empty. The audit flags it so a person can settle it against reality.

It does not know whether the room is really occupied or whether housekeeping simply had not updated the status when the audit ran.

My rule for settling them is the same rule I use for any system conflict. Trust whatever is closest to physical reality. A room attendant standing in an empty room beats a status flag from six hours ago. The card the guest handed you beats a stale note in the folio. This same principle runs through every interface in the building, and I get into it more broadly in the front desk tech stack, explained. On the audit specifically, it means you do not just note the discrepancy and move on. You assign someone to physically confirm the room, then correct the record so the next person to touch it is working from the truth.

  • Occupied in the system, empty in the room. A possible skip or an early checkout the desk never processed. Confirm and correct before you resell it.
  • Vacant in the system, clearly occupied. A guest who may not be registered, or a status never updated. This one you settle fast, because it touches security and billing.
  • Out of order with no note. A room pulled from inventory without a reason attached. Chase down why before you either sell it or leave money on the table.

Why does the audit have to balance at all?

It is worth understanding why balancing matters, because it explains why you can trust the report in the first place. Every charge and every payment has to tie out before the business date rolls forward. Room and tax posted, deposits applied, the day's payments matched against the day's charges. When it all ties, the numbers on your morning report are true. When it does not, the error does not disappear. It carries forward into the next day's figures and hides inside the folios, quietly corrupting every report built on top of it.

This is why a sloppy audit is so expensive. A morning manager reading a report that did not truly balance is making decisions on numbers that lie. The occupancy might be off, the revenue might be overstated, a discrepancy might be masking a real problem. The whole value of the report as a briefing depends on the discipline of the close that produced it. When I ran audits, I treated the balance as non-negotiable for exactly this reason. Someone was going to trust those numbers to run a hotel in a few hours, and they deserved numbers that were actually true.

From reading the report to running the day

The point of all this is not to admire the numbers. It is to turn them into a plan before the day starts. By the time I have read the four sections, I know most of what I need. I know whether the desk is going to be slammed and should be staffed up. I know whether housekeeping is under real pressure to turn rooms for a heavy arrival. I know which folios I need to touch before they become a problem, and which room discrepancies I need someone to physically confirm in the first hour.

That is the difference between a manager who reacts and one who is ahead of the day. The reactive manager finds out about the sold-out arrival crunch when the line backs up, discovers the discrepancy when a guest complains, and learns about the runaway folio at checkout. The prepared manager saw all of it on the report at seven, made three quiet moves before the lobby filled, and spent the busy hours handling guests instead of chasing surprises. Nothing on the report was hidden. One manager read it and the other did not.

There is also a coaching dimension to reading the audit well, which is that the report is a record of how the prior shifts performed. A pattern of the same discrepancy showing up morning after morning usually points to a habit that needs fixing, not a one-off. Rooms consistently left in the wrong status tell me the checkout process is being rushed somewhere. High balances that keep slipping past authorization tell me the desk is not reauthorizing when it should. I read the report not just to run today, but to notice the trends that tell me what to work on with the team. A single bad number is noise. The same bad number three days running is a message, and the audit is where you hear it first.

I also make a point of reading the report before I let anyone tell me how the night went. It is easy to walk in and accept the overnight team's summary of a quiet night, but the numbers occasionally tell a different story than the person handing off does, not because anyone is hiding anything, but because a tired auditor at the end of a long shift may not have connected every dot. Reading the package myself, in order, before I form an opinion, keeps me honest and keeps my read of the property grounded in what actually balanced rather than in someone's memory of the night.

Build the habit, keep the calm

If you are new to leading a shift, make reading the audit report the first thing you do, every single day, before you talk to anyone. Do it in the same order until it is automatic. House count, revenue and ADR, discrepancies, high balances. Five focused minutes with that package will tell you more about the day ahead than an hour of walking the floor guessing.

The report can feel like a wall of figures the first few times. It stops feeling that way the moment you realize it is answering a small number of questions you already care about. How full are we, how well did we sell, what disagrees with reality, and what money is at risk. Learn to pull those four answers out fast and the night auditor's overnight work becomes exactly what it was meant to be, a clear-eyed briefing handed from the shift that closed the day to the one about to run it. Read it well and you walk onto the floor already knowing how the morning is going to go.

Questions from the desk

What is a night audit report?

It is the package of reports the night auditor produces when the property closes out the business day. It summarizes occupancy, room and other revenue, the day's balances, and any discrepancies, so the morning team starts with a clear picture of where the hotel stands.

What numbers should a manager check first?

Start with occupancy and the house count, then room revenue and ADR, then the discrepancy and high-balance reports. Those four tell you how full the house is, how well it sold, and where the risks are before the lobby fills.

What is a room status discrepancy?

It is a mismatch between what the PMS says about a room and what is physically true. A room shown occupied that housekeeping found empty, or the reverse, is a discrepancy. The report flags them so the desk can reconcile the record before it causes a bad checkin.

Why does the night audit have to balance?

Because every charge and payment has to tie out before the business date rolls forward. If the numbers do not balance, the error carries into the next day's reports and hides in the folios. Balancing is what makes the morning's numbers trustworthy.

What reports are included in a night audit package?

Typically the manager's flash or daily revenue summary, the occupancy and house count, room revenue and ADR, a room status discrepancy report, a high-balance or credit-limit report, in-house and departure lists, and the arrivals for the day. The exact set varies by PMS, but those pieces answer the questions a morning manager needs.

What is the difference between the manager's flash and the night audit?

The night audit is the whole close, the process and the full package. The manager's flash, sometimes called the daily report, is the one-page revenue and occupancy summary inside it that leadership reads first. The flash gives you the headline numbers; the rest of the package tells you the risks and the detail behind them.