Taking an order without writing it twice

A server takes an order for a table of six on a pad: two starters to share, six mains, three with changes, a bottle of red and a jug of water. They walk to the till, wait for a colleague to finish, find the table, and type the whole order in again from their handwriting. Four minutes later, the order reaches the kitchen, missing one of the changes, because "no mush" on the pad became nothing on the till.

Writing every order twice is so normal in many restaurants that nobody questions it. Yet each order taken that way costs time, a walk and a second chance to make a mistake. Taking an order once, at the table, straight into the system, removes all three, as long as it is done well.

This guide compares the two ways of taking an order, a pad and then the till, or straight into the till at the table, with the time each costs, the mistakes each produces and how to choose between them. Every venue and figure in it is an example.

There are two main ways of taking an order at the table. In the first, the server writes it on a pad, walks to a till and types it in. In the second, the server enters it straight into a device at the table, a handheld or a tablet, and sends it to the kitchen from there.

A third way, where guests order themselves from their phones, is growing too. It removes the server from the ordering step entirely, and it brings its own advantages and problems.

Each way has a place. In most restaurants, taking orders is the job of the waiting staff, and how they do it shapes every step that follows. The question for each venue is which way serves its guests and its team best.

The pad is simple, quick at the table and familiar to every server. It needs no battery, no network and no training. A good server can write an order in their own shorthand faster than anyone can type it.

The cost comes afterwards. The server must walk to the till, which takes time and leaves the section unattended. They must find a free till, which at a busy hour can mean waiting. And they must type the order in, reading their own shorthand, which is the moment mistakes creep in.

Every order is written twice: once on paper, once on the screen. Every change, every allergy and every seat has two chances to be lost.

Tableside ordering means taking the order directly into the system at the table, on a handheld device or a tablet. When the server presses send, the order goes straight to the kitchen and the bar. There is no walk to the till and no second entry.

That saves time, and it removes the most common source of mistakes: copying from the pad. The changes, the allergies and the seats are entered once, while the guest is in front of the server and can be asked if anything is unclear.

The cost is in the device and the skill. Handhelds must be bought, charged and looked after, and servers must learn to use them without losing eye contact with the table.

The time saved by handheld ordering is easiest to see in the walk. A server who takes an order at a table, walks to a till, waits and types it in may spend two or three minutes on each order away from the floor. Across a busy evening of thirty tables, two orders per table, that can add up to well over an hour of a server's time.

The order also reaches the kitchen sooner. An order sent from the table starts cooking two or three minutes earlier than one typed in later, which shortens the guest's wait for every course.

In a small room with the till a few steps away, the saving is small. In a large room, a terrace or a venue on two floors, it can be large.

Pad-and-till ordering produces copying mistakes: a change written on the pad and not typed in, a dish misread from handwriting, an order typed into the wrong table, a seat number lost. It also produces mistakes of memory, when a server who did not write something down tries to remember it at the till.

Tableside ordering removes most of those, but it brings its own: a wrong button pressed on a small screen, an order sent to the wrong table because the wrong one was selected, a change missed because the server was looking at the guest instead of the screen.

On balance, entering an order once, at the table, produces fewer mistakes than entering it twice. Our guide to ticket accuracy: where the wrong plate comes from covers how to trace mistakes to their step.

A table of eight, all talking at once, is where orders go wrong. Take control gently: start with one guest and go round the table in seat order, so nobody is missed and every dish is linked to its seat. Ask each guest about changes as they order, rather than at the end.

If the table is noisy, step closer and lean in rather than raising your voice. If a guest is undecided, move on and come back to them. The aim is an order taken once, correctly, without the table feeling processed.

Order accuracy starts with how the order is taken. Whatever the method, the server should listen fully, ask about allergies, confirm cooking points and changes, and read the order back before leaving the table.

The read-back is the single most useful habit. It catches mishearing and forgotten changes while the guest is still there to correct them, and it takes seconds. With a device, the server can read straight from the screen, so what the guest hears is exactly what the kitchen will receive.

