Operations coordinator

Taking what was sold, working out what it actually requires, booking each piece in the right order, and confirming every piece is locked before the date arrives.

Emailing, calling and re-calling suppliers until availability, price and time are confirmed in writing, then noticing when a reply contradicts the last one.

Something fell through at an hour when nobody answers: deciding in minutes what the least-bad rearrangement is, who to wake up, and what the customer is told.

Permits, manifests, insurance certificates, customs forms — collecting them, checking the names and numbers match, and catching the one field that is wrong before it stops everything.

The status field says confirmed and the supplier has not replied. Reconciling what the system believes with what has actually happened, before someone downstream acts on the wrong one.

Spot-checking what the workflow booked, confirmed and sent on its own, and finding the confident error — the one that looks like a normal record and is not.

One US-listed freight brokerage. What makes it unusual is that the hardest alternative explanation is ruled out inside the same filing: in the same quarter total revenue rose from $4.14bn to $4.93bn (+19.3%) and income from operations from $216m to $256m (+18.4%), so this is not a demand-driven cut. By segment, North American Surface Transportation went from 5,283 to 4,671 and Global Forwarding from 4,436 to 3,699. What it does not establish needs saying: the filing does not break the reduction down by role or task, so which task was automated is our attribution and not the company's statement; the company itself names natural employee turnover alongside automation as a factor in timing; and a brokerage's coordination work is unusually digitisable because its inputs are already electronic, so this does not transfer to operations roles whose inputs are physical.

Verifiable change in hiring, headcount, hours or job scope. Highest weight — but causal attribution still has to be argued, not assumed.

This used to be one of the most reliable ways into a company without a specific degree: start by chasing confirmations and filing documents, learn how the business actually works from the inside, move up. Those two starting tasks are the ones automating fastest. Expect to be hired into exceptions and relationships instead — which is the part that used to be earned after two years.

Your value has moved from throughput to the phone call: which supplier will take your call at midnight, what this customer will actually tolerate, and which rearrangement is the least bad. None of that is in the system. The risk is that it is also not in any report — so when headcount is reviewed, your contribution reads as the absence of incidents.

Stay and strengthen

Make the exceptions countable

The part of this job that survives is the part nobody logs, which is why it is invisible in a headcount review. Coordinators who record what broke, what it would have cost, and what they did have an argument; the ones who just handle it have a feeling.

Reshape the role

Own the workflow, not the queue

Someone has to decide which steps the system may take unattended, what it must escalate, and how often its output is sampled. The people who know where it goes wrong are the ones running it — and in most companies nobody has been given this job.

Adjacent move

Move upstream, to where supply is decided

Coordination automates faster than procurement, because deciding what to buy and from whom involves negotiating terms and carrying the consequence. Your knowledge of which suppliers actually deliver is the scarce input to that, and it does not exist in any database.

Cross-industry

Cross into the systems side of operations

Every company running this kind of workflow needs someone who understands both the operational reality and how the software encodes it. That person is almost always a former coordinator, because the failure modes are only obvious to someone who has been burned by them.

The routine half is going quickly: booking in sequence, chasing confirmations, checking documents. What does not go is the night a plan breaks and someone has to decide, spend money and tell the customer. Most operations roles are mostly the first half, so the honest reading is a much smaller team of more senior coordinators, not an empty function.

Count it yourself, in your own system. Take the orders your team handled last month and work out what share went from booked to delivered without anyone touching them. Then do the same for the same month a year ago. That share is the fraction of your job that has already left, and it moves before any announcement does — in most operations teams it is visible a year before headcount changes.

Chasing confirmations first, then document checking, then sequencing the booking itself. All three are reading-and-acting on information that already exists somewhere. Reconciling the record is being assisted rather than removed. Exception nights and supplier relationships are the parts nothing on the market currently does.

Because the work changed shape rather than disappearing. When booking was manual, a missed step was obvious and stopped there. When it runs unattended, the failures are completed steps that were wrong and look right — so you moved from doing to sampling, and sampling has no natural end point. Nobody set a rate, so the honest answer is usually that you are doing an unfunded second job.

For the chasing, yes — a timed follow-up is strictly better than a forgotten one. For the commitment, read it first. The failure that costs money is not a clumsy email, it is an automated message that accepts terms, a price or a date nobody authorised. Check what your tool is allowed to agree to before you check what it is allowed to send.