A
alvisan
“For implementing ISO9001:2000, we must approve, update and carry out revision control on all quality records. It is because record is a type of documents”. Right? Wrong?
Actually there may be a simpler way to keep terminology accurate:To add on to Colpart's response, if you're are talking about records - that is forms which have information on them - then what he said is great. If, by record, you are talking about the blank form, you should:
- Understand the difference between a form and a record
- Control forms like work instructions, procedures, etc., to ensure that everyone is working on the same revision.
Wes, I was attempting to keep my answer short and to-the-point as my gut says that our Original Poster's first language is not english. And I didn't wish to repeat what Colpart had already said (aligned with your response)...merely add on to it.
I thought the same thing when I read Wes's contribution.
But sometimes they should be changed in order to correct errors. This is why some level of control of records is important. That control can be accomplished in the form of explicitly defining when such changes are permissible, how they are to be carried out (so as to leave a trail), and by whom. How customers are to be notified when changes are made should also be explicitly defined.Since the static documents describe something in the past (history), they should not be changed.
It may sound like Abbott and Costello doing "Who's on First?" but this is absolutely right if it is data of an activity that has been performed. It may be only a document if it is data filed in on a form for an activity yet to take place (like filling in an Engineering Change Order Request.) Isn't this nit picking about terminology frustrating?And of course (just to confuse things further) a document (e.g. a form) becomes a record when is is filled in with data!