Do not close on deployment state
Assigned, succeeded, and compliant are different signals. Verify the user-facing outcome too.
Launch package 8 · New
Desktop Change Evidence Checklist
A field-ready checklist for making endpoint changes auditable. Capture the baseline, approval, pilot evidence, rollback trigger, and user-impact verification before closing the ticket.
Change controlEndpoint evidenceRollbackVerification
The 20-point evidence path
Check an item only when it is observed, recorded, or linked to evidence. A blank check is an open risk, not a pass.
1. Define the change
2. Capture the baseline
3. Approve and pilot
4. Execute and observe
5. Verify and close
One owner, one exit gate
Give one person responsibility for exceptions and define the evidence required to close.
Trust note
This checklist improves evidence quality; it does not make an unapproved change safe.