Verification checklist

Post-Cleanup Verification Checklist for X Accounts (2026)

Cleanup execution is only half the job. The other half is verification: proving what was removed, confirming what stayed protected, and identifying whether any visible leftovers are true residuals or short-term UI lag.

This checklist gives operators a clear close-out protocol for founder and agency cleanup runs.

A. Identity integrity checks (must pass)

• Profile photo unchanged
• Banner unchanged
• Bio and link fields unchanged
• Followers/following counts not unexpectedly altered

If any of these fail, stop and resolve before content verification.

B. Scope completion checks (posts/replies/reposts/likes)

For each selected cleanup scope, log:

• target IDs in batch,
• successful actions,
• failed actions,
• remaining IDs for follow-up.

“No errors in console” is not enough. You need count-level confirmation.

C. Residual detection checks

When old activity still appears, classify quickly:

1. cache lag: visible in one session only,
2. propagation lag: inconsistent across checks within short window,
3. residual: stable visibility across multiple checks after follow-up.

This avoids both false alarms and false confidence.

D. Multi-view validation checks

• Desktop browser (logged in)
• Mobile app (logged in)
• Secondary browser session
• Optional logged-out profile check for public post/repost visibility

Use UTC timestamps so your support and engineering notes align.

E. Quality gate checks before closing run

• All critical residual IDs either removed or documented
• Follow-up window scheduled (typically 12-24h)
• Action log written with operator + run timestamp
• Customer-facing summary drafted in plain language

F. Recommended close-out note format

Keep close-out notes short and structured:

• Run ID: date + operator + scope
• Outcome: complete / follow-up required
• Verification: sample size + residual count
• Next check: UTC date/time

Structured notes reduce support time and improve repeatability.