Your Most Experienced Operator Is Retiring. What Happens to Their Knowledge?

A replacement headcount cannot recover the context behind years of decisions. Your retiring operator may know why a procedure was revised, where supporting records live and which unresolved questions still need review. The immediate task is to identify that knowledge, verify it and give someone responsibility for using and maintaining it.

Start with one question: What would become harder to explain, find or verify if this person were unavailable tomorrow? That produces a more useful handover list than asking the operator to document everything they know.

The Canadian Water and Wastewater Association’s workforce-development guide addresses continuity as staff leave or retire, using tools such as checklists, gap analysis and progress tracking. The sequence below is an editorial approach for Canadian utility managers, not a regulatory requirement or operating instruction.

1. Find the single-person knowledge dependencies

A single-person dependency exists when useful knowledge has no reliable route beyond one employee. It might be an undocumented explanation, a record that others cannot locate or a review responsibility with no clear successor.

Ask the retiring operator, their supervisor and likely learners to identify these dependencies separately. Compare their lists: the operator may overlook something familiar that everyone else finds difficult.

• Which recurring questions are usually directed to this person?
• Which records can they find quickly that others struggle to locate?
• Which approved procedures have a history that helps explain their wording?
• Which outstanding issues or administrative responsibilities lack another informed owner?

Record each dependency as a specific topic. “Knows the plant” is too broad. “Can explain the documented reason for the current inspection-record format” is something a manager can assign, verify and close.

2. Prioritize records that will matter after departure

Do not begin with a long video interview or a wholesale file-copying exercise. First identify the approved references and existing records that support each topic. Capture what is missing rather than duplicating material already maintained elsewhere.

Give priority to topics with these features:

• Frequent use: colleagues regularly need the information.
• Limited backup: no other person can reliably explain or locate it.
• Consequences of confusion: a misunderstanding could affect safety, record quality or continuity.
• Unfinished work: a decision, review or follow-up will outlast the employee’s final shift.

For example, an unresolved records-review item may deserve attention before a well-documented routine with several capable backups. Assign a reviewer and learner to each priority topic. Keep the first list small enough to finish, then expand it as topics close.

3. Interview for context, not substitute instructions

Use the approved reference as the starting point for each conversation. Ask the operator to explain the context around it, rather than describe an unofficial alternative.

• What question does this reference answer?
• What documented history helps explain the current version?
• Where are the supporting records?
• What do newer staff commonly misunderstand?
• What remains uncertain, and who should review it?

Separate recollection from evidence. If the operator remembers why a form changed but cannot locate the supporting record, label that explanation as unverified. Do not turn a confident memory into an accepted fact.

Capture concise notes in the utility’s approved record location. If recording is permitted, follow existing privacy, security and records practices. Avoid placing passwords or security-sensitive site information in open handover documents. A note or video is not an approved procedure, and experience does not authorize bypassing one.

4. Reconcile the handover with approved documents

Before learners rely on the captured material, have the responsible reviewer compare it with current standard operating procedures, or SOPs, and supporting records. An SOP is the approved written procedure, not the retiring operator’s summary of it.

Use three clear outcomes:

1. Verified: the explanation agrees with the approved reference and supporting evidence.
2. Needs clarification: a reference is missing, ambiguous or difficult to locate.
3. Conflict identified: the recollection or local habit differs from the approved document.

Keep unresolved material visibly separate from verified content. Assign conflicts to the appropriate reviewer through existing processes; do not quietly edit a handover note to make the disagreement disappear. The useful result is a traceable explanation, not a polished document that conceals uncertainty.

5. Check learning within existing authorization limits

Pair the mentor and learner for short sessions tied to priority topics. Agree on what the learner should be able to explain or locate afterward. Keep all activity within existing safety, supervision and authorization limits.

For a records topic, the learner might locate the current approved version and explain where related evidence belongs. Where suitable and already permitted, an approved supervised demonstration can provide another check. Observing once or saying “I understand” is not the same as showing understanding.

Keep certification preparation separate from this site-specific work. Ontario’s OWWCO says exam-study resources do not replace appropriate training and experience. For any candidate, match preparation to the actual jurisdiction, exam type, class and current official instructions.

Use Echelon for Teams for certification preparation only, not as a substitute for this handover. The separate guide to building a certification-ready workforce addresses that planning track. Do not assume a handover session earns continuing education units or on-the-job training credit, demonstrates site competence or changes authorization.

6. Use one handover card per topic

This suggested template keeps evidence, learning and unfinished work together. Store it through existing document controls and link to approved records rather than creating competing copies.

• Topic: the specific knowledge dependency being addressed.
• Approved reference/version: document title, identifier, version and controlled location.
• Context: a short explanation, with supporting records identified and recollections labelled.
• Verified owner: the named person responsible for reviewing and maintaining this card, with responsibility confirmed.
• Learner: the person receiving the knowledge and any remaining learning need.
• Verification method/date: how understanding was checked, when and by whom.
• Unresolved items: the question, named reviewer, next action and target review date.

“Interview completed” describes activity. “Learner located the approved reference and explained the verified context” describes evidence of learning. Record the latter where it accurately reflects what happened.

7. Review before the last shift and after departure

Before the last shift, check that each priority topic has an accessible approved reference, a responsible owner and a recorded learner check. Confirm that open questions have named reviewers. Arrange any account or access changes through established administrative processes, never through password sharing.

After departure, schedule a review with the learners and owners. Ask what they could not find, what remained unclear and whether references have changed. Update cards through existing controls and retain unresolved items until the responsible reviewer closes them.

Start now with the three dependencies most likely to leave with the operator. Name an owner and learner for each, locate the approved references and book the first focused handover session.