LO
Get told when a verified record lands on this occupation →
Waiter / restaurant server
Runs the room: takes the order, times the courses, notices the table that has gone quiet, and absorbs it when the kitchen is late.
This is not a probability of losing your job. It combines how much of the role's task load is exposed to automation with how far adoption has actually gone — useful for comparing occupations on one consistent basis, and for nothing else.
Covers table service. Counter and fast-food service is a different job with much higher exposure — the order there is already a screen in many markets — and delivery is a separate occupation here. Tipping culture changes this job more than any technology does, because it decides whether the server is paid by the employer or by the customer, and this page does not generalise across that.
The evidence base holds verified records for other occupations, but not one for this one yet. Until it does, the analysis below is reasoning about task structure and known technical capability — for this job in particular it is not backed by traceable sources, and we would rather say so than cite things we have not verified. An empty section here is a gap in our coverage, not a finding about the work.
What is actually changing#
The unit of analysis is the task, not the job title. A role is not replaced — its task mix shifts.
Is this your job? Say so and this page narrows to your share of it.
A job title is a bundle of tasks bought together, and no two people hold the same bundle. Nothing is sent anywhere — it stays in this browser.
Taking the order
Automating≈ Platform inferenceRecording what each person wants, with the modifications, the allergy, and the one they changed their mind about.
QR-code ordering moved a large share of this to the customer's own phone during the pandemic and it stayed, which makes it the clearest completed automation in this job — and it was not done by AI. The saving is real because the task is pure data entry once the menu is digital.
Where this has happened, the covers per server went up and the job got harder rather than smaller — the server now handles more tables and has lost the thirty seconds at the table where they used to read the room. Removing a task can degrade the job it was part of, and this is the cleanest example of it in the service group.
Running the room
Still human-led≈ Platform inferenceHolding twelve tables in your head at once: who is waiting, who needs to be left alone, which course goes out next and which table will complain in five minutes if nobody goes over.
The scheduling part of this is genuinely computable and some systems attempt it; the input is not. Knowing that table six has gone quiet in a bad way rather than a good way is a reading of people that nothing in a restaurant is instrumented to capture, and the decision it drives — go over now, or leave them — is made in seconds with no data.
This being human does not set how many tables one person is given. The same judgement performed across eighteen tables instead of ten is a different job at the same job title, and that ratio is set by a manager after the ordering tablet arrives — which is how automation reaches this task without touching it.
Carrying things through a crowded room
New task≈ Platform inferencePlates, trays, drinks — through a space full of moving people, chair legs and children.
Running trays is the one task in this job that robots do at scale today: delivery robots are deployed in thousands of restaurants, mostly in Asia, and they work because the route is fixed and the failure mode is stopping. What they do not do is the last metre — putting the right plate in front of the right person and clearing it.
A running robot in a dining room is as often a marketing decision as a labour one, and where it has been deployed the reported effect is usually on how far staff walk rather than on how many staff there are. Read this direction as the technology working, not as a headcount result — the site holds no verified record of a restaurant reducing service staff because of one.
When it goes wrong
Still human-led≈ Platform inferenceThe wrong dish, the hour-late main, the allergy that was on the ticket and not on the plate — and the decision about what to take off the bill.
Recovery is the whole of hospitality's reputation and it is performed in person under time pressure, with the authority to give something away. That authority is the mechanism: the customer is being shown that a person with power over the bill is sorry, and a screen cannot perform that even if it can issue the refund.
The authority is the thing, and it is withdrawn more often than it is automated: chains that centralise comp decisions into an app remove this task from the server without a robot being involved at all. What looks like a durable human task can be hollowed out by a policy change in an afternoon.
Which technologies matter here#
Four separate signals. They are deliberately not added together — a job exposed to two technologies is not twice as exposed.
How it got here#
The index is not a static number. This is where it would have sat at each capability checkpoint since ChatGPT — reconstructed, and labelled as such.
The step in this curve is 2023 and it was not caused by AI: QR-code ordering moved a large share of order-taking to the customer's own phone during the pandemic and stayed there, which is the clearest completed automation in the occupation. It flattens early because what is left — holding twelve tables in your head, reading the one that has gone quiet, and the recovery when the kitchen is an hour late — has no instrumented input. The height understates the change to the job: where ordering left, covers per server went up and the thirty seconds at the table disappeared, so a task was removed and the work got harder rather than smaller.
A flat line is not a forecast of safety. It says which tasks automation has reached so far — the occupations that moved least here are the ones where the constraint is physical or regulatory, and both of those can change.
Recent changes#
No verified events recorded yet.
This section will fill from the monitoring pipeline as events are collected, de-duplicated, graded and linked to the tasks above. An empty list here means we have not verified anything — it does not mean nothing is happening.
"We found no news" is not the same as "you are safe."
What this means for you#
Getting in is not the problem and will not be. What to watch is which half of the job you are being trained into: a place where ordering is on the customer's phone and you run eighteen tables is teaching you speed, and a place where you take the order at the table is teaching you the reading of a room, which is the part that transfers to better-paid rooms later.
The covers-per-server ratio is the number that decides your working life, and it moves quietly after any ordering technology lands. It is also the number nobody negotiates, because it is framed as a scheduling detail rather than as a change to the job.
Your options#
Four directions, each with its real constraints and one thing you can test this week. Continuing as you are is a legitimate choice — it just has to be a chosen one.
Move to rooms where the order is taken at the table
Where the ordering stays with the server, the reading of the room stays with it, and that is the skill that carries a career rather than a shift.
Those rooms are fewer, more formal, and usually require a reference from one before you can work at one.
Count what share of your tables this week ordered through a screen. That share is the part of the job that has already left.
Take the room, not the tables
Somebody has to decide seating, pacing and who covers what, and that judgement is the same one you already make for your own section — scaled up and paid better.
It is management, so the hours get worse before the pay gets better, and in tipped rooms it can mean a pay cut.
For one shift, write down every seating decision the host made that you would have made differently. That list is your case.
Common questions#
Running food is the one part robots genuinely do at scale, mostly in Asia, and they work because the route is fixed and failing means stopping. What they do not do is the last metre — the right plate to the right person — or the recovery when something has gone wrong, which is performed in person by somebody with the authority to take it off the bill. Where running robots have been deployed, the reported effect is on how far staff walk, not on how many there are.
No date, and for this job the honest signal is not a technology at all — it is the covers-per-server ratio on your own rota. Every ordering technology that lands is followed within a couple of months by a quiet change in how many tables one person is given. Track that number month to month; it will tell you more about your working life than any forecast, and it is the only one you can actually check.
Yes, and it is the clearest completed automation in the occupation — done without any AI at all. The part worth noticing is what it did to the rest of the job: where ordering moved to the customer's phone, covers per server went up and the thirty seconds at the table, which is when a server reads the room, disappeared. The task was removed and the job got harder rather than smaller.
No, and the difference matters for the answer. Counter service has already had its ordering step replaced by a screen in many markets, which makes its exposure much higher than table service. This page is about table service, where the order, the pacing and the recovery are still held by one person — and where the automation arriving is aimed at the legs rather than at the judgement.
Method and sources#
- Assessment date
- 2026-09-14
- Basis of the task judgements
- 0 evidence-backed · 4 platform inference · 0 not enough evidence
- Verified events
- 0