Clause 3.2 Documentation Control - Version Control Question?
As depicted in Clause 3.2 Documentation Control a version number is needed to show the latest revision. I have a list of all documents and their last revision dates to reflect documents currently in use. Can I use the last revision date of said document to work in lieu of a version number?
As depicted in Clause 3.2 Documentation Control a version number is needed to show the latest revision. I have a list of all documents and their last revision dates to reflect documents currently in use. Can I use the last revision date of said document to work in lieu of a version number?
My understanding of the version number is the ability to achrive your records or historicaly see the changes you made to your documents.
Revision date would be the date the version number changed let's say from 1.0 to 2.0.
In addition there are only 3 possible states documents should exist:
Working File
Draft
Archive
In your list of documents you should have an additional column for version number and the revision date.
As depicted in Clause 3.2 Documentation Control a version number is needed to show the latest revision. I have a list of all documents and their last revision dates to reflect documents currently in use. Can I use the last revision date of said document to work in lieu of a version number?
FWIW, for policies, programs and procedures, I have a version number and date of revision on all of my documents. I also include a table at the end of the document that lists revision number, date of revision and reason for revision.
For process paperwork, I have a revision number and date of revision as the footer on the paperwork.
I keep all document info in an Access database with document title, original approval date, revision number, revision date, approval authority and reason for approval/revision. That allows me to print a report with all pertinent info.
Marshall
IMEX, BRC auditors are not usually “picky” over the finer aspects of documentation procedures, unlike ISO, as long as the practical implementation is within the BRC context and demonstrably effective.
Beautiful, NASA-type schematics are wonderful if you hv someone else to do the data processing IMO. Otherwise it can become a labour of Pain.
I hv certainly seen yr method used in some non-BRC applications although, for reasons such as mentioned in previous posts, it is rather unorthodox / inelegant and will surely be irritating to some auditors. Personally, I contacted my auditors in advance of the main audit and verified that the documentation system I proposed to use was in principle acceptable to them. Just a thought.
Rgds / Charles.C