A quality manual can be complete while the organization remains one resignation away from an expensive stoppage. A veteran specialist may know why an apparently acceptable supplier batch is unsuitable for a particular machine, which customer exception needs executive approval, or how a legacy test result must be interpreted. These facts may never appear in formal procedures. The practical challenge is to find knowledge that makes an operational difference, not to declare every stored document critical.

01Begin with the decisions that can fail
Start from consequential decisions rather than asking each department to list everything it knows. Examine product release, equipment recovery, complaint escalation, regulatory submissions and customer-specific approvals. For each decision, ask which facts, experiential judgments and external sources are needed to reach a defensible result when normal conditions change. The answer is often a combination of documented instructions, practiced judgment and a contact who can interpret exceptions.
Use process failures and near misses as discovery clues. Repeated calls to one retired engineer, unexpected rework following a shift change and conflicting interpretations of the same inspection finding indicate missing shared understanding. They do not automatically prove inadequate competence; the missing element might be a rationale, supplier history or a decision threshold that has never been made accessible.
Criticality test. If the regular expert is unavailable for two shifts, can a qualified substitute identify the limits of their authority, make the routine decision and recognize when to stop? An affirmative answer requires more than knowing where a procedure PDF is saved.
Technical context: ISO 30401:2018 (with amendments) — Knowledge management systems — Requirements is one verified source for the concepts discussed here.
02Classify knowledge by consequence and substitutability
Distinguish knowledge that supports ordinary efficiency from knowledge that prevents severe safety, compliance, service or quality consequences. Estimate the time available to recover it, whether an independent source exists and how frequently the decision arises. A rarely used emergency shutdown sequence may be more critical than a frequently used but well-documented administrative workflow.
Create a compact critical-knowledge register with process, key decision, expert or source, failure consequence, alternate source, current capture method and next review trigger. Do not rank people as indispensable; rank the operating dependency and vulnerability. Human resources teams can help understand mobility risk, while process owners remain responsible for whether essential knowledge is available to operate controls.
Classification guardrail. Use a consequence-based score with clear examples but avoid false precision. A high ranking should lead to a specific mitigation—cross-practice, controlled job aid, supplier technical agreement or access arrangement—not simply another red square in a spreadsheet.
An effective criticality discussion includes the person who performs the task and someone who receives its output. In a production release process, laboratory staff might understand the test method while customer service understands a contractual exception. The knowledge risk sits at that interface. Examine the last real disputed transaction and identify which interpretation each role contributed; recording only one expert would leave the dependency intact.
03Locate knowledge that sits outside controlled documents
Shadow an experienced operator during a non-routine job and ask why the chosen sequence differs from the written work instruction. Compare versions of process maps, customer concessions and engineering changes to find unresolved reasoning. Recorded deviations may reveal institutional memory that was never converted into an accepted control.
Knowledge is often distributed across vendor emails, design notes, meeting decisions, annotated drawings and unofficial shift books. Finding it does not mean transferring everything into one central repository. The important task is to preserve an understandable chain between the problem, accepted decision, evidence and limits of application without exposing confidential information.
Search beyond folders. Examine actual work orders, incident reviews and customer escalations. Interview operators on different shifts; disagreements about when to stop a process can reveal more risk than the presence of numerous similarly worded procedures.
Before assigning a high criticality rating, test what would actually happen if the usual specialist were absent. Could staff rely on a current manufacturer publication, a qualified external laboratory or a previously approved technical decision? These alternatives may reduce dependency, but the organization needs evidence that the route exists and will respond within the available operating window. A contact name alone does not prove recoverability.
04Choose a preservation method that fits the knowledge
Explicit requirements and stable instructions belong in controlled documents with ownership and revision. Judgment about unusual operating conditions often transfers better through paired problem solving, supervised demonstrations and decision examples. Relationships and supplier escalation knowledge may require contact maps, service agreements and deputy arrangements rather than dense narrative notes.
For each critical item specify the receiving role, acceptable evidence of transfer and preservation interval. Some knowledge can be encoded as a parameter range; other knowledge needs a qualified person to interpret the range. High-risk activities may require both a technical job aid and observed competence, especially after a machine, regulation or product specification changes.
Transfer design. Ask the receiving employee to explain how they would handle a genuinely different case, not simply reproduce the departing expert’s last example. Where the expert disagrees with an approved procedure, escalate that conflict before publishing the shortcut.

