How to Write If-Then Plans for a Reporting and Follow-Up Routine

Every aviation training team has routine reporting and follow-up work: logging events, passing on information, chasing the missing form. When that work depends on memory and goodwill, things slip. The nine steps below turn a reporting and follow-up routine into a set of if-then plans, so the right action fires without anyone needing to remember it. It deals with the administrative side only; how events are classified and handled is set by your organisation’s own safety procedures and the regulator, and nothing here replaces them.

What you will need

You need very little: a shared document or note that everyone on the team can open, thirty minutes with the people who run the routine, and a recent set of examples where follow-up went wrong or went late. Real examples matter more than imagination, so gather three or four before you begin.

Step 1: Map the routine in plain words

Write the routine as a short sequence of ordinary steps, with no jargon. For example: a report comes in; someone acknowledges it; someone passes it to the responsible person; that person replies; the record is closed. Keep it to what actually happens now, not what the manual says should happen. If you spot a step that nobody owns, mark it. Unowned steps are where reports go to sleep.

Step 2: Find the points where things stall

Look at your examples and ask at each step: what usually goes wrong here? Typical answers include an acknowledgement that never gets sent, a hand-off with missing detail, a reply that arrives late and a record left open for weeks. Circle the three stalls that appear most often. These are the places that deserve a plan; ignore the rare ones for now.

Step 3: Write the trigger

A trigger is the observable event that tells you a plan applies. Make it something a colleague could confirm without asking you. “A report has been in the inbox for a full working day without an acknowledgement” works. “The report seems to be getting ignored” does not, because it asks for a judgement. Aim for a trigger with a clear time, a clear status or a clear missing item.

Step 4: Write one response

Choose a single action that can start straight away and that moves the matter forward. For the unacknowledged report: “send the standard acknowledgement message and note the date on the record”. For the hand-off with missing detail: “return it to the sender with the checklist of missing items”. Avoid combining several tasks in one response. If you feel the urge to add “and then”, you probably have two plans.

Check that each response stays within the role of the person who will carry it out. Where a step needs a decision from a manager or from the safety lead, the response is to inform that person and record that you did so.

Step 5: Name an owner and a deadline

Each plan gets one owner, even if several people could do the job. Next to it, put the time by which the response should happen: for instance, “within one working day”. With an owner and a clock, the plan stops being a good intention. If your team is small, the owner may be the same person for every plan, which is fine as long as a deputy is named for absences. A line such as “if the owner is away, then the deputy acts” makes your system sturdier at little cost.

Step 6: Put the plans where they will be seen

A plan nobody sees cannot fire. Place the list on the page the team already uses: pinned in the group chat, at the top of the shared tracker or printed beside the desk. Resist the temptation to create a new tool. If people must open something unfamiliar, they will not.

Step 7: Cover the logistics around the routine

Reporting does not happen in a vacuum. Staff move between sites, attend courses and travel for work, and a device without data can hold up follow-up for days. Add a few logistics lines: if a team member will be travelling abroad for work, then they confirm how they will stay connected before they leave. For those heading overseas, a travel-focused website that compares SIM and eSIM options sets out its content by country, provider and plan, with guides to read alongside, which makes pre-trip checks quick. A second line might read: if the shared tracker cannot be opened on the road, then send a short message to the deputy so the item is not lost.

Step 8: Test the plans on past cases

Take your three or four examples and run each through the new plans as if the trigger had just fired. Would the response have prevented the delay? If not, the trigger was probably too late or the response too weak. Adjust and test again. This replay costs an hour and saves weeks of finding out the hard way.

Step 9: Start small and review weekly

Do not launch all your plans at once. Begin with the top three stalls, run them for a couple of weeks and then add more. At a short weekly meeting, spend five minutes on two questions: which plans fired, and what happened when they did? Rewrite anything that was unclear and remove any plan that has been unnecessary for a long stretch.

Example set for a small training team

  • If a report has had no acknowledgement for a working day, then the desk owner sends the standard acknowledgement and notes the date.
  • If a hand-off arrives with items missing, then the receiver returns it with the missing-items list the same day.
  • If a reply is overdue by two days, then the owner sends one reminder and tells the manager that a reminder went out.
  • If a record has stayed open for longer than the agreed period, then the owner puts it on the agenda for the next team meeting.
  • If the owner is away, then the deputy acts and notes it on the record.

Common mistakes

The first is writing plans that duplicate existing formal procedures. If a rule already exists in your manual, point to it and do not restate it. The second is making triggers depend on opinion. The third is forgetting about absences; plans that work only when everyone is in the office fail on the first holiday. The fourth is never removing anything, which leads to a list so long that nobody reads it.

One last tip: keep the language of your plans the same as the language your team already uses. If everyone says “close the loop” or “chase the sender”, write it that way. Plans phrased in familiar words get used; plans phrased in formal wording get admired and ignored.

Wrapping up

The result of these nine steps is a short, practical list that keeps your reporting and follow-up moving without anyone having to remember to nag. You will spend a little time at the start and save much more across the year. Begin with your three worst stalls, give each an owner, and let the routine take care of itself.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top