Knowledge Momentum: What ISO 9001 Clause 7.1.6 Really Asks of You

Every organisation has at least one of them: the person who just knows how it works. Where everything is kept, why that customer gets handled differently, how to coax the old machine back to life. Then one day they hand in their notice, and you find out how much of your quality system was living in a single head.

ISO 9001 has a clause for exactly this moment. It is clause 7.1.6, organisational knowledge, and it was new when the 2015 version landed. It asks you to work out what knowledge your processes depend on, to hold onto it, and to keep topping it up as the business changes. Simple to state, quietly demanding to do.

A requirement that only ISO 9001 makes

Here is something worth knowing if you run an integrated system. Most of clause 7 is shared, almost word for word, across the management standards. ISO 27001, ISO 45001, ISO 14001 and ISO 42001 all inherit the same common text for resources, competence, awareness, communication and documented information. Organisational knowledge is the exception. Clause 7.1.6 sits only in ISO 9001. It is a quality idea, and the other standards do not ask for it.

That tells you something about intent. Quality is about doing the work consistently and improving it over time, and you cannot do either if the know-how keeps leaving the building. So 9001, alone among the standards, makes you treat knowledge as an asset worth managing.

A personal gripe: knowledge is filed in the wrong place

Allow me a personal aside, because this one has bugged me for years. Look at where they actually put organisational knowledge. It is 7.1.6, the very last sub-clause of 7.1 Resources, tucked in behind people, infrastructure, the working environment and your monitoring and measuring equipment. A third-level afterthought, filed next to the calibrated gauges.

That placement has never sat right with me. A forklift is a resource. Knowledge is something else entirely: the raw material that competence and awareness are both built from, and the thing that makes the rest of the system worth anything. In the harmonised structure that every modern management standard shares, competence gets its own clause at 7.2 and awareness gets 7.3. Knowledge, which quietly underpins both, is relegated to a bullet at the bottom of the resources list, and only in 9001 at that.

If it were up to me, I would give it equal billing with its natural siblings. Competence at 7.2, awareness at 7.3, and knowledge promoted to a clause of its own at 7.4, with communication shifting to 7.5 and documented information to 7.6. Line up the three ideas that are really about what your people know and understand, so the connection between them is obvious, rather than hiding the foundation stone at the end of a different clause. It is a small thing, but structure signals importance, and right now the structure quietly undersells the requirement that is arguably doing the most work.

Think of it as knowledge momentum

Picture your organisation’s collective know-how as a heavy wheel that is already turning. Every time someone works out a better way to do a job, trains a colleague, or writes down what they learned from work that went wrong, they give the wheel a push. Momentum builds. New starters get up to speed faster, the same mistakes stop repeating, and improvement compounds, because people build on what came before instead of rediscovering it.

Now take one of your most knowledgeable people and let them leave without capturing what they held. That is a brake on the wheel. The bigger the head they walk out with, the harder it jolts. And there is a sting in the tail that the standard does not spell out, though every business owner feels it: that knowledge does not disappear, it usually turns up at a competitor. You do not simply lose momentum, you hand some of it to the other side.

Managed deliberately, knowledge builds its own momentum. Left to chance, it leaks away one resignation at a time. Clause 7.1.6 is the standard’s way of asking which of those two your organisation is actually running on.

What clause 7.1.6 requires

Stripped back, the clause asks four things of you.

1. Determine the knowledge your processes need to run, and to deliver products and services that conform. Not everything the business knows, just what the work genuinely depends on.
2. Maintain that knowledge and make it available to the people and processes that need it, at the point they need it.
3. Look ahead. Compare the knowledge you hold now against where the business is heading, so you can see the gaps before they bite.
4. Acquire what is missing. Decide how you will get or reach the extra knowledge you need, whether that is training, hiring, mentoring or bringing in outside expertise.

The knowledge itself comes from two directions. Internal sources are the things your organisation has learned for itself: intellectual property, hard-won experience, the lessons from both failures and successes, and the results of the improvements you have already made. External sources are what you bring in from outside: standards, academia, conferences, and knowledge shared by your customers and suppliers.

One reassurance for anyone picturing a mountain of paperwork: 7.1.6 is not a formal knowledge-management standard, and it does not require you to build one. It asks for practical awareness and control of the knowledge that matters, at a level that fits your business.

Why the clause exists

