Batch record Review before release of finish product

Hello, 

I don't see anywhere specifically where SQF code 2 & 11 require a Batch Record Review before release of finish product, however I see it as a best practice. How have people integrated this with SQF in the past to explain to their teams we should be performing a batch record review? Also who was responsible for the review; Production, QA, someone else?

Thank you 

It's under 2.4.7 Product release that you must have a method in place for releasing product. So no, it doesn't have to be batch records UNLESS there is something specific that needs to be verified prior to product being release (for me it's pH tested for each batch)

But perhaps you need to verify metal detection records, or sensory etc and perhaps you don't have anything in which case you will write a policy stating as much (but your probably checking labels or something that you could incorporate into the policy)

If you don't perform a batch review, how do you know there were no non-conformances?  Are you just relying on your production staff to alert you every time there is a non-conformance?  That's asking for trouble, IMHO. 

At my previous position at a food plant, my QA team conducted batch review of every single batch...and we regularly found non-conformances that would have otherwise gone unreported.  Granted, many were minor...but some were pretty serious, and even minor non-conformances can indicate the beginning of a serious problem.

Not a SQF user but it's a question as to whether either "Positive" or "Negative" Release (or either) is accepable.

The former necessitates a (satisfactory) review.

What does SQF Guidance say ?

Hello - thank you everyone for your comments. We have it built into our product release program that the product is release after QC tests the finish product and all is within spec(GC, RI, SG). I am attempting to implement the batch record review to have a final verification of the entire batch record, to ensure the pours do not look off, inventory location looks correct, etc.... How have others implemented this and in what department?

It sounds like you should have a QC manager review the records generated by the QC tests that currently release the product and sign off on it.

In my position, I review the 'daily paperwork' as we call it informally, which includes production documenting lot codes, product weights, pre-op inspections, as well as receiving and shipping documents (temperature control, cleanliness, and security), temperature monitoring logs, and quality inspection reports.  I assemble them all into a 4-6" packet with a cover page I made where I check off the documents in the packet I'm signing off on.  It's not really pretty but it does ensure that a senior QC person is reviewing the paperwork and makes it really easy to find what you're looking for if you ever want to go back and look in your records.  They're all together and dated and sorted.

not all process' will allow for a review of records PRIOR to product being shipped (i.e. slaughterhouse) then it's up to the QA tech to put product on hold if it needs rework etc...in which case it would be a negative release program; QA is monitoring production throughout the day and would catch an issue as it occurred, then that portion would be held (or more depending)....paperwork is not actually reviewed until the next day

Whatever your program ends up being, it has to be attainable and sustainable

The SQF guidance Tony posted does not actually require a "batch review record" but rather that production records are completed, reviewed and maintained

Hello - thank you everyone for your comments. We have it built into our product release program that the product is release after QC tests the finish product and all is within spec(GC, RI, SG). I am attempting to implement the batch record review to have a final verification of the entire batch record, to ensure the pours do not look off, inventory location looks correct, etc.... How have others implemented this and in what department?