What is cover count (restaurant)?

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.

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.

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.

Rules of thumb

Covers are only useful once you know what a healthy per-cover figure looks like for your concept. The ranges below are standard hospitality rules of thumb, not fixed targets — a starting point for reading your own numbers, not a scorecard, and every one of them shifts with service style, table turn and how much of your trade is groups.

Common mistakes

Cover count is cheap to capture and easy to get wrong. These five errors are why an operator can have a covers field in the POS and still be flying on transactions.

• Not capturing covers at all. Most POS systems support guest count at bill open but ship with it off, so the server has to ask. Skip it and every per-cover metric — average check per cover, labour per cover, food cost per cover — is unavailable.
• Reading demand off transactions. A 60-transaction Saturday is 140-180 covers in a full-service format. Staff to the transaction count and you under-resource the kitchen and floor by 2-3× on your busiest nights.
• Confusing per-cover and per-transaction average check. A €70 per-ticket average and a €28 per-cover average describe the same service; quoting the wrong one makes upsell discipline look far better or worse than it is.
• Trusting door-side and POS-side counts interchangeably. A host clicker counts walk-in arrivals; the POS counts guests tied to a bill. They diverge on no-shows, walk-outs and bar-only guests — pick one source per metric and stick to it.
• Never checking covers per labour hour. Without it, you cannot tell an over-staffed slow service from a well-run busy one, and the roster keeps repeating the same mismatch week after week.

How it shows up in your daily P&L

Covers are the denominator that turns your daily EBIT into per-guest economics. nouz takes gross revenue, subtracts tax and card fees to reach net revenue, then subtracts COGS, variable costs and the day's slice of fixed costs to land on same-day EBIT — and once covers are recorded for the session, that same EBIT can be read per guest, alongside average check per cover, food cost per cover and labour per cover. EBIT alone tells you the shift was profitable; EBIT per cover tells you whether each guest through the door actually paid their way, which is the number you can compare fairly across a busy Saturday and a quiet Tuesday.

That per-cover view is what makes a thin EBIT day actionable. A profit line that dipped because you served fewer guests is a demand problem; one that dipped while covers held steady is a pricing or cost problem — and only the cover count lets the daily P&L tell the two apart the same evening, in time to fix next week's roster or menu.

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.

Common questions