The call came on a Friday afternoon. A charter customer’s itinerary had been confirmed, the aircraft was ready, and yet the dispatch desk could not tell whether the contract captain scheduled for Saturday was still cleared to use the operator’s booking system. Her paperwork said one thing, the roster said another, and the access list said something else again. Nobody had done anything dramatic. Three records had simply drifted apart, and the drift is exactly what PeopleOps exists to prevent. This is a short diagnosis in the form of a story, with the fix laid out at the end.
The symptom: three lists, three answers
The operator in this made-up scenario is small, with a mix of employed staff, freelance crew and seasonal ground handlers. It keeps an HR spreadsheet, a crew roster and a list of who has logins to the booking and flight-planning tools. Every list is maintained by a different person, and every person believes theirs is the accurate one.
Anyone who has run a charter business will know the pattern: a freelancer still visible in the booking tool months after the last contract; a new ground handler who could not log in on the first morning; a returning pilot whose old permissions reappeared without anyone choosing to grant them. None of these is an emergency alone. Together they tell you the operation has no single, trusted account of who is part of it today.
The diagnosis: the lifecycle has no owner
PeopleOps, as described in the Atlas write-up on running the employee lifecycle, begins with a simple observation: hiring, onboarding, role changes, pay, performance and exit are a chain of transactions, and a chain needs owners. The Atlas pictures three parts: an effective-dated record that acts as a ledger, owned transitions that behave like a state machine, and a service desk with written response times. Our fictional operator had none of the three. It had lists.
Walking the chain turned up four specific faults.
Fault one: contractors fall between departments
The freelancers were engaged by the operations manager, paid through accounts payable and never entered in the HR sheet. The Atlas flags this pattern, noting that temporary-staff contracting often belongs to procurement and that orphaned contractor accounts are a common failure. If nobody records the start and end of a freelance engagement, nobody can end the access either.
Fault two: a rehire inherits the past
The returning pilot was reactivated from her old record, so her old permissions came back with it. The source’s advice is to restore the identity but with no prior access, and then grant what the current role needs. Convenience here is the enemy of control.
Fault three: the exit that happened during leave
One ground handler had resigned while away on leave. The roster showed him as on leave, the HR sheet as resigned, and the access list as active. The Atlas lists separations during leave as one of the risky arrows in the lifecycle, because no routine day-to-day trigger fires for a person who is not at work.
Fault four: the no-show
A seasonal handler never turned up, but accounts had already been prepared for him. They stayed live for weeks. Another listed risk, and another case where a daily comparison would have caught the problem.
The treatment: five small changes
- One list of people. Merge the HR sheet and roster into a single record that includes freelancers, with a permanent identifier per person. When systems need to match, they match on that identifier, not an email address that may change.
- Dates on everything. Every contract and role change is entered with its effective date, including future ones, so the closing of access is planned rather than remembered.
- A named owner for each transition. One person is responsible for joiners, one for movers, one for leavers. Write the names on the page.
- A daily comparison. Every morning, list people who are marked as left or inactive and compare them with people who still hold access. An alert goes to the owner, not a report to a folder. The Atlas is blunt about this: someone terminated in HR and active in identity must raise an alarm.
- A rule for the edge cases. Rehires start with no inherited access. No-shows trigger a review after a set number of days. Resignations during leave are handled as leavers on the effective date.
There is also a service dimension. Dispatchers and crew need somewhere to ask where their access stands, ideally a short self-service page for the common questions and a named person for anything that needs a judgement call. The Atlas describes this as tiers, starting with self-service and rising to specialists and policy owners, plus a private route for sensitive employee matters that never touches a shared inbox. Even a two-tier version, a one-page guide and a single responsible person, removes a surprising amount of Friday-afternoon panic.
How the fix felt in practice
The first daily comparison produced an embarrassing list: five people who should not have had access, including two freelancers from the previous season. It also produced relief, because the list was short enough to fix before lunch. After two weeks the number settled near zero, and the owners had learned which exceptions caused most of the noise.
The operator added two light measures. One was the share of leavers whose access closed within the written deadline, which the Atlas illustrates with a one-hour policy. The other was readiness for new joiners on their first morning. Both numbers were reviewed monthly in a ten-minute meeting, with a named person assigned to any gap.
What to borrow if you run a charter business
A large team is not required. The source suggests that a very small single-country business needs one accountable owner and a reliable provider, not a department, and it labels its size guidance as editorial rather than a benchmark. What you do need is a habit of looking at the lists side by side. Our archive’s piece on what high-end clients want when they hire a private aircraft, as a provider should see it argues that trust is built in small details, and that principle extends to the crew and ground staff behind the aircraft. For a lighter example of detail-led service, see the advantages of private car transfers to and from the airport.
A caution before you act
This is an operational story, not legal advice. Contractor status, employee data and record retention are treated differently from one country to the next, and the rules move, so check the specifics with a qualified professional. And keep the spirit of the exercise humane: the aim is to know who is part of your operation and to make their first and last days smooth, not to watch what individuals do.

