What should a revision history include to enable traceability?

• A. Training schedule only
• B. Changes, rationale, dates, and sign-offs
• C. Audit findings summary
• D. Access log only

Answer: (B)

Tracking what changed, why it changed, when it changed, and who approved it is essential for traceability. A revision history that includes changes, rationale, dates, and sign-offs provides a complete record of the document’s evolution: exactly what was altered, the reason for the change, when it was made, and who authorized it. This makes it easy to audit, verify updates, and, if needed, revert to a prior version.

The other options don’t serve traceability as directly. A training schedule focuses on training activities, not the evolution of the document itself. An audit findings summary relates to the results of an audit, not the document’s revision trail. An access log shows who opened the document, not what was changed or who approved those changes.