Re: Updated Quality Manual for ISO 9001:2008
Typically in the past I have written my manuals to reflect the standard's requirement and then answer the "how do we comply with that requirement" question from a policy level (the high-level how, why and who). The 'why' seems an important step as it can also describe reasoning behind interrelated processes, as well as reasoning behind business decisions - seems appropriate in the top-level 'policy' manual.
I then refer to the Quality Operating Procedure that details the 'detailed how, when, who and where' and other specifics. Does that make sense? My earlier documents have withstood audits well, and have given the companies a clear path they can follow.
I think it really comes back, as always, to the purpose of the particular document and its main audience. I can see the logic behind writing a
policy manual to reflect the requirements of a Standard, but I abhor the structuring of any manual along the lines of 'clause by clause of the Standard' because while it may well make the auditors happy, it's often less than comprehensible to anyone outside of them. And I definitely don't like procedures strictly aligned to the particular Standard/s either.
No one sets up and runs an organisation (business or otherwise) that mirrors a Standard, and to structure the org's documents on one to me is unintelligent, as well as a whole lot of other negative reasons.
(As you'll have gathered, opinions for and against are strongly held and argued in the Cove.)
But if you're saying in general, I use a 2-tier level (policy at top, procedures next), write policies to meet the requirements of a Standard, and then put the 'how we do this' in the procedures, I have no issue with that.
And welcome to the Cove and this thread, and it's good to hear from you.