Modifiers help too. A device that offers the common changes as taps, rather than typing, produces clearer tickets. Our guide to modifiers on the ticket: no onions, really covers how changes should reach the kitchen.

The strongest argument against devices at the table is hospitality. A server staring at a screen while the guest talks feels like a clerk, not a host. Guests notice, and some dislike it.

That is a matter of training, not of the device. A good server listens first, looking at the guest, then enters the order quickly, then looks up again to read it back. With a well laid out system, the time spent looking at the screen can be a few seconds per dish.

Some venues, especially in fine dining, keep the device out of sight and enter the order away from the table. That keeps the moment at the table personal, while still entering the order only once.

Taking an order by seat helps the kitchen and the floor: each dish is linked to the guest who ordered it, so the runner can place each plate without asking. A pad can record seats, but they are often lost when the order is typed in. A device can record them directly.

Agree a seat numbering for every table, such as clockwise from the seat nearest the door, and use it consistently. Shared dishes, such as starters for the table, can be marked as for the table rather than a seat.

Ask about allergies every time, at the start of the order, in a way that makes guests comfortable telling you: does anyone at the table have any allergies or dietary needs the kitchen should know about? Record each one against the guest and their dishes, as an allergy, not a note.

When a guest mentions an allergy, check the dishes they choose against it, and tell them honestly if you are not sure. An allergy recorded once, at the table, as an allergy, reaches the kitchen in the clearest form. Our guide to allergy notes: the record that must not fail covers the record.

Many venues take the drinks order first, quickly, then the food order a few minutes later. With a device, the drinks can be sent to the bar the moment they are ordered, so they arrive while the guests read the menu.

With a pad, the drinks often wait until the server has also taken the food, or make a separate trip to the till. Either way, the guests wait longer for their first drink, which sets the tone for the meal.

Taking an order is also the moment to recommend. A server who knows the specials, the dishes that pair well and the wine that suits the main can lift the table's evening and its spend at the same time. That is hard to do with eyes on a pad or a screen.

Learn the specials before service, so they can be described without reading. Recommend from what the guest has said they like, not from a script. Then enter the order quickly and return your attention to the table.

Drinks orders need the same care as food. A cocktail with a change, a spirit with a particular mixer or a glass of wine from a specific bottle must reach the bar exactly as ordered. Enter drinks with their options, just like dishes.

When drinks are entered once, at the table, they reach the bar immediately, often before the server has left the table. That alone can shorten the wait for the first drink by several minutes, which guests notice more than almost anything else.

The pad still makes sense in some venues. In a small room with the till close by, the time saved by a device is small. In a venue with very few staff, the cost of devices may not be worth it. And in a power cut or a network failure, the pad is the fallback that always works.

If you keep the pad, reduce the copying mistakes: write orders in the same structure every time, record seats and changes clearly, and type the order in as soon as possible, not after taking three more.

Keep pads ready even if you move to devices. They are your fallback when the system fails.

Handheld ordering works best when it is quick and reliable. The device must be fast, the menu easy to navigate on a small screen, and the network strong across the whole floor, including the terrace and the corner by the kitchen door.

Give each server their own device for the shift, charged and signed in, with a few spares. Decide where devices live between shifts and who charges them. A dead battery at seven o'clock is a server back on the pad.

Our guide to types of POS systems, and who each one suits covers when handhelds are worth it.

Large tables and parties need a plan. For a party of twelve or more, consider taking the order before the guests arrive, from a set menu or a pre-order, so the kitchen can prepare. On the night, take any changes and the drinks, and send the courses in sequence.

If the party orders on the night from the full menu, take the order in sections, by seat, and send each course complete. Two servers taking one large table's order in halves can work well, as long as both use the same seat numbering.

When guests order from their own phones, by scanning a code at the table, the order is entered once, by the guest, and goes straight to the kitchen. That removes copying mistakes and saves servers' time, especially for repeat rounds of drinks.

