Endnotes

[1] I am not the only one concerned with this requirement. See, for example, Page, Stephen B., "The Continued Importance of Documented Procedures to ISO 9000:2000 Standards," Software Quality, Summer 2001, p. 13.

[2] The use of checklists has begun show up as articles. See, for example, Kaganov, Mark, "Checklists—A Perfect Tool To Tune Up Your Quality Manual," Quality Progress, October 2000, p. 37.

[3] See "Quality System Requirements, QS-9000," obtained from AIAG at tel: [phone].

[4] See, for example, Taylor, C. Michael, "Bored with the Same Old Standards Books?" Automotive Excellence, Spring 1997, p. 6.

[5] As with all powerful ideas, an ISO 9000 mythology has been created in spite of its short 15-year existence. One of the myths is that each tier must have a document for each mandatory, and for that matter, each implied requirement. We feel that such an approach is not only contrary to the spirit of the Standard, but the redundancy that results from such a viewpoint is counterproductive and serves to confuse the users instead of support their efforts. The new revision attempts to remedy this attitude but may have oversimplified the requirements.

[6] Although the supplier is ultimately responsible for the choice of exclusion and how that exclusion is justified to their organization, it is essential to keep in close touch with your registrar on interpretation because the registrar has a similar issue (i.e., how the Standard should be interpreted against the requirements of the accreditation board).