Profit & control
The Seven Profit Leaks I Check First in a Hospitality Business
A practical field guide to labour, purchasing, waste, menus and the daily routines that quietly decide whether a busy venue makes money.

Hospitality profit rarely disappears in one dramatic incident. It slips away in small amounts, across dozens of decisions, while the building looks busy and the team feels stretched. That is why a full restaurant or a sold-out hotel can still produce a disappointing month-end result.
When I review an operation, I do not begin with a complicated report. I begin with the routines that create the numbers. These are the seven places I check first because they are visible, fixable and usually connected.
1. Labour deployed by habit, not demand
A roster can look reasonable and still be expensive. The common problem is not simply too many hours; it is having the wrong hours in the wrong place. Teams are often scheduled around old habits or fear of being short rather than current bookings, arrivals, covers and trading data.
I compare the roster with real demand in short trading windows. Where did the queue form? When did the kitchen get hit? Which hour carried excess cover? Good labour control protects service by putting capability where it is needed, not by cutting blindly.
2. Portions and extras that were never costed
Generosity matters in hospitality, but inconsistency is not generosity. Oversized portions, automatic sides, unrecorded upgrades and different plating by different chefs create a cost that rarely appears in one obvious place. A clear specification can protect margin while still giving the guest genuine value.
3. Buying without a simple control rhythm
Ordering becomes dangerous when it relies on memory, urgency or whoever happens to be on shift. I look for approved suppliers, current prices, realistic par levels and somebody clearly accountable for receiving. A good deal is not a saving if the product is over-ordered, poorly stored or never sold.
4. Waste, comps and remakes nobody records
Most teams know waste exists, but many businesses cannot say why it happened yesterday. Spoilage, preparation waste, returned dishes, staff food, complimentary items and till errors should be recorded in a way that takes seconds. The point is not blame. It is seeing a pattern early enough to act.
5. Popular menu items that do not pay their way
Sales volume can flatter the wrong item. A dish may be popular but slow to produce, waste-heavy or priced against an old ingredient cost. Menu engineering means looking at contribution as well as popularity, then improving placement, description, price or specification without damaging the guest experience.
6. Revenue missed before the guest arrives
Telephone handling, booking confirmation, room upgrades, breakfast, late checkout and clear pre-arrival information all affect revenue. Upselling should feel like useful guidance, never pressure. The easiest sale is often the one that helps an existing guest have a better stay.
7. Managers without a daily control routine
The biggest leak is often the absence of a short management rhythm. If nobody reviews yesterday, checks today and assigns the next action, small problems become monthly surprises. A fifteen-minute control meeting can cover sales, labour, incidents, maintenance, stock concerns and the one priority each manager owns.
What I would do on Monday morning
Take the last seven days and choose two leaks, not seven. Establish the starting number, name one owner and agree what better looks like by the same time next week. Repeat the review until the routine becomes normal.
- Match labour hours to actual demand by trading period.
- Cost and specify the five highest-volume menu items.
- Record every waste, comp and remake for seven days.
- Give one manager ownership of the daily control check.
Control is not about squeezing the life out of hospitality. It creates room to pay people properly, maintain the property, invest in the guest and operate with less panic. Busy is not the goal. A controlled, respected and profitable operation is.