Average Check

Average check is a restaurant's sales divided by the number of checks, so it describes what a party spent. Sales divided by covers is the per-person average, which is a different number. The two differ by roughly the average party size, and they get used interchangeably far more often than they should.

Average check is a point-of-sale number and every POS reports it. What no report says is which denominator was used, and that matters: two defensible calculations of “average check” can differ by a factor of three in one dining room.

What is the difference between average check and per-person average?

The denominator. Average check is sales divided by the number of checks, so the unit is a party. Per-person average is sales divided by covers, so the unit is a guest. Both are useful and they answer different questions.

Take a room that did $10,000 across 200 checks and 500 covers. The average check is $50 and the per-person average is $20. Neither figure is wrong, and calling the $20 an average check is, because it describes a guest rather than a party. The error scales with party size, so a room with large parties produces the widest gap.

The per-person figure travels under several names: per-person average, PPA, average cover, and average spend per head.

Why does average check drop when nothing changed?

Because the check count moved, not the money. This is the most common false alarm in restaurant reporting, and split checks cause most of it. A four-top that asks for separate checks turns one check into four at identical revenue, which cuts the reported average check by three quarters for that table. A shift in a group’s separate-check policy, or a season with more corporate diners who each need a receipt, moves the metric with no change in guest behaviour at all.

Other mechanics do the same thing. Bar tabs pull the average down, so pooling bar and dining checks lets the mix between rooms drive the result. How the system treats voids, comps, tax, and service charge also changes what the number means, and two venues in one group often configure that differently.

The practical rule is to read average check against its own history in one revenue centre, with the check count beside it. When average check falls while check count rises on flat sales, nothing happened to spending.

How do you get average check per guest?

By attaching checks to people, which the point of sale cannot do on its own. A nightly average check is a property of the menu and the service style. A per-guest average check is a property of a relationship, and it does not exist until checks are joined to guest profiles.

Once it does, the direction matters more than the level. A regular whose average check has climbed over six visits is trading up, and a candidate for the wine list or the tasting menu. One whose check is shrinking is often on the way out, and that shows in spend before it shows in absence. A restaurant CRM holds the checks and the identities in one place, so it can report average check per guest and also say what share of checks it could attribute to anyone at all.

Last updated