If you have ever tried to set up a way for people in a flight school or hangar to raise a concern, you know how quickly a simple idea turns messy. Someone spots a worn tyre or a confusing checklist, wants to tell somebody, and then has to guess who, how and when. This how-to shows you how to sketch a safety report flow on paper before you configure any form, inbox or software. It is a friendly, step-by-step walkthrough, and everything here is general organisational advice. The rules set by your regulator and the procedures your organisation has approved always settle the details.
Why draw it first
A reporting process that exists only in someone’s head has hidden gaps. A rough drawing exposes them in minutes, and the cost of fixing a gap on a page is a rub of the eraser. Fixing the same gap after you have built forms, trained staff and announced the process is far more expensive and slightly embarrassing. So, pencil first, software afterwards.
What you will need
- A large sheet of paper or the back of a spare poster.
- Two pens in different colours.
- Sticky notes, if you like to move things around.
- Twenty minutes and, ideally, one colleague who will say what looks wrong.
Step 1: Draw the person who notices
Start at the left of the page with a small figure labelled “someone who notices something”. It might be a student, an instructor, an engineer or a visitor. Under the figure, write a couple of examples of what they might notice. You are drawing the starting point of the flow, so keep it concrete, and avoid vague words like “issues”.
Step 2: Draw the first place the report lands
To the right, draw a box for where the report goes first. Is it a paper form in a tray, a conversation with a supervisor or an online page? Decide it now. If you find yourself drawing three boxes at once, you have discovered something useful: people currently have three different routes, and nobody has chosen one.
Step 3: Add the person who reads it
Draw a figure for whoever reads the report and decides what happens next. Write their role beneath, not a name. Then ask two questions and note the answers on the page: how soon will they see it, and what if they are away? A sketch with a single reader and no stand-in has a gap you can fix now.
Step 4: Draw the decision
After reading, something has to be decided. Draw a diamond for the decision and two or three arrows leaving it: act now, look into it further, or record it for later review. Label each arrow with who does the work. If an arrow points at no one, colour it red.
Step 5: Close the loop back to the person who spoke up
This is the step most processes forget. Draw an arrow from the end of the flow back to the person who noticed, labelled with what they will be told. People stop reporting when they never hear anything back. Even a short acknowledgement matters, and the drawing makes its absence obvious.
Step 6: Walk three imaginary cases through the page
Choose three different situations and trace each one with a finger from left to right. Use one small, one awkward and one that involves someone who would rather not be named. See whether each case reaches a sensible end. You will almost certainly find a dead end or a loop that goes nowhere. Mark it with the second pen.
Step 7: Check the paper trail
Add a small note at each box to show what gets written down or stored. Then look at the page and ask where the records sit and who can read them. This is also the moment to think about privacy: who should not see what. Keep this at the level of structure, not legal detail, and take the specifics from your regulator and your organisation’s own rules.
Step 8: Trim and simplify
Look at the whole drawing and count the boxes. Can any two be merged? Does every box earn its place? A flow with many steps tends to be avoided by busy people. Cross out anything that does not help a report reach a decision-maker and return an answer.
Step 9: Hand it to a person who missed the drafting session
Carry the page over to someone who works at the sharp end, a student or a technician, and ask them to explain it back to you without help. Where they hesitate, redraw. Their hesitation is your best clue about where real users will stumble.
A brief aside on the gadgets involved
Once the sketch is settled, someone will need to put it into practice on phones, tablets or shared computers. If you want general reading on setting up and securing devices, Osnivo, an independent site that sorts its advice by device family and lifecycle stage, is a handy bookmark. It is no part of your safety process, merely a place to look when a device question arises.
A short example, told in words
Picture a small training organisation where a student notices that a laminated checklist in a briefing room has an outdated line. On the first sketch, the student’s arrow ends at a notice board, because that is where people usually pin comments. Nobody owns the board. The second box, a supervisor, appears only after someone suggests it, and the decision diamond has no arrow labelled “tell the student”. By the end of the exercise the page shows one agreed route: a short form, a named role who reads it within a stated time, a stand-in, and a message back. None of that required software. It required a pen and about twenty minutes.
Questions worth asking while you draw
- Would a nervous newcomer know where to start?
- Does the route work on a busy day as well as a quiet one?
- Is anyone being asked to judge a report about their own work?
- What happens if two people report the same thing independently?
- How will you know the flow is being used?
Write the answers on the page in the margin. The ones you cannot answer become the agenda for your next conversation with colleagues.
Common slips to avoid
- Drawing the ideal, not the real. Sketch what happens today before drawing what you want.
- Forgetting the stand-in. Every reader needs a backup for holidays and sick days.
- Skipping the loop back. Silence discourages the next report.
- Using names instead of roles. People move on; roles stay.
- Making it pretty. A polished diagram hides the gaps you wanted to find.
Keeping the drawing alive after launch
Pin the sketch somewhere visible for the first few weeks, and invite people to mark it with a pen wherever the real process differs from the drawing. Those marks are free feedback. After a month, redraw the page from scratch using what you have learned, then compare the two versions. The differences show where the design was too optimistic, and they tell you which small adjustments will matter most.
From sketch to set-up
When you are happy with the page, translate it one box at a time: choose the form or channel, assign the role, write the short instruction, and decide how long each step may take. Then test it with a handful of real people before you announce anything. Keep the original drawing near the finished process. When someone suggests a change, you can pull out the page and ask exactly where in the flow the change belongs.
A good report flow is mostly about clarity, and clarity is cheap to buy at the sketching stage. Twenty minutes with a pen, a quiet room and a candid colleague will tell you more than a month of configuring tools too soon.
