# AI website change recovery worksheet

Use one copy for one suspected change. Keep secrets, passwords, tokens, private customer records, and payment data out of this file.

## 1. Incident record

- Website / project:
- Date and time noticed:
- Reported by:
- Recovery decision owner:
- Release owner:
- Current public URL:
- Current workspace / draft identifier:
- Last known-good identifier:
- Is the live site affected? Yes / No / Unknown
- Are new edits paused? Yes / No
- One-sentence symptom:
- Business impact:
- Immediate safe workaround, if any:

## 2. Reproduce and preserve

- Exact route:
- Viewport / device:
- Account or visitor state:
- Steps to reproduce:
  1.
  2.
  3.
- Expected result:
- Observed result:
- Evidence saved:
- Current state preserved before recovery? Yes / No / Not available
- Later useful work that must survive:

## 3. Layer map

Mark each layer as Affected, Unaffected, Unknown, or Not applicable.

| Layer | Status | Evidence / owner |
| --- | --- | --- |
| Page copy and media |  |  |
| Layout, styles, and responsive behavior |  |  |
| Site code and configuration |  |  |
| CMS content |  |  |
| Application database records |  |  |
| Uploaded files / storage |  |  |
| Forms and lead destinations |  |  |
| Authentication and permissions |  |  |
| Analytics and tags |  |  |
| Domain, DNS, and TLS |  |  |
| Email, CRM, payments, bookings, or other external services |  |  |
| Live deployment |  |  |

## 4. Checkpoint comparison

- Candidate checkpoint / version ID:
- Created at:
- Created by or associated change:
- Is a read-only preview available? Yes / No
- What the checkpoint contains, according to the platform:
- What it explicitly excludes:
- Retention or plan restriction checked:
- Current state observations:
- Checkpoint observations:
- Difference that explains the symptom:
- Useful later changes that a restore would remove:
- External actions a restore cannot reverse:

## 5. Recovery decision

Choose the smallest action that corrects the affected layer.

| Option | Best when | Risk / note | Selected? |
| --- | --- | --- | --- |
| Undo or edit one item | The defect is narrow and current state is otherwise correct | Requires precise identification |  |
| Revert one change | One bounded code change caused the defect | Dependencies may conflict |  |
| Restore a workspace checkpoint | Many file changes are wrong and the checkpoint scope matches | Can replace useful later workspace work |  |
| Restore data separately | The problem is in CMS or database records | May overwrite newer records |  |
| Repair forward | Current data or later work must remain | Needs a bounded implementation and tests |  |
| Roll back the live release | Visitors face severe production impact | Does not necessarily repair the working draft |  |

- Selected action:
- Why it is the smallest safe action:
- Approved by:
- Approval time:
- Stop conditions:
- Preserved state location / identifier:
- Separate external recovery actions:

## 6. Verification plan

List only checks that match the incident, plus critical connected journeys.

| Check | Environment | Evidence | Result |
| --- | --- | --- | --- |
| Original symptom no longer reproduces |  |  |  |
| Intended copy / layout / behavior is present |  |  |  |
| Useful later work remains |  |  |  |
| Phone layout |  |  |  |
| Desktop layout |  |  |  |
| Keyboard and focus behavior |  |  |  |
| Form or business journey reaches its destination |  |  |  |
| Current CMS / database records remain correct |  |  |  |
| Permissions and account states remain correct |  |  |  |
| Analytics / external services remain connected |  |  |  |
| Production hostname and critical routes |  |  |  |

## 7. Completion record

- New baseline identifier:
- Public release identifier, if authorized:
- Released by:
- Release time:
- Production verification result:
- Known items, owners, and dates:
- Client-facing explanation:
- Follow-up process change:

## Example completion note

Illustrative only: "The current homepage layout broke at narrow widths after change C42. We preserved C42 and the current database, compared checkpoint C41 in read-only preview, and repaired the navigation forward rather than restoring the whole workspace. The menu, focus order, contact route, and phone and desktop layouts passed on candidate C43. The agency release owner published C43 and repeated the menu and contact checks on the production hostname. No database or CRM recovery was performed."
