LO
Operations coordinator — how we know
The page itself gives the judgements. This one gives what they rest on: which technologies bear on the work, how the estimate moved since language models reached the public, and the method behind both.
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.
—— this stretch contains a verified event- - - no event in this stretch — reconstruction only0 = no task exposed, 100 = every task exposed
● 2 verified events for this occupation, plotted at the date it happened — the parts of the line near a marker are anchored to something checkable.
Starts high because this job was already surrounded by software before 2022 — order management, EDI, document capture and workflow engines automated the structured middle of fulfilment decades ago. What the language-model wave added was the unstructured edge that used to be the whole reason a person sat there: a supplier's free-text reply, a request that does not fit the form, a document that does not match the template. The climb is steady rather than sharp because each of those edges is a separate integration, bought and configured one at a time, not a single capability arriving at once.
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.
Written about this#
These pieces argue from the same records this page holds, and each of their sections names what it rests on.
Method and sources#
- Assessment date
- 2026-09-11
- Basis of the task judgements
- 3 evidence-backed · 3 platform inference · 0 not enough evidence
- Verified events
- 2