Faster payment, measured in actual seconds

Ask any server how long it takes a table to pay and you will get a guess: "a few minutes", "not long", "depends on the table". Ask a guest who has been waiting for the card machine and you will get a different answer. The end of the meal is one of the least measured parts of service, and one of the most often complained about.

Faster payment is worth chasing, but only once you know how long payment actually takes now, where the time goes and what a faster method would really save. This guide shows how to time the payment step in your own room, compares three common ways of paying, and works through what the minutes saved are worth over a year, honestly, including the cases where they are worth less than they seem. Every figure in it is an example from an invented venue.

Payment sits at the end of the meal, after the food and the conversation, when the guest's impression of the evening is almost formed. A long wait at that point can spoil a good meal, because it is the last thing the guest remembers before leaving.

It also ties up the table and the server. A table waiting to pay is a table that cannot be reset for the next guests, and a server walking back and forth with bills and card machines is a server not looking after other tables.

But most venues have no idea how long it takes. Without a measurement, every change, a new card machine, paying by QR code, training servers to bring the bill sooner, is a guess. Measuring first turns it into a decision.

The payment step is not one moment but four, and each can be timed separately:

Each part has different causes and different fixes. A long first part means servers are not noticing tables; a long second part means bills are slow to produce or carry; a long third part means the card machine or the split is slow.

Timing the payment step needs nothing more than a notebook, a watch and a few quiet observers, such as a manager or a host with a few minutes to spare. Pick a normal busy service and follow a sample of tables, say twenty, from the moment they look ready to pay to the moment they leave.

For each table, note the time at each of the four points, the party size, how they paid and whether they split the bill. Do it again on another night, and again with a different method if you are comparing.

Be consistent about what counts as each point. The moment a table is ready to pay is often a guess, such as menus closed and coats being reached for, so agree the signs in advance. Twenty tables on two nights usually give a clear enough picture.

The traditional method is still common: the table asks for the bill, the server prints it and brings it, the guest checks it, the server goes back for the card machine, returns, and the guest pays. Each journey to and from the counter adds time, and on a busy night the server may be stopped on the way.

Timed in an example room, the four parts might look like this: two minutes to get the server's attention, three to bring the bill, four from the bill arriving to payment complete, including the second trip for the card machine, and two to leave. About eleven minutes from wanting to pay to an empty table.

The slowest part is usually the middle: the server's two trips. Bringing the bill and the card machine together removes one of them.

With pay at table, the server brings the bill and a handheld card machine together, and the guest pays at the table in one visit. Splitting can happen there and then, one card at a time.

In the same example room, the four parts might be two minutes to get attention, three to bring the bill and machine, two to pay, and two to leave: about nine minutes. The saving comes from the single trip, and from contactless payments, which take a few seconds once the card machine is in front of the guest.

The asking part does not change. A table still has to catch a server's eye, and on a busy night that can be the longest wait of all. Training servers to notice the signs, and to offer the bill before it is asked for, attacks that part directly.

When guests pay from their own phones, by scanning a code at the table, the first two parts can almost disappear. The guest does not need to catch anyone's eye or wait for a bill; they open the page, see the bill and pay when they are ready.

In the example room, the parts might be close to nothing for asking and bringing the bill, two minutes to pay, including splitting, and two to leave: about four or five minutes. Our guide to paying by QR code at the end of the meal covers what has to be true for it to work first time.

Not every guest uses it, and some prefer the card machine, so in practice a venue offering it sees a mix. The saving applies to the tables that use it.

One of the biggest savings needs no new equipment at all. Bringing the bill before it is asked for, or at least offering it, cuts the first part of the payment step, which is often the longest.

Servers can learn the signs: closed menus, finished coffees, coats being reached for, guests looking around. A server who notices and asks "can I bring you the bill?" saves the table several minutes of trying to catch someone's eye, and the guest feels looked after rather than forgotten.

The art is in the timing. Offering the bill too early, while guests are still enjoying the meal, can feel like being hurried out. Offering it at the right moment feels like attentive service. Our guide to pay at table: minutes back on every turn covers how to train for it.

Contactless payments, by card or phone, are much faster than chip and PIN once the card machine is in front of the guest: a few seconds rather than half a minute or more. Wikipedia's article on contactless payment explains how the technology works and where limits apply.

Those seconds matter less than the minutes spent waiting for the machine to arrive, but they add up across a table of six paying separately. Six contactless payments might take well under a minute; six chip and PIN payments, with the machine passed around the table, can take several.

Make contactless the easy default where it is allowed. Keep card machines charged, connected and quick to wake, because a machine that takes a minute to connect wipes out the seconds contactless saves.

Splitting is where the payment step most often stretches. A table of eight paying separately, some for their own dishes, some splitting equally, can take far longer than the same table paying once.

Time split bills separately when you measure, because they behave differently. Look at where the time goes: working out who owes what, passing the card machine round, re-entering amounts. Each has a fix: a point of sale that splits by item or by equal shares in a few taps, a handheld machine that moves round the table, or paying by QR code where each guest pays their own share.

Our guide to splitting the bill for a table of eight covers the common ways guests split and how to handle each quickly.

Once the table has paid, the clock is still running. Guests may finish their drinks and their conversation, and the table cannot be reset until they leave. That part is the guests' time, and rushing it is rarely wise.

What the venue can control is the reset. A table that empties at nine and is reset by five past is available sooner than one reset at a quarter past. Our guide to turn times, the number every booking rule needs covers how the reset fits into the whole turn.

Measure the reset as well, from guests leaving to the table being ready, because a faster payment step is worth little if the table then waits ten minutes for someone to clear it.

The value of faster payment depends on what the saved minutes become. There are three possibilities, and they are worth very different amounts.

