Elsmar Cove Forum Header Graphic 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
Miner's MSA (Measurement Systems Analysis) Blog 
Go Back   The Elsmar Cove Forum > Common Quality Assurance Processes and Tools > Records and Data - Quality, Legal and Other Evidence
Forum Username

Wooden Line

Document vs. Record - What's the Difference under TS 16949?

Wooden Line
Search the Elsmar Cove
Search Elsmar
Monitor the Elsmar Forum
Follow Marc & Elsmar
Elsmar Cove Forum RSS Feed  Marc Smith's Google+ Page  Marc Smith's Linked In Page   Marc Smith's Elsmar Cove YouTube Page  Marc Smith's Facebook Page  Elsmar Cove Twitter Feed
Elsmar Cove Groups
Elsmar Cove Google+ Group  Elsmar Cove LinkedIn Group  Elsmar Cove Facebook Group
Donate and $ Contributor Forum Access
Courtesy Quick Links

Links that Elsmar Cove visitors will find useful in your quest for knowledge:

Howard's
International Quality Services
Marcelo Antunes'
SQR Consulting
Bob Doering's
Correct SPC - Precision Machining

NIST's Engineering Statistics Handbook
IRCA - International Register of Certified Auditors
SAE - Society of Automotive Engineers
Quality Digest Portal
IEST - Institute of Environmental Sciences and Technology
ASQ - American Society for Quality

Related Topic Tags
ts 16949 - automotive quality system standard
Reply
 
Thread Tools Search this Thread Rate Thread Content Display Modes
  #1  
Old 15th August 2002, 10:39 AM
dbzman's Avatar
dbzman

 
 
Posts: 223
Unhappy Document vs. Record - What's the Difference under TS 16949?

Under 4.2.3 Control of documents - records are said to be a special type of document.
I'm in the habit of keeping two control listings. One for records and one for document (intructions, SOPs, etc).
Under this definition if a document has data entered on it then it becomes a record.
Would it be better to just have one listing or is there another way to control records? Am I making this too complicated?


Sponsored Links
  #2  
Old 15th August 2002, 12:51 PM
Ken K's Avatar
Ken K

 
 
Posts: 406
The way we separate the two is if we update or change a document it would require a revision change because it's controlled.

But, we also use various files and logs which are updated as part of normal operations without necessitating a revision change.

Both are considered part of our quality system.
Sponsored Links

  #3  
Old 15th August 2002, 02:16 PM
db's Avatar
db

 
 
Posts: 2,574
Record vs document

Quote:
if we update or change a document it would require a revision change because it's controlled.
Very good Ken! And if we change a record it is called an update, but the revision level doesn't change. Or does it? If I update a record, then the last entry could be considered the rev level, although it would not show on the master list, which gets back to your statement.
  #4  
Old 15th August 2002, 06:37 PM
Al Dyer

 
 
Posts: n/a
Cool

As my mind is, this may sound too simplistic:

If you change the info on a procedure, instruction, or form, there is a need for a revision.

A record is just that, a record. Do we revise records? I would not think so, revising records could lead to what has been going on recently in many corporations, If we don't like the results let's change the records.

If there is a record that is disfavorable it needs to be acted upon with some type of preventive or corrective action.

Just a thought!

ASD...
  #5  
Old 5th June 2008, 11:19 AM
durnan

 
 
Posts: 4
Re: Document vs. Record - What's the Difference under TS 16949?

Quote:
In Reply to Parent Post by dbzman View Post

Under 4.2.3 Control of documents - records are said to be a special type of document.
I'm in the habit of keeping two control listings. One for records and one for document (intructions, SOPs, etc).
Under this definition if a document has data entered on it then it becomes a record.
Would it be better to just have one listing or is there another way to control records? Am I making this too complicated?

Document is the form in a blank state then it changes to a record when it is filled in.
the document would prob be stored on the hard drive on pc then when it is turned into a record prob filed away. Hope this helps.
  #6  
Old 5th June 2008, 11:30 AM
dbzman's Avatar
dbzman

 
 
Posts: 223
Re: Document vs. Record - What's the Difference under TS 16949?

Hello everyone!


I am coming in on this discussion a little late but it looks like the question is “what is the difference between a document and a record”.
I look at this in a slightly bent way.

The way that I look at records vs. documents is this:

1. If I wanted to see how a job/activity was performed I would look at a record.
2. If I want to look at how a job/activity is to be performed I would look at a document.

Once data is placed on a document it becomes a record.

You would revise a document but not a record. You may update the information on a record (with signatures and dates) but not the revision.

Maybe I just oversimplify but that is my take on the difference.

  #7  
Old 5th June 2008, 11:40 AM
Helmut Jilling

 
 
Posts: 4,223
Re: Document vs. Record - What's the Difference under TS 16949?

Quote:
In Reply to Parent Post by dbzman View Post

Under 4.2.3 Control of documents - records are said to be a special type of document.
I'm in the habit of keeping two control listings. One for records and one for document (intructions, SOPs, etc).
Under this definition if a document has data entered on it then it becomes a record.
Would it be better to just have one listing or is there another way to control records? Am I making this too complicated?


Whatever works best for you. Although, under the general principle of less is better, if you can comfortably do it on 1 log, so much the better. I have seen some companies do that by adding some columns for Retention Times and Storage and Disposal requirements to the right hand side of the log.

The main thing is control the stuff so the information is accurate, and it is available if some needs to read it. If you achieve that aim, you have met the ISO intent pretty well.
Reply

Lower Navigation Bar
Go Back   The Elsmar Cove Forum > Common Quality Assurance Processes and Tools > Records and Data - Quality, Legal and Other Evidence

Do you find this discussion thread helpful and informational?


Bookmarks


Visitors Currently Viewing this Thread: 1 (0 Registered Visitors (Members) and 1 Unregistered Guest Visitors)
 
Thread Tools Search this Thread
Search this Thread:

Advanced Forum Search
Display Modes Rate Thread Content
Rate Thread Content:

Forum Posting Settings
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off


Similar Discussion Threads
Discussion Thread Title Thread Starter Forum Replies Last Post or Poll Vote
The difference between a Document and a Record? David J Quality ISO/TS 16949 - International Automotive Quality Systems Standard 6 11th March 2009 06:53 PM
Difference between Record and Quality Record DAWELAH ISO 9000, ISO 9001, and ISO 9004 - Questions and Discussions 12 16th August 2008 10:11 PM
The Difference between a Document and a Record xiahmi Documentation Control Systems, Procedures, Forms and Templates 5 23rd March 2008 08:52 AM
The Difference between a Document and a Record - Training Plan D.Salman Documentation Control Systems, Procedures, Forms and Templates 11 23rd March 2008 05:53 AM
Document and Record Control - One Procedure or Two? TS 16949 jkittle Documentation Control Systems, Procedures, Forms and Templates 9 17th November 2006 11:57 AM



The time now is 03:53 PM. All times are GMT -4.
Your time zone can be changed in your UserCP --> Options.


   


Marc Timothy Smith - Elsmar.com
8466 LeSourdsville-West Chester Road, Olde West Chester, Ohio 45069-1929
513 341-6272
NOTE: This forum uses "cookies".