Every organisation that works with aircraft depends on people knowing what to do next. Some of that knowledge sits in formal manuals. A surprising amount sits in a few experienced heads: the order in which the hangar is opened, how a job is passed to the next shift, what to say when something looks wrong. When one of those people is off sick or moves on, the knowledge goes with them. A runbook is a plain, short, written routine that keeps it in the building. This explainer describes what runbooks are, what they cover, how they sit alongside safety management work, and how a team can draft one. Treat it as general background; it can never stand in for official regulations, manuals or approved procedures.
The core concept, briefly
Picture a numbered set of steps for a recurring task, written clearly enough that a trained colleague can carry it out unaided when the usual person is absent.
That is all. It is not a policy statement, a training course or a regulation. It is the practical, day-to-day layer: the “who does what, in which order” of an ordinary working routine.
How it differs from other documents
Aviation organisations already hold several kinds of documents, and it helps to keep them apart.
- Regulations and approved manuals: formally controlled, they set what must be done. Only authorised people change them.
- Checklists for aircraft and equipment: official, type-specific, and followed as written.
- Safety management documentation: the organisation’s formal approach to identifying and managing risk, including how concerns are reported and reviewed.
- Runbooks: informal in status but disciplined in form. They cover the routine, practical tasks around the formal material, such as housekeeping, handovers and coordination.
The rule is straightforward. Wherever a runbook touches something covered by an official document, it points to the official document and does not restate it. If the two disagree, the official document wins and the runbook is corrected.
What a runbook page contains
Good pages are boring in the best way. They share a few features.
- A title that names the task, such as “Close the training building at night”.
- A trigger saying when the task starts.
- Numbered steps in order, each beginning with a verb.
- A named role for each step where it matters.
- A fallback describing what to do if the expected step fails, and who to contact.
- A finish line saying what “done” means.
- A date and an owner so everyone knows how current it is.
An everyday example
Consider handing a shared training aircraft’s paperwork folder from the morning instructor to the afternoon one. Without a runbook, the handover may be a hurried chat. With one, it looks like this.
- The morning instructor places the folder in the agreed location.
- They note the time and any unusual observation on the handover sheet.
- The afternoon instructor reads the sheet before touching the folder.
- Anything unclear is raised with the supervisor, not guessed.
- Both initial the sheet to show the handover took place.
Nothing here changes how the aircraft is inspected or released. It only makes the human handover consistent.
Why organisations bother
The benefits are practical.
- Continuity. The task is done the same way whoever is present.
- Faster onboarding. New staff learn the routines from pages rather than from weeks of shadowing.
- Fewer repeated questions. Experienced staff are interrupted less.
- Clearer improvement. When a step fails, there is a written baseline to correct.
Where the idea comes from
Runbooks became standard practice in technical operations, particularly where services must keep running and whoever is on call needs a clear procedure. Data engineering is a good example, and the TheDataOps.org site, with its articles on moving from DevOps toward dependable data operations, gives a window into how those teams reason about it. Their equipment has little in common with a hangar, yet the principle travels well: repeated work should never depend on a single person.
How to write one, in five moves
- Choose one task. Select a job that is repeated and that causes questions.
- Watch it done. Have a colleague note every action, including the ones that seem too small to mention.
- Draft the steps. Short lines, plain words, no jargon the newest team member would not know.
- Test it. Ask someone unfamiliar with the job to follow the page, and record where they pause.
- Review it with a supervisor. Confirm it does not conflict with any approved procedure.
A word on tone and length
Tone matters more than most authors expect. A page written in a stern, legalistic voice gets skimmed and ignored; one written in short, friendly, direct sentences gets used. Aim for the way a good colleague would explain the job at the bench. Length matters too. If a page cannot be read in under two minutes, it is probably two tasks, and dividing it gives each half a cleaner shape.
Finally, think about where pages live. Printed copies at the point of work, plus one shared digital folder, usually cover everyone. Make sure the printed and digital versions carry the same date, so nobody follows an old copy by accident.
Common misunderstandings
“It will replace judgment.” It does not. It covers the predictable skeleton so people can apply judgment where it matters.
“It needs special software.” It does not. A shared document or a printed sheet is enough.
“Once written, it is finished.” Pages need regular review. An out-of-date page can mislead.
“It belongs only to maintenance.” Routines exist in offices, classrooms, stores and dispatch desks too.
A short closing note
Written routines turn individual knowledge into shared capability, and they do it without drama. Begin with a single page, keep it short, let a supervisor check it against the approved material, and review it on a calendar. The first one is the hardest. After that, the habit tends to spread by itself.
