A guide to charging for a coffee break: per person, per event or by actual consumption

It is ten in the morning and the group in the meeting room steps out for coffee. Forty people are guaranteed, thirty-three are in line, and there is coffee, juice, pastries and fruit on the table. Someone at your hotel has to decide what that is worth, and that decision was made, or should have been made, when the event contract was signed. If it was not made well, it will be argued on departure day.

What is really being charged in a coffee break

A coffee break is not a sale of coffees. It is a service: the product, the setup, the staff who attend it, the time the table stays up and the certainty that at ten sharp it will be ready. The event organizer does not buy pastries; they buy the assurance that their course will not stop because coffee ran out. That is why the service price does not resemble the menu price at the hotel coffee shop, and should not try to.

Understanding that settles half the arguments. The three ways of charging that follow are three ways of sharing risk between the hotel and the organizer: who absorbs the difference when fewer people show up, when more show up, or when they consume more than planned. None is correct in the abstract; each one is correct for a type of event.

Model one: per person

It is the most common in hotels. The contract sets a price per person per service and a guaranteed number of attendees. The guarantee is charged even if fewer show up; if more show up, the actual number is charged. The hotel knows how much to prepare and the organizer knows how much they will pay before the event begins.

What the organizer asks for in this model is clarity on three things: the unit price, how and when the guarantee is confirmed, and what happens with the extra people. If those three things are in the contract and in the system, the coffee break is posted in a minute: service, headcount, price, master folio.

When it makes sense

When the headcount is known in advance and changes little: courses, conventions with prior registration, company meetings. And when the hotel needs to know how much to prepare without waste.

Model two: per event

The contract sets a closed price for each coffee break service, valid within an attendee range, for example up to forty-five people. Whether thirty or forty-four show up, the price is the same. If the range is exceeded, the contract states how much each additional person costs or what the next range is worth.

Here the organizer buys simplicity: a single number per service, with no headcount and no argument over guarantees. In exchange they accept paying the same if fewer come. The hotel absorbs the risk of more people within the range, which is why the package price usually sits above what the per-person model would yield at the expected headcount.

When it makes sense

When the headcount is uncertain until the last day, when the organizer prefers a fixed budget, or when the service is short and counting people costs more than the difference.

Model three: by actual consumption

What was consumed is recorded: so many coffees, so many juices, so many pastries, so many fruit portions, each at its price, plus a fixed setup and service charge if the contract provides for it. The organizer pays exactly what their people took from the table.

It is the fairest model in appearance and the hardest to run. It requires someone to count, at the moment, what left the table, and to capture it at the hotel’s revenue center as products tied to the event’s master folio. If the count is done at the end, from memory, the organizer will argue over every piece. Done well, it is the model that leaves the least waste.

When it makes sense

Small groups, long events with a permanent coffee station, or frequent clients with whom there is trust and a consumption history. It works better in the hotel coffee shop (Hotel coffee shop) than in a meeting room, because there is already a revenue center there with a register and capture.

The three models side by side

The numbers below are made up to show the calculation; they are not real rates. The event guaranteed forty people and thirty-three attended. The agreed price per person is 85. The per-event package is worth 3,000 up to forty-five people. Under actual consumption, 60 coffees at 20, 25 juices at 30, 45 pastries at 12 and a setup charge of 400 were recorded.

With these numbers, the organizer would have paid less under actual consumption and more per person, because seven attendees failed to show. Had forty-four arrived, the per-person model would have risen to 3,740, the package would have stayed at 3,000 and actual consumption would have depended on how much they took. That is the conversation worth having with the organizer before signing, not after.

How it is posted at the hotel’s revenue center

All three models share one rule: the coffee break is posted against the event’s master folio at the moment of service, from the revenue center that served it, with the time and the meeting room. In the per-person model a service is captured with headcount and unit price. In the per-event model a service is captured with a fixed price and the range as reference. Under actual consumption, products are captured as on any check, and the setup as one more line.

What changes is how the service is configured in the hotel catalog, not how it is collected. The per-person price, the per-event price and the price of each product are data from the group contract, and the system applies them. That way the group statement (Groups and banquets) carries every coffee break with its model, its quantity and its amount, and the organizer compares it against what they signed.

Last-minute changes

At nine forty the organizer says ten more people arrived. In the per-person model the quantity is updated and the amount rises on its own. In the per-event model the range is checked and the additional charge stated in the contract is applied. Under actual consumption nothing is done, because the count will reflect what they took. The only indispensable thing in all three cases is that the change be recorded with the organizer’s signature, because that is the paper that closes the argument on departure day.

• Any increase in attendees is confirmed with the organizer on the spot and recorded with the time.
• Any extension of the service, such as half an hour more of coffee, is charged per the contract and recorded as a separate line.
• Any product added outside the agreed menu is recorded as an authorized extra, never mixed into the base service.
• Any reduction in attendees after the guarantee date does not lower the amount, and that must be stated in the contract.

Mistakes that generate arguments

• Charging per person without having set the guarantee date, so the organizer adjusts the figure on the same day.
• Charging per event without a range, and discovering mid-morning that twice as many people came for the same price.
• Charging by actual consumption by counting at the end of the day from memory, with no capture at the moment.
• Posting the coffee break at the close of the event instead of at the moment of service, and losing the time and the room.
• Using the coffee shop menu price as the reference for the service, when the service includes setup and staff the menu does not.

What to do this week

1. Review how your hotel charged the last five coffee breaks and which of the three models it used in each, even if it had no name.
2. Put the guarantee rule in writing: deadline and what happens with people above or below it.
3. Define the per-person price, the per-event price with its range and the setup price, and put them in the hotel catalog.
4. Have the next coffee break posted at the moment of service, against the master folio, with the organizer’s signature.
5. Ask the controller to check that the coffee break revenue landed in banquets and not mixed into the coffee shop.

Inn Restaurant posts every coffee break as an event service, with the charging model the contract states, against the master folio and from the revenue center that served it. If you want to see what an event statement at your hotel would look like under the three models, the 15-minute demo is booked on the contact page (contact).