A worker who lands without a current ticket is not a paperwork problem. Here is how to price the flights, the beds and the lost shift, so the delay stops being invisible.
The cheapest sentence in the industry
"We'll sort it when he gets to site."
Every mobilisation coordinator has heard it. Most have said it. It is usually said on a Thursday afternoon, about a worker flying Sunday, regarding a ticket that expired last month or a medical that has not come back yet or an induction the client portal will not release until something else clears. And it feels reasonable in the moment, because the alternative is pulling a name off a manifest and having an awkward conversation with a project manager who needs bodies on Monday.
The problem is that the sentence has a price, and nobody in the room can see it. The cost of a slipped mobilisation does not appear on any invoice with the words "mobilisation slip" on it. It is smeared across a flight change fee in one cost centre, an extra camp night in another, a day of unbillable wages in a third, and a blown productivity assumption in the project baseline where no one will ever trace it back. Because the cost is invisible, the behaviour never changes. Because the behaviour never changes, the cost repeats every swing.
So let us make it visible. Let us actually price one.
Anatomy of a slip
Take a single, completely ordinary case. An electrician is mobilising to a mine site in the Pilbara for a shutdown. He is on a Sunday flight, starting Monday. On Friday, someone notices his working at heights ticket expired three weeks ago. Nobody caught it earlier because it lives in a spreadsheet that gets checked when someone remembers to check it.
Option one, you pull him from the flight. Option two, you fly him anyway and sort it at site. Both options cost real money. Walk through them.
If you pull him: the flight change or cancellation fee, typically a few hundred dollars on a charter seat that may simply be forfeited. A refresher course that cannot be booked until Tuesday, call it $400 plus a day of paid, unproductive time. A rebooked flight Wednesday. Three nights where the project is running one electrician short during a shutdown, which is the one scenario where labour shortfalls translate directly into schedule risk. If the shutdown critical path slips even a few hours because a crew was under strength, the cost has just jumped from hundreds to tens of thousands, because shutdown hours on a major asset are priced in lost production, not in wages.
If you fly him anyway: he lands Sunday night, occupies a bed, eats camp meals, and presents at the gate Monday where the client's system, quite correctly, refuses him. Now he is on site but not on the job. He sits in the wet mess or the training room while someone begs the client rep for a supervised exemption that may or may not be permitted. You are paying his hourly rate, his camp costs, his flight, and getting zero output. If the exemption is refused, you fly him home again and you have paid for everything in option one plus a return flight, two camp nights and two days of dead wages. And you have spent something less tangible: the client has now watched you send a non-compliant worker to their gate, and clients keep score.
Cost either way, on a boring, single-person, garden-variety slip: somewhere between $2,500 and $6,000 in direct, countable money, before any schedule impact. Now multiply by how often it happens. If your business mobilises a few hundred people a month and even five per cent of mobilisations slip in some form, you are quietly burning a mid six-figure sum every year on a problem your management reports do not have a line for.
The costs that never make the spreadsheet
The direct costs are the ones you can price. The indirect ones are worse.
The rework tax. A slipped mobilisation is never handled once. The coordinator rebooks the flight, re-requests the bed, resubmits the access application, re-notifies the supervisor, updates the tracker, and answers the same "where is he?" question four times. Industry rule of thumb from anyone who has done the job: a clean mobilisation is touched a handful of times, a slipped one is touched twenty or more. Your mobilisation team's capacity is not consumed by mobilisations. It is consumed by re-mobilisations. This is why the team always feels understaffed even when volumes look manageable on paper.
The credibility drawdown. Every contractor holds an invisible account with every client. Turn up compliant and on time, the balance grows. Send someone to the gate who gets refused, it draws down. The balance is what you are spending when you ask that client for a favour, an exemption, a fast-tracked approval, an extension. Slips do not just cost money, they cost the currency you need to fix future slips, which is a nasty compounding loop.
The worker experience cost. The electrician in our example did nothing wrong. The expiry was visible to his employer for months. But he is the one sitting in a demountable feeling like a spare part, being messaged by his supervisor asking why he is not on the tools. Do that to people often enough and the good ones, the ones with options, go work for the contractor across the road who seems to have their act together. In a tight labour market, mobilisation competence is quietly a retention tool.
The planning corrosion. When project managers learn that mobilisations slip, they respond rationally: they pad. They ask for crews earlier than needed, request more people than the plan requires, and build buffer into every estimate. Padding means extra flights, extra beds and extra standing time, all purchased as insurance against a process nobody trusts. The cost of unreliability is not just the failures. It is the insurance everyone buys against the failures.
Why it slips, and why it is nobody's fault in particular
Here is the awkward part. Almost every slip, examined afterwards, was knowable weeks in advance. The ticket had an expiry date printed on it. The medical had a booking lead time everyone knew. The client induction had a published turnaround. Nothing about the failure was a surprise in the information-theory sense. It was a surprise only in the organisational sense, meaning the information existed but was not looked at by the right person at the right time.
That happens because mobilisation, in most contracting businesses, is a relay race run across systems that do not talk. Recruitment confirms the start date in one tool. Training records live in another, or in a spreadsheet. Medicals sit with a provider. Flights and camp sit in the client's booking portal. Site access sits in a different client portal with its own login, its own formats and its own moods. The mobilisation coordinator is the integration layer, a human API, copying data between systems and holding the dependencies in their head.
Human integration layers are remarkably good, right up until volume rises, or the coordinator goes on leave, or two shutdowns land in the same fortnight. Then the dependencies stop fitting in one head, and the process fails in exactly the way you would predict: silently, at the weakest link, discovered at the gate.
Blaming the coordinator is the standard move and it is the wrong one. You do not fix a relay race by yelling at the runner who dropped the baton you greased.
Pricing it is the fix, or at least the start of one
You cannot manage what you refuse to count, so start counting. Three practical moves.
Give the slip a cost code. Literally. Create a way to tag flight changes, forfeited camp nights, dead standing time and repeat course bookings as mobilisation slip costs. It will be imperfect and people will forget to use it. It will still, within a quarter, produce a number large enough to change the conversation. The difference between "mobilisation is a bit clunky" and "mobilisation slippage cost us $480,000 last year" is the difference between a moan and a business case.
Measure clean mobilisation rate, not mobilisation count. Most teams report how many people they mobilised. Report instead the percentage who arrived at site, on the planned day, fully compliant, with zero rework touches. That single metric captures everything: data quality, lead time discipline, client portal performance and internal handoffs. When it becomes a number leadership sees monthly, the upstream behaviours start correcting themselves, because now someone owns it.
Push the deadline upstream of the flight. The gate is the worst possible place to discover a problem and the flight is the second worst. Set an internal compliance gate, seven to ten days before travel, at which every requirement must be green or the mobilisation formally escalates. Escalation, not workaround. The point is to move the awkward conversation from Sunday at the airport to the previous Tuesday at a desk, where it costs a phone call instead of a shift.
None of this requires new software, though software helps once expiry dates and requirements live somewhere that can look forward rather than backwards. It requires deciding that a slipped mobilisation is a costed operational failure, like a safety incident or a defect, rather than weather.
The shift you get paid for
The whole game in contracting is having the right people, compliant, at the right place, on the day the client is paying for them. Everything else, the recruitment, the tickets, the flights, the beds, is scaffolding around that one delivered shift.
A slipped mobilisation is a shift you built all the scaffolding for and never delivered. You paid for the recruitment, the training, the flight and the bed, and the one thing you did not get is the only thing the client buys. Priced that way, mobilisation stops looking like administration and starts looking like what it actually is: the last hundred metres of your entire revenue process.
"We'll sort it when he gets to site" is still the cheapest sentence in the industry to say. It is just one of the most expensive to mean.
