SQF System Layout?
First post here!
I am taking over as Quality Manager for someone who is retiring and trying to overhaul our Quality System. We are a small manufacturer with one location. Best suggestions on how to concisely layout SQF system that audits well and is concise. Current system is several binders.
I feel like there are a lot of unnecessary policies? Do I need a policy to say the code doesn't apply to us? Help!!
Good day,
Answering this one first --
Do I need a policy to say the code doesn't apply to us? Help!!
The best SQF (and it was paper) system I ever audited as an SQF Auditor was one that was indexed per the code sequence and for one or two items there was simply a sheet of paper - such as one for contract manufacturers - that simply declared that the company did not utilized the services of a contract manufacturer but that if they ever do they will follow such and such code, etc.
I found their documentation system so well laid out and informative to me as the Auditor that we took the same idea and do the same for our clients - thus our past and the next development client gets indexed binders, for modules 2, 11 and 12 and may include pages that simply indicate that certain items are not applicable.
I liked that when I was an Auditor and Auditors that audit the doc systems that we create now like it too - makes for non-events during the process of an audit.
You could of course buy a BIG binder and put it all in there - indexes in code sequence for 2 and whatever your separate modules are.
Good day,
Answering this one first --
Do I need a policy to say the code doesn't apply to us? Help!!
The best SQF (and it was paper) system I ever audited as an SQF Auditor was one that was indexed per the code sequence and for one or two items there was simply a sheet of paper - such as one for contract manufacturers - that simply declared that the company did not utilized the services of a contract manufacturer but that if they ever do they will follow such and such code, etc.
I found their documentation system so well laid out and informative to me as the Auditor that we took the same idea and do the same for our clients - thus our past and the next development client gets indexed binders, for modules 2, 11 and 12 and may include pages that simply indicate that certain items are not applicable.
I liked that when I was an Auditor and Auditors that audit the doc systems that we create now like it too - makes for non-events during the process of an audit.
You could of course buy a BIG binder and put it all in there - indexes in code sequence for 2 and whatever your separate modules are.
I've attempted to do things like this in the past, but found that there are a few SOPs that would apply to multiple sections of the code. I hesitated putting more than one copy in a binder (document control, I just knew that a copy would get missed if it was updated)... How did you approach this?
I've attempted to do things like this in the past, but found that there are a few SOPs that would apply to multiple sections of the code. I hesitated putting more than one copy in a binder (document control, I just knew that a copy would get missed if it was updated)... How did you approach this?
Yup same here. What I've done is use an excel spreadsheet with each section of the code in order and hyperlink it to the specific "proof" we are complying with that section of the code. It was rather easy to do at that facility because everything was electronic, even our records were scanned and filed in the system.
I'm not sure of another way around this.