ISO 9001 Documentation

by Mark Kaganov

ISO 10013, Guidelines for Developing Quality Manuals, gives an example of a documentation structure for ISO 9001 quality management systems. While this document suggests using a three-level structure, most companies implement four-level documentation structures to include records, as required by element 4.2.4 Control of quality records, of the ISO 9001:2000 Standard. A typical four-level documentation structure includes:

Quality Manual – level 1

Procedures – level 2

Instructions – level 3

Records – level 4

While auditing systems like the one above, I always asked clients about the position of their quality policy in this structure. If you start from a quality manual, how go you know what standard this manual should cover? The quality policy defines it and therefore it should be included into the structure:

Quality Policy – level 1

Quality Manual – level 2

Procedures – level 3

Instructions – level 4

Records – level 5

Document titles for your ISO 9001 QMS

As you may have noticed, the titles of the documents in the structure above are quite short. Various companies use different conventions for their document titles. For example, one of my customers titled their quality manual as “Quality Management System Quality Manual.”

This tendency to use long titles and document identifiers like “Standard Operating Procedure” most likely comes from regulated industries. Even though I could not find a requirement for such title formats, many companies still use these apparently outdated and ineffective conventions. If a short name sufficiently describes a document, let’s use it. I suggest streamlining all elements of management systems. Consider this and do not make your system more complicated than it can be.

ISO 9001 QMS document numbers

No standard prescribes to give a part or a document its number. It is an industry standard to give a document or a component its name, number and a revision level. Similar to part titles that we discussed above, document numbering conventions are often also may be optimized and simplified.

A company had some 130 employees. They had two part number formats: one for procedures, another for drawings. Procedures used XX-XXX number format. Drawings were numbered as XXXXXXX-XXX. One of the drawings had a number 000022-003. Assemblers simplified the system and called it “twenty two.”

Do these long numbers identify documents? Yes, they do! Are they economical? No, they are not! My customer’s system above allowed seven digits and therefore could deal with ten million documents or part numbers. When I worked with this business, they used some 300 documents. If one plans to grow from 200 – 300 documents to a million, one has a long way to go! It is not only how many documents your QMS uses, reading these long strings with five sequential zeros gave everybody headache. Even though this example looks too complicated, “The Worst Part Number” Grand Prize won my other client. They used 14-digit alphanumeric part numbers!

I hope it is clear that only when extensive part numbers are justified, we do not have other options. If you build helicopters or satellites, you, no doubt, will need millions of parts and therefore will need long part numbers. If not, make your life easy and stay away from all those zeros. The most practical system I worked with used a three-digit format for their part numbers. 202, 203, 204, and so on. Worked just fine!

There is another opportunity for improvement of many QMS – part number designation. Many companies relate a document number to a document type. For example, 20-xxxx indicates a procedure, 30-xxxx indicates a drawing, SOP-xxxx indicates a standard operating procedure, etc. My practice with a few QMS that used designation approaches showed that “no designation” systems are more practical. Several QMS that used designation I have worked with have failed. Not long ago, one of my clients mentioned that they ran out of range in their document numbering format. The QMS initially permitted for identifying suppliers through a two-digit identifier within the part number. While the company grew, the number of supplier increased beyond expectations and eventually the company needed more than 99 suppliers. This resulted in the document number format to being able to support new needs.

To get around this issue, there is a simple solution – a “no designation” system. Part or document numbers in such systems are assigned sequential unique numbers. Areas of use, materials, suppliers, and other attributes are not reflected in part numbers. Moving in this direction, you can simplify your system even more. I worked with a company that did not use document No. at all. That documentation system used just document name followed by a revision number, like Process Validation Protocol AB.

About the Author:

Leave a Reply