Tableside ordering: eyes up, not on a screen

A couple sit down for an anniversary dinner. The server arrives, says good evening to the tablet in their hand, and starts tapping. Every question is asked while looking down: still or sparkling, any allergies, are you ready to order. The order is perfect when it reaches the kitchen. The couple remember the evening as the night the waiter never looked at them.

Tableside ordering is meant to make service better: no walk to the till, no copying mistakes, orders in the kitchen sooner. Done badly, it makes service worse, because the most important thing a server brings to the table is attention, and a screen takes it away.

This guide covers how to take an order on a device without losing the conversation, how to keep screen time to seconds, the three moments when the device should go down altogether, and how to train servers to do it well. Every venue and figure in it is an example.

A server holding a device is pulled towards it. The screen lights up, the menu needs navigating, a modifier needs choosing, and the server's eyes go down. Each glance is short, but together they can fill most of the time at the table.

Guests notice. A conversation where one side keeps looking away feels like a transaction. The guest who mentions an allergy while the server is scrolling may wonder whether it was heard. The table celebrating something may feel processed rather than welcomed.

None of that is the device's fault. It is a habit, and habits can be trained.

The simplest rule of tableside ordering is to listen first and tap second. When a guest orders, look at them while they speak. Let them finish. Then enter what they said, quickly, and look up again.

Entering each dish as the guest says it, with eyes on the screen throughout, is faster for the server but worse for the guest. Listening first and entering in short bursts costs a few seconds and keeps the conversation alive.

For a large table, go round in seat order, listening to each guest in turn and entering their order before moving to the next. That keeps each guest's moment their own.

The best tableside ordering feels like a conversation, not an interview. Ask open questions: what are you in the mood for tonight, have you been here before? Let guests tell you about themselves, and recommend from what they say.

The device records the result of the conversation, not the conversation itself. A server who talks first and taps second gathers more about the table, makes better recommendations and leaves the guests feeling they were heard.

Servers who know the menu well look at the screen less. They can describe dishes, answer questions and suggest pairings without searching for the answer on the device. The screen is then only for entering the order, not for finding out what is on it.

Make menu knowledge part of training: what each dish is, how it is cooked, what is in it and what goes with it. A short quiz at the briefing, or tasting new dishes, builds the knowledge that keeps eyes up.

The less time the server spends looking at the screen, the better. That depends on how well the system is laid out and how well the server knows it. A common dish should take a single tap; a change should be a tap or two from the dish's own options; finding a dish should be quick, by category or by search.

Set the menu up so the most common dishes are easiest to reach, and so their usual changes are ready to tap. Our guide to taking an order without writing it twice covers why entering the order once matters.

A server who knows the layout by heart can enter an order in the time it takes to say "lovely, I'll get that started".

How the device is held matters. A device held up between the server and the guest is a barrier. One held low, at the side or below the table's edge, leaves the server's face open to the table.

Stand where guests can see you without turning, at a comfortable distance, and hold the device so you can glance down at it without lowering your head. Some servers keep it in an apron pocket until the moment they need it.

The one moment when looking at the screen helps the guest is the read-back. Before leaving the table, read the order back: each dish, each change, each allergy. Reading straight from the screen means the guest hears exactly what the kitchen will receive.

Look up between items as you read, and check that each guest nods. A read-back done with care catches most mistakes and reassures the table that their order, and especially their allergy, has been heard.

When a guest asks for a change, such as no onions, a sauce on the side or a different side, listen, confirm it out loud and then enter it. Saying it back while looking at the guest reassures them it has been heard, and the tap that follows takes a second.

If the system does not have an option for the change, enter it as a short, clear note. Avoid long negotiations with the screen while the guest waits; a quick note and a word to the kitchen are better than a minute spent searching.

Large tables are where tableside ordering helps most and where eye contact is hardest. Go round the table in seat order, look at each guest as they order, enter their dishes and move to the next.

Keep track of where you are. A table of twelve, half of whom want changes, can easily lose a guest in the middle. Read the whole order back at the end, seat by seat, so everyone hears their own dish.

