I didn't say review at "scheduled intervals", I said "planned intervals"....back to semantics.
We "plan" to review the SOPs subsequent to the following precipitous events:
No it won't satisfy 4.2.3 b...You have to ensure that you plan to review documents under any of the conditions mentioned above...and possibly others (this list not intended to be exhaustive). The review does not necessarily guarantee that there will be a "process change" (example...a new standard comes out...the SOP is reviewed for compliance...No changes to documentation are deemed necessary...You still had to have the review). They may result in a 'Process change", but a "process change" is only one event which might trigger a review of an SOP.
Patricia
We "plan" to review the SOPs subsequent to the following precipitous events:
a) When the SOP fails to meet performance objectives.
b) When System Audits identify nonconformances, the root-cause of which lie in the inadequacy and/or inaccuracy of the SOP.
c) When errors/omissions/suggestions for change are submitted to the SOP owner.
d) When there is a process/technological change that impacts on the respective SOP.
e) When there is re-assignment/change in ownership of the SOP.
f) When changes/revisions are identified in sources which impact on the design/documentation of the Management System, including changes in: -
b) When System Audits identify nonconformances, the root-cause of which lie in the inadequacy and/or inaccuracy of the SOP.
c) When errors/omissions/suggestions for change are submitted to the SOP owner.
d) When there is a process/technological change that impacts on the respective SOP.
e) When there is re-assignment/change in ownership of the SOP.
f) When changes/revisions are identified in sources which impact on the design/documentation of the Management System, including changes in: -
-Corporate/Divisional Requirements
- ISO 9000 (or any other Standard, as applicable)
- Policy Statement
- Customer-specific requirements
- Legal/regulatory requirements.
- Environmental requirements
- Health and Safety requirements...etc., etc.
- Any other requirements/guidelines to which the organization subscribes
- ISO 9000 (or any other Standard, as applicable)
- Policy Statement
- Customer-specific requirements
- Legal/regulatory requirements.
- Environmental requirements
- Health and Safety requirements...etc., etc.
- Any other requirements/guidelines to which the organization subscribes
No it won't satisfy 4.2.3 b...You have to ensure that you plan to review documents under any of the conditions mentioned above...and possibly others (this list not intended to be exhaustive). The review does not necessarily guarantee that there will be a "process change" (example...a new standard comes out...the SOP is reviewed for compliance...No changes to documentation are deemed necessary...You still had to have the review). They may result in a 'Process change", but a "process change" is only one event which might trigger a review of an SOP.
Patricia