ISO put 7.1.6 in for two reasons, and holding both in mind keeps you on the right side of it. The first is defensive: to safeguard the organisation from losing knowledge, whether through staff turnover or simply through never capturing and sharing what people know. The second is active: to push the organisation to go and acquire knowledge, by learning from experience, by mentoring, and by benchmarking against others. One protects the wheel’s momentum. The other adds to it.

What an auditor looks for

On audit, 7.1.6 is one of the clauses where you can see the gap between a system on paper and a system that runs. I am not hunting for a “knowledge register” for its own sake. I am looking for evidence that the knowledge your processes depend on is not trapped in one person. Can someone other than the expert follow the process and get the same result? When a key person left last year, what did you do to capture what they knew before they went? When something went wrong, did the lesson get written down and fed back in, or did it stay a story people tell at lunch?

The organisations that handle this clause well are rarely the ones with the thickest manuals. They are the ones where capturing and sharing knowledge is simply how the place works.

How to capture knowledge without drowning in documents

The mechanics do not need to be sophisticated. Two approaches cover most of what a small or medium business needs.

• Work instructions, the old-school way: clear steps in text, backed up with a photo or a diagram at the points where words alone fall short. Cheap, fast-ish, and sometimes still the right tool.
• Short videos, the genuine alternative: a screen capture or a phone recording of the task actually being done, with a voiceover explaining the why, not just the what. Loom is built for exactly this, and if your team already has Microsoft 365, Clip Champ is included at no extra cost. Video shows the task rather than describing it, which is often the difference between a procedure people ignore and one they can actually follow.

The reason to treat video as a real alternative, and not just a nice extra, is that it scales in ways a written procedure never could. Record the task once, and the AI now built into these tools will generate a transcript for you and translate it into whatever languages your team speaks, so one recording can serve an English-speaking supervisor and a shop floor that speaks several others. That same short clip can then reach ten people, a hundred or a thousand with no loss of fidelity, and no expert having to repeat themselves for the tenth time. You capture the knowledge once, and it lands with everyone who needs it, in a form they can actually absorb.

The verification step matters more than people expect. Capturing knowledge and confirming it transferred are two different jobs, and 7.1.6 is really about the second. A short quiz, a supervised first run, or a sign-off that says “yes, they can now do this without me”, is what turns a document into momentum.

The 2026 revision raises the bar

If you are planning ahead, know that 7.1.6 is one of the clauses the ISO 9001:2026 revision strengthens. The expectation is shifting from “we have some knowledge” toward showing, more systematically, how you capture, share and apply it. The revision also brings knowledge held in digital and automated tools into scope. Where an AI model or an automated system makes a quality-critical decision, you are expected to be able to show how that model is validated, kept current and managed. If part of your process knowledge now lives in software rather than in a person, the standard is starting to treat it the same way: it still has to be understood, controlled and kept fit for purpose.

Where Streamline fits

Most of our work on 7.1.6 lands on the same problem: too much depends on too few people. Our ISO mentoring service is built to move knowledge the right way, into your team rather than into a consultant you then depend on. If key-person risk is the real worry, our outsourced ISO manager service keeps the system running while people come and go. And an independent internal audit under clause 9.2 is the honest test of whether your knowledge is genuinely captured or merely currently present, because it asks the awkward question while the expert is still there to answer it.

This article is general guidance from a practising ISO auditor’s perspective, and is not a substitute for the text of ISO 9001 itself. Clause references are to ISO 9001:2015. Where we mention the 2026 revision, the detail may change before it is finalised.

Frequently asked questions

Is clause 7.1.6 a knowledge-management standard?

No. It does not require you to implement formal knowledge management. It asks you to determine the knowledge your processes need, keep it available, and top it up as the business changes, at a level that fits your organisation.

Does organisational knowledge appear in ISO 27001 or ISO 45001?

No. Clause 7.1.6 is specific to ISO 9001. The other management standards share a common clause 7 covering competence, awareness and documented information, but organisational knowledge is a quality-management requirement that only 9001 makes.

What is the simplest way to start?

Pick the two or three processes that would hurt most if the person who runs them left tomorrow, and capture those first. A work instruction with photos, or a short narrated video with a quick check at the end, is enough to begin building momentum.

Speak with an experienced ISO auditor

If your quality system leans too heavily on one or two people, we can help you capture what matters before it walks out the door. Email hello@streamline.business or call us. You will deal directly with an experienced ISO auditor.

• Brisbane 07 3667 8280
• Sydney 02 8315 7780
• Melbourne 03 9034 3990