Cover

What a cover actually means

A cover is one paying customer. Not one check, not one table, not one seat. If a table of four orders, that is four covers. If one person at the bar orders two drinks and pays on one tab, that is one cover. The word comes from the old hospitality use where each guest had a “cover” setting at the table: plate, napkin, silverware.

Covers are the unit restaurants and bars use to measure how many humans they served in a night.

How it is used on the floor

Hosts and servers count covers as they seat guests and enter orders. The POS tracks covers per check, per server, per hour, and per day. Managers use that data for staffing, forecasting, and revenue planning.

A manager asks “how many covers last night?” and the answer is the single most important number for the shift after total revenue. Covers divided into revenue gives you average check, which is the fastest way to measure how well the menu is selling.

The math that matters

Average Check = Revenue / Covers Covers Per Server Hour = Total Covers / Total Server Hours

Example: Saturday night pulled 180 covers and $6,400 in revenue. Average check is $35.56. If four servers worked a 6-hour shift, that is 24 server hours and 7.5 covers per server hour. Those two numbers tell you whether the shift was tight or loose.

Covers vs guests vs checks

“Cover” and “guest” are used interchangeably in most of the industry. “Check” is the bill, and one check can cover multiple guests. A table of four on one check is four covers, one check, and one table.

Some POS systems default to counting checks instead of covers if the server does not enter a guest count. That is a common source of skewed data. Always verify your POS is tracking covers, not checks, for the reports.

Why it matters for forecasting

Cover counts drive every prediction the bar makes. How many burgers to prep, how many servers to schedule, how many kegs to tap, how many reservations to accept. Historical cover data for the same day last year is the foundation of every forecast.

A typical bar tracks covers in 30-minute or hourly buckets. That granularity lets you staff up before the rush instead of reacting to it.

Common mistakes

Counting checks instead of covers. Forgetting to enter guest counts on bar tabs. Not tracking covers by server for productivity analysis. Using average check without looking at cover count (a high average check on low covers is worse than the other way around).

How PourIQ handles it

PourIQ pulls cover data from your POS and ties it to beverage revenue and per-cover beverage spend. You see average beverage check per cover, so you know whether your upselling and drink pricing are working at the unit level, not just the dollar level.