Does a Quality Manual have to be in the format of ISO 9001:2000?

Peter Fraser

Trusted Information Resource
hjilling said:
I don't buy the idea of a one page manual, but your idea makes sense to me. Many companies use a webpage to hyperlink the documents of the system. I would lokk at the whole thing as you quality system, and not get hung up on which part is the "manual." The whole thing could actually qualify. I like the idea, and it is easy to access and control.
Folks

It’s not surprising that there is so much divergence of views on this. Looking at ISO9000 and ISO9001 for guidance (not perhaps recommended for documents which suggest that a “driver’s manual” is “software”?), you will find the following contradictory definitions [some paraphrased, my comments in brackets]:

A “management system” is “a system to establish policy and objectives and to achieve those objectives”. [I like this]

A “quality management system” is a “management system to direct and control an organization with regard to quality” [Not too bad either]

A “quality manual” is “a document specifying the quality management system of an organization”. [This works for me if eg you have an electronic system and treat the entire system (policies, process definitions including responsibilities, documents and records) as “the way we do things around here”]

”A document that provides consistent information, both internally and externally, about an organization's quality management system is referred to as” a “quality manual”.
[I am really struggling with this. First of all, how many organisations have a manual which isn’t “consistent”? I’ve seen a few – does that by definition disqualify their manuals from being quality manuals (or are they just “poor quality” manuals?)
And why “internally and externally”, and what does the phrase mean? Surely what you do with a document is irrelevant. To me, a “quality policy” is of as much interest to customers, yet its definition makes no mention of “internally and externally”.
And what does “information” mean? I would expect (eg) the quality policy to be included, but it is not one of the mandatory items listed elsewhere. At least this (vaguely) hints at a purpose for a quality manual – folk might understand all this better if the standard made it clear why you need to produce one. Then again they might question the need for one at all.]

“The quality management system documentation shall include a quality manual” … and also “documented statements of a quality policy and quality objectives, documented procedures required by this International Standard, documents needed by the organization to ensure the effective planning, operation and control of its processes, records required by the standard.”
[So how is a “quality manual” “a document specifying the quality management system of an organization” if we have this long list of other stuff as well?]

My view is that you should put the standard (all standards) to one side and define how you run the business (processes, documents, records, roles and responsibilities) then check against whatever standard you feel the need to comply with. Do it in a way that suits the business, and don’t define anything that is not useful to you and your staff. An electronic system with a simple "home page" that tells a user where to find the information they need is ideal.
 
F

floman

Thanks for your assistance

I browsed around the forum and found a number of manuals with 10 or less pages, and I chose the one from xxxx (weight scale manufacturer). It was 10 pages and when I rewrote it, it reached 6 pages. I got as far as writing two procedures for the second tier, and suddenly:

I got laid off!:D :eek: :lol:

I really liked that manual, but it doesn't matter now. Anyone want to see my resume?

Now that I've found this forum I will stay on board. Good find.

Thanks again for your advice!

bp
Brian Park
Austin, Texas.
29 years of esoteric product design.
 
M

Murphys Law

Just to add to the "No" crowd. I work for a major Semiconductor manufacturer and our Quality manual does not match ISO9001 in it's organization.

It is legacy organization based on Military requirements for a Quality System in the 70's. I personally wish it was organized to ISO sections as it would be easy for people to understand.

My experience our our corporate Quality system is that it is too complex and despite what all our certificates say, people don't follow it. Since it is called "Quality System", most people don't read it nor know how to call it up unless they are to be audited. The functional managers similarly don't understand that they can formally change procedures if they are impractical.
If I had my way, I would call it "Operating Manual" not quality system. (A trick I remember from a training course we had : Called "Basics of Marketing" nobody turned up. Changed the title to "Marketing High Technology" and it became oversuscribed".

I also see some positive trends coming out of newer ISO. :applause: The "thou shalt" approach has been eased off and usage of flow charts and turtle diagrams are being allowed as alternative. A) The picture paints a thousand words B) It is not so daunting to read.
 

Helmut Jilling

Auditor / Consultant
Murphy's Law said:
...If I had my way, I would call it "Operating Manual" not quality system. (A trick I remember from a training course we had : Called "Basics of Marketing" nobody turned up. Changed the title to "Marketing High Technology" and it became oversuscribed".


A few of my clients weren't permitted to change the title from Quality Manual, so they just began to call it "Business System" or the "Acme Co. Business Operating Manual." It begins to change the perception without officially worrying about the title.

Call it that often enough, and people start to believe it... (Marketing 101).
 

Helmut Jilling

Auditor / Consultant
Sidney Vianna said:
Permitted by whom? :confused:


Sometimes the Quality Manager wanted to officially name it a Business Management System, but top management didn't agree.

However, it would be easy to just call it that in conversation, and let it take root.
 

RoxaneB

Change Agent and Data Storyteller
Super Moderator
hjilling said:
Sometimes the Quality Manager wanted to officially name it a Business Management System, but top management didn't agree.

However, it would be easy to just call it that in conversation, and let it take root.

If I may ask, hjilling, why didn't top management agree? My top management darn near jumped for joy when it was suggested to them that we streamline our systems...and all of the associated paperwork (including the manual).
 

RoxaneB

Change Agent and Data Storyteller
Super Moderator
floman said:
I got laid off! I really liked that manual, but it doesn't matter now. Anyone want to see my resume?

:topic: Sorry to hear about your job! There is a career section here in the Cove...it might have something (even leads) for you. You can also post your resume there, I believe.
 

Helmut Jilling

Auditor / Consultant
RCBeyette said:
If I may ask, hjilling, why didn't top management agree? My top management darn near jumped for joy when it was suggested to them that we streamline our systems...and all of the associated paperwork (including the manual).


When it is suggested this program should be classed as a business management system, that it is not exclusively the domain of the Quality Dept., in most companies, the idea is accepted and embraced. However, the "official name" is not always changed.

Once in a while, particularly in larger bureaucracies, top management resists. Can't say for sure, but I assume they are concerned it pushes more responsibilities onto them. Can't recall any companies who were progressive opposing the idea.
 

RoxaneB

Change Agent and Data Storyteller
Super Moderator
hjilling said:
When it is suggested this program should be classed as a business management system, that it is not exclusively the domain of the Quality Dept., in most companies, the idea is accepted and embraced. However, the "official name" is not always changed.

I suppose one could argue that Quality applies to everything. In fact, that's we say (tongue in cheek) as we are unable to modify the template in our document control system for the manual...so, when printed, it says Quality Philosophy and stuff like that. We are in the process of trying to convince the software developer to provide something a little more generic. :)

hjilling said:
Once in a while, particularly in larger bureaucracies, top management resists. Can't say for sure, but I assume they are concerned it pushes more responsibilities onto them. Can't recall any companies who were progressive opposing the idea.

While I'm sure I'm preaching to the choir, I just don't see how responsibilities increase. After all, if what is documented is truly what the organization does, then the responsibilities were already there before the manual was developed. If accountability is the concern, however, that's a completely different issue. ;)
 
Top Bottom