Boutique hotel: the financial discipline of a chain without the team of a chain

In a twelve-room boutique hotel the restaurant is half the experience and, quite often, half the problem. The owner is the manager, the front desk clerk rings up the restaurant in the evenings and the chef buys with the hotel card. Nobody has time to be the controller, so the hotel restaurant is run from memory. The good news is that the financial discipline of a chain does not depend on the size of the team: it depends on five routines that fit in twenty minutes a day.

Discipline is not a department, it is a routine

A chain has a controller because it has sixty hotels. What that controller does every day, however, is not complicated: check that the shift close reconciles, that every room charge has a folio, that every comp has a signature, that inventory moves in the same direction as sales and that the month closes with the same criteria as the month before. Five questions, and none of them requires an accounting degree to answer.

In a boutique hotel those five questions can be answered by the owner, the front desk person or the floor manager. What cannot happen is that nobody answers them, or that they only get answered once something has already gone wrong. The difference between the chain and the boutique that loses money is not the org chart: it is that the chain asks the questions every day and the boutique asks them when the bank calls.

So this article will not ask you to hire anyone. It will ask you to define who answers each question, at what time, and with which data on screen.

The five controls that fit in twelve rooms

Each control has an owner, a moment of the day and a duration. If a control lacks any of those three things, it is not a control: it is a good intention.

Look at the time column. All the rigor of a chain, in a boutique, fits in about twenty minutes a day plus half an hour a month. What makes those minutes twenty and not two hundred is that the data already exists: every order was recorded, every charge has a folio and every comp has a reason. If the data lives in a notebook, the twenty minutes become a Saturday afternoon.

Room charge when the front desk and the restaurant are the same person

In a large hotel, room charge has a natural barrier: the server records, the front desk verifies, and they are different people. In a boutique, the same person often waits the table, welcomes the guest and closes the bill. That closeness is what the guest values, and it is also what makes the charge informal: "I know it is room 4, I will write it down later".

The control is not about distrusting the person. It is about the system doing the verification for them. When the server picks the room on screen, the point of sale looks up the folio at the front desk and shows the name of the primary guest and the departure date. If the room is empty or the guest checks out today at eleven and it is ten thirty, the system says so before the charge is recorded. That cannot be achieved with a text field where a number is typed: it takes a lookup against the folio.

With twelve rooms the volume is low, and that is why every lost charge weighs more. A breakfast that never reached the folio in a two-hundred-room hotel is a rounding error; in a twelve-room hotel it is the margin of a night.

The five-minute shift close

The shift close is the control most often skipped in a boutique, because it is almost always closed by the same person who opened it, and that person wants to go home. A close that requires counting bills, adding up tickets by hand and looking for comp slips in a shoebox does not get done every day. A close that shows on screen what is expected by payment method and only asks you to count the cash does get done.

The structure is always the same: shift sales by payment method, room charges that do not enter the drawer but do count as sales, comps and voids with a reason, and cash counted against cash expected. The guide to the shift close by revenue center (A guide to the shift close by revenue center in a hotel) walks through it step by step, and it applies the same to one revenue center as to five.

What the owner checks the next morning

• The difference between expected cash and counted cash, with the explanation from whoever closed if there was one.
• The day’s comps, with the reason written down, and whether any of them repeats with the same server.
• Voids after the order was sent to the kitchen, because that is where consumption that was served and not charged hides.
• The day’s room charges against the front desk list of occupied rooms.

An illustrative example with numbers

The figures below are invented to show the calculation. They do not describe any real hotel or the industry. They serve to see how much a small oversight weighs in a small hotel.

Six breakfasts a week that never reach the folio does not sound like much. It is one a day, one guest who came down, ate and left, and the front desk closed the bill without the charge because nobody wrote it down. In the example, that is 4,320 a month, almost 6 % of food and beverage revenue, and in a year it is 51,840. For a twelve-room hotel, that amount is a bathroom renovation or a month of payroll for the whole restaurant.

What matters in the example is not the figure, it is the shape: lost consumption is small per event and large in accumulation, and you only see it if revenue per occupied room is compared week against week. One bad month is explained by occupancy; four weeks with the same occupancy and falling revenue are explained by leakage.

Pocket-size USALI

The hospitality accounting standard, USALI, sounds like chains and audits. But its central idea fits in a twelve-room hotel: separate revenue and cost by department, and report food and beverage apart from rooms. That is all you need to know whether your hotel restaurant makes or loses money on its own, without the room rate covering for it.

The pocket version has three lines for the restaurant: net food and beverage revenue (without tax or tips, with room charges included), ingredient cost for the same period and restaurant payroll. With those three lines, every month, you have the departmental margin. The article on what USALI is and why it suits you even with twenty rooms (What USALI is and why it pays off even with twenty rooms) explains how it is built without a full-time controller.

What USALI gives you, even if you are small, is comparability. When you want to sell the hotel, refinance it or bring in a partner, the buyer will ask for the departmental statement. If you have it from today, the conversation takes an afternoon. If you do not, it takes three months of reconstruction.

What you do not need

Chain discipline also includes knowing what to leave out. In a boutique there are things chains do because of scale that would only cost you time.

• You do not need a twenty-page line-item budget. You need revenue per occupied room and ingredient cost, every week.
• You do not need a night audit with a dedicated person. You need the shift close done in the system and someone reading it the next morning.
• You do not need a daily count of the whole storeroom. You need to count ten key ingredients every Monday and compare them with sales.
• You do not need results meetings. You need five minutes with the chef and the front desk clerk every Monday, with the screen in front of you.
• You do not need a policy manual. You need comps to require a reason and voids after sending to the kitchen to require authorization.

What to do this week

1. Write on one sheet who does each of the five controls, at what time and with which screen. Tape it next to the register.
2. Turn on room charge with verified folio and ban room numbers typed by hand, even if it is the usual room 4.
3. Close tonight’s shift in the system, count the cash against what is expected and write down the difference even if it is zero.
4. Pick ten key ingredients from the restaurant and count them on Monday; compare them with the week’s sales.
5. Calculate food and beverage revenue per occupied room for the last four weeks, one by one, and look at them side by side.

Inn Restaurant is built for the hotel that has no controller: the shift close, the charge with folio and the departmental report come out of the same record the server makes, with no extra work. You can see what it looks like in a twelve-room hotel on the boutique hotel page (Boutique hotel), and the fifteen-minute demo is booked on the contact page (contact).