The Elsmar Cove Business Standards Discussion Forums More Free Files Forum Discussion Thread Post Attachments Listing Elsmar Cove Discussion Forums Main Page
Welcome to what was The Original Cayman Cove Forums!
This thread is carried over and continued in the Current Elsmar Cove Forums

Search the Elsmar Cove!

Wooden Line
This is a "Frozen" Legacy Forum.
Most links on this page do NOT work.
Discussions since 2001 are HERE

Owl Line
The New Elsmar Cove Forums   The New Elsmar Cove Forums
  4.5 Retention of Reason for Change

Post New Topic  Post A Reply
profile | register | preferences | faq | search

UBBFriend: Email This Page to Someone! next newest topic | next oldest topic
Author Topic:   4.5 Retention of Reason for Change
Marc Smith
Cheech Wizard

Posts: 4119
From:West Chester, OH, USA

posted 28 February 2000 06:53 AM     Click Here to See the Profile for Marc Smith   Click Here to Email Marc Smith     Edit/Delete Message   Reply w/Quote
From: ISO Standards Discussion
Date: Fri, 18 Feb 2000 05:15:09 -0600
Subject: Re: Questions on ISO9000 4.5 /../Hankwitz/Kozenko/Hankwitz

From: "Hankwitz, John " jhankwitz@QGRAPH.COM

> Subject: Re: Questions on ISO9000 4.5 /Raffy/Hankwitz/Kozenko
> From:
> > > For 4.5 Document and Data Control - it states that where
> > > practicable, the nature of the change shall be identified in
> > > the document or the appropriate attachment. Does this mean
> > > that on a cover page wherein the "Description of Change" was
> > > indicated, Do we have to be more specific on what particular
> > > number that was been revised or changed. e.g. revise item
> > > # 3.1, 3.2 or update item # 5.6... and so on. In our
> > > application, we make use of the word "general revision" even
> > > though there were only few paragraphs that was changed on
> > > that particular document, instead of the specific on the
> > > example given. Please advise.
> Raffy:
> Agree with John's response, but need to add an important
> point that will help put perspective on how to record
> "changes to documents" of any nature.
> No where does the Standard require that "pertinent background
> information" be circulated with every change, or any change...
> just that it's available to reviewers. An appendix electronically
> recorded with the procedure or other document is an easy way to
> solve "where to put it" in the event no other reasonable location
> crosses anyone's mind.
> David Kozenko

David is so right. Keeping the reasons for the change are important for tracking purposes. In our case, the reasons are recorded on our Change Request form which is filed along with the review & approval copy of the new revision. The reasons are documented to the extent needed to clearly communicate what and why the changes were made.

John Hankwitz

IP: Logged

All times are Eastern Standard Time (USA)

next newest topic | next oldest topic

Administrative Options: Close Topic | Archive/Move | Delete Topic
Post New Topic  Post A Reply Hop to:

Contact Us | The Elsmar Cove Home Page

Your Input Into These Forums Is Appreciated! Thanks!

Main Site Search
Y'All Come Back Now, Ya Hear?
Powered by FreeBSD!Made With A Mac!Powered by Apache!