Agency-exit checklist · 6 minutes

Finish the website handoff before the final support day.

Use this when an agency, freelancer, or maintenance partner is leaving a website project. The goal is a receiver who can operate the site without reopening the old engagement.

1. 01

   Name the receiver for every control.

   Assign a receiver-owned account for domain, hosting, deployment, source, analytics, backups, renewals, and recovery. Do not send one shared credential as proof of transfer.

2. 02

   Separate transfer from training.

   Access proves control. A short operating note explains the next deploy, restore, renewal, and support request. Keep credentials and confidential client material in the systems already approved for them.

3. 03

   Ask the receiver to verify independently.

   Do not read each item aloud and collect agreement. Let the receiver test their own access and mark Ready, Missing, or Unsure before seeing the outgoing answers.

4. 04

   Resolve gaps while the team still exists.

   A mismatch is cheaper before the final invoice and account shutdown. Write a public-safe resolution, then require the other role to confirm it.

5. 05

   Keep the receipt narrow.

   The receipt should show which controls matched or were resolved. It should never contain passwords, access tokens, private links, customer records, or sensitive evidence.

HandoffMirror records independent control states and confirmed gap closures. It does not move assets, validate ownership, or replace contractual acceptance.

Receiving the site? Use the receiver-side guide →