The first inventory should be selective. A dozen carefully chosen decisions with owners, backups and evidence are easier to govern than a hundred vague entries. After the pilot, consider whether each high-risk knowledge item should be controlled in the QMS, transferred through a competence plan or covered by a contractual support arrangement. Choose the route that preserves the ability to decide, not the appearance of completeness.
05Link the register to risk and change management
Review the register at the points where knowledge is most likely to expire: planned retirements, new products, significant equipment changes, outsourced services, major complaints and restructuring. A calendar-only annual review can leave a process exposed for months after its knowledge source becomes invalid.
Treat critical knowledge like a dependency in business continuity planning. Identify an alternative expert, verified instruction, protected reference or external support arrangement, and check that it remains accessible during a systems outage or site disruption. The plan should distinguish the availability of information from the capability to act on it safely.
Ownership check. A process owner should confirm who authorizes changes to preserved knowledge, who can access it in a disruption and when an outdated item must be withdrawn. IT availability is not a substitute for technical validation.
| Decision domain | Owner or objective | Observable evidence |
|---|---|---|
| Critical decision | Process owner | Consequence and substitute decision path |
| Source fragility | Operations and HR | Named expert, alternate and expected availability |
| Capture route | Technical authority | Approved method and scope of use |
| Proof of transfer | Supervisor | Observed alternate performance |
06Test retrieval and competent use in normal work
Run a substitution exercise: give a qualified alternate a representative exception and observe which resources they need, whether they understand the decision boundary and what they escalate. Record friction such as missing passwords, outdated contacts and unclear version status. A successful repository search alone does not prove that a decision can be made responsibly.
Sampling should include familiar and unusual situations. Confirm that an alternate can identify a withdrawn instruction and that the record includes sufficient source context to avoid applying a solution to the wrong material or machine. Cross-training evidence is stronger when it includes performance observation rather than attendance alone.
Useful effectiveness measures. Track unplanned dependence on a sole expert, retrieval success for critical scenarios, controlled knowledge revisions triggered by change and the time needed for a qualified alternate to demonstrate safe execution.
Knowledge transfer is not always a document project. A practical trial may involve reproducing an unusual diagnostic reasoning sequence with a deputy who can challenge assumptions. Record where the substitute requested new information and whether the current authorized sources answered the question. This observation creates an evidence-based priority for updating a job aid or adding supervised practice, instead of assuming another uploaded manual will solve the problem.
07Keep the critical set small enough to govern
An organization that labels every document and every employee as critical will struggle to sustain protection. Periodically challenge whether each register item still requires special treatment. Move routine material into standard document control, retire obsolete guidance and combine duplicate sources whose meanings are genuinely equivalent.
Executive review should focus on exposed operating decisions and mitigation status, not document totals. Ask which critical activities have no dependable substitute, whether temporary risks are explicitly accepted and how new knowledge will be captured during improvement work. The objective is operational resilience, not a larger knowledge inventory.
Management action. Select the three highest-consequence dependencies and allocate time for a witnessed alternate performance. If substitution fails, define the temporary restriction that prevents an unsafe or unauthorized decision while knowledge transfer is completed.
At management review, discuss whether critical knowledge risks were created by organizational changes. Centralizing maintenance may reduce local staffing but increase dependence on a remote specialist; replacing a vendor may remove access to proprietary tuning instructions. The review should connect these changes to temporary safeguards, qualified support and documented decision limits. An elevated rating without resource allocation does not change operating resilience.
Practical Review Questions
- Can a qualified alternate handle the last significant exception without calling the sole expert?
- Do new work instructions preserve technical rationale and boundaries?
- Does the knowledge register trigger review following personnel and equipment changes?
- Can staff retrieve essential knowledge if the primary platform is unavailable?
Protect the Next Critical Decision
Choose one high-consequence activity and identify the exact decision that depends on undocumented experience. Observe an alternate attempting a representative task, with a safe stop rule and the appropriate supervisor present.
Approve the necessary instruction, technical rationale or coaching plan only after the process owner verifies its accuracy. Put the item under a change trigger so newly discovered exceptions are not preserved as unreviewed folklore.
Closing Perspective
The knowledge worth protecting first is the knowledge that changes whether a material decision can be made safely and correctly when its usual source disappears.
References & Further Reading
Official ISO standards and guidance informing knowledge preservation, process control, competence, records and organizational learning. The relevance of each source depends on the organization and the decision being addressed.
- ISO 30401:2018 (with amendments) — Knowledge management systems — Requirements
- ISO 9001:2026 — Quality management systems — Requirements
- ISO 10015:2019 — Competence management and people development guidance
- ISO 15489-1:2016 — Records management concepts and principles
- ISO 31000:2018 — Risk management — Guidelines