Document release

Step by step

1. Prepare revision Document Controller

   Document Controller enters the title, version, attachment and intended effective date of a controlled document. Draft identifies work still being prepared.

   • Captures title, version, date and attachment
   • Updates Controlled documents

2. Submit for review Document Controller

   The controller sends the revision to Review after checking that the file and revision identity agree. The reviewer needs the actual attachment as well as the title.

   • Presents the revision for decision
   • Updates Controlled documents

3. Approve release Document Controller

   Document Controller verifies the title and version before approving the release. The controlled document moves from Review to Approved and the effective date gives readers its operating context.

   • Makes the reviewed revision Approved
   • Updates Controlled documents
   ApprovalA person approves before the work moves on.

4. Record acknowledgment Document Controller

   The controller links each person's training acknowledgment to the approved document and records the acknowledgment date. The link identifies the specific revision that person acknowledged.

   • Connects a person and date to the revision
   • Updates Training acknowledgments, Controlled documents, People

5. Retire an older revision Document Controller

   When a newer approved revision replaces the old instruction, the controller marks the old record Obsolete under the team's agreed change practice. Its history stays available for a later review.

   • Distinguishes the superseded record
   • Updates Controlled documents

Document Controller

Prepares, approves and tracks the revision.

Inspector

Uses the effective instruction during assigned inspections.

Admin

Manages the linked person and user identities.