Strong guest check from weekly sales
A dining room took $12,000 with 300 guests. Average check is $40 per guest (Excellent).
Calculate restaurant average check from revenue and guests or transactions. Project revenue to a target check, see the revenue gap, optional tax and service charge, and spend benchmarks.
Mode guests: Average Check = Total Revenue ÷ Number of Guests Average Revenue Per Guest = Average Check Average Revenue Per Transaction = Total Revenue ÷ Transactions (optional) Mode transactions: Average Check = Total Revenue ÷ Number of Transactions Average Revenue Per Transaction = Average Check Average Revenue Per Guest = Total Revenue ÷ Guests (optional) Mode projected: Current Average = Revenue ÷ Guests, or Revenue ÷ Transactions Projected Revenue = Current Average × Projected Guests (or Target Average Check × Projected Guests when no current average) Target Revenue = Target Average Check × Projected Guests Revenue Gap = Target Revenue − (Current Average × Projected Guests) Average Check Increase Needed = Target − Current Optional on average check: Tax Amount = Average Check × (Tax % ÷ 100) Service Charge = Average Check × (Service % ÷ 100) Benchmarks (full-service casual to polished casual): Guests: Excellent ≥38, Good ≥30, Average ≥22, Low ≥15, Critical <15 Transactions: Excellent ≥80, Good ≥65, Average ≥48, Low ≥33, Critical <33
Average check is period sales divided by the unit you care about. Guests measure spend per person. Transactions measure spend per party ticket. Projected mode multiplies that average by expected covers so you can see the dollar gap to a target before you rewrite the schedule. Tax and service charge sit on the average check so guest-facing totals stay clear. Guest benchmarks suit full-service casual rooms. Transaction bands assume a typical party near 2.2 guests. This page does not classify menu items (use Menu Engineering), set list from food cost (use Menu Price), build markup from cost (use Markup), stack full profit margin (use Profit Margin), or solve break-even volume (use Break-even).
Real numbers through the same formula this tool uses.
A dining room took $12,000 with 300 guests. Average check is $40 per guest (Excellent).
$9,100 across 130 checks is $70 per transaction (Good on the ticket band).
Current average is $28 on $8,400 / 300 guests. At 400 projected guests and a $32 target, projected revenue is $11,200, target is $12,800, and the gap is $1,600.
Pull one clean period, pick guest or transaction units, then project to a target if you need a dollar gap.
Use guests for spend per person, transactions for party tickets, or projected when you already know the average and want a forecast.
Add total revenue with guest count and/or transaction count from the same POS date range.
Enter expected covers and the average spend you want. The tool shows projected revenue, target revenue, and the gap.
Optional percents apply on the average check so you can talk about the ticket guests actually see.
Use the status band to decide whether you need selling habits, promo discipline, or pricing work on underpriced dishes.
This tool measures how much guests spend, not which dishes win the matrix or what list price food cost would justify. Use it when traffic looks fine but dollars feel light.
Revenue divided by guests is spend per person. Revenue divided by transactions is spend per table or check. A $50 party ticket with 2.5 guests is a $20 guest check. Don't mix the two when you set targets.
If you want $32 per guest and you're at $28, four dollars times projected covers is the money you're leaving on the table before you change a single schedule hour.
Average check tells you the size of the ticket. Menu Engineering tells you which Stars and Dogs built it. Run both when covers are steady but contribution is soft.
Menu Price sets list from a food cost target. Markup builds price from cost. Profit Margin stacks expenses. Break-even finds volume to cover fixed cost. This page stays on spend per guest or per check.
Check average moves when the floor sells with intent and the menu makes high-margin adds easy to choose.
Don't divide last week's sales by this week's covers. Pull both from the same POS date range.
A blended $26 check can hide a $18 lunch and a $34 dinner. Set targets by daypart when the gap is wide.
Pick a shareable, a dessert, or a beverage and track it for two weeks. Stacking five upsell scripts usually trains nothing.
If covers are fine and the check is soft, more hours won't fix the dollar gap. Close the check first.
Most soft-check problems start with mixed definitions or promo habits that quietly reset guest expectations.
A $40 goal means different things per person versus per table. Label the target clearly and stick to one unit.
Heavy percent-off codes pull the check down even when covers look healthy. Model promo depth separately on the Discount calculator.
If staff meals and voided tickets sit in the revenue figure, the average check will look softer than cash sales alone.
Across-the-board increases without selling habits often shrink party size. Lift the check with adds, then reprice the underpriced dishes.
Short answers managers search when covers look fine but sales feel light.
Average check is period revenue divided by guests (per person) or by transactions (per party ticket). It shows how much guests spend, not how many walked in.
No. Covers count people. Average check measures dollars per person or per ticket. You need both to understand sales.
Start with guided selling and menu placement on high-margin adds. Use Menu Price and Markup only on underpriced dishes, not as a blanket hike.
Track both. Per guest compares concepts fairly. Per transaction helps when party size shifts. Set one primary target so the floor isn't confused.
Use Menu Engineering when you need to classify Stars, Plow Horses, Puzzles, and Dogs. Use Average Check when you need the size of the ticket and a revenue gap to a target.
Average check sits beside pricing and mix tools. Use the right page for the next decision.
Classify items by popularity and contribution when you need to know which dishes built the check.
Measure promo depth when soft checks follow heavy percent-off offers.
Find the volume you need when fixed cost, not guest spend, is the constraint.
Set list from a food cost target when a dish is underpriced relative to plate cost.
Complementary calculators that often pair with this workflow.
Classify menu items into Stars, Plow Horses, Puzzles, and Dogs from selling price, plate food cost, and units sold. See menu mix %, contribution margin, profit rank, quadrant actions, and overall menu benchmark.
Calculate restaurant sales mix from units sold and selling price per item or category. See mix %, revenue share, contribution and profit rankings, top and lowest performers, and a concentration benchmark.
Set menu price from plate cost using food cost % or markup %. See recommended selling price, gross profit, optional tax/service/discount, and revenue summary.
More tools to browse after you finish this calculation.
Work out what share of your food sales is spent on ingredients. Enter total food cost and food sales to get your food cost percentage instantly, with the formula shown.
Calculate restaurant labor cost percentage from total labor and sales. Optionally include payroll taxes and benefits for a loaded labor figure.
Compare expected versus actual restaurant inventory to calculate shrinkage quantity, shrinkage value, shrinkage percentage, inventory accuracy, and adjusted loss after recovery — with optional cause breakdown for waste, spoilage, damage, and theft.