These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Food and Beverage QMS
- Process
- Audit and document review
Audit and document review
Audits and controlled documents give the quality team two related review paths. The audit records the scope and auditor; findings carry owners, due dates and closure dates. A controlled revision carries a version, effective date, file and status. A person can acknowledge the version they received.
Step by step
-
Plan the audit Auditor
Auditor sets the scope, planned date and audit number, and the audit begins as Planned.
- Set scope, schedule and auditor
- Updates Audits, People
-
Record findings Auditor
Auditor records each requirement, finding and severity under the audit, with an owner and due date.
- Assign issues and due dates
- Updates Audit findings, Audits, People
-
Review the report Auditor
Auditor examines findings while the audit is Reporting and confirms that scope and follow-up are clear.
- Confirm scope and follow-up
- Updates Audits, Audit findings
-
Review the revision Quality Manager
Document Controller enters a titled version and file in Review. Quality Manager decides whether it becomes Approved with an effective date.
- Decide effective version
- Updates Controlled documents
ApprovalA person approves before the work moves on. -
Acknowledge the document Document Controller
Document Controller follows which People acknowledged the approved controlled documents revision and when.
- Record who received the revision
- Updates Training acknowledgments, Controlled documents, People
Who does what
Roles and permissions- Auditor
- Owns audit records; Quality Manager reviews decisions; Document Controller handles revisions and acknowledgments.
Set up Food and Beverage QMS your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.