What to Do When Your Best Maintenance Engineer Retires

Every plant has someone who knows why the machine does what it does. They know which fault code is really a dirty sensor, which guard needs a shove to seat properly, and why Line 3 trips on cold Monday mornings. It isn't in the manual and it isn't in the CMMS.

Then they hand in their notice. Here is a practical way to handle it, whether you have six months or six weeks.

1. Work out what actually walks out of the door

Don't start by asking the engineer to write everything down. Nobody can, and it won't be read. Start with a short list instead:

• The ten faults that come back most often on your problem machines.
• The jobs only this person is called for, on or off shift.
• The workarounds nobody has written up, and the reasons for them.

Ask your shift leads which calls go to this engineer's phone. That list is usually more honest than any audit.

2. Capture the fix while it's happening, not afterwards

Engineers explain things best with the machine in front of them. The next time one of those ten faults occurs, film it on a phone. Ask them to say what they're doing and why as they go. A two-minute clip with a spoken explanation holds more than a page of notes, and it takes far less of their time.

Where there's no fault to film, walk the machine with them and ask questions: "What do you check first?", "What would you never do on this machine?", "What did the manual get wrong?"

3. Mark up what you already have

Manuals and SOPs are often nearly right. Ask the engineer to flag the pages that are wrong, out of date or missing context. Photograph the annotated page or the handwritten note taped inside the cabinet door. That tells your team where the written documentation can't be trusted by itself.

4. Make it findable by someone who wasn't there

This is where most handovers fail. A folder of videos called "Dave stuff" is no use at 2am. Whoever captures the fix should name it by machine and symptom, for example "Line 3 labeller: intermittent trip on start-up". It needs to sit with the manual and the work orders for that machine, and it needs a short written summary.

5. Check that someone else can use it

Pick a colleague who doesn't know the fault. Give them the captured material and ask them to talk you through the fix. If they get stuck, the gap is in the capture, so fix that while the engineer is still around to ask.

Where software helps

Doing this by hand works, but it depends on people searching folders and watching clips. A knowledge tool like Machine Mesh brings the manuals, work orders and captured fixes together, so an engineer can ask a question in plain language and see the supporting source. It doesn't replace the conversation with the person who is leaving. It makes sure the conversation isn't wasted.

The short version

• List the repeat faults and the jobs only one person is called for.
• Film fixes with spoken explanation, in the moment.
• Annotate the documents that are wrong.
• Name and store everything by machine and symptom.
• Test it with someone who wasn't there.

You won't capture everything. You'll capture the things that stop the line, and that is the part that matters.