Guest Experience and Hospitality

Speed of Service Standards for Full-Service Dining

Starting targets for greeting, drinks, starters and mains in full-service dining, how to measure ticket times with POS and KDS data, and where time leaks.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing6 min read

On this page
  1. Why full-service restaurants need written speed standards
  2. Pace is not the same as rush
  3. Starting targets for each step
  4. How to measure ticket and table times
  5. Where the minutes actually go
  6. Course timing that feels right
  7. Staffing and speed
  8. Example: finding the slow step
  9. Coaching individual servers on pace
  10. A weekly speed review
  11. Frequently asked questions
  12. References
Guest Experience and Hospitality: Speed of Service Standards for Full-Service DiningArticle coverGUEST EXPERIENCE AND HOSPITALITYSpeed of ServiceStandards forFull-Service DiningAva for RestaurantsInsightsGuest Experience and Hospitality: Speed of Service Standards for Full-Service DiningArticle coverGUEST EXPERIENCE AND HOSPITALITYSpeed of ServiceStandards forFull-Service DiningAva for Restaurants

Key takeaways

  • Write targets for each step of the meal, from greeting to check, and measure them from timestamps rather than impressions.
  • Ticket time is only part of the story; most lost minutes happen before the order is fired and after the food is ready.
  • Review times by daypart and station weekly, and fix the slowest step first.
  • Speed matters to guests across channels: 94 percent of consumers say speed is critical when ordering off-premises[1], and dine-in guests notice slow steps just as much.

Why full-service restaurants need written speed standards

Full-service dining is not meant to be fast in the way a drive-thru is. Guests expect to relax. But they also expect each step to happen when they are ready for it: a greeting soon after sitting, drinks before they get restless, mains that arrive while the starter conversation is still going, and a check that comes when they ask. When one of those steps drags, the whole meal feels slow.

Operators know the dining room is worth protecting: 90 percent of fine dining and 87 percent of casual dining operators say growing on-premises business is important to their success[2]. Written standards turn 'good pace' from a feeling into something a manager can check, coach and improve.

Speed expectations are shaped outside the dining room too. The same guests order takeout and delivery, where 94 percent of consumers say speed is critical[1]. They bring that sense of time to the table. A guest used to an order-ready text in 15 minutes notices when nobody takes their drink order for ten.

Consumers who say speed is critical when ordering off-premisesNational Restaurant Association, 2025
Consumers who say speed is critical when ordering off-premisesDonut chart. Say speed is critical: 94%.Say speed is critical: 94%94%
  • Say speed is critical 94%

Source: National Restaurant Association, 2025[1]

Show the data
ItemValue
Say speed is critical94%

Pace is not the same as rush

Standards are not about turning tables faster at the guest's expense. A guest who wants to linger over coffee should be able to. The goal is that no guest waits for something they are ready for: the menu, the order, the food, the check. Train servers to tell the difference between a table that is enjoying a slow pace and one that is waiting.

  • Signs a table is waiting: menus closed and stacked, guests looking around the room, empty glasses, cutlery placed together on a finished plate, coats being gathered.
  • Signs a table is lingering by choice: deep conversation, a fresh round of drinks, no attempt to catch anyone's eye.
  • When in doubt, ask about pace once, early, and note the answer for the rest of the meal.

Starting targets for each step

These are starting points for a casual or upscale-casual dining room, not industry rules. Adjust them to your concept and menu, then hold the team to your own numbers.

Starting speed-of-service targets for a full-service dining room.
StepStarting targetMeasured fromHow to measure
GreetingWithin 1 minuteGuest seatedHost seat time to server's first POS action, or spot checks
Drinks on the table4 to 6 minutes; beer and soft drinks fasterDrink order enteredBar ticket time on KDS or printer timestamp
Starter order takenWithin 8 to 10 minutes of seatingGuest seatedOrder fire time in POS
Starters arrive10 to 12 minutesStarter firedKDS bump time
Mains firedWhen starters are nearly finishedServer or expo judgmentCourse fire timestamps
Mains arrive12 to 18 minutes after fire, depending on menuMains firedKDS bump time by station
Check-backWithin 2 minutes of mains landingPlates deliveredSpot checks by manager
Check presentedWithin 3 to 5 minutes of request or dessert plates clearedRequest or clearSpot checks; check print time
Payment processedWithin 3 minutesCard or cash receivedPayment timestamp

Set your targets by daypart. A business lunch may need mains within 12 minutes of ordering; a Saturday tasting menu runs on a different clock entirely.

How to measure ticket and table times

  1. Turn on the timestamps you already have

    Most POS and kitchen display systems record when an order is entered, fired, started and bumped. Check that servers fire courses in the system rather than calling them verbally, or the data will be wrong.

  2. Pull a baseline

    Export two weeks of ticket times by station and daypart. Look at the median and the slowest tenth of tickets, not just the average.

  3. Fill the gaps with spot checks

    Greeting, check-back and check presentation are rarely timestamped. A manager times ten tables per shift with a phone stopwatch and notes the result.

  4. Measure table time end to end

    Seat time from the host stand to check closed in the POS gives total table time by party size and daypart.

  5. Share the numbers

    Post the week's times by station at pre-shift. Teams improve what they can see.

