Private charter runs on details: who is the passenger contact, what time the car meets the crew, which catering order goes in, which request changed at the last minute. If those details sit in one coordinator’s head, a sick day can unravel a booking. This guide shows how to write a charter-day runbook, a short numbered routine that lets any trained team member handle a trip the same way. It is practical, general information. It never replaces operator procedures, regulatory rules or the official documents that govern flight operations.
Step 1: pick one repeating task
Do not start with “everything about charter.” Start with a single task you perform often, for example “receive a trip request and confirm the details with the client.” Choose the one that causes the most back-and-forth within your team. Write its name at the top of a blank page.
Step 2: do it once with a note-taker
Have the person who knows the task perform it while a colleague writes down every action in order, including small ones like checking the time zone or confirming the passenger spelling. People skip steps they consider obvious, and those are the steps a newcomer needs most.
Step 3: turn the notes into numbered steps
Rewrite the notes into short lines starting with verbs. A request-handling page might read like this.
- Log the request time, requester name and contact number.
- Confirm departure point, destination, date, time and number of passengers.
- Ask about luggage, special requests and any needs the traveller wishes to share.
- Send a written summary of the request back for confirmation.
- Pass the confirmed summary to the operations contact and record who received it.
Step 4: add the money and rules line
Every charter page benefits from one clear line about commercial points: where the price basis is explained to the client, and where the written terms are stored. Your team does not need to improvise answers on cost. To refresh the basics, the beginner’s walk-through in a first-timer’s overview of what private charter costs and the explanation of the elements that move charter pricing make good background reading for anyone filling in this section. Link to your own price documents on the page rather than copying numbers into it, since numbers change.
Step 5: write the fallback
For every runbook, decide the most likely thing to go wrong and write one line for it. A late client, a changed passenger count, a last-minute date shift. Write who to call and which decision belongs to whom. A fallback needs only two or three lines, but it is the part people reach for when stressed.
Step 6: add contacts and a finish line
Put phone numbers and email addresses on the page itself. End with a “done” statement: for the request routine, “done” might mean the client has a confirmed written summary and operations have it too. Without a finish line, tasks drift.
Step 7: test it on a newcomer
Give the page to someone new to the desk, and have them follow it while the author watches silently. Note every question. Update the page after each. Two rounds are normally enough.
Step 8: store, date and own it
Put every page in a single shared folder with a consistent name. Add the date and the name of the owner. The owner’s job is to review the page when anything changes and at least every few months.
A second example: the empty-leg inquiry
Some of the most repeatable tasks in charter involve flexible, short-notice flights. When a client asks about a repositioning flight, the same questions come up every time: flexibility on dates, how much notice, and what happens if the schedule moves. A page for that routine keeps the answers consistent. For the concept itself, the explanations of how repositioning flights offered at reduced fares work help you describe the idea accurately and without overpromising.
- Record the dates the client could move.
- Explain in plain words that availability depends on the operator’s schedule.
- Note that confirmation is subject to the operator’s own terms.
- Offer a standard alternative if nothing fits.
- Write down what you promised, so the next person does not contradict it.
Where this practice comes from
The runbook habit was sharpened in technical operations, particularly data and software teams who need repeatable responses when something breaks. A DataOps blog that publishes about the move from DevOps toward dependable data practice, TheDataOps.org, is one place to see how they talk about it. Charter desks can take the same discipline without any of the tooling.
Keeping the pages useful over time
A runbook earns trust through small corrections. After each trip that uses a page, take two minutes to ask the person who ran it whether anything on the page was wrong, missing or unclear. Make the change straight away while the memory is fresh. Over a season, this habit turns rough first drafts into pages that match how the desk really works.
It also helps to keep a short change note at the bottom of each page: the date, who edited it, and what changed. Colleagues glancing at the note can see at once whether the routine has been touched recently, and a newcomer learns that the pages are living documents rather than archive material. When the operator or a partner changes how they want something handled, the page is the first thing to update, before the next trip comes through.
Mistakes to avoid
- Writing for yourself. Write for the colleague who covers on your day off.
- Copying official procedures into your page. Link or refer to them instead, so there is one source of truth.
- Letting pages pile up unreviewed. Retire what is outdated.
- Hiding the pages. If nobody can find them in a minute, they will not be used.
Your next move
Choose the task that most often makes colleagues say “ask Priya, she knows.” Write it in eight lines today. Test it this week. Within a few weeks the shelf holds a handful of dependable pages, and the desk that no longer holds its breath whenever one person is off.

