Skip to content
Pricing

Restaurant Average Check Calculator

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.

Restaurant average check formulas

Formula
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

What it means

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).

Good to know

  • Revenue and counts come from the same period.
  • Guest mode classifies with per-guest bands; transaction mode uses per-ticket bands.
  • Tax is remitted; service charge is kept by the house.

Ideal range

  • Not a substitute for Menu Engineering when you need Star/Plow Horse/Puzzle/Dog mix.
  • Not food-cost menu pricing. Use Menu Price to set list from a target food cost percentage.
  • Not markup from cost. Use Markup to build or audit price from item cost.

Variables

Total RevenuePeriod revenue
Net sales for the analysis period.
Number of GuestsGuest count
Covers or guests in the same period.
Number of TransactionsTransaction count
Closed checks or party tickets in the same period.
Average CheckWorking average check
Revenue per guest or per transaction for the active mode.
Projected GuestsProjected guest count
Expected covers for the forecast period.
Target Average CheckTarget spend
Desired per-guest or per-ticket average.
Revenue GapRevenue gap
Target revenue minus projected revenue at the current average.

Assumptions

  • Benchmarks assume full-service casual to polished casual concepts.

Limitations

  • Not full-stack profit margin. Use Profit Margin when several expense lines drive the decision.
  • Not break-even volume. Use Break-even when fixed cost coverage is the question.
  • Does not model channel mix, delivery commissions, or party-size forecasts beyond the counts you enter.

Worked examples

Real numbers through the same formula this tool uses.

  1. 1
    Restaurant scenarioExample 1

    Strong guest check from weekly sales

    A dining room took $12,000 with 300 guests. Average check is $40 per guest (Excellent).

  2. 2
    Restaurant scenarioExample 2

    Healthy party ticket average

    $9,100 across 130 checks is $70 per transaction (Good on the ticket band).

  3. 3
    Restaurant scenarioExample 3

    Revenue gap to a target check

    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.

How to use the restaurant average check calculator

Pull one clean period, pick guest or transaction units, then project to a target if you need a dollar gap.

  1. Choose guests, transactions, or projected revenue

    Use guests for spend per person, transactions for party tickets, or projected when you already know the average and want a forecast.

  2. Enter revenue and matching counts

    Add total revenue with guest count and/or transaction count from the same POS date range.

  3. Add projected guests and a target check (optional)

    Enter expected covers and the average spend you want. The tool shows projected revenue, target revenue, and the gap.

  4. Add tax or service charge if you need guest-facing totals

    Optional percents apply on the average check so you can talk about the ticket guests actually see.

  5. Read the benchmark and act on the recommendations

    Use the status band to decide whether you need selling habits, promo discipline, or pricing work on underpriced dishes.

How to read average check results

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.

  • Guest check and party ticket answer different questions

    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.

  • Projected revenue and revenue gap show the dollar cost of a soft check

    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.

  • Item mix belongs on Menu Engineering

    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.

  • Cost and volume tools stay on their own pages

    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.

Best practices for average check

Check average moves when the floor sells with intent and the menu makes high-margin adds easy to choose.

  • Match revenue to the same guest count period

    Don't divide last week's sales by this week's covers. Pull both from the same POS date range.

  • Split lunch and dinner when they behave differently

    A blended $26 check can hide a $18 lunch and a $34 dinner. Set targets by daypart when the gap is wide.

  • Coach one attach habit at a time

    Pick a shareable, a dessert, or a beverage and track it for two weeks. Stacking five upsell scripts usually trains nothing.

  • Set a target check before you add labor

    If covers are fine and the check is soft, more hours won't fix the dollar gap. Close the check first.

Common average check mistakes

Most soft-check problems start with mixed definitions or promo habits that quietly reset guest expectations.

  • Mixing guests and transactions in one target

    A $40 goal means different things per person versus per table. Label the target clearly and stick to one unit.

  • Ignoring promo drag on the average

    Heavy percent-off codes pull the check down even when covers look healthy. Model promo depth separately on the Discount calculator.

  • Leaving comps inside net sales without noting them

    If staff meals and voided tickets sit in the revenue figure, the average check will look softer than cash sales alone.

  • Raising every list price before fixing attach

    Across-the-board increases without selling habits often shrink party size. Lift the check with adds, then reprice the underpriced dishes.

People also ask

Short answers managers search when covers look fine but sales feel light.

  • What is average check in a restaurant?

    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.

  • Is average check the same as covers?

    No. Covers count people. Average check measures dollars per person or per ticket. You need both to understand sales.

  • How do I raise average check without scaring guests?

    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.

  • Should I track per guest or per transaction?

    Track both. Per guest compares concepts fairly. Per transaction helps when party size shifts. Set one primary target so the floor isn't confused.

  • When should I use menu engineering instead of average check?

    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.

Related tools and next steps

Average check sits beside pricing and mix tools. Use the right page for the next decision.

  • Restaurant Menu Engineering Calculator

    Classify items by popularity and contribution when you need to know which dishes built the check.

  • Restaurant Discount Calculator

    Measure promo depth when soft checks follow heavy percent-off offers.

  • Restaurant Break-even Calculator

    Find the volume you need when fixed cost, not guest spend, is the constraint.

  • Menu Price Calculator

    Set list from a food cost target when a dish is underpriced relative to plate cost.

Frequently asked questions

You may also need

Complementary calculators that often pair with this workflow.

Continue exploring

More tools to browse after you finish this calculation.