A business analyst uses Copilot chat to draft a release checklist, accepts several edits that added wrong owners and dates, and needs to keep the good early draft without manually retyping everything. Which revert method should the analyst use to revert changes by using checkpoints?

Copilot chat automatically saves session checkpoints as the draft evolves. Open the checkpoints list in the same session and restore the version captured just before the incorrect owner and date edits; this returns the conversation and draft to the good early state, keeping useful work without manual retyping. Saving a new checkpoint that preserves the draft with incorrect edits only snapshots the current state for future safety; it does not roll anything back, so the wrong owners and dates remain. Restoring the checkpoint saved before checklist drafting began rewinds too far, removing the good early draft and requiring the checklist structure to be rebuilt. Opening a new chat session and trying to restore the checkpoint from before the incorrect edits fails because checkpoints belong to the session that created them, and a separate session cannot access that history. An exam caveat: read checkpoint timing carefully; a point before the incorrect edits preserves good work, while one before drafting began loses it, and restoring after the edits retains errors. As a practical check, preview the checkpoint timestamp and content snippet in the list to confirm it shows the clean checklist without the wrong owners and dates before you confirm the restore.