Re: Who is registered to ISO 9001:2015?
"I agree with you that an organisation always has to do more than inform the customer."
"I don't believe there is any glaring error in clause 8.7, you do"
That looks like circular logic. First you say you agree then you say you don't.
Back on the topic of how I write a manual.
"I don't need to see a manual if you've already told me you follow ISO clause numbering."
From my comment that it doesn't hurt what the order is you seem to have already made up your mind that it is a bad manual, or perhaps just a bad approach to writing a manual. That's an awfully arrogant attitude. Sight unseen it was condemned because it is not your preferred method. That is a broad brush condemnation.
With as much fun as you have had over there is no problem addressing the requirements out of order, I'm certainly not willing to send you a copy of one of the manuals I have written. You have had enough fun with the little tiny piece you think you have.
So where, exactly did I quit?
In Sidney's post he directed you to an interpretation on ISO 9001:2008 where someone asked the very specific question (linked in Sidney's post):
The TC 176 answer, correctly, is that the standard doesn't require it and nothing in the 2015 edition changes that.
I'm not aware of a request for interpretation on this matter. Perhaps most users don't see it the same way as you?
Perhaps you could contact ANSI and see if you can get the question raised.
The first mention of a manual was in your post - here - where you spoke about changing the order of clauses from those in ISO 9001.
You shouldn't be surprised to see that I am not impressed that someone recommends following ISO clause numbering in the structure of their manual - I've been saying this for years, through multiple clause number structures.
You've taken it personally, your prerogative. I don't need to see a manual if you've already told me you follow ISO clause numbering.
So where are these bad and broad assumptions?
I have been very specific in my responses and try to link my responses to sections of your post to keep the discussion together.
I don't believe there is a misunderstanding. I have responded to every point you have made and you choose to change the argument and cry foul.
Untrue. I never said any such thing. ISO 9001 provides a flexible framework for responding to nonconformance, I don't see any inadequacy.
As ever, Jim, all I did was repeat your words back to you and comment on them.
I don't like manuals that follow standard clause structure - happy to agree to disagree.. again, if you want a review, please feel free to post an example - take out anything personal to your client of course.
I'd be interested in where you find the circular logic. I go out of my way to break your responses down and reply to each point individually, not the case for your replies.
The TC 176 answer, correctly, is that the standard doesn't require it and nothing in the 2015 edition changes that.
I'm not aware of a request for interpretation on this matter. Perhaps most users don't see it the same way as you?
Perhaps you could contact ANSI and see if you can get the question raised.
The first mention of a manual was in your post - here - where you spoke about changing the order of clauses from those in ISO 9001.
You shouldn't be surprised to see that I am not impressed that someone recommends following ISO clause numbering in the structure of their manual - I've been saying this for years, through multiple clause number structures.
You've taken it personally, your prerogative. I don't need to see a manual if you've already told me you follow ISO clause numbering.
So where are these bad and broad assumptions?

I have been very specific in my responses and try to link my responses to sections of your post to keep the discussion together.
- 8.1 is a valid clause to have before 8.2 as it covers 'big picture'
- I don't like manuals that follow ISO Clause structure or regurgitate standard requirements - by your posts it seems you do at least like ISO clause numbering in manuals - we don't have any information on whether you regurgitate standard requirements I don'
- t believe there is any glaring error in clause 8.7, you do
- I understand clause 8.7.1 requires more than just informing the customer but you think that option 8.7.1 c would be allowable on its own (even if not desirable)
- We agree the manual shouldn't be used as a checklist. My criticism here was of you looking at 8.7.1 c in isolation of all the other standard clauses I listed.
I don't believe there is a misunderstanding. I have responded to every point you have made and you choose to change the argument and cry foul.
Untrue. I never said any such thing. ISO 9001 provides a flexible framework for responding to nonconformance, I don't see any inadequacy.
As ever, Jim, all I did was repeat your words back to you and comment on them.
I don't like manuals that follow standard clause structure - happy to agree to disagree.. again, if you want a review, please feel free to post an example - take out anything personal to your client of course.
I'd be interested in where you find the circular logic. I go out of my way to break your responses down and reply to each point individually, not the case for your replies.
"I don't believe there is any glaring error in clause 8.7, you do"
That looks like circular logic. First you say you agree then you say you don't.
Back on the topic of how I write a manual.
"I don't need to see a manual if you've already told me you follow ISO clause numbering."
From my comment that it doesn't hurt what the order is you seem to have already made up your mind that it is a bad manual, or perhaps just a bad approach to writing a manual. That's an awfully arrogant attitude. Sight unseen it was condemned because it is not your preferred method. That is a broad brush condemnation.
With as much fun as you have had over there is no problem addressing the requirements out of order, I'm certainly not willing to send you a copy of one of the manuals I have written. You have had enough fun with the little tiny piece you think you have.





