Skip to content

Website Handoff

A website handoff is the structured transfer of access, documentation, knowledge, and operational responsibility for a website from one person or team to another.

A website handoff is the structured transfer of access, knowledge, documentation, and operational responsibility from one person or team to another.

It commonly happens at the end of a project or when responsibility for an existing website changes.

What a Handoff Can Include

A useful handoff may include:

The exact list depends on the project.

Handoff Is More Than Credentials

Sending:

username + password

is not a complete handoff.

The recipient may still not know:

  • What the account does
  • Whether it is important
  • Who owns billing
  • Which environment it controls
  • What will break if it disappears
  • How changes are deployed
  • Which dependencies need maintenance

A useful handoff transfers understanding as well as access.

Ownership Transfer

Where possible, foundational accounts should already be organization-owned.

The handoff can then focus on:

  • Removing unnecessary contractor access
  • Adding new administrators
  • Transferring operational responsibility
  • Confirming billing
  • Reviewing account recovery

This is safer than transferring personally owned accounts after the project ends.

Why It Matters

A website should not become difficult to operate simply because the original developer is unavailable.

A good handoff reduces Single Points of Failure and makes future maintenance more competitive and flexible.

Common Problems

Common problems include:

  • Handoff postponed until relationship has ended
  • Accounts owned personally by contractor
  • No repository access
  • Unknown plugins or subscriptions
  • No documentation
  • Shared passwords
  • Former vendor retains administrator access
  • Nobody tests the transferred access
  • New team receives files but not deployment knowledge

How to Improve

Treat handoff as a project deliverable.

Before closing the work:

  1. Review accounts
  2. Confirm organization ownership
  3. Transfer appropriate Administrative Access
  4. Deliver Technical Documentation
  5. Confirm Version Control
  6. Explain Deployment
  7. Verify Backup & Restore
  8. Review dependencies
  9. Remove unnecessary access
  10. Confirm who owns maintenance next