Where the minutes actually go

When owners think about slow service, they think about the kitchen. But timestamps often show that ticket times are reasonable and the delays sit elsewhere.

  • Before the order: guests waiting for a greeting, for drinks or for the server to return to take the order. Each delay pushes the whole meal back.
  • Holding orders: servers taking orders but not entering them until they have several tables, so tickets reach the kitchen in waves.
  • The pass: food ready under the heat lamp waiting for a runner. If expo bump times are fine but table delivery is slow, you need more runners or a better handoff.
  • Course firing: mains fired too late after starters are cleared, leaving a long gap, or too early, so mains land on top of starters.
  • The end of the meal: guests waiting for the check, then for the card to come back. This is the most common complaint in survey comments and the easiest to fix.

Course timing that feels right

  1. Fire mains when starters are about two-thirds finished, not when they are cleared. Expo can adjust by table.
  2. Hold mains for a table where a guest has stepped away, and tell the kitchen.
  3. Deliver all mains for a table together. If one dish will be late, tell the table before the others arrive and offer to hold them.
  4. Ask the table about pace at the starter check-back: some want to linger, some have a show to catch.
  5. For large parties, fire in stages and agree the pace with the organizer when booking.

Staffing and speed

Speed problems are often staffing problems. Employees in food services and drinking places averaged 25.1 hours a week in September 2026[3], so most floors are built from part-time shifts that change daily. Waiters and waitresses numbered about 2,270,910 in May 2025[4], and the quality of a shift depends heavily on who is scheduled together.

  • Schedule to forecast covers by hour, not by day.
  • Assign a dedicated runner or expo on busy shifts so servers stay on the floor.
  • Cap section sizes on peak nights for newer servers.
  • Pair new servers with experienced ones during the first weeks.

Example: finding the slow step

Example (fictional): an Italian restaurant's guest surveys keep mentioning 'slow service' on Fridays. The kitchen display shows main-course ticket times of about 15 minutes, which is on target. The manager starts spot-checking other steps and finds two problems: drink orders take around 9 minutes on Friday because one bartender covers the bar and the service well, and checks take around 8 minutes to arrive after guests ask.

The fix is a second bartender from 6 to 9 p.m. on Fridays and a rule that checks are printed as soon as dessert plates are cleared or the guest asks. Four weeks later, drinks land in about 5 minutes and checks in about 3. Total table time on Fridays falls slightly, survey mentions of slow service drop, and the kitchen, which was never the problem, is left alone.

Coaching individual servers on pace

Station and daypart averages hide individual patterns. Once a month, look at each server's greet times, order entry patterns and check times from spot checks and POS data, and coach on the one step where they lose most time.

  • A server who enters orders in batches needs a habit of firing each table's order before taking the next.
  • A server with slow drinks may need the bar to prioritize simple drinks, or to learn to carry beer and soft drinks themselves.
  • A server with slow checks may be avoiding the end of the meal on busy nights; handhelds or a rule to print the check when dessert plates are cleared help.
  • Share good examples as well as problems, and pair slower servers with the fastest for a shift.

A weekly speed review

  1. Median and slowest-tenth ticket times by station and daypart, against target.
  2. Spot-check results for greeting, drinks, check-back and check presentation.
  3. Total table time by party size.
  4. Guest survey and review comments that mention speed or pace.
  5. One step to fix this week, with an owner.

Speed and attention go together. A check-back at the right moment catches problems early; see check-backs and manager table visits. The end of the meal is often the slowest step, which is why many restaurants are rethinking how guests pay; see pay-at-table options compared.

Frequently asked questions

What is a good ticket time for a full-service restaurant?

It depends on the menu, but many casual dining rooms aim for starters in about 10 to 12 minutes and mains in about 12 to 18 minutes after firing. Set your own targets by daypart and measure against them.

How do you measure speed of service in a restaurant?

Use POS and kitchen display timestamps for order, fire and bump times, and spot-check steps that are not timestamped, such as greeting, check-back and check presentation, with a stopwatch.

Why does service feel slow even when ticket times are fine?

Delays often sit outside the kitchen: slow greetings and drinks, servers holding orders, food waiting at the pass, and slow checks and payment at the end of the meal.

When should mains be fired after starters?

A common approach is to fire mains when starters are about two-thirds finished, adjusted by expo for each table's pace.

References

  1. National Restaurant Association (2025). From Trend to Transformation: Off-Premises Dining Now Essential for Restaurant Consumers, Operators (opens in a new tab) ↑

  2. National Restaurant Association (2025). Restaurant Industry Poised for Growth in 2025 (2025 State of the Restaurant Industry press release) (opens in a new tab) ↑

  3. US Bureau of Labor Statistics (2026). Current Employment Statistics: series CES7072200002 (opens in a new tab) ↑

  4. US Bureau of Labor Statistics (2025). Occupational Employment and Wage Statistics, May 2025 national estimate: Waiters and waitresses employment (series OEUN000000000000035303101) (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo