D
David Mullins
any which way but loose
Put 5 quality managers in charge of 5 identical companies and you'll get 5 diverse views on what should be in the manual.
As one of the "made my own recipe" manual people, I'd ask this:
If we forgot about compliance with ISO 9001 and asked ourselves what should we have in the primary 'mother' document for our company (assuming a fully integrated system), what would we include.
Also, before being able to answer that, we need to determine what it is that we are attempting to gain from having this document.
Based on Marc's poll, and not wanting to start a bun fight, I'd say less than 10% of quality managers would be in a position to answer these questions. Aternatively (saving my rear end here), others probably can answer, but went for the safety net in terms of the appearance/structure of the manual.
So, how does your company benefit from the manual, and what did you put in it to meet these needs? (And therefore, why did you put the other stuff in it?)
For Lucinda's question, I'd say if you're expecting to update stuff that's in the manual more regularly than yearly, then just refer to it and make it a separate document (and make that manual smaller!).
Put 5 quality managers in charge of 5 identical companies and you'll get 5 diverse views on what should be in the manual.
As one of the "made my own recipe" manual people, I'd ask this:
If we forgot about compliance with ISO 9001 and asked ourselves what should we have in the primary 'mother' document for our company (assuming a fully integrated system), what would we include.
Also, before being able to answer that, we need to determine what it is that we are attempting to gain from having this document.
Based on Marc's poll, and not wanting to start a bun fight, I'd say less than 10% of quality managers would be in a position to answer these questions. Aternatively (saving my rear end here), others probably can answer, but went for the safety net in terms of the appearance/structure of the manual.
So, how does your company benefit from the manual, and what did you put in it to meet these needs? (And therefore, why did you put the other stuff in it?)
For Lucinda's question, I'd say if you're expecting to update stuff that's in the manual more regularly than yearly, then just refer to it and make it a separate document (and make that manual smaller!).