Which element ensures traceability of changes across SOP versions?

• A. Approvals page
• B. The master copy name
• C. Revision history, including version numbers, dates, and the master copy
• D. The distribution list

Answer: (C)

Keeping a detailed revision history is what enables traceability of changes across SOP versions. It records each update with a version number, the date of the change, and the master copy involved, creating a clear audit trail that shows exactly what was changed, when, and by whom, and allows you to compare or revert to earlier versions if needed. The approvals page notes who signed off but doesn’t systematically capture the edit timeline. The master copy name identifies the current document but doesn’t reveal the history of edits. The distribution list only shows who received the document, not how it evolved. So, the revision history is the mechanism that preserves a complete, auditable trail of all changes across SOP versions.