Cover count (restaurant): the headcount metric your transaction report is not telling you.
A cover is one guest served, not one bill paid. A table of four is one transaction and four covers — and the difference is what tells you whether last night was busy or just expensive.
Cover count is the number of individual guests served in a service period. A four-top is one transaction and four covers. The distinction matters because the costs of running a restaurant scale with people in the room (food consumed, server attention, plates washed) far more than with bills printed. Every meaningful per-guest metric — average check, food cost per cover, labour per cover — depends on counting covers, not transactions.
Definition
A cover is one guest served a meal during a service period. The term comes from the original "table setting" or "place setting" — one cover was one set of cutlery laid for one diner. In modern usage it is purely a headcount: the number of people in the dining room across the shift, counted at the door or entered at the POS at order time.
Operationally, covers are captured one of two ways. POS-side: the server enters guest count when opening the bill ("table 7, 4 covers"). Most modern POS systems support this; many operators do not enable it because they have to ask. Door-side: a host clicker or reservation system counts arrivals. Door-side is more accurate for walk-ins; POS-side is more accurate for revenue-tied calculations.
Covers vs transactions
A transaction is one closed bill. A cover is one guest. They are almost never equal in a full-service restaurant.
| Concept | Avg covers per transaction | Why |
|---|---|---|
| Coffee shop / espresso bar | 1,0-1,2 | Mostly single-cup, single-bill |
| Quick-service / fast-casual | 1,1-1,4 | Some groups split, some pay together |
| Casual full-service | 2,0-2,8 | Couples and small tables dominate |
| Full-service restaurant | 2,4-3,2 | Higher share of 4-tops, groups |
| Fine dining | 2,2-2,8 | Mostly 2-tops and 4-tops, single bills |
If you run a full-service restaurant and look only at transactions, you are systematically under-counting demand by 2-3×. A 60-transaction Saturday is 140-180 covers — and your kitchen, your front-of-house, your dishwasher, your reservation grid all scaled to 150 people, not 60. Decisions made off transactions alone over-staff slow services and under-staff fast ones.
The formulas it unlocks
Average check (per cover) = Net Revenue / Covers
Average check (per ticket) = Net Revenue / Transactions
Food cost per cover = Food COGS / Covers
Labour per cover = Total Labour Cost / Covers
Covers per labour hour = Covers / Labour Hours
The two average-check conventions matter. Per cover is what tells you how much each guest spent — it is the upsell metric, the menu-engineering metric, the "is the wine list working" metric. Per transaction is what tells you the table-level economics — useful for tip averages and bill-presentation decisions. Operators conflate the two and then wonder why their "average check" reads €52 but the food cost per guest implies €18 meals.
Worked example
Tuesday lunch service at a casual bistro.
| Metric | Value | Calculation |
|---|---|---|
| Net revenue | €1.400,00 | |
| Transactions (closed bills) | 20 | Counted at POS close |
| Covers (guests served) | 50 | Entered at bill open |
| Avg check per cover | €28,00 | €1.400 / 50 |
| Avg check per ticket | €70,00 | €1.400 / 20 |
| Food COGS | €420,00 | |
| Food cost per cover | €8,40 | €420 / 50 |
| Labour cost | €385,00 | 24 hours rostered |
| Labour per cover | €7,70 | €385 / 50 |
| Covers per labour hour | 2,08 | 50 / 24 |
The same service measured per transaction looks completely different (€70 average check, €19,25 labour per transaction, 0,83 transactions per labour hour) and gives a worse signal. Per-cover metrics expose the actual workload of the kitchen and dining room. They are the basis for staffing the equivalent service next Tuesday — see coffee shop KPI tracking for the daily-tracked KPI list and the daily prime cost routine for how covers feed into the same-day P&L.
Why it matters
Three decisions get measurably better when covers are tracked instead of transactions. Staffing: covers per labour hour is the cleanest staffing benchmark — 2,0-2,5 covers per labour hour is healthy for a casual full-service; below 1,8 is under-priced or over-staffed. Menu engineering: average check per cover tells you whether the upsell discipline (starters, sides, desserts, wine) is landing; transaction-level average check is contaminated by group size. Demand forecasting: covers by day-part are the right input for next-week's roster; transactions over-weight large-bill services and under-weight high-volume ones.
Cover count is one of the cheapest upgrades any restaurant operator can make. The POS already supports it. The hosts already see arrivals. Five seconds of input per table at open time gives you a metric that improves every staffing and pricing decision for the rest of the year. nouz stores covers per session and computes average check, labour per cover, food cost per cover as standard on every daily report.
Related concepts
- Average check — the per-cover or per-ticket revenue metric that covers anchor.
- Prime cost (restaurant) — covers go into the per-guest version of prime cost.
- Labour cost percentage — labour per cover is the per-guest cut.
- Restaurant prime cost mastery — covers as the staffing denominator.
- Coffee shop KPI tracking — daily-tracked KPI list that includes covers.
FAQ
What is the difference between a cover and a transaction in a restaurant?
A cover is one guest served. A transaction is one closed bill. A four-top is one transaction and four covers. In a full-service restaurant the ratio is typically 2,0-3,2 covers per transaction; in a coffee shop it is closer to 1,0-1,2. Decisions made off transactions alone systematically under-count demand by 2-3× in full-service formats.
How do I count covers if my POS doesn't prompt for it?
Most modern POS systems support cover count but require it to be enabled in settings. Square, Lightspeed, Toast, Tabit, Untill and Restablo all allow guest-count entry at bill open. If your POS truly does not support it, a host-side clicker at the door is the fallback — count arrivals, reset at end of service, log the total in your daily P&L tool.
Should I track average check per cover or per transaction?
Per cover for menu-engineering and upsell decisions — it tells you how much each guest spent and whether the starters, sides, desserts and wine programme are landing. Per transaction for tip-share and bill-presentation decisions. Most operators conflate the two; tracking both takes the same POS data and gives two different actionable signals.
What is a healthy covers-per-labour-hour ratio?
2,0-2,5 covers per labour hour is healthy for a casual full-service restaurant. Below 1,8 usually means under-pricing or over-staffing. Above 3,0 means service quality is at risk (servers and kitchen can not maintain attention). Coffee shops run 3,5-5,0 covers per labour hour because counter service is faster; fine dining runs 1,2-1,8 because service is more intensive.