Capturing tribal knowledge before key employees retire

What counts as tribal knowledge in a trades business?#

Tribal knowledge in a trades business is the know-how that lives in someone's head instead of in the job record. It is the service manager who knows which rooftop units at a school district always need a second technician, the estimator who adds labor for houses from a certain building era, and the dispatcher who knows which technician a difficult customer will accept.

Most of it is not secret, just unwritten. It shows up as unexplained choices in the record: an estimate with extra hours and no note, a part substituted without a reason, a job assigned to the same person every time. When that person leaves, the choices stop, and the company relearns them through callbacks and lost bids.

Tribal knowledge also hides in habits that never reach any system: the supplier counter clerk a purchasing lead calls for hard-to-find parts, the inspector who wants a specific photo before signing off, or the commercial customer whose facility manager must be called before anyone touches the boiler. These are easy to miss because the veteran no longer thinks of them as knowledge.

Who should you interview first?#

The first people to interview are those whose decisions others cannot explain and who are closest to leaving. A retirement date matters, but so does concentration: a dispatcher with no backup can be a bigger risk than a senior installer surrounded by experienced crews.

Use the table to decide where each person's knowledge should end up before you schedule the first conversation. Knowing the destination keeps sessions focused on what the company will actually use.

Method one: structured interviews#

Structured interviews capture the reasoning behind routine decisions, and they work best when questions are about specific situations rather than general advice. Ask a veteran what they do, then ask what would make them do something different.

Record interviews only with the employee's agreement, and check how your state treats recorded conversations. Transcribe the recording, then ask the employee to correct the transcript; the corrections often add the most useful detail.

• 1Which jobs do you check personally, and what are you looking for?
• 2When do you override the standard price or labor estimate, and why?
• 3Which customers, buildings or pieces of equipment need special handling?
• 4What mistakes do newer technicians make that you catch?
• 5Which suppliers or parts do you avoid, and what do you use instead?
• 6What do you wish someone had told you in your first year here?

Method two: walk through real job records together#

Walking through real job records is the strongest capture method because it ties knowledge to evidence. Sit with the veteran in front of ServiceTitan, FieldEdge or whatever system you run, open closed jobs they handled, and ask them to explain each decision as if training a new hire.

Pick jobs deliberately: a callback, a job that ran well over its estimated hours, a large replacement that was won, one that was lost, and a commercial service call with an unusual fix. Unusual cases teach more than routine ones.

Shadowing adds what a desk review cannot. Have a successor ride along on a few calls the veteran would normally take, then review those same jobs together afterward. The successor's questions show which steps the record still fails to explain.

Add the explanations to the job record as internal notes, or keep them in a separate log keyed by job number. The goal is that a future reader, human or software, can see the decision and the reason side by side.

Method three: update SOPs, templates and the price book#

SOP updates turn captured knowledge into daily practice, which a transcript nobody reads cannot do. Put each lesson where the next person will meet it during the job.

Review each updated SOP with the veteran before they leave. A second pass usually catches steps they perform so automatically that they forgot to mention them.

• 1Add pre-job notes to equipment and location records, such as access instructions or known defects.
• 2Attach labor adjustment notes to price book tasks so estimators see the reason for extra time.
• 3Build install and maintenance checklists into job forms, with required photos where they help.
• 4Write dispatch rules for skill tags and job types instead of relying on the dispatcher's memory.
• 5Keep a short decision log for warranty and goodwill calls so future approvals follow the same logic.

Illustrative: a service manager retires from an electrical contractor#

Illustrative: a fictional commercial and residential electrical contractor learns that its longtime service manager plans to retire. She handles most commercial service accounts personally and assigns every complex troubleshooting call.

The owner schedules regular sessions. In each one, she reviews closed jobs from her key accounts and explains which panels, buildings and facility contacts need special handling. The notes go into location records in the field service system, and her skill-matching rules become tags on each technician profile.

A younger supervisor shadows her dispatching in the final months. After she leaves, he relies on the location notes during his first calls to several accounts, and the owner keeps the interview transcripts in a restricted folder with her written agreement.

Why recorded decisions hold value beyond training#

Recorded decisions hold value because they show how experienced people solve real problems, which generic manuals lack. The same notes that help a new technician also make the company less dependent on any one person, a point buyers examine closely in a sale.

Job records that link a problem, an expert's reasoning and an outcome are also the kind of workflow data AI developers seek. SourceX reviews such records through the SourceX Enterprise Data Value Framework, where domain expertise and human-generated signal raise value and privacy burden lowers net value.

Interview transcripts that mention customers and coworkers need careful review. Employees should know how their recorded knowledge may be used before any licensing is considered, and nothing leaves the company without the owner's approval at each step.