SOP – Management Review
Management review is where the food safety system gets its annual MOT – or its quarterly one, if you’re serious. This SOP defines the inputs, the agenda, and making sure the actions actually happen.
SOPs only work if people actually read them. Train each operator, get the read-and-understood signature, and keep the language as plain as the job allows – this isn’t the place to show off vocabulary.
1. Document control
| Field | Details |
|---|---|
| Document title | SOP – Management Review |
| Document no. | [QA-SOP-023] |
| Version | [1.0] |
| Effective date | [YYYY-MM-DD] |
| Prepared by | [Name / Title / Date] |
| Approved by | [Name / Title / Date] |
| Review date | [YYYY-MM-DD] |
2. Purpose
To ensure top management reviews the food safety system’s performance and drives improvement.
3. Scope
Covers the food safety management system of [site name]; held at least [annually].
4. Responsibilities
| Role | Responsibility |
|---|---|
| Top management | Attend; make decisions; provide resources. |
| QA Manager | Prepares inputs; records minutes and actions. |
5. Materials and equipment
- Management review agenda and input pack
- Previous actions tracker
- KPI data
6. Safety precautions
- None specific – it’s a meeting. Keep it focused and finish on time.
7. Procedure
Follow the steps in order. Steps marked [CHECK] are the ones people skip under pressure – don’t.
- Schedule the review with top management; circulate the input pack at least [1 week] ahead.
- Present the standard inputs: audit results, customer complaints, nonconformances and corrective actions, supplier performance, incident/recall events, verification results, training status, and regulatory changes. [CHECK]
- Discuss what the trends are saying – not just the numbers, but what they mean.
- Decide outputs: improvement actions, resource needs, and any changes to policy, objectives or the system itself.
- Record minutes with every action assigned an owner and due date. [CHECK]
- Track actions to completion; review overdue items at the next meeting – or sooner.
- Communicate relevant outcomes to staff; people engage more when they see the system responding.
8. Records
- Meeting agenda and input pack
- Minutes
- Action tracker
9. Revision history
| Version | Date | Change description | Changed by |
|---|---|---|---|
| 1.0 | [YYYY-MM-DD] | Initial issue | [Name] |
Approval and control
| Role | Name | Signature | Date |
|---|---|---|---|
| Prepared by | [Name] | [Signature] | [Date] |
| Reviewed by (QA) | [Name] | [Signature] | [Date] |
| Approved by | [Name] | [Signature] | [Date] |
Keep completed forms for [Define retention period, e.g., 2 years beyond shelf life] at [defined location] – and make sure someone besides you knows where that is.