What's New Unreplied Topics Membership About Us Contact Us Privacy Policy
[Ad]

Revisions on SQF Procedures

Started by , Nov 10 2022 04:00 PM
6 Replies

I am reviewing my company procedures for the SQF. As I understand it, it needs to be reviewed yearly, but not necessarily changed if there aren't changes in the process.

 

How would it be noted that the procedure is reviewed? Would you add another revision or have a separate review line?

 

Thanks!

Share this Topic
Topics you might be interested in
Revisions on SOPs How to manage document revisions? Do I change a documents revisions status if I only change its name? Revisions of Controlled Documents Guide To The Issue 2 Revisions
[Ad]

I've used something as simple s a page at the end of the SQF/SOP book saying all procedures were reviewed on:, by:.  Currently, I use a simple document audit sheet, that shows the date I reviewed the document, lists any changes if needed and I sign off on it.  However works best for you to show that you are reviewing documents.  I would also think if you are using the checklist from SQF to review the system every year that could also show evidence that you are reviewing documents.

2 Likes1 Thank

We maintain review dates in our Master Document List instead of in the actual document (though we do note draft dates and effective dates in the document).

1 Like

I use a reassessment form for all procedures as well as for my internal audits (the same form)

 

I can fill it in electronically, and it simply asks if it was compliant to the code or not,  if it's all good, a tick in the compliant box and move on

1 Like

All good suggestions.

The answer is "whatever works best for you".

 

Excel document that has conditional formatting that shows when a document is due for review, and a box that you can tic (Scampi) that shows that the document was reviewed and no changes were necessary, along with a review date.

 

Software solution where you set up documents for review, when said document comes up for review, you review and indicate that the document was reviewed and changes were made (or not). Software keeps an audit log.

 

Table on the document itself that shows a revision/review history.

 

Again, whatever works best for you. As long as you can show that documents are being reviewed in accordance with whatever standard you are certificated against, and you can show that what you are doing is what you say you are supposed to be doing, is fine.

 

Marshall

I've done this a couple of different ways.  At one company we would divide portions of our FSQMS into sections, review a section during a quarterly management meeting (documenting which procedures were reviewed in meeting minutes), and have the food safety team sign off on the meeting.  Another way was to break the SQF code down by the program it covered in my FSQMS (receiving/shipping, sanitation, etc) onto some internal forms, and review the programs throughout the year to make sure each part was covered over the year.  Both have been accepted by SQF auditors.

 

I've never believed in the need to reprint/reissue a document with a note in the revision history stating the document was reviewed with no changes.  By having the reviews documented separately, it covered me when an auditor would notice a document was last revised years ago.  I'm lazy in that I don't want to reprint my entire FSQMS over the course of each year, and depending on the size of your manual it can be a lot of printer toner saved.

I use a chart at the end of the document that lists the changes, if any, with the date or review. If a new revision is issued, I list in on the chart, save it as a new document and then move the previous version to an archive folder. I have had auditors ask why I print every document in the FSQM but as long as I can produce the document with a review from the last 12 months, or less, I haven't had any push back.


Similar Discussion Topics
Revisions on SOPs How to manage document revisions? Do I change a documents revisions status if I only change its name? Revisions of Controlled Documents Guide To The Issue 2 Revisions