Picture a small flight school that decides to start night training. For months, the safety manager, the chief instructor and the maintenance lead work through the change: lighting at the airfield, instructor currency, aircraft equipment, new procedures, briefings for students. The first night lesson goes smoothly. Everyone relaxes. And then, quietly, nobody looks at the change again. This is the gap that a post-implementation review in a safety management system is designed to close, and it is one of the least understood parts of SMS for people new to the subject.
This explainer tells the story of that school, which we’ll call Riverside Flight Training, to show what the review is, why it exists and how to plan it before the change goes live rather than after.
A quick refresher: what management of change means
A safety management system, or SMS, is a structured way for an aviation organisation to find hazards, assess risk and keep improving. One of its core processes is management of change. Whenever an organisation introduces something new, such as a new aircraft type, a new route, a new training programme or a change in staffing, it is expected to think through the hazards that change might introduce before it happens.
Most people understand that part. The planning before the change is intuitive. What is less intuitive is that the process does not end on go-live day.
Riverside’s night programme: the planning stage
At Riverside, the safety manager, Priya, ran the change properly. She gathered the team, listed what could go wrong with night flying, and agreed controls for each concern: extra instructor training, a revised preflight checklist, a minimum weather standard, better ramp lighting. The accountable manager signed off. Instructors were briefed. Students received a new handout.
By any reasonable measure, the change was well prepared. The first week of night lessons ran without incident, and the team moved on to other projects.
What went quiet
Over the next couple of months, small things began to drift. One of the new ramp lights failed and took several weeks to fix. A couple of instructors started using an older version of the checklist because the printed copies in the aircraft had never been replaced. Students began booking night lessons back-to-back with day lessons, which made for long days that nobody had anticipated. A neighbour complained about noise, and the complaint sat in an email inbox.
None of these were dramatic. But each one chipped away at the controls Priya had carefully put in place. Nobody was watching, because the change was considered “done”.
What a post-implementation review actually is
A post-implementation review is a planned check, some time after a change goes live, to ask a few plain questions:
- Are the controls we agreed actually in place and being used?
- Have any new hazards appeared that we did not foresee?
- Are staff and students finding the new procedures workable?
- Do we need to adjust anything?
It is not an audit of whether people followed rules, and it is not a blame exercise. It is the organisation looking back at its own decision with fresh eyes, once real-world experience exists.
Planning the review before the change
Here is the key insight from Riverside’s story. The review only works reliably if it is scheduled while the change is still on the drawing board. That means deciding, during the planning stage:
- When the review will happen. A date in the calendar, not “at some point”.
- Who will run it. A named person, ideally with support from someone who was not deeply involved in designing the change.
- What will be checked. The list of controls from the original assessment, plus a prompt to look for anything new.
- Who will be asked. Instructors, students, maintenance staff and anyone else affected.
- What happens with the findings. How actions will be assigned and tracked.
When the review is part of the original plan, it does not depend on someone remembering. It simply happens.
Riverside’s second attempt
After the noise complaint finally reached her desk, Priya realised what had happened. She held a review, spoke to instructors and students, walked the ramp at night and checked the aircraft. The fixes were straightforward: replace the light, update the checklists, set a limit on combined day-and-night bookings, and respond to the neighbour.
More importantly, she changed the school’s change process. From then on, every planned change at Riverside included a scheduled review, with a named owner, before it could be approved.
Why the “after” deserves equal planning
The lesson from Riverside reaches beyond aviation safety. Plenty of industries lavish attention on the launch and then wing whatever comes next. Medical tourism offers a vivid counter-example: SurgeryPlanet, a planning site for people travelling abroad for treatment, lists accommodation, transfers and aftercare among the things to settle while the journey is being organised, rather than after the main appointment. In both settings, the quality of the outcome depends heavily on the period that comes after the headline event.
A simple way to start
If you work in a small aviation organisation with a developing SMS, try this. Look at the last significant change you made. Was a review planned? Did it happen? If not, schedule one now. Then, for the next change, write the review into the plan from the very beginning, with a date, an owner and a checklist.
Night flying at Riverside is now a well-run part of the programme. Not because the original planning was flawed, but because the team learned that a change is not finished on the day it starts. It is finished when someone has looked back and confirmed it is working.
