Академический Документы
Профессиональный Документы
Культура Документы
A Position title (i.e. Leadhand) - the position title is linked to a persons' name listed
in a document of the written program. (i.e leadhands are John Smith and Suzie Smith)
An External Company (i.e PCO) - records are available for review and the personnel
available for interviewing.
A Name (i.e John Smith)
Delegate (i.e Leadhand or delegate) - names of delegated employees are listed in a
document of the written program.
WHAT/HOW
What defines the monitoring, verification and deviation tasks to be completed. Use a simple
sentence to state the goal of the tasks and its expected outcome. What must address the
requirements of the bullet as well as any additional program requirements.
How defines how the tasks are conducted to ensure the company standard, the program standard,
or critical limit is being met. This should be a step-by-step procedure that guide the who and
explains how the task is performed.
WHEN or FREQUENCY
Is the frequency that the monitoring/verification function is conducted.
Frequencies must:
Frequency Examples:
2006-10-27
page 2
RECORDS
Must be listed for all monitoring, deviation and verification procedures. Monitoring, Deviation and
Verification procedures must indicate that records are signed/initialled and dated. Records of
exception (recording only deviations and not recording when conditions are acceptable) are not
allowed.
If on going monitoring is identified, a record must still be generated or it is not considered to be
auditable.
Example: Observing GMPs will be completed on a continuous basis and will be
recorded once per day at the end of the day. Deviations will be recorded whenever
one is observed.
MONITORING PROCEDURES must include, as a minimum:
2006-10-27
page 3
documented so that the responsible employee is able to fully understand and perform the
corrective action(s) appropriately.
It is difficult to predict every deviation that may occur, let alone develop corrective actions
and preventative measures for each. Therefore, deviation procedure will often include the 5
generic steps above that requires the monitor or someone with appropriate authority to make
an on-the-spot decision as to the method to best get the deviation corrected, thereby meeting
the standard again. All information or results related to the 5 generic steps must appear on the
deviation records.
Record must identify all records associated with all of the corrective actions taken.
Deviation records must identify for each corrective action and preventative measure:
-
Verification must assess whether the monitoring procedures are effective enough in
providing the control necessary to maintain the standard or meet the critical limits.
2006-10-27
page 4
Date:_____________
Type of Task
Type of Task: OC = Outstanding CAR; LB = Log Book; HP= HACCP Plan; PPS=Prerequisite Program Sub-element;
HSR = HACCP System Review
2006-10-27
page 5
Outs. CARs
Log Book
CCPs
PP Subelements
HACCP system
Review
INCOMPLETES
Note incompletes identified in the
written program ( nil if none identified)
MONITORING/DEVIATION/VERIFICATION
Note non conforming objective evidence (including
regulatory compliance action) identified during:
- Past record(s) review;
- Interviews;
- On site observations.
( nil if none identified)
AUDIT
FINDINGS
FOLLOW UP
DATE/INITIAL
- Conformity
- Audit
observation
- N/C
- Major N/C
( note CAR # if
applicable)
when:
- amended written
procedures were
reviewed and found
to be complete
and/or
- CAR is closed
(if applicable)
Establishment #: _________
page 6
2.
3.
Specify the requirements in the establishments written plan, FSEP requirements and/or
Program requirements in relation to the deficiency.
Note if an establishments written program does not meet the regulatory or FSEP program requirements,
the establishments program is considered incomplete. Incompletes not corrected during the audit are noted
on the audit report and selected at the next audit.
Part B: Description of Action Plan
2006-07-06
page 7
How to develop an
Acceptable Action Plan
An extension on the agreed upon date for completion of corrective action could be granted under the
following circumstances:
-
requested in writing no later than the committed to date for completion of corrective action;
food safety is not compromised;
the date for completion for corrective action is not met for reasons out of the companys control and this can be
backed up with records (e.g. letter from parts suppliers that a part is on back order); &
the new date for completion of corrective action must be agreed to by the CFIA and this date is entered and initialed
by the CFIA in Part B of the CAR form.
2006-07-06
page 8
Example:
Part A: Non-Conformity
Description of non-conformity:
The companys verification procedures for Sub element E2.1 Pest Control Program
are not being implemented as per the companys written plan as per the companys
written plan and this is considered a non- conformity because it has an impact on the
integrity of this sub element.
During the review of The Pest Summary Report for May-Nov 2003, the warehouse
supervisor completed the verification once per month. The companys written plan
states QC will verify records weekly.
Area of reference (Company written program): E2.1 Pest Control Program
Auditor*: Suzie Safety
Date CAR is issued: January 7, 2004
Date for submission of corrective action (completed Part B) January 21, 2004
Establishment representative*: Carl Control
Date: January 7, 2004
Part B: Action Plan
B.1: Corrective actions:
On January 8, 2004 The QC resumed weekly verification of the pest summary report.
By Jan 12, 2004 QC reviewed all Pest Summary Report Records verified from MayNov 2003 by the warehouse supervisor to ensure they are completed as required by
the written plan, and QC will initial and date all records reviewed. If deviations are
identified during this review, QC will evaluate possible food safety concerns and hold
product for disposition, as appropriate.
Date for completion of corrective actions: Jan 12, 2004
B.2: Preventative Measures:
By Jan 30, 2004, the warehouse supervisor will have been trained by QC to complete
the record verification of the Pest Summary Report and the warehouse supervisor`s
training file will be updated to include this training. On Jan 30, 2004, the written plan
will be adjusted to change the Who for this task from the QC to the Warehouse
Supervisor and this will be logged in the company logbook.
From Jan 30, 2004-Feb 28, 2004, QC will also verify all the Pest Summary Reports
that the warehouse supervisor verified to ensure they are being verified as required,
and he will sign and date all reports reviewed. If any deviations are identified, the
company deviation procedures will be implemented.
Date for completion of preventative measures: Feb 28, 2004
Establishment representative*: Carl Control
Date: Jan
21, 2004
* Print name below signature
2006-07-06
page 9
Audit date:
CAR#:
Major
N/C
Amended
Part A: Non-conformity
Description of non-conformity:
Date:
Date:
Part C: Follow-up
C.1: Written action plan assessment (Part B): Acceptable
Auditor*:
Not acceptable
Date:
CAR closed:
Yes No
Auditor*:
* Print name below signature
2006-07-06
Date:
page 10
N/C
CAR #
ISSUED
2006-07-06
OR
MAJ
DUE DATE
DATE
CLOSED
INITIALS
COMMENTS
page 11
Follow-up Audit 9
ESTABLISHMENT:
Identifies Name, address and registration number of establishment audited.
DATE OF AUDIT:
Identifies day(s)/month/year audit conducted .
SCOPE:
Lists audit tasks including outstanding CARs, Log book, CCP(s), Prerequisite program
sub-elements, HACCP System Review .
AUDITOR(S):
Identifies Lead Auditor and members of the Audit Team, if applicable.
ESTABLISHMENT REPRESENTATIVE(S):
Identifies HACCP Coordinator/designated liaison and any other company
representatives.
REFERENCE DOCUMENTS:
Lists company prerequisite programs, HACCP plans, SOPs etc. reviewed during the
audit.
COMMENTS: summarization of results
Prerequisite Program(s) written program incompletes:
HACCP plan(s) written program incompletes:
Audit Findings (Audit Observations (including objective evidence) and Part A of
CARS):
2006-07-06
page 12