Approval Workflow in Simple Terms
An approval workflow answers three questions: who must review this, in what order, and what happens if someone rejects it. In manufacturing it is used for drawings, SOPs, work instructions, engineering change requests, deviations and purchase requests.
ISO 9001 expects documents to be reviewed and approved for adequacy before issue, and an approval workflow is the usual way to show that.
How It Works
- Submit: the author creates or revises the item and sends it for review.
- Review: each reviewer checks it and approves, rejects or comments.
- Route: steps run one after another or in parallel, depending on the rules.
- Release: after the final sign-off the item becomes the current revision.
- Record: names, dates and comments are kept as an audit trail.
Example
A process engineer revises a torque work instruction from revision C to D. The workflow sends it to the area supervisor and the quality engineer in parallel. Quality rejects it once because the torque value does not match the control plan, the engineer corrects it, both approve, and revision D is released while C is withdrawn from the line.
Common Mistakes
- Too many approvers, so simple changes wait for weeks.
- No backup approver when someone is on leave.
- Approvals by email that leave no clear record.
- Releasing a new revision without removing the old one from use.
OperaHive document control software manages approval workflows with revision history and read acknowledgements.