Aircraft work rarely finishes in one sitting. A job on the hangar floor may begin with one technician, pause for a missing part, and resume with someone else on the next shift. That gap is where mistakes breed, and it is why a clean aircraft maintenance handover deserves more attention than it usually gets. The questions below are the ones workshop leads and parts buyers tend to raise, and the answers lean on observation and common practice rather than slogans.
What exactly is an aircraft maintenance handover?
It is the transfer of an unfinished task, together with enough context for another person to continue it safely. The task might be a component swap, a part-sourcing request, an inspection that spans two days, or a records check. The handover is complete when the receiver can state, in their own words, what has been done, what has not, and what comes next.
Note the wording. The test is the receiver’s understanding, not the sender’s note. A beautifully written page that nobody can act on has not handed anything over.
Why does so much go wrong at the changeover point?
Three patterns appear repeatedly. First, the person leaving is mentally elsewhere and compresses the account. Second, the person arriving assumes that anything not mentioned is fine. Third, the physical evidence is ambiguous: a part sitting on a bench might be serviceable, awaiting inspection, or waiting for disposal, and only the person who put it there knows which.
Each pattern is a failure of labelling more than a failure of skill. Experienced workshops respond with tags, status boards and written entries that name the state of every item, so that nothing relies on memory or goodwill.
What should a good handover note include?
An analytical way to answer this is to list the questions a stranger would need answered in the first ten minutes:
- Scope: which aircraft, which task, which reference document governs it.
- Completed steps: each one named, with who finished it and when.
- Open steps: where work stopped, and whether the stop was planned or forced by a missing item.
- Parts and materials: what is on hand, what is on order, what was removed and where it now sits.
- Hazards and quirks: anything that behaved unexpectedly or that the next person should treat with care.
- Contacts: who can answer a question about each area, and when they are reachable.
If a line is empty, write “none” rather than leaving it out. A blank field and a considered “none” look similar on a page, but they tell the reader very different things.
How does the parts side of a handover differ?
Sourcing work hides more loose ends than most people expect. An open purchase may have been quoted, discussed on the phone and half approved, and none of that shows up in an order system. When a buyer leaves or changes role, the successor inherits requests whose history lives in someone’s head.
A tidy parts handover lists each open request with its status, what was agreed verbally, what documents still have to arrive, and what the requesting technician is waiting for. It also pairs naturally with good buying habits. Our notes on common slips buyers make with flight-control parts make a handy checklist for the receiver, because the usual pitfalls are easier to dodge when the previous buyer has said which ones they already ran into.
Does hardware need special treatment in a handover?
Small items such as fasteners and fittings create disproportionate confusion because they look interchangeable. A tray of loose hardware left on a bench tells the next person nothing about where it came from or whether it is going back on the aircraft. Label the container, state the purpose, and say whether anything has been counted. For a refresher on why this category needs such care, see the overview of rivets, bolts and other small aircraft hardware.
The principle is not specific to hardware. Any item whose status cannot be read from its appearance needs a label that does the talking.
Who signs off, and does the handover change that?
A handover moves the work, not the accountability rules that already govern it. Release, inspection and sign-off steps stay with the people and procedures that your organisation and its regulator require. What a good note does is make those steps easier to honour: it shows which stages have been signed, which are still waiting, and which documents the next person must see before putting a signature on anything.
The temptation is to let the incoming person infer the state of the paperwork from the state of the aircraft. Resist it. Paper and metal drift apart quietly, and the note is where you pin them back together by stating plainly which inspection entries exist and which do not.
Should handovers be reviewed afterwards?
A quick look back after a week pays off. Ask the receiver which lines of the note they used, which they ignored, and what they wished it had said. Over a few weeks the template sharpens itself, shedding fields nobody reads and gaining the one or two that keep getting asked about.
How long should the handover conversation take?
Observation from busy workshops suggests short and structured beats long and rambling. A typical effective pattern has three beats: the sender walks the receiver through the note, the receiver repeats the key points back, and both look at the physical work together where possible. Where a face-to-face is impossible, a written note plus a short call covers most of the ground.
Keep the allowance for follow-up questions open for a defined window. Once the window closes, ownership is the receiver’s alone.
What if the person leaving cannot be reached afterwards?
This is the scenario that justifies the whole practice. People change jobs, fall ill, or go on leave. If your process only works when the previous owner is a phone call away, it does not work. Test it by asking a colleague who was not involved to read the note and describe the job back to you. Every wrong turn they take marks a sentence that needs rewriting.
Is this relevant when the work is done by outside specialists?
Yes, and perhaps more so. Contractors come and go by design. Software projects that support parts catalogues, records or ordering are often built by freelancers on short engagements. Browse a directory like DevOps FreeLancers, a portal that arranges DevOps freelancers by country, and you can see how routine short technical engagements have become. The practical lesson for a parts business is that the end of any outside engagement is a handover like any other: what was delivered, what is partly built, where it is kept, what to watch.
What is the single best habit to adopt?
Write the handover before the last hour of the job, not during it. People who leave the note until the final minutes produce shortened versions, and those are the ones that cause rework. A note drafted while the details are fresh and revised at the end is almost always better than one rushed at the door.
What does a clean handover cost, and what does it save?
Time is the only real cost: a few minutes per changeover. The saving is harder to measure but easy to recognise. It is the absence of the phone call asking where something is, the repeated inspection because nobody trusted the previous check, and the stalled job waiting for someone to find a document. Workshops that adopt the habit seldom go back, because the benefit is felt by the whole crew on the next shift.
If you take one thing from these questions, make it this: the work is not finished until the next person can continue it with confidence. Everything else in the note is just a way of proving that.

