A charter coordinator named Lena once told a story at a dinner I attended. A client’s flight was set for early morning, the aircraft was positioned and the crew was rested. Then the one colleague who normally arranged the ground transfer fell ill the night before, and nobody else knew which car company she used, which terminal door the family preferred or what the passengers had said about dietary needs. The flight left, but the beginning of that trip was a scramble. “It was never the flying,” Lena said. “It was the knowledge that lived in one person’s head.” Her team has since written a booking-to-boarding routine, a runbook, and the story is a good doorway into six myths about how charter operations really keep their promises. This article is informational and general; every operator has its own regulations and procedures, which always prevail.
Myth 1: “Luxury service is all about instinct”
The picture many people hold is of a gifted concierge who simply knows what a client wants. Instinct matters, but the people who deliver consistent service also write things down. A great arrival may look effortless, yet behind it sits a list: confirm the lounge, confirm the car, confirm catering, confirm the passenger names against the manifest, confirm who meets whom. When instinct is the only system, the quality of the trip depends on who happens to be rostered that day.
A runbook does not replace the human touch. It protects it. Once the basics are guaranteed by the routine, the coordinator has the time to notice that a client prefers still water or that a child is nervous about flying.
Myth 2: “A written routine makes service feel robotic”
This is the objection teams raise first, and it is understandable. Nobody wants a client to feel processed. But the evidence of everyday experience points the other way: the most polished service tends to rest on dull, repeatable foundations. Think of a hotel that always remembers the guest’s name. It is not magic. It is a note in a system and a habit of reading it.
A good booking-to-boarding routine is deliberately plain. It might say: confirm passenger names and travel documents with the client; record preferences; brief the ground handler; check the transfer; send the client a single message with times and meeting point; and confirm on the morning. Each step is small. Together they leave space for warmth, since nobody is frantically trying to remember whether the car was booked.
Myth 3: “Only the big operators need this”
Small teams are in fact the most exposed. In a three-person charter desk, each person is a single point of failure for something. If the same colleague always liaises with the handling agent, her absence leaves a hole. Large operators have more people, but they also have more handovers between teams, shifts and time zones, and handovers are where details fall away.
So size is no excuse either way. A small desk benefits because one absence is a big share of the workforce. A big operator benefits because the number of conversations multiplies the chance of a gap. For perspective on what experienced travellers expect from the cabin and the service around it, the article on the preferences premium travellers bring to a charter shows exactly how much detail is worth capturing.
Myth 4: “Writing it down takes more time than it saves”
Expect the opening draft to cost an hour or two of somebody’s afternoon. The saving shows up quickly: each new coordinator learns faster, each handover is shorter, and fewer last-minute questions land on the senior people. A simple method keeps the cost low. For each recurring task, ask the person who does it best to talk through it once while a colleague types the steps. Tidy it into numbered lines. Pin it where it is used.
The routine should also carry the “done when” line that people forget: the observable sign that a task is complete, such as “the client has replied to the confirmation message” or “the handler has acknowledged the passenger list”. Nothing should be assumed complete until the sign appears.
Myth 5: “Passengers never see the routine, so it does not matter to them”
Passengers do not see the page, but they feel its absence. The transfer that does not arrive, the lounge that was not told, the wrong name on a card: these are the visible traces of a missing step. The ground leg is an especially common weak spot, because it sits at the edge of the operator’s control. A short checklist for it, covering pick-up point, contact numbers, backup plan and timing, makes a real difference. A piece on why private cars suit airport transfers explains why the arrival and departure legs deserve as much care as the flight itself.
Helicopter charters add their own details, from briefing passengers about approaching the aircraft to explaining baggage limits. A written briefing script means every passenger hears the same clear information, whoever is on duty. The etiquette notes for first-time helicopter passengers are a good starting point for what a briefing might cover, though the operator’s own safety briefing always takes priority.
Myth 6: “If something goes wrong, experience will fix it”
Experience helps, but only when someone with it is present. The day a delay or a diversion happens is exactly the day when the experienced person may be asleep, in the air or on holiday. A short “when plans change” page, with the first four calls to make, the information to gather and the person who may authorise changes, turns a panic into a procedure.
The aim is not to script every contingency. It is to make sure that the first ten minutes, which set the tone for the rest of the disruption, unfold in the same sensible order, whoever is covering the desk.
What a booking-to-boarding routine can look like
Here is an illustration of the shape, not a rule book. Adapt it to your operation and your regulations.
- At booking: record names as they appear on travel documents, contact numbers, preferences, and special needs.
- Forty-eight hours before: confirm aircraft, crew, handler, catering and ground transport; send the client a single message with the plan.
- Day before: re-check weather and timing with the operator; confirm the meeting point and the contact person.
- Morning of: confirm the car has left, the handler is ready and the passenger list matches.
- After landing: confirm arrival transfer and ask the client how it went, noting preferences for next time.
The preference record that travels with the booking
One page deserves special mention: the client profile. Charter clients often return, and the quiet pleasure of being remembered is one of the strongest reasons they do. Yet in many teams those details sit in the head of the coordinator who looked after them last time. A good profile page is short and respectful. It holds the practical things the client has told you they like: how they prefer to be contacted, seating or cabin arrangements the operator can honestly offer, catering notes, who usually travels with them and any accessibility needs. It leaves out guesses and gossip, and it respects privacy rules about how personal information is kept and shared.
When the profile is part of the routine, a colleague stepping in can greet a returning client as warmly as the regular coordinator would have. Nobody has to ask the client to repeat themselves, which is a small courtesy that clients notice.
A side note on where the idea comes from
Lena first met the word “runbook” in the software world. When she searched for how technical teams use it, she found TheDataOps.org, a blog where data teams read about keeping pipelines running dependably, and recognised her own problem in their language. The settings could hardly be more different, yet the lesson is the same: the work should not rest on one person’s memory.
The takeaway
Good charter service looks like hospitality, and it is. But it is hospitality with a spine of simple, shared routines. Writing them down does not make a team colder. It frees the team to be warm, because the essentials are covered. The next time someone says that their best coordinator “just knows”, ask what happens when she is away, and then ask her to teach the rest of the team, one page at a time.

