The Shop's Most Valuable Operating System Is in People's Heads

In the maintenance shops we work with, everyone knows who to ask.

The person changes with the question. An IA or seasoned A&P remembers a recurring discrepancy and what finally resolved it. Someone in parts knows which supplier came through when the regular sources could not. A service manager remembers the customer conversation behind an unusual request. The owner knows why the shop handles a recurring situation the way it does.

That knowledge is part of how the shop runs. It was earned over years, one aircraft and one difficult situation at a time.

Some of it is easy to retrieve from a work order or the maintenance records. Some lives in estimates, emails, vendor conversations, and customer notes. Some of it exists only in one person's memory.

Accessing it usually depends on knowing who remembers. Someone walks across the hangar, makes a phone call, or sends a message. The person with the answer may be working on an aircraft, dealing with a customer, or trying to finish something that requires their full attention.

Experience should remain central to maintenance. The shop should not have to interrupt an experienced person just to recover facts and reasoning it has already learned.

The shop should not have to relearn what it already knows

An airplane comes back with a familiar discrepancy. The last work order shows the corrective action and the part that was installed. What it often does not show is the rest of the visit: what was checked first, which possibility was ruled out, whether a measurement changed the direction of the troubleshooting, and whether the repair actually ended the complaint.

The technician on the airplane now knows who to ask. That person is in another bay, on the phone, or already gone for the day. If they can be found, the shop gets the story. If they cannot, the research begins again.

The same pattern shows up in parts, in the office, and in estimates. Parts personnel remember which suppliers accepted an order and then failed to deliver. Someone preparing an estimate may know that a particular configuration adds access time. The final number alone tells the next person very little. They need the facts that changed the scope, and why.

Whenever an operating decision is likely to come up again, the useful knowledge includes both the result and the reason behind it. Without that, the shop can document every transaction and still find itself rebuilding the explanation later.

Keep what the shop learns with the work

An experienced person cannot be expected to document everything they know before anyone needs it. The practical time to retain useful knowledge is while the work is being done and the details are still clear.

When a shop resolves a recurring discrepancy, finds a source for a hard-to-find part, learns which intake question prevents a surprise, or discovers what needs to be captured before closeout, that knowledge should remain connected to the work that produced it. It should be available the next time the same aircraft, component, customer, or situation comes through.

A searchable archive is better than relying on memory. Search still requires someone to know the information exists and go looking for it. The better result is for relevant history to appear with the work already in front of them: prior troubleshooting with the current work order, sourcing history with the part and aircraft configuration, customer preferences with the customer, a closeout requirement while the task is still open.

None of this should be treated as permanent. Vendor availability changes. Customer preferences change. The shop may revise its own procedures. Someone using prior information should be able to see when it was recorded, where it came from, and whether it was later corrected.

Past work is a starting point

Knowing what happened last time does not mean repeating it without question.

The same symptom can have a different cause. A previous sourcing option may no longer be available. A customer may want something different today.

For technical work, the current condition of the aircraft and current applicable maintenance data still govern. The appropriately certificated and authorized person remains responsible for the technical decision.

Prior work gives that person a better starting point. They can see what was observed, what was tried, and what happened afterward. Their time can go toward comparing that history with the aircraft in front of them.

Preserving experience does not mean reducing it to a checklist. The shop is making prior facts and reasoning available so the current discussion can concentrate on what still requires judgment.

Start with the questions people keep asking

A shop can find the first opportunities by paying attention to the questions that keep reaching the same people.

For one week, notice what repeatedly gets directed to an IA, a seasoned A&P, someone in parts or service, someone in the office, or the owner. Some questions require new judgment. Others are requests for information the shop has already established.

What did we replace last time? Who had the part? What did the customer approve? Why did the previous estimate include additional labor? What needs to be photographed or measured before access is closed?

Choose one recurring question and follow the answer back to its source. Did it come from memory, an old work order, an email, or another vendor call? Could the next person have known the answer without first knowing who to ask?

If not, change the process so the useful context is captured with the work and appears the next time it matters.