Document release and acknowledgment

Review a new quality document version and retain each person's acknowledgment history.

Step by step

Prepare revision Document Coordinator

Document Coordinator creates a document with title, version, effective date and attachment.
- Establishes the version and effective date
- Updates Controlled documents
Send to review Document Coordinator

The revision moves from Draft to Review for Quality Manager.
- Requests a release decision
- Updates Controlled documents
Approve release Quality Manager

Quality Manager reads the new version and approves it for use.
- Makes the reviewed revision Approved
- Updates Controlled documents
ApprovalA person approves before the work moves on.
Acknowledge Document Coordinator

Document Coordinator records the person and acknowledgment date for the approved document.
- Records who acknowledged the document
- Updates Training acknowledgments, People
Amend Document Coordinator

A later change creates a new version while earlier acknowledgments stay linked to their documents.
- Preserves prior revision history
- Updates Controlled documents, Training acknowledgments

And how to keep it from happening.

A version is changed in place after release. Create a new revision so old acknowledgments retain their meaning.
An acknowledgment has no named person or date. Complete both before using it as training evidence.
A Draft attachment is treated as current instruction. Use the approved version and effective date when the team begins an inspection.

Start free, then use Proto to change fields, steps and approvals before your team goes live.