It also changes the server's role: less taking orders, more greeting, recommending and checking on tables. Some guests love it; others want to order from a person. Many venues offer both, so guests can choose. Our guide to scan to order: the flow that actually works covers how to set it up.

Second and third rounds of drinks are where much of a table's spend comes from, and where ordering is often slowest. A guest who has to catch a server's eye to order another glass may decide not to bother.

Make repeat rounds quick. A server who notices empty glasses and offers another, and can enter the round in seconds at the table, keeps the table's evening going. Where guests can order from their phones, repeat rounds become easier still.

Before an order is sent, check it once on the screen: the table, every dish, every change, every allergy and the timing of the courses. It takes a few seconds and catches the wrong table, the missing side and the main that should have been held.

Pair that check with the read-back to the guest, and most ordering mistakes never reach the kitchen.

Taking the order is the first step of order management, not the last. Once the order is in, the kitchen must receive it, the courses must be timed, changes must be passed on and the check must be kept correct until the guest pays.

Entering the order once makes every later step easier, because there is only one record of what the guest asked for. Our guide to order management from table to pass covers the whole journey.

Moving from pads to devices needs training. Servers must learn the menu's layout on the device, how to enter changes and seats, how to send and hold courses and how to fix a mistake. They must also learn to keep their eyes on the guest.

Practise with real orders before the first service, and pair less confident servers with someone who has picked it up quickly. Expect the first few services to feel slower; most servers become faster on a device than on a pad within a week or two.

If you move from pads to devices, measure the effect. Before the change, time how long orders take to reach the kitchen and count the remakes caused by ordering mistakes. After the change, measure the same things over similar services.

Ask the servers how their evenings feel, and ask guests what they notice. The best measure of success is a team that would not go back.

An invented brasserie with a large terrace takes orders on pads. Servers walk to one of two tills inside, often waiting at the busiest hour. Orders take several minutes to reach the kitchen, and remakes for missed changes happen most nights.

The brasserie gives each server a handheld for the shift, sets up the menu with the common changes as taps, improves the wifi on the terrace and trains every server before the switch. Servers read orders back from the screen before leaving each table.

After a month, orders reach the kitchen sooner, remakes for missed changes have fallen to one or two a week, and servers spend more time on the terrace. A few regulars mention that service feels quicker.

servearound's point of sale runs in a browser, so a server can take the order at the table on a tablet and send it to the kitchen from there, with no second entry at a till. Dishes are rung in with their options and removals, and by seat if the server likes, with a note for the kitchen on any dish or the whole round, and the till will not send an order for a table nobody is seated at yet.

Guests can also order from their phones using the menu they open with the table's QR code, when the venue turns ordering on, and their rounds join the same table's check. See Order Fulfillment.

Entering it once, at the table, straight into the system, with a read-back before leaving. Pads still make sense in small rooms and as a fallback.

Usually, especially in large rooms and on terraces, by removing the walk to the till and getting orders to the kitchen sooner.

Entering an order once removes copying mistakes, though it brings its own, such as wrong buttons on a small screen.

Not if the server listens first, looks at the guest and uses the device quickly. Some venues enter orders away from the table.

Reading the order back to the guest before leaving the table, so mistakes are caught while they can be corrected.

Yes. Linking each dish to a seat lets the runner place plates without asking.

It removes copying mistakes and frees servers for hospitality. Many venues offer it alongside server ordering.

Yes, as a fallback for a power cut or network failure.

Taking an order on a pad and typing it into the till means writing it twice: a walk, a wait and a second chance to make mistakes. Taking an order straight into a device at the table, or letting guests order from their phones, enters it once, gets it to the kitchen sooner and removes copying mistakes.

Whichever way you choose, listen first, record seats and changes clearly, read the order back before leaving the table, keep devices charged and the wifi strong, train servers to keep their eyes on the guest, and keep pads ready for the night the system fails.