Document Structure for Hazard Analysis Worksheet and CCP Decision Tree
Hi all,
All this while our Hazard Analysis Worksheet categories in Level 4 , under type 'Form" ., so it wouldn't be have any changes on Revision No and Date whenever we have new input on Hazard Analysis Worksheet & CCP Decision Tree. Any changes will be reflected in revision history .
However, this commented by auditor shouldn't categories under Level 4, any changes the content of worksheet should reflect on the documents.
.
May i know how u guys control over Hazard Analysis Worksheet , which level categorized in it.
Greetings Carine,
I am really sorry but I can't make sense from what you are writing and what is the actual question / problem. What does "Level 4" refer to and what is its relation to the "Form" and what is this ????? What does the categorization have to do with the revision of a document ??? If the auditor raised an N/C on this, please provide the exact wording.
Regards.
If you're saying that you do not revise your document date when you input a new hazard and decision tree than I side with the auditor.
These 2 documents make up the very foundation of your food safety plan and MUST be revised when changes are made
If you're saying that you do not revise your document date when you input a new hazard and decision tree than I side with the auditor.
These 2 documents make up the very foundation of your food safety plan and MUST be revised when changes are made
Yes, this is what im trying to said. because we treat HACCP worksheet as 'FORM", there is no revision changes regardless how many times contents had change unless the worksheet format had changed.
The HACCP worksheet is not a form no matter how you look at it. It's something dynamic and when you make changes it needs be updated to the current revision/version. You may know the current version, but how will other people recognize it? How will you prove that your HACCP remains up-to-date with legislation etc if the date on top is for example from 2010 ? An auditor may take your word for it, a state authority inspector even less but why get in all this potential trouble?
Lastly the first edition/ edition/ revision/ version in every standard, whatever term may someone use are there so you can track the current version. ISO 22000 is 2nd edition, BRCGS is Issue 9, IFS is version 8, FSSC is going to v6. They are based on the same "form" but there are changes to the content and the essential point is the content and that's what you track with the revision.
Without knowledge of what "Level 4" is referencing in your docs, I can explain how I've done document control numbers in the past:
For all forms, things that get filled out by staff, they followed a dept-form#-version# number format. Example: QAC-101-1.2. The version number decimal would be changed to reflect minor changes on the form (adding an extra signature line, an extra check box, etc). The primary number would reflect a large scale revision (totally rewriting a receiving form would bring about version 2.0). I never added revision histories to forms to keep them from being too long on the floor, but I do keep the revision histories in a change control log where all document changes are recorded.
For SOPs, programs, policies, they'd follow a xx.xx.xx.xx number format similar to the SQF structure. Example: 2.5.7.1. I never mirrored their format, instead normally splitting my FSQMS into 29 chapters. First number denotes the chapter, second number counts the documents within that chapter, third and fourth numbers denote sub-programs related to the documents in that chapter. So 14.2.0.0 might be my Equipment Sanitation Program within my Sanitation chapter, where 14.2.1.0 thru 14.2.12.0 might cover 12 different sanitation procedures for specific equipment. Those numbers never change when a revision is made to the document, as the document control number does not include a revision number. But the full revision history of those SOPs and programs is at the end of each one, and the current date of that doc is joined with a supersedes date that correlates to the revision history.
TL;DR to the OP's question: I don't use revision numbers in my SOPs/programs, but I absolutely do update the date when ANY change is made, and cover it in the revision history within that document.