The Elsmar Cove Wiki More Free Files The Elsmar Cove Forums Discussion Thread Index Post Attachments Listing Failure Modes Services and Solutions to Problems Elsmar cove Forums Main Page Elsmar Cove Home Page
Google
  Web Elsmar.com
*Please be aware that SOME RECENT forum threads may not yet be indexed by Google.

View Full Version : Can ISO 9001 4.2.3 and 4.2.4 Documents and records be one procedure?


kcoryell
29th January 2007, 09:30 AM
Do I need to break out 4.2.3 and 4.2.4 Documents and records into two documented procedures or can I have one? Please offer your opinion on either side.

Thanks Kevin

Jim Wynne
29th January 2007, 09:35 AM
Do I need to break out 4.2.3 and 4.2.4 Documents and records into two documented procedures or can I have one? Please offer your opinion on either side.

Thanks Kevin

There is no requirement for separate documents. So long as control of documents and control of records are both addressed, you can do it in a single document if you want to.

Colpart
29th January 2007, 09:50 AM
I can't comment about ISO/TS 16949 but certainly it is OK in ISO 9001. However, I find there is a lot of confusion over what is a document and what is a record so I tend to keep them separate to help differentiate between them.

Duke Okes
29th January 2007, 10:14 AM
I see no advantage to combining them, but do see disadvantages:

- as Colpart said, it may just confuse people as to the difference between a document and a record

- it will just make the procedure longer, and if you want people to read it, that's not good

- documents tend to be controlled by a relatively small number of people/departments, while records are usually managed by almost all departments

CarolX
29th January 2007, 10:49 AM
Do I need to break out 4.2.3 and 4.2.4 Documents and records into two documented procedures or can I have one? Please offer your opinion on either side.

Thanks Kevin

Kevin,

My opinion is I have no opinion :D !

I say that because since there is no requirement for seperate procedures - do what works for you. Size and complexity of your system will really dictate what you will need.

JMHO

Ajit Basrur
29th January 2007, 11:02 AM
Kevin,

I say that because since there is no requirement for seperate procedures - do what works for you.

Absolutely true, BUT ....

I see no advantage to combining them, but do see disadvantages:

- as Colpart said, it may just confuse people as to the difference between a document and a record

this is not good. If people find it difficult to differentaite between a document and a record, there is something drastically wrong with training. :cool:

Claes Gefvenberg
29th January 2007, 11:23 AM
Do I need to break out 4.2.3 and 4.2.4 Documents and records into two documented procedures or can I have one? Please offer your opinion on either side.As far as the std is concerned you can deal with this as you please, but you also asked for our opinions: Mine is to keep them separate. It is often easier to keep small and to the point written procedures updated.

/Claes

CarolX
29th January 2007, 12:23 PM
As far as the std is concerned you can deal with this as you please, but you also asked for our opinions: Mine is to keep them separate. It is often easier to keep small and to the point written procedures updated.

/Claes

Claes,

I agree. I have always had them as seperate procedures, but I can envision situations where it might work to have them as one. So much is dependent on the enviroment. A very small company with 10 employees could very easily have them contained in one procedure, in fact, I would find that to be ideal. But a company my size (150 ppl), 2 procedures are definitely needed.

Randy
29th January 2007, 12:47 PM
Do I need to break out 4.2.3 and 4.2.4 Documents and records into two documented procedures or can I have one? Please offer your opinion on either side.

Thanks Kevin


Answer to question....You can have one procedure if you determine it will effectively meet your needs. It's all about effectiveness and not numbers.

My opinion? Personally, I don't care either way. As an auditor, I don't care either way as long as everything is effectively controlled.

Keep it as simple as possible. Simple to understand, simple to use.