The first moment to put the device down is the greeting. The first thirty seconds at a table set the tone for the whole meal. A server who arrives, looks at the guests, smiles and welcomes them sets a very different tone from one who arrives looking at a screen.

Keep the device out of sight for the greeting: in an apron pocket, at your side or not yet picked up. Welcome the table, offer water, mention the specials and ask if anyone has allergies, all with eyes on the guests. Pick up the device only when it is time to take an order.

The second moment is when a guest asks for a recommendation or a question about a dish. "What would you recommend?" is an invitation to a conversation, not a search query. Answer it looking at the guest, from your own knowledge, with enthusiasm.

This is also where good upselling happens: suggesting a wine that suits the main, a side that goes with the steak or a dessert worth saving room for. Upselling done with eye contact and real knowledge feels like hospitality; done while scrolling, it feels like a sales script. Our guide to upselling that does not sound like selling covers the approach.

The third moment is when something has gone wrong: a complaint, a mistake, a guest who is unhappy. A server who keeps looking at a device while a guest explains a problem appears not to care.

Put the device away completely. Listen, look at the guest, acknowledge the problem and say what you will do. Only then, if needed, step away and use the device to put things right. Our guide to service recovery: putting a bad night right covers what to do next.

Wine is where knowledge and eye contact matter most. A guest asking which wine goes with the lamb wants a person's opinion, not a list read from a device. Learn the wine list well enough to recommend two or three bottles at different prices from memory.

Recommend with the price in mind. Offering a mid-priced bottle and a more special one, rather than only the most expensive, makes the guest comfortable choosing. Then enter it on the device after the guest has decided.

Some tables are in a hurry: a theatre booking, a business lunch, a family with tired children. They want speed more than conversation. Read the table, take the order quickly and efficiently, and let the device do its job.

Tableside ordering suits hurried tables well, because the order reaches the kitchen the moment it is taken. Tell the kitchen when a table is short of time, so the food can be prioritised.

Allergies deserve the same care as a complaint. When a guest mentions an allergy, look up, listen fully and repeat it back: "So that's a nut allergy, including traces?" Then record it carefully on the device, as an allergy rather than a note, and check their dishes against it.

A guest who sees the server stop, listen and record their allergy properly trusts the kitchen far more than one who sees it tapped in while the server looks elsewhere. Our guide to allergy notes: the record that must not fail covers how it should be recorded.

How much eye contact feels right varies between cultures and between guests. In some places, steady eye contact feels warm and attentive; in others, it can feel intense. Some guests want a chatty server; others want quiet efficiency.

Train servers to read the table: warm and attentive by default, adjusting to what each table seems to want. The point is not a rule about seconds of eye contact, but that the guest feels the server's attention is on them, not on the device.

In fine dining, many venues avoid devices at the table altogether. The server takes the order in conversation, remembers it or notes it discreetly, and enters it on a device away from the table. That keeps the experience personal while still entering the order once.

If you use handheld ordering in a formal setting, keep the device small and out of sight, and use it away from the table where you can. Our guide to handheld ordering: does it really save a lap? covers when handhelds are worth it.

Write the habits down as service standards, so every server learns the same way. Keep them as actions anyone can do: greet without the device, listen before tapping, hold the device low, read back from the screen, put the device away for recommendations and problems.

Short, specific standards are easier to train and easier to check than general ones such as "be attentive". Our guide to service standards written as actions, not values covers how to write them.

Think about what the guest sees. A device with a bright screen, held up in the guest's line of sight, draws the eye. One held low, with the screen dimmed, fades into the background.

Some venues choose small devices or cases in the venue's colours, so they look like part of the service rather than technology. Small details like these change how guests feel about a server holding a device.

Train tableside ordering in two parts. First, the device: the menu's layout, how to enter changes, seats and allergies, how to send and hold courses, and how to fix mistakes, until the server can do it without thinking. Second, the hospitality: greeting, listening, reading back and knowing when to put the device away.

