Must we state revision date on records and other documents?
Started by Aegean, Sep 06 2012 07:20 AM
Hi All,
Just a question : should we have to state revision date on the records (forms) and other documents (like specifications and procedures etc)?
thnks for quick responses :)
Just a question : should we have to state revision date on the records (forms) and other documents (like specifications and procedures etc)?
thnks for quick responses :)
Date Coding Inner Pouches vs. Retail Boxes: Compliance with Labeling Laws
FSMA Final Rule on Requirements for Additional Traceability Records
204 Rule Compliance for Assembled Sandwiches & Wraps – What Records Are Required?
Food Safety Policy Date – Should It Be Updated Annually Even If Unchanged?
Best Before Date Format for Fresh Pork in Canada – Numeric or Alphanumeric?
[Ad]
Hi There
Unless specified within a particular standard to which you are operating, I would suggest this is really just a matter of preference - with 'pros' and 'cons' for both having and not having an expiry date.
Just some thoughts, which may help:
1) if your documents do not have an expiry date, there should still be a documented procedure for checking both their validity and performance (on a predetermined frequency and to a schedule) - which is usually within internal audit systems.
2) If you produce documentation, specifications for example, that are for seasonal, or non-regular use, it may be worth having an expiry date to act as a trigger to revisit specifications / documents that have not been used for a while.
With Expiry Date:
documents may be revisited and reviewed more regularly - PRO
documents that don't often change still need revising - 'unnecessary' use of resources (time, paper, ink) - CON
increased chance of 'out of date' documents being available, or worse used, at an operating level (especially if there is not one central issuing hub) - CON
during an audit there 'will' be an OOD document found - lost confidence in document control? - CON
Hope this helps, or aids discussion.
Stuart
Unless specified within a particular standard to which you are operating, I would suggest this is really just a matter of preference - with 'pros' and 'cons' for both having and not having an expiry date.
Just some thoughts, which may help:
1) if your documents do not have an expiry date, there should still be a documented procedure for checking both their validity and performance (on a predetermined frequency and to a schedule) - which is usually within internal audit systems.
2) If you produce documentation, specifications for example, that are for seasonal, or non-regular use, it may be worth having an expiry date to act as a trigger to revisit specifications / documents that have not been used for a while.
With Expiry Date:
documents may be revisited and reviewed more regularly - PRO
documents that don't often change still need revising - 'unnecessary' use of resources (time, paper, ink) - CON
increased chance of 'out of date' documents being available, or worse used, at an operating level (especially if there is not one central issuing hub) - CON
during an audit there 'will' be an OOD document found - lost confidence in document control? - CON
Hope this helps, or aids discussion.
Stuart
Hi All,
Just a question : should we have to state revision date on the records (forms) and other documents (like specifications and procedures etc)?
thnks for quick responses :)
Dear Aegean,
A very quick response.
Yes. Maybe not always obligatory but always very highly recommended IMO.
Rgds / Charles.C
Before I answer this, lets ask why do we need the features such as revision date, doc. reference no. and such. Its to keep track of when such a document was established and whether there have been changes and why those changes. All systems are dynamic in nature coz it about continual improvement. When you have the issue date / revision date, reason for revision,... etc, you keep a track of why documents have been amended. Remember, its not necessarily that you remain the document cordinator; may be after sometime, you will have to delegate or leave an organization. The one who replaces you need to understand when the document has been in use and whether any changes have been proposed and such.
In a nutshel, YES, Its necessarly to have the revision statuses of any document. Very important
In a nutshel, YES, Its necessarly to have the revision statuses of any document. Very important
Date Coding Inner Pouches vs. Retail Boxes: Compliance with Labeling Laws
FSMA Final Rule on Requirements for Additional Traceability Records
204 Rule Compliance for Assembled Sandwiches & Wraps – What Records Are Required?
Food Safety Policy Date – Should It Be Updated Annually Even If Unchanged?
Best Before Date Format for Fresh Pork in Canada – Numeric or Alphanumeric?
Chill and Frozen Date Labelling
Dating of required supplier documents?
Records: Paper or Electronic
Document control of records and logs
Electronic Maintenance Records for BRCGS Compliance