Opening the book…
Controlled procedures support consistency while change control enables justified improvement. A change must be assessed before implementation for its effect on product quality, safety, data integrity, validation, training, and regulatory commitments. Not every affected person must personally approve every change; the required reviewers and approvers follow defined responsibilities.
A document change request may be initiated by anyone permitted under the procedure. It identifies the current document, proposed revision, reason, impact, approvals, effective date, distribution, and training. Different organizations use different names for this record.
Document-control personnel release the approved revision and prevent unintended use of obsolete working copies. Retain historical versions and change records as required. Do not destroy completed records simply because their associated instructions have been revised.
A change notice can include the request identifier; date; initiator; document title and revision; existing and proposed wording; scientific or business justification; impact assessment; affected departments and linked documents; training and validation actions; approvals; implementation date; and confirmation that actions were completed. Cost can be included when relevant but does not replace a quality impact assessment.
This page titled 13.18: Managing Changes in Documentation was last modified on Sun, 08 Nov 2026 21:47:00 GMT and is shared under a CC BY-SA 4.0 license and was authored, remixed, and/or curated by Emalee MacKenzie.
The book could not be loaded just now.