Aviation safety management starts from a simple idea: people who do the work should be able to say what could go wrong, and the organisation should listen. That idea depends on a lot of small written things, such as a hazard report form, a short procedure, or a briefing card. This explainer is about one habit that makes those documents better: showing a rough draft to someone who will actually use it, before it goes out, and asking them a specific question.
What do we mean by a rough draft?
A rough draft is a version you would not be proud to publish. It may have missing steps, awkward wording and a title that does not quite fit. That is fine. The only requirements are that it is complete enough to be understood and open enough that you are willing to change it. Think of it as a sketch on a whiteboard, not a framed picture.
Why not just finish it first?
Because finishing takes time, and time spent on the wrong version is wasted. Suppose you are writing a one-page form for reporting a hazard on the ramp. You choose the headings, the order of the questions and the wording of each box. You spend an evening on it. Then someone who works on the ramp looks at it and says they would never have time to fill in six boxes during a shift. Now the whole structure has to change. If you had shown them a list of the questions on a scrap of paper first, you would have heard the same remark in two minutes.
Who should see it?
Choose someone who would use the document in real life, not just someone who is good at reviewing. A person who will have to fill in the form, follow the checklist or read the briefing is the best reader, because they instantly notice anything that does not fit their working day. A second reader can be a colleague who understands the subject and can say whether the content is sensible. Two is enough. Too many opinions can make you lose sight of your own aim.
What do I say when I hand it over?
Say three things. First, that it is rough and you expect to change it. Second, what you want to know, for instance “is anything here confusing or too long?” Third, when you would like to hear back. You might write: “Here is a first sketch of the form. I am only asking whether the questions are in a sensible order and whether anything is missing. No need to worry about layout. Could you let me know by Thursday?”
- Be specific: one question beats five.
- Be brief: the shorter your request, the faster the reply.
- Be open: invite criticism, and mean it.
Why does this matter more for safety documents?
A safety document helps only when people really pick it up and follow it. If a form is confusing, people skip it. If a procedure is too long, people shorten it in their heads. Those problems are almost never visible to the author, who knows what was intended. They are plainly visible to the person who has to follow it. That is why involving the future user early is not a courtesy but a practical step toward a document that gets used.
This explainer is general information only. It does not replace your organisation’s own approval process or the official requirements that apply to safety documents. Early feedback is about making a draft clearer and more usable, and final sign-off always goes through the proper channels.
What does good feedback sound like?
It is usually concrete. “I did not know what ‘contributing factor’ meant here” is good. “I would not have time for this at the end of a shift” is good. “I like it” is pleasant but not very helpful. When a reader gives you vague praise, ask a small follow-up: “Was there any point where you had to stop and think?” That nudges them from general approval to something you can use.
What should I do with the feedback?
Write each comment down and give it one of three labels: change now, look into it, or leave. Changes that fix confusion or remove steps are usually worth making. Comments you do not understand deserve a quick follow-up conversation. Suggestions that conflict with each other can be resolved by asking each person why they said it; the reasons often reveal different working situations rather than real disagreement.
Are there examples outside aviation?
Plenty. Any community that depends on contributions learns to ask early. A public website such as KeralaOrbit, a Kerala events site that sits next to its own discussion board, articles and place pages, depends on visitors to ask and answer questions. The lesson for a safety team is simple: make it easy for people to speak up, and respond kindly when they do.
How often should I do this?
Whenever you write something other people will rely on. Keep the whole thing informal. A brief message and a half-page draft will do, and you can be done in an afternoon. Over time, you will notice patterns in the feedback you receive, such as a tendency to use jargon or to put the most important point too late, and you can fix those habits at the source.
A quick recap in plain words
- Write a rough version, without polishing.
- Show it to someone who will use it.
- Tell them it is rough and ask one question.
- Sort their comments and change what helps.
- Thank them and show the result.
It is a small routine, but it changes the way documents are made. Instead of presenting a finished piece and hoping it lands, you invite the readers in while there is still time to listen. In a field that takes learning from mistakes seriously, that is entirely in keeping with the spirit of the work.
