A few seasons ago a passenger sent a charter desk a message at eleven at night: “Is everything fine for tomorrow?” The coordinator on duty read it three times. Fine in what sense? The departure time, the catering, the car that meets the aircraft, the paperwork for the guests? She replied with a cheerful “Yes, all on track” and went to bed. By morning the passenger was upset about a detail that had never been confirmed, because nobody had known it mattered. The lesson from that kind of night is the reason for this checklist: in private aviation, a clear question to your charter desk is part of the service, and you can audit your own questions the way a crew audits a pre-flight list.
Why a vague question gets a polite non-answer
Charter coordinators are trained to be reassuring. Faced with an open question, they answer the most likely version of it. That is a kindness, but it can hide the very thing you wanted to settle. A question that names a specific item gets a specific reply, with a person’s name, a time or a confirmation attached.
The audit: run your message through these seven checks
Before pressing send, read your draft and tick each item. If you cannot, add a sentence.
- Does it say what the trip is for? “A family of four travelling to a wedding with small children” shapes the answer in ways that “a flight on Friday” cannot.
- Does it name what you have already arranged? If you booked the ground transfer yourself, say so, so the desk does not assume otherwise.
- Does it state what you were expecting? “I understood the aircraft would be ready for boarding forty minutes before departure” reveals the assumption you want checked.
- Does it describe what you were told or saw? Quote the itinerary line or the earlier message instead of paraphrasing it.
- Does it isolate a single item? One topic per message, or a numbered list, makes it easy to confirm point by point.
- Does it say what you need back? A confirmation, a time, a name, a written note. State it.
- Does it say by when? A deadline helps the desk prioritise, especially around busy holiday weeks.
A rewrite you can borrow
Here is how the eleven o’clock message could have looked after the audit: “We fly tomorrow with two adults and two children under ten. I understood the car would meet us at the aircraft steps and that the child seats would already be fitted. Could you confirm both in writing tonight? If the seats are not arranged, please tell me, so we can bring our own.” It runs five lines. It would have saved a morning.
What good looks like on the receiving end
Ask any experienced coordinator which messages they enjoy, and they will describe the same thing. The sender knows the plan and says so. The sender mentions the one detail that worries them. The sender tells the desk what would make the day easier. Those messages let the coordinator do real work, such as calling the ground handler, double-checking a catering order or moving a boarding time, instead of spending the first half hour decoding the request. In a business where trust is built on small confirmations, a passenger who asks precisely tends to be served precisely, and the relationship improves with each trip.
For the crew and coordinators reading this
The audit works from your side as well. When you send a status update, check that you have said what the passenger can rely on and what remains open. A candid “this part is confirmed, this part we are still chasing” is warmer and more useful than a blanket reassurance.
There is also a good case for keeping your own copy. After the desk replies, paste the confirmation into one note on your phone, together with the time you received it. If a plan shifts on the day, you and the crew can compare the same words rather than competing memories, and the conversation stays friendly because it begins from shared text.
Borrowing habits from other communities
Technology people have spent years refining the art of the well-shaped request because software faults are hard to describe. A glance at Debug School, a site where IT operations practitioners and students share what they have learned, shows the same discipline in a totally different domain: say the situation, say the attempt, say the surprise. You do not need to follow the technical detail to see how the writing works.
Pairing questions with background knowledge
You will ask sharper questions if you know how things usually run. Our note for newcomers on what is expected of passengers stepping aboard a helicopter for the first time covers behaviour and boarding practice, and the article on understanding what high-end travellers want from a provider shows what operators try to anticipate, which in turn tells you where a clear request can fill a gap.
A final pocket version
- Purpose of the trip, in a clause.
- What you arranged yourself.
- What you expected to happen.
- The exact line or message you are relying on.
- The one thing you need confirmed, and the time you need it.
Keep that list in your phone notes. When the temptation comes to type “Is everything fine?”, pause for half a minute and fill in the blanks instead. The reply you receive will be shorter, firmer and far more likely to describe the morning you actually get.

