Two charter desks, two very different mornings. At the first, a client’s departure is delayed by a crew-scheduling glitch and the phone rings for forty minutes before anyone with authority picks up. At the second, the same glitch triggers a calm, scripted response: a named coordinator, a first message to the client within minutes, and a clear promise about the next update. The aircraft, the airport and the fault were identical. What differed was the method. That method has a name in technology operations, IncidentOps, and this comparison sets the two styles side by side so charter coordinators can see which one they resemble.
Round one: how the problem gets named
The improvised desk waits until the problem is undeniable. Someone mentions it in passing, another person hopes it will clear, and by the time a manager hears about it the client has already called twice. The organised desk uses written triggers. In technology teams these often read: another team is needed, a customer can see the damage, or the trouble has lasted about an hour. For a charter operator the translation is easy: a passenger-facing delay, a handoff to a ground handler, or an unresolved issue past the first hour.
The Ops Atlas, summarised on its IncidentOps reference page, stresses the economics. Calling an incident that turns out to be minor wastes a few minutes. Calling late wastes hours. A desk that treats every early flag as a small win will outperform one that treats it as an admission of failure.
Round two: who is in charge
On the improvised desk, the loudest or most senior person tends to take over, usually by diving into the problem. The organised desk separates the commander from the fixer. The commander keeps the whole picture, decides priorities and does not personally rebook aircraft or ring suppliers. The hands-on group, the only people changing the plan, works under that direction. One person writes updates to clients; another keeps a log.
There is a subtle human point here. The Atlas observes that roles are hats rather than titles. The managing director may be wonderful at relationships and still be a poor choice to coordinate a live disruption at midnight. A trained duty officer can wear the commander’s hat and invite the director to be the client-facing voice for a high-profile passenger. It feels like a demotion until you see it work.
Round three: what clients hear
Luxury clients rarely mind a delay as much as they mind ignorance. The improvised desk gives updates when somebody has time, and the tone shifts with whoever picks up the phone. The organised desk works to a clock. A first note goes out inside roughly five minutes, a scope note follows, and after that nobody waits more than twenty minutes for news while the first two hours play out. Even “no change, next update at 14:20” is valued.
Reassurance is part of the product, a point familiar to anyone who has read the article on what high-end passengers want from the operator they charter with. The Atlas also records a case that shows the cost of missing it. A major software company’s multi-day outage in 2022 affected hundreds of customer sites, and the first broad public message came roughly forty-one hours after the damage began. Whatever the technical reasons, customers noticed the silence.
Round four: fix or explain
The improvised desk wants to know whose fault the delay is before moving. The organised desk gets the client moving first. If a crew timing problem is detected, the generic mitigations are obvious: swap in a standby crew, switch the aircraft, rebook a ground transfer, or offer a lounge. None of them requires a perfect explanation. Explanation comes in the review.
The same attitude helps with ground logistics. A late aircraft that leaves a client waiting at the kerb is a more manageable problem if the transfer has already been rebooked, a theme explored in the site’s discussion of why private car transfers suit airport journeys. Treat the car, the crew and the cabin as one system with one commander, not three separate conversations.
Round five: the night shift change
Disruptions do not respect shift patterns. The improvised desk lets the departing duty manager drift off with a vague “it’s all in hand”. The organised desk uses a spoken exchange in which the outgoing coordinator says the incoming one is now in command and waits for a clear yes, with a written summary of the state of play, the leading theory and the pending actions. It takes a minute and removes the nightmare scenario in which two people each believe the other is steering.
The Atlas also advises against letting the response bloat. When more than about five people report to one coordinator, form sub-teams, say a crew-and-aircraft group and a client-and-ground group, each with its own lead, and keep the commander above the noise. Observers get an announcement channel instead of a seat at the working table.
Round six: the morning after
The improvised desk closes the day with relief and moves on. At the organised desk somebody is already assigned to write the debrief while the incident call is still open. The meeting happens within days, ideally run by a colleague who stayed out of the response, and it produces a handful of tasks, each carrying one name and one deadline. Long lists of good intentions are a classic trap; so are actions phrased as “be more careful” and the habit of closing items by calling them lower priority.
The Atlas also warns against the neat verdict of human error. It quotes a safety researcher’s point that hindsight makes past choices look simpler than they were. For a charter business that is good news, because it moves the discussion from “who was on shift” to “what in our process made this slip likely”.
Round seven: measuring what happened
The improvised desk reports an average delay. The organised desk knows that one very long event distorts any average, so it tracks how long detection, first response, mitigation and resolution each took, plus the share of follow-up actions finished on time. It is also careful with labels, because the abbreviation for mean time to repair is used for several different phases in the wider industry. A group of sceptical researchers tested the averages against real incident data and found that real improvements were often invisible in the noise.
Scorecard
- Naming the problem: the organised desk wins by acting on written triggers instead of gut feel.
- Command: the organised desk wins by separating decisions from repairs.
- Client messaging: the organised desk wins on rhythm, honesty and a clear closing note.
- Immediate action: the organised desk wins by reaching for reversible fixes first.
- Handover: the organised desk wins with a spoken, confirmed transfer of command.
- Learning: the organised desk wins with short, owned, dated actions.
The improvised desk does keep one advantage, which is flexibility, and a good organised desk preserves it by treating the written rules as defaults rather than handcuffs. Choose the method that your most stressful Friday evening would thank you for. Write a single page, assign the hats, rehearse once, and let the next delay prove the difference.

