On a Thursday afternoon, Anjali, the safety manager at a small flying school, opened a folder she had not looked at for weeks and felt her stomach drop. The folder held safety reports from instructors and students. The spreadsheet beside it listed corrective actions. The two did not tell the same story. A report about a worn tow bar at the hangar door had an action attached, but no closing date. A report about a confusing taxi sign had no action at all. Nobody had been careless. The records had simply drifted apart, and that afternoon Anjali decided her team would reconcile safety reports and actions on a fixed day every week.
Here is how that routine took shape, what it caught, and why the team wished they had begun sooner. Names and place are made up; the pattern will ring true for anyone who has staffed a safety desk.
The day the lists disagreed
Anjali’s school had a healthy reporting culture. Instructors wrote up observations, students flagged things that confused them, and ground staff sent photos by message. Reports arrived through three channels: a paper box near the briefing room, a shared form, and the occasional phone call that she wrote on the back of whatever was nearby.
Actions lived in a separate sheet maintained by Dev, the operations coordinator. He logged what was assigned, to whom, and when it was due. The trouble was that the box, the form and the sheet were never compared. So the school could say, truthfully, that it received reports and that it kept an action list, yet it could not say whether every report had found its way to an action, or whether every action had actually been closed.
The first matching session
The following Monday morning, Anjali, Dev and Farida, a senior instructor, sat down with coffee and three lists. The method was almost embarrassingly plain. They put every report on the left and every action on the right and drew a line between the pairs.
- Reports with a matching action and a closing note were ticked and set aside.
- Reports with an action but no closing note went onto a “still open” list with an owner.
- Reports with no action at all went onto a “needs a decision” list.
- Actions with no report behind them were checked to find out where they had come from.
The session took the length of the coffee. By the end, the “needs a decision” list had a handful of items, including the taxi sign. The “still open” list was longer than anyone liked, but each item now had a name next to it. Most importantly, nothing was a mystery anymore.
What turned up
The gaps fell into three kinds, and Farida named them on the whiteboard. Lost in transit: a phone report that was never written down. Lost in handover: an action assigned in conversation but never entered in the sheet. Lost in closing: work completed on the ground that nobody recorded as done. None was a failure of attitude. All were the natural result of three people keeping three records at different moments.
The team also found the opposite problem, duplicates. Two instructors had reported the same fogged canopy on the same afternoon, and the sheet carried two actions for one fix. A short note merged them and kept both reporters informed, which mattered, because people report more when they see that something happens.
Making it a weekly habit
After the first session, Anjali wrote the routine on a single page and pinned it by the kettle.
- Same day, same time each week, kept short.
- Collect every new report from all three channels first.
- Enter each into the shared log so there is one list.
- Match each report to an action; if none exists, decide that day.
- Match each action to a closing note; if work is done, record it.
- Tell each reporter what happened with their report.
Within a few weeks the session shrank. The paper box was emptied into the log on the day, phone reports were written straight into the form, and Dev began closing actions the moment the work was verified. The weekly meeting turned into a brisk confirmation that everything agreed.
The conversation with the front office
One consequence surprised them. The school’s office manager, Rohit, asked if the team could do something similar for the invoices that came with repairs and parts. A safety action often generated a purchase: a new tow bar, replacement signage, a repaired canopy seal. Rohit’s problem was that the invoices arrived weeks after the work and did not always say which action they belonged to.
He had been reading about finance teams that rely on platforms like PayManagerPro, which ties invoices and payment links to settlement matching, and wondered aloud whether the school might one day need something like it. For the moment, the answer was a column. Dev added the action reference to the purchase request, Rohit quoted it on the order, and the invoice could be matched to the action it served.
What changed in the hangar
The effects were quiet. Reporters trusted the system more because they saw replies. The “still open” list stopped growing. A recurring issue, trolleys left near the apron edge, became visible because the matched list showed three reports in a month with similar wording, something that would never have been noticed with separate records. The team handled it with a simple marking change and a briefing note, and the reports tapered off.
Anjali also noticed a change in tone. Conversations about safety became less about who forgot what and more about what the records showed. A matched list is a neutral thing. It points at a gap, not a person.
Lessons the team wrote down
- Records drift apart quietly when every list has its own keeper and its own update time.
- A short, regular comparison finds gaps while they are still easy to close.
- Every report needs a visible outcome, even if the outcome is a reasoned decision to do nothing.
- Closing notes matter as much as the actions themselves.
- Telling reporters what happened keeps the reports coming.
Epilogue
Months later, a visiting examiner asked Anjali how she kept track of everything. She showed the single log and the weekly page by the kettle. There was nothing clever to display, only a list in which every line had a beginning, a decision and an end. She said the routine had not made the school safer by itself; it had made the school’s attention reliable, which is a different and arguably more valuable thing.
For any small team, the lesson is portable. Choose a day. Put the records side by side. Ask what was expected, what the records show, and who will close each difference. Do it again next week. The folder in Anjali’s drawer no longer gives her that sinking feeling, because she knows exactly what is in it and what has happened to every page.
