V
venkat
What is the difference between document and report. Can we say that all reports are documents
Can I have the views of others please
Can I have the views of others please
Elsmar Forum Sponsor
A
Al Dyer
venkat:
Written/electronic reports are documents.
I can't think of any document that did not report something, whether it be procedure, instruction, templates, evidence etc...
-Is a flow chart a document? Yes
-Is a flow chart a report? Yes, It report how the process is set-up.
-Is a control chart a document? Yes
-Is a control chart a report? Yes, it reports the characteristics to be controlled.
ASD...
Written/electronic reports are documents.
I can't think of any document that did not report something, whether it be procedure, instruction, templates, evidence etc...
-Is a flow chart a document? Yes
-Is a flow chart a report? Yes, It report how the process is set-up.
-Is a control chart a document? Yes
-Is a control chart a report? Yes, it reports the characteristics to be controlled.
ASD...
CarolX
Trusted Information Resource
Al,
Some thoughts....
A drawing - document, yes, a report???? no
Procedures - document - yes, a report???maybe if required to record some data or information.
Just throwing it out to see how it bounces back
CarolX
Moderator test edit 9/13/01
Some thoughts....
A drawing - document, yes, a report???? no
Procedures - document - yes, a report???maybe if required to record some data or information.
Just throwing it out to see how it bounces back
CarolX
Moderator test edit 9/13/01
Last edited by a moderator:
Wes Bucey
Prophet of Profit
The professor pontificates:
All the written information (electronic or hard copy) "in the organization" is comprised of documents.
Records are a special category of documents which are a snapshot history of an activity.
Reports are documents which are compilations or explanations of records. (Example - an organization may have a series of 100 inspection records on the production of a widget on four separate machines. A report of the inspection records might conclude that one of the four machines ought to be retired because it does not seem capable of maintaining control over critical dimensions.)
Does this help make sense of the terms?
All the written information (electronic or hard copy) "in the organization" is comprised of documents.
Records are a special category of documents which are a snapshot history of an activity.
Reports are documents which are compilations or explanations of records. (Example - an organization may have a series of 100 inspection records on the production of a widget on four separate machines. A report of the inspection records might conclude that one of the four machines ought to be retired because it does not seem capable of maintaining control over critical dimensions.)
Does this help make sense of the terms?
Last edited:
Thinking of you, Wes! Documentation Out of Control - What classifies as a document?
Wes Bucey
Prophet of Profit
In addition to understanding definitions of
document
record
report
folks need to tune in on
management
maintenance
Control
retention
Configuration Management
There certainly seems to be a lot of confusion and anxiety about the topic of dealing with documents. There are a lot of folks who are bombastic in saying they have the only true way.
Some folks get so enamored of electronic systems they forget "one size does NOT fit all." Many small organizations can get by with paper and filing cabinets.
"Configuration Management" is very confusing when folks don't include "associated documents" and processes as part of the thinking of what else needs to be considered when modifying a document.
The entire process of FORMALLY modifying or revising a document is frequently haphazard at many organizations. Entire books are written on changing documents, but even I don't buy those books. Where do people learn how to do this is a systematic, uniform manner?
document
record
report
folks need to tune in on
management
maintenance
Control
retention
Configuration Management
There certainly seems to be a lot of confusion and anxiety about the topic of dealing with documents. There are a lot of folks who are bombastic in saying they have the only true way.
Some folks get so enamored of electronic systems they forget "one size does NOT fit all." Many small organizations can get by with paper and filing cabinets.
"Configuration Management" is very confusing when folks don't include "associated documents" and processes as part of the thinking of what else needs to be considered when modifying a document.
The entire process of FORMALLY modifying or revising a document is frequently haphazard at many organizations. Entire books are written on changing documents, but even I don't buy those books. Where do people learn how to do this is a systematic, uniform manner?
M
Mr BS7799
Just wanna add a bit to the action.
Here's my analogy:
A document is used BEFORE the action. A record is done AFTER the action.
Example:
a. Inspector Gadget wants to perform outgoing QC on a number of items.
b. He reads/browses through the Outgoing QC Procedure. (document)
c. He then proceeds to conduct the outgoing QC inspection (action)
d. He fills-in the appropriate records. (record)
Records are "evidences or proofs" that the process owner has done something.
Here's my analogy:
A document is used BEFORE the action. A record is done AFTER the action.
Example:
a. Inspector Gadget wants to perform outgoing QC on a number of items.
b. He reads/browses through the Outgoing QC Procedure. (document)
c. He then proceeds to conduct the outgoing QC inspection (action)
d. He fills-in the appropriate records. (record)
Records are "evidences or proofs" that the process owner has done something.
