The Clause Most Firms Underestimate
When engineering firms discuss ISO documentation, they think about process descriptions, work instructions, forms. Clause 7.1.6 — "Organizational Knowledge" — is often treated as a footnote.
Until the next audit.
ISO 9001:2015 explicitly requires that organizations:
1. Determine what knowledge is necessary for their processes and the quality of their deliverables 2. Maintain this knowledge 3. Make available to the extent it's needed 4. Address changing needs — including acquiring new knowledge when requirements change
Most firms handle this with a sentence in their quality manual: "Knowledge is secured through onboarding, training, and documentation." Formally correct. Substantively empty.
What Auditors Actually Want to See
An experienced auditor doesn't ask: "Do you have a knowledge management policy?" They ask: "Show me how a new employee accesses the knowledge they need for their role."
Typical audit questions on 7.1.6:
- How do you ensure critical knowledge doesn't depend on individual people?
- What knowledge is required for your core processes, and where is it documented?
- What's your approach when an experienced employee leaves the company?
- How do you identify knowledge gaps when requirements change?
If the answer to every one of these is "We handle it informally," you have an audit risk.
The Gap Between Should and Is
The QMS documents how processes should work. But the knowledge Clause 7.1.6 refers to is different: it's the actual operative knowledge — the experience, the assessments, the decision bases your employees deploy every day.
This gap is particularly wide in engineering firms because:
- Technical experience knowledge is hard to formalize
- Every engineer has individual calculation approaches and assessment standards
- Code interpretations vary by region and reviewer
- Project experiences are rarely captured systematically
How askSOPia Substantively Fulfills the ISO Requirement
Determine Knowledge
askSOPia systematically identifies what knowledge exists in your firm — including implicit knowledge that's not in any document. Knowledge Cards make visible where expertise resides.
Maintain Knowledge
Every Knowledge Card has a timestamp, context, and source. askSOPia detects when knowledge becomes outdated or contradictory and flags it for review.
Make Knowledge Available
Every employee can search the knowledge base — in natural language. No navigating folder structures, no guessing where something is filed.
Address Changing Needs
When codes change, new client requirements emerge, or processes are adapted, the knowledge base grows automatically. New insights are captured as cards and linked to existing knowledge.
The Starting Point: Knowledge Sprint
During the Knowledge Sprint, we build an initial knowledge base in 5 days that substantively fulfills Clause 7.1.6 requirements. Not a paper tiger — a real, searchable, living knowledge base.
Frequently Asked Questions
Next Step
Ready to Secure Your Knowledge?
Less than the cost of a bad first month of a mis-hire.
20 minutes. No slides. No prep needed.