Why use pre/post-change evidence?

• A. To publish to customers
• B. To estimate cost of changes
• C. To determine staffing levels
• D. Proves starting state, validates success, supports audit and rollback if needed.

Answer: (D)

Pre/post-change evidence provides a concrete record of the system state before a change and the state after. This lets you prove the starting condition, verify that the change achieved the intended result without introducing unintended issues, and create an audit trail showing what was changed, when, and by whom. With this documentation, you can accurately rollback to the pre-change state if needed, since you have a known good baseline to restore. While publishing results, estimating costs, or planning staffing are useful, they aren’t the primary purpose of collecting pre/post-change evidence. The main value is reliable verification, accountability, and a safe path to undo changes when necessary.