Picture a flight academy with forty staff, three training sites and a head of operations who has just realised that she is also, unofficially, the person in charge of hiring, payroll queries, instructor onboarding and who still has a hangar key. The academy below is invented, and so are the people in it, who appear by job title only. But the ninety days it goes through are a realistic way to see what PeopleOps looks like when a small team decides to take it seriously.
Day zero: the awkward Monday
It began with an ordinary mess. A new ground instructor arrived on a Monday to find no desk, no tablet and no schedule. The week before, an instructor who had left for an airline was discovered to still have access to the student records system. The operations head mentioned both episodes to the school’s part-time bookkeeper, who happened to have read about a discipline called PeopleOps and passed along the Ops Atlas explainer on PeopleOps.
Two things from that page stuck. First, the page admitted that the label mostly relabels ordinary HR work, which meant nobody had to feel intimidated. Second, the useful part was the habit: treat the staff lifecycle, from hire to exit, as an operation with owners, records and measurable timing.
Days one to thirty: draw the journey, name the owners
The operations head started on a whiteboard. Hire, paperwork, first day, training, role change, pay, review, exit. Beside each box she wrote who currently did it, and for three boxes the answer was nobody in particular. That was the first finding, and the group nearly laughed.
They chose a tiny structure. For a business of this size the Atlas leans toward one named owner and a trustworthy payroll partner, with no department, though it labels its size bands as editorial guidance. So the operations head became the owner, the bookkeeper stayed with payroll, and a senior instructor agreed to act as the buddy-in-chief for newcomers.
They also gave each person a permanent staff number and put every record in one shared register, with dates for when each fact took effect. When the chief flight instructor announced a move to the second site starting the following month, the register showed it immediately and the future date triggered a reminder to review his permissions.
Days thirty-one to sixty: go live carefully
The source describes a stage it calls go-live, where a new system is run alongside the old one before the old one is retired. The academy took the idea to heart on a small scale. For one pay cycle, the bookkeeper kept the old spreadsheet and the new register side by side and reconciled them line by line. Two entries differed, both from a change in hours that had been recorded in only one place. Catching them cost an hour, and it won the team’s trust in the new routine.
In the same month they wrote a short first-week plan for new starters. The manager would supply a thirty-sixty-ninety day outline by the third day, a named buddy would sit with the newcomer on the first morning, and the equipment would be waiting. The Atlas is also candid about surveys: one large company’s 30, 90 and 365-day onboarding survey was valuable because of the changes it drove, not because of the questions. The academy ran a three-question check-in after two weeks and, importantly, wrote down one change made in response to it.
The leaver check
The most useful routine was the smallest. Every Friday the bookkeeper compared two lists: people marked as having left, and people who could still log in. In the first week, one name appeared on the second list that should not have. In the second week, two shared logins were identified that belonged to no one in particular. By week four, the lists matched.
The awkward exceptions
Around week six, the team sat down and listed the situations most likely to go wrong, borrowing the idea of risky arrows in the lifecycle. A newly hired instructor who withdrew before the start date while accounts were already prepared. A part-time controller who resigned during a long period of leave and therefore never triggered the usual departure routine. A seasonal lineman returning after eighteen months. For each one they wrote a single sentence describing what should happen and who would do it. The page took twenty minutes to draft and has been pinned beside the register ever since.
The exercise surfaced one more gap: the academy’s flight-simulator contractor had a login but did not appear on any staff list, because the contract was handled by the finance side. The Atlas notes that routing temporary-staff supplier arrangements through procurement is common, and that orphaned contractor accounts are a typical consequence. The fix was dull and effective: every external person with access now appears in the register with an end date.
Days sixty-one to ninety: run it, then review it
With the basics stable, the team set three modest targets and an easy review habit. They wanted every new starter ready on their first morning, every leaver’s access closed on the day, and no statutory paperwork overdue. Those targets echo the example goals in the source, which names thresholds like at least 95 percent readiness on day one and 99 percent of leavers closed within an hour, though it presents them only as illustrations. The academy tracked its own baseline instead, and celebrated the first month in which nothing was late.
They also added one rule that mattered more than expected: when a former instructor later returned for seasonal work, the register recreated the identity without restoring the previous permissions. The returning instructor received exactly what the current role required, nothing inherited.
What the story is meant to show
Nobody in this story purchased software or hired a specialist. They did four things: gave the lifecycle owners, put dates in the record, compared two lists on a schedule, and reviewed the numbers in a short monthly meeting. The conversation is the same one you would have about any aircraft: who is responsible, what is the standard and how do we know it was met.
If you are exploring how structured preparation reduces risk in aviation, take a look at a rundown of safety slips charter passengers should watch for and a guide to booking errors first-time charter customers make, both of which show how a checklist mindset prevents avoidable problems.
A closing thought
The academy’s next step is a yearly review of its policies and a look at how long records are kept. That is deliberately dull, as good operations tend to be. Remember also that employment and data rules differ by country, so any real academy should ask a qualified adviser to confirm what applies to it before changing contracts or storing staff data.

