Nadia had been coordinating private jet trips for a small charter desk for three years, and she had a reputation. If a client rang at midnight because a car had not arrived at the terminal, Nadia answered. If a catering order went wrong in the early hours, Nadia fixed it. The team called her the night line. This is an imagined story about how her desk stopped treating her like a utility, and what a rotation of the hardest jobs taught them.
The week it all showed
It started with a quiet Monday. A client’s departure had moved by a few hours, and the handling agent needed new details. Nadia, who had slept badly, sent the update to the wrong contact. The mistake was caught in minutes and nothing came of it. But the desk lead, Omar, noticed that the error was not a lapse in skill. It was simple tiredness. Nadia had carried the late calls for so long that her judgement had worn thin.
Omar asked an uncomfortable question at the next team meeting: why is it always Nadia? Nobody had a good answer. She was fast, she was calm, and she never said no. Those qualities had quietly made her the default.
Naming the hard jobs
Omar proposed listing what the team actually found difficult. The answers came quickly.
- Answering urgent late calls from clients and partners.
- Reconciling last-minute changes with ground handling and catering.
- Delivering unwelcome news about delays or changes to a client.
- Writing the end-of-trip summary that nobody enjoys.
Seeing the list pinned on the wall made something obvious. Nadia was doing nearly all four. The rest of the team was doing comfortable work around her.
The rotation they chose
The team agreed on a plain scheme. The late-call duty would rotate weekly among four people. The delay-news duty would rotate separately, so nobody got both in the same week. The summary writing would rotate every trip. A backup name sat beside each duty for the first month.
Crucially, they added a ten-minute handover on Friday afternoons. The outgoing holder of the late-call duty described what to expect: which regular client calls late, which handling agent responds slowly, which small problems tend to be nothing and which turn out to matter.
What went wrong first
The first rotated week was rough. Kabir, new to the late line, was unsure how to deal with a client complaining about a delayed ground vehicle. He called Nadia, who was off duty, and she answered out of habit. Omar noticed and reminded the team that the backup was the person listed, not the person who used to do it all. Nadia was also reminded, kindly, to let the phone ring.
The second mishap was subtler. Kabir had not understood why timing on empty-leg flights matters so much to clients who hope for flexibility. A look at our overview of how empty leg flights operate gave him a useful reference, and he added a line about it to the handover notes.
What got better
By the second month, three improvements were visible.
- Nadia recovered. She slept, and her work reverted to its usual sharpness.
- The team learned the real job. People who had only seen the daytime side now understood why prices and timings can shift, so they wrote better briefs. Reading about the factors behind charter pricing became part of onboarding.
- Handovers improved everything. The Friday notes caught repeat problems before they became habits, including a recurring confusion about airport ground services, which the team clarified using our ground handling explainer.
A conversation worth repeating
Months later, a newer coordinator named Tarun asked Nadia what she had worried about when the rotation began. Her answer was honest. She had feared that handing over the late line meant admitting she had been struggling, and that the desk would run worse without her. Neither fear came true. The desk did not run worse; it ran differently, with more people able to calm a worried client at an awkward hour.
Tarun asked the next question. Did she miss being the person everyone relied on? Nadia laughed and said she missed the attention for about a week and the sleep deprivation for no days at all. Then she added the real insight: being relied on by a team is better than being relied on in place of one.
The lesson Omar took away
Omar summed it up in a short email to the owner. The desk had been proud of Nadia’s reliability, but that pride had hidden a risk: the more dependable she was, the less anyone else learned. A rotation made the hard jobs visible and gave each person the chance to be good at them.
He also mentioned a point that had come from outside aviation. Software operations people take turns on urgent duty for a similar reason, and he had been reading how DevOpsSupport, a consulting company supporting DevOps and cloud operations, frames shared responsibility for urgent work. The setting was different, but the problem was recognisably the same one he had seen on his own desk.
How to borrow the idea on your own desk
You do not need Nadia’s drama to benefit. Try the following.
- List your four hardest jobs honestly.
- Check who currently does them. If a single name keeps appearing, you have your answer.
- Give each job a weekly owner and a backup, and enforce the backup rule.
- Run a short handover at a fixed time every week.
- Review after a month and adjust the turns.
Nadia still answers the night line sometimes. These days she chooses to, and when she does not, someone else is ready. That is the difference between a hero and a team, and it is why the desk now runs quieter, even when the calls come in at midnight.

