What the night costs.

Lede

Everyone in hospitality knows what the night audit is. Far fewer people can say what the night actually costs, because most of the cost is not in the audit at all.

The audit, and the other audit

The formal night audit is the hotel's daily close. In the small hours the night auditor rolls the business date in the PMS, posts room and tax charges, reconciles the day's payments against the day's folios, chases the discrepancies that never quite reconcile, and prints or files the reports that let the next day start from a known position.

That work is well understood, largely unglamorous, and mostly solved. It takes as long as it takes; it happens whether or not the property is busy; and if it is done badly, someone finds out within a day.

There is a second audit running at the same time, and nobody is assigned to it. It is the audit of everything that arrived overnight and was not a financial transaction: the guest who wrote from a timezone where it is mid-afternoon, the arrival whose flight moved, the complaint that was typed in a hotel bed at two in the morning by someone who could not sleep because of a noise. That audit does not close. It accumulates, and then it is handed to whoever opens the property in the morning.

The messages that arrive anyway

Nobody has to staff a channel for it to receive traffic. Sarah Klein writes at 02:14 asking whether she can extend by a night, and whether the late checkout she was offered on arrival still applies if she does. Rami Aziz writes at 03:40 to say the air conditioning in his room is making a noise he can hear over the television.

Neither message is an emergency. Both are the kind of thing that, answered promptly, costs the hotel nothing and buys it a great deal, and that, answered at ten in the morning, costs it a small amount of goodwill and a much larger amount of somebody's time.

What happens to them tonight depends entirely on the property. In a well-run hotel the night auditor sees them, decides which ones are his to answer, writes the rest on a pad or posts them into a group chat, and goes back to the folios. In a less well-run hotel nobody sees them until the morning, and then they are seen by someone who has also just walked into a lobby with a queue in it.

What the pad cannot hold

The pad is the interesting part, because the pad is where the actual loss happens.

Rami's message contains three separable things. There is a fact: a unit in a specific room is making a noise. There is an implied task: someone from engineering has to look at it, and preferably before tonight, because he will be in the same room again tomorrow night. And there is a state: a guest is currently having a worse stay than he paid for and knows that the hotel has been told.

The pad holds the first one. It usually holds it badly — “313 AC noisy” — and it holds nothing at all of the second and third. So in the morning, someone has to read those four words and reconstruct from them a task, an owner, a deadline and a tone of reply. That reconstruction is done at speed, by a person who was not there, with no access to what the guest actually wrote.

This is the shape of almost every overnight cost in a hotel. It is not that the night shift failed to act. It is that the night shift could only record a fraction of what it saw, and the morning shift has to pay to rebuild the rest.

A draft that waits

Here is the same night in a property where the inbox is not empty of intelligence.

At 02:14 Sarah's message arrives and is read immediately — not by a person, by GEX. It is classified: this is a request about an existing reservation, with a policy question attached, from a guest who is currently in the building. Her profile is pulled up alongside it: her arrival, the late checkout she was offered, the fact that she has stayed before.

A reply is drafted. The drafting is not invention; it is retrieval. The extension question is answered against what the property's knowledge base says about extensions, and the late checkout question against what it says about late checkout, and both citations are attached to the draft so that whoever approves it can see the procedure being quoted rather than take the sentence on faith.

Then nothing happens. The draft sits, unsent.

At 03:40 Rami's message arrives and is handled differently, because it is a different kind of thing. It is classified as a maintenance issue affecting an occupied room. A task is opened on the engineering board with the room on it, the guest thread linked, and the relevant procedure attached. A short acknowledgement is drafted for Rami. That also sits, unsent.

At 07:00 the duty manager opens the inbox and finds two drafts and a task. She changes a sentence in the first draft because she knows Sarah and knows the register to use with her. She sends both. She checks that the engineering task has landed with a name and not a department. The whole exercise takes her a few minutes, and it happens before the lobby fills.

The part that has to stay human

It matters that the replies were not sent overnight.

A drafted reply and a sent reply are different objects with different risks. A draft that is wrong costs a manager a moment's editing. A sent reply that is wrong is a promise the hotel has made to a guest in writing, at three in the morning, with nobody awake to notice. There is no version of that trade that favours automation, and any system that offers to make it for you is selling something other than operations.

So the rule is worth stating plainly: the machine may read, classify, retrieve, draft, open a task and route it. Sending something to a guest remains an act performed by a person who is accountable for it. What the overnight work buys is not a hotel that answers itself. It is a morning that starts already started.

The morning that starts already started

Ask a duty manager what the first hour of a shift is for and the honest answer is: finding out what happened. Reading the pad, checking the group, asking the person who is leaving, opening the PMS to see which of last night's notes turned into anything.

That hour is the night's real invoice, and it is charged every single day. It is charged when the night was busy and when it was empty, because the manager has to establish which it was before she can do anything else.

The alternative is not more automation at three in the morning. It is that the night leaves behind objects instead of anecdotes: a triaged inbox rather than an unread one, tasks that exist with owners rather than notes that need translating, a briefing assembled from what actually changed, and drafts waiting for the judgement of the first person qualified to give it.

A good night shift is one that produces work, not homework.

Most hotels are already paying for the second thing. They simply have not seen it written down as a line, because it never appears as one.