What does a hotel cost controller do? The daily cost sheet, counts and reporting line
A hotel cost controller protects the gap between buying and selling by checking documents and counts. Learn how to run daily cost sheets, blind monthly counts, and weekly reporting.
Contents
Key takeaways
- A cost controller checks the chain from purchase order to plate; the role does not order, receive or hold the store key.
- The daily cost sheet is a control only when it is produced the next day, with the exceptions listed beside the total.
- The monthly count tests the book only when the counter cannot see the book quantity first.
- The role usually sits in finance because the person who measures should not be the person measured; this is good practice, not law.
- A small hotel can cover the same checks with the accountant, a fixed monthly count and one unannounced spot check.
A hotel cost controller measures what the hotel buys against what it sells. The role checks receiving, requisitions and transfers, produces the daily food and beverage cost sheet, keeps recipe costs current and counts stock with the storekeeper each month. It usually reports to finance, not to the kitchen, so the person measuring is not the person measured.
The delivery arrives before service, the storekeeper signs the delivery note, the invoice goes to accounts, and the kitchen starts cooking. Nobody in that chain compares the price on the invoice with the price that was agreed, and nobody notices until the month closes. After reading this article you will know the hotel cost controller duties in a working day, how the monthly count is run so it actually tests the book, and how a 40-room hotel covers the same checks without a full-time post.
What does a hotel cost controller protect?
A cost controller protects the gap between what the hotel buys and what it sells. The role does this by comparing documents, counts and recipes, not by running the kitchen or tasting the food.
Value leaks in three places: at the door during receiving, in the store during issuing and transfers between outlets, and on the plate through portion size and selling price. Each leak leaves a paper trail, and reading that trail is what the role is paid to do.
The role is a checker, not a stock owner. It does not place orders, does not hold the storeroom key and does not approve its own corrections. It usually reports to the finance manager or financial controller, with a working line to the food and beverage manager for operational questions but never for approval. The reason is separation of duties: the person who measures should not be the person measured.
Separation of duties is good practice, not a legal requirement. A hotel may organise the role differently, but it should be able to say in one sentence who checks whom. Equally, the role does not set menu prices alone, does not discipline staff, and does not sign off the explanation for a variance it discovered. In a group, one controller can cover two or three properties on a rota, which is often how smaller hotels get the check without a full-time post. The wider structure this role sits inside is set out in the hotel organisation chart: departments, roles and who decides what.
What does a cost controller do in a day?
The day is built around receiving, issuing and the daily food and beverage cost sheet, which turns yesterday's sales and stock movements into a cost figure before the day gets away.
The morning starts with matching yesterday's deliveries against the purchase orders and delivery notes. Any difference in price, quantity or unit is queried before the invoice is approved for payment. Then the requisitions are read: what left the store, to which outlet, at what value. Transfers between kitchen, bar and banqueting are where costs quietly land in the wrong place.
The controller then builds the daily cost sheet per outlet: opening stock plus purchases minus closing stock, set against that outlet's sales for the same day. The figure is only useful with the outlet and the covers beside it. The work is on the exceptions, not the total: voids, complimentary items, staff meals, discounts, and any issue made without an approved requisition. The sheet is issued the next day; a cost sheet produced a week later is a history report, not a control. Escalation is in writing and brief: one line per exception, to the food and beverage manager, copy to finance. Long reports do not get read.
The daily round, in order
Checklist
- Delivery notes matched to purchase orders, differences noted before payment approval
- At least one delivery a week weighed or counted at the door, unannounced
- Every requisition carries the signature of someone entitled to request that value
- Transfers posted to the receiving outlet, not left in a general kitchen line
- Voids, comps and staff meals listed with a reason and an approver
- Daily cost sheet issued per outlet before an agreed hour
- Exception list sent to the F&B manager and finance the same morning
The controls behind this daily round are explained in detail in food and beverage cost control in hotels: a working guide.
Who keeps recipes and selling prices current?
The chef owns the recipe, the food and beverage manager owns the selling price, and the cost controller keeps the cost of the plate current so the other two are never deciding on stale numbers.
A standard recipe lists ingredients with quantities and a yield. The portion cost is that list priced at current purchase costs, divided by the portions the recipe actually yields. Re-pricing should happen when purchase prices move, not once a year: a change of supplier, a butcher's yield or a smaller fish changes the plate cost without anyone touching the menu.
Weighing a portion at service now and then, and comparing it with the recipe, is the most direct routine check that shows whether the recipe is being followed rather than merely written. The controller supplies the cost and the effect of a change; the price decision belongs to the food and beverage manager and the general manager. A dated record of each cost and price change should be kept, so a margin question six months later has an answer instead of an argument. The same cost data feeds menu engineering, which sorts dishes into four groups by popularity and margin, but that is a separate exercise; keeping the cost right comes first. The mechanics are covered in standard recipes and portion cost: how hotel kitchens price a plate.
What happens at the monthly count?
The storekeeper and the cost controller count together, the count is valued on the same price basis as the cost sheet, and every difference between the book and the shelf is explained item by item with the chef.
Count blind: the counter does not see the book quantity first. Otherwise the count confirms the book instead of testing it. Two people count, and at least one of them does not hold the storeroom key; both sign the sheet. High-value and fast-moving items are counted every month, slow movers go on a rota, but nothing should go uncounted for a year.
The count is valued at the same prices used in the cost sheet, or the variance reported is a price effect dressed up as a quantity problem. The variance talk with the chef is a set of questions, not an accusation: portion drift, over-issuing, waste that was never recorded, a transfer posted to the wrong outlet, a delivery signed but never received. The explanation is written down with a date. The same explanation three months running is a finding, not an explanation.
Reading a variance before you argue about it
| What the variance looks like | Usual cause | Who answers | What to check next |
|---|---|---|---|
| One item short month after month, others clean | Issuing without requisition or unrecorded staff use | Storekeeper and chef | The requisition file for that item |
| Cost up while covers are flat | Purchase price moved or portion grew | Chef and purchasing | Last three invoices, then a weighed portion |
| Issues high on a dish that sells little | Recipe not followed, or small made-to-order batches | Chef | The production sheet against the recipe yield |
| Bar short on spirits, beer clean | Free pouring or unrecorded comps | Bar manager | The void and comp list for the period |
| Closing stock valued higher than usual | Delivery counted but not yet invoiced, or a price basis change | Cost controller | The receiving log against the count sheet |
The bar-specific measures behind the last two rows are set out in beverage cost control in hotel bars: measures, par stock and the monthly count.
How does the role work with purchasing and stores without doing their job?
The cost controller checks the chain; it does not run it. Purchasing negotiates and orders, stores receive and hold, and the controller compares the documents that should agree.
The core tool is the three-way match: purchase order, delivery note, invoice. Any difference in price, quantity or unit is queried before payment, in writing. Approval limits should follow the same logic: whoever can commit the hotel to a purchase should not be the person who receives it or the person who pays for it.
The controller may sit in on supplier price comparisons and should say what a change does to plate costs, but should not choose the supplier. The storekeeper keeps the key; the controller keeps the count sheet and the valuation. Splitting those two is the whole point. In a small hotel one person may hold two of these jobs; write down which two, and have someone outside that loop check the result. The controller should never post a correction to its own variance without a second signature.
When does a hotel need a cost controller, and how does a small hotel cover it?
A hotel needs the post when food and beverage is large enough that one month of unnoticed leakage costs more than the salary, and a small hotel can cover the same checks with the accountant, a fixed monthly count and spot checks.
The signals that the checks have outgrown an informal arrangement are concrete: several outlets, banqueting, a bar with spirits, a buffet with high waste, purchases spread across many suppliers, a store that issues without requisitions. A single-outlet hotel can carry the role part time; the checks stay the same, only the frequency drops.
For example, for a 40-room hotel a workable split might be: the accountant or bookkeeper counts with the storekeeper once a month, the chef signs requisitions, the owner or general manager approves purchases above a set amount, and one spot check a month is unannounced. The common mistake is giving the work to the storekeeper or the chef because they know the stock; that removes the check and keeps the paperwork. Write the routine as a calendar: what happens daily, weekly and monthly, and who signs each step. A routine that lives in one person's head leaves with that person. This is about the method, not the job market: no salary figures and no career advice belong in the decision.
NoteThe smallest version that still works
One named person outside the store counts once a month; one unannounced spot check on a high-value item each month; one page to the owner each month with the count variance and its written explanation. If the same person holds the key, orders and counts, the hotel has a storeroom, not a control.
What should the general manager see each week?
One page: a small number of figures and a short list of exceptions, enough for the general manager to ask two or three questions and stop.
The page carries the cost sheet trend by outlet, with covers beside it, so a rise can be read against volume rather than in isolation. Voids, comps and discounts appear by outlet and by reason, with the name of the approver. Purchases made above the agreed price list are listed, along with any supplier whose price moved without notice. Requisitions issued without the right approval, and issues with no matching sale, are flagged. The last count variance appears with its written explanation and the date it was given.
What the general manager should not do is redo the controller's work or ask only for the total. The total hides the exception, and the exception is the job.
Key pointThe weekly one page
(1) Cost sheet by outlet against covers; (2) voids, comps and discounts with reasons and approvers; (3) purchases above the agreed price list; (4) requisitions without approval; (5) last count variance and its dated explanation. Five lines, one page, every week, same shape.
What to do next
Write the routine down as a calendar: what is checked daily, weekly and monthly, and who signs each step. Once the calendar exists, the role has a shape whether it is filled by a full-time controller, a part-time one across two hotels, or the accountant in a 40-room property. The method behind each check is set out in the food and beverage cost control guide, and the person fits into the wider structure described in the organisation chart article.
Frequently asked questions
Is a cost controller the same as a purchasing manager?
No. Purchasing negotiates with suppliers and places orders; the cost controller checks that what was ordered, what arrived and what was invoiced agree. Combining the two in one person removes the check, because the same person would be setting the price and confirming it was met. In a small hotel the two jobs may sit with one person, but then someone outside that loop should review the result.
How often should a hotel count its stock?
A full count once a month, done by two people, one of whom does not hold the storeroom key. High-value and fast-moving items, especially spirits, are worth counting more often, and slow movers can go on a rota as long as nothing goes uncounted for a year. The count is only a control if it is blind and valued on the same price basis as the cost sheet.
What is the difference between a cost controller and a financial controller?
The financial controller owns the ledgers, the accounts and the overall profit and loss. The cost controller owns the bridge between the physical side of the business and the numbers: what was received, what was issued, what was counted, and what the recipe says a plate should cost. In a small hotel one person may hold both, but the counting should still be done by someone else.
Does a cost controller have to be in the kitchen every day?
No, but presence matters at the points where value moves. Receiving should be checked in person now and then, unannounced, and portions should be weighed at service occasionally. The rest of the work is documents and figures. A controller who never leaves the office sees the paperwork version of the kitchen, not the kitchen.