Role-play helps. Let servers take orders from each other, with one playing a guest who talks a lot, changes their mind or mentions an allergy. Watch how often they look down, and give feedback.

The device can help the kitchen as well as the server. Recording seats, holding mains, marking allergies properly and adding short, useful notes all make the kitchen's tickets clearer. A server who uses the device well at the table saves the kitchen questions later.

Take a moment after each order to check that it is complete before sending: every dish, every change, every allergy and the timing. Do it once you have stepped back from the table, so the check costs the guest nothing.

Devices fail: a battery dies, the wifi drops, the screen freezes. Have a plan. Keep a pad in your apron, take the order on paper and enter it as soon as the device or a till is available. A calm server with a pad is still a good server, and the table need not know anything went wrong.

Report the problem so it can be fixed before the next service: a device that will not charge, a dead spot in the wifi or a screen that keeps freezing.

Habits slip under pressure. On a busy night, servers look at their devices more, because they are rushing. Managers can help by watching a few table visits each shift and giving quick, kind feedback afterwards.

Praise what goes well: a warm greeting, a good recommendation, a clear read-back. Point out one thing to improve, not ten. Over a few weeks, the habits settle.

Guests are the best judges of whether tableside ordering feels personal. Ask a few regulars what they think of the service since the devices arrived. Read reviews for mentions of servers, attention and the devices.

If guests mention the screens, look at how they are being used. If they do not mention them at all, the devices have probably become invisible, which is the aim.

Upselling works best when it fits the moment: a dessert suggested when the mains are cleared, a second glass offered when the first is nearly empty, a side recommended when a guest orders a steak on its own. Each is a suggestion made to the guest, not to the screen.

Train servers to suggest one thing at a time, sincerely, and to accept a no gracefully. A server who suggests and then enters the order quickly, without lingering on the device, sells more and feels less like a salesperson.

An invented bistro introduces handheld ordering. Orders reach the kitchen sooner and mistakes fall, but two reviews in the first month mention servers who "never looked up". The owner watches a few table visits and sees servers greeting tables while unlocking their devices and scrolling through the menu as guests order.

The bistro writes five short standards: greet without the device, listen before tapping, hold it low, read back from the screen, and put it away for recommendations and problems. Servers practise in pairs before service, and the manager watches two table visits per server each week.

Within a month, the comments about screens stop, and one regular remarks that the service feels warmer than it did before the devices arrived.

servearound's till is built to keep the taps down, so a server spends seconds on the screen, not minutes. A dish is a picture card that goes on the check with one tap, and only a dish that needs a choice opens its options first, with search beside the category chips for a dish you can name faster than you can find. Changes happen on the check itself: tap a line to change its quantity, hold it, give it a seat, change its options or add a note.

The total and one large button sit at the foot of the check, Send while there is a round to send and payment once there is not, with Hold beside Send and the rarer check actions behind one menu. The till runs in a browser and is laid out for a tablet, and a guest's allergies from their profile reach the head of every kitchen ticket. See Order Fulfillment.

Taking the order on a device at the table and sending it straight to the kitchen and bar, without a pad or a walk to the till.

Only if servers look at the screen instead of the guest. Listening first and tapping second keeps it personal.

At the greeting, during recommendations and when a guest has a problem.

A well laid out menu with common dishes and changes one tap away, and servers who know the layout well.

Look up, listen fully, repeat the allergy back and record it as an allergy, then check the dishes against it.

Often with the device kept out of sight and the order entered away from the table.

Train the device and the hospitality separately, with role-play and feedback during service.

Guests stop mentioning screens, and servers report that orders are quicker without the table feeling processed.

Tableside ordering speeds up service and removes copying mistakes, but a server looking at a screen loses the guest. Listen first and tap second, keep screen time to seconds with a well laid out menu, hold the device low and read the order back from the screen.

Put the device down altogether at three moments: the greeting, recommendations and problems. Give allergies full attention, write the habits down as service standards, train the hospitality as well as the device, coach during service and ask guests what they notice.