Different industries, different words, same fifteen jobs. If you recognise more than eight of these, you have a straightforward automation project and you do not need anyone to tell you that.
We have now counted the work in enough companies to say something slightly deflating: the tasks are almost always the same. The nouns change — policies, orders, patients, matters, jobs, loads — and the shape does not.
Here is the list, in the order it usually shows up on the volume ranking, with the automation shape each one takes.
| # | The task | Shape | Gate |
|---|---|---|---|
| 1 | Retyping a document into a system of record | extraction + confidence gate | per-field |
| 2 | "Where is my [order/claim/appointment]?" | read + reply | none needed |
| 3 | Sending a document somebody asked for | retrieve + attach | none needed |
| 4 | Answering the phone outside business hours | voice agent + calendar write | L3, recall |
| 5 | Booking, rescheduling or cancelling an appointment | calendar write | L2 → L3 |
| 6 | Small credits, refunds and adjustments | reversible write | L2, ceiling |
| 7 | Correcting an address or contact detail | reversible write | L2 + history rule |
| 8 | Opening a return, ticket, case or claim | create action | L2 → L3 |
| 9 | Chasing somebody for a missing document | scheduled workflow | none needed |
| 10 | Copying data between two systems that do not talk | orchestration | idempotency |
| 11 | Building the same report every week by hand | scheduled generation | none needed |
| 12 | Routing an inbound thing to the right person | classification | abstain on doubt |
| 13 | Onboarding checklist that lives in someone's head | workflow + templates | human sign-off |
| 14 | Reconciling two lists that should match | diff + exception queue | exceptions only |
| 15 | Answering the same five internal questions | grounded Q&A | none needed |
Six of the fifteen need no approval gate at all. They are read-only or they generate something a human was going to check anyway. Those can ship in weeks and they are how you build organisational confidence cheaply.
Most of the rest are reversible writes. Which is exactly the population the approval queue exists for: real actions, real time saved, and a one-click undo if it goes wrong.
Almost none of them require a frontier model. They require good retrieval, a typed action layer, and somebody who counted. The intelligence is in the plumbing.
Not one of them is a job. Every one is a slice of several jobs — the slice nobody enjoys. This is worth being precise about with your staff, because the fear is real and the honest answer is better than the vague one.
#14, reconciliation, is almost always underrated. It is invisible — nobody complains about it because it happens at month end and then it is over — and it is often the single most expensive task on the list in hours. Ask specifically.
#11, the weekly report, is usually overrated. It feels automatable and it often is, but the volume is one per week. Two hours a week is 100 hours a year, which sounds fine until you compare it with the 630 hours in row two.
#4, the phone, is systematically underrated in service businesses because the loss produces no record. There is no row in any report for the person who rang, waited nineteen seconds, and called somebody else.
Support automation, AI phone agents, n8n back-office work, and the engineering loop itself — always behind a gate you control.