If the saved minutes let the venue seat another table that would otherwise have been turned away, they are worth that table's spend. If they let servers look after more tables, or the same tables better, they are worth some labour and some service quality. If the venue is never full, they may be worth little more than happier guests.

So before working out the value, ask the honest question: on the nights when payment is slow, is the venue turning guests away? If the answer is yes, faster payment can be worth a great deal. If it is no, the main benefit is the guest experience, which is still worth having, but is not a revenue line.

Take an example 80-seat bistro that is full on Friday and Saturday nights, with a waitlist most weekends. It times the payment step and finds that moving from the traditional method to pay at table with handheld machines would save about two minutes a table, and that paying by QR code, for the half of tables that would use it, would save about six.

Over a weekend night, the bistro serves around 70 tables. Saving an average of about four minutes a table gives back roughly 280 minutes of table time a night. If even a small share of that time lets the bistro seat two more tables of two from the waitlist each weekend night, at an example spend of 45 a head, that is 180 a night, 360 a weekend and, over 50 weekends, about 18,000 a year.

That figure depends entirely on the waitlist. On weeknights, when the bistro is not full, the same minutes save staff time but not covers.

Table turnover rate, the number of times a table is used in a service, is where faster payment shows up most clearly in the numbers. A venue that shortens the end of the meal by a few minutes on every table can turn some tables an extra time on busy nights, or simply offer later booking times with less risk of overlap.

Faster payment is only one part of turnover. The pace of the meal, the time to seat guests and the reset all matter too, and pushing guests to leave faster is rarely good for the venue. Our guide to table turnover rate and how to raise it politely covers the whole picture.

What faster payment does is remove waiting that guests do not want. A guest who is ready to leave and can, promptly, is a guest who leaves happy.

After changing the payment method, time the payment step again, the same way, on similar nights. Compare each of the four parts before and after, not just the total, so you can see where the time was saved.

Look at the effect on the rest of the evening too. Did tables become available sooner? Did the waitlist move faster? Did servers handle more tables comfortably? Did guests comment on it?

And look at the unintended effects. A new card machine that is faster to pay but slower to connect, or a QR payment page that confuses some guests, may save time for most tables and cost it for a few. The measurement shows both.

The fastest single change to the payment step is often servers noticing sooner. Train them to read the signs that a table is ready: menus closed, plates cleared, coffees finished, guests looking around or reaching for coats. A server who reads those signs and offers the bill removes the longest wait in many rooms.

Make it part of the rhythm of every section. A server passing a table that looks finished should ask, not wait to be called. On busy nights, the host or a manager can help by watching the room and telling servers which tables look ready.

A slow payment step costs the guest something too: the last impression of the evening. Guests who enjoyed their meal but waited fifteen minutes to pay often mention the wait in reviews, more than the food.

That cost is hard to measure but easy to see in feedback. Read reviews and comments for mentions of the bill, the wait at the end or chasing a server. If they appear often, the payment step is costing the venue goodwill, whatever the numbers say.

An invented brasserie with 90 seats is full on Friday and Saturday nights, with walk-ins regularly turned away after eight. Guests' reviews mention waiting for the bill. The manager times twenty tables on two busy nights: on average, eleven minutes from ready to pay to an empty table, with the longest waits in getting a server's attention and the second trip for the card machine.

The brasserie trains servers to offer the bill when the signs show, and buys handheld card machines so the bill and the machine arrive together. Timed again a month later, the average falls to about seven minutes. The time to get attention halves, and the second trip disappears.

On busy nights, tables become free a few minutes sooner, and the host is able to seat two or three more walk-in parties before the kitchen closes. Reviews stop mentioning the bill. The card machines cost less than the brasserie earns from those extra tables in a month.

In servearound, guests can request the bill from the menu they open with the table's QR code, which tells the team straight away, so the first part of the payment step does not depend on catching someone's eye. The team brings the bill and records how it was paid, by cash, card, bank transfer or another method; servearound does not process card payments today, and card processing is coming, so paying from the guest's phone is not available yet.

When a bill is settled, the table's seating ends, and table analytics show the median seating time, the gap between seatings, utilisation and revenue per seated hour, so a faster end to the meal shows up in your own figures. Payment analytics show what was collected by method and by hour, and the average check. See Order Fulfillment and Analytics.

It varies widely, which is why it is worth timing. In many venues, the whole end of the meal takes around ten minutes, much of it waiting.

Follow a sample of tables on busy nights and note four times: ready to pay, bill arrives, payment complete and table empty.

Often getting a server's attention, and the second trip when the card machine arrives separately from the bill.

Usually, because the bill and the card machine arrive together, removing one trip. Contactless payments then take only seconds.

For the tables that use it, often much faster, because guests do not need to wait for anyone. Not every guest will use it.

They should offer it when the signs show the table is ready. Too early feels like hurrying; at the right moment it feels attentive.

It depends on what the saved minutes become. On full nights with a waitlist, they can become extra tables; otherwise, mostly staff time and happier guests.

Shorter waits at the end let tables be reset sooner, which can allow an extra turn or later bookings on busy nights.

Time the four parts again on similar nights, and look at table availability, the waitlist and guest comments as well as the totals.

Faster payment starts with measurement. Time the end of the meal in four parts, asking, bringing the bill, paying and leaving, for a sample of tables on busy nights, and look for where the minutes go. Often the longest waits are catching a server's eye and a second trip for the card machine.

Compare methods in your own room: the bill and then the machine, pay at table with a handheld machine, and paying by QR code. Train servers to offer the bill at the right moment, keep contactless quick and card machines ready, and handle splits smoothly. Then value the saved minutes honestly: they become covers only on nights when guests are being turned away, and otherwise mostly become better service.