A website handoff should leave the business able to identify its accounts, understand who controls them, and recover access through legitimate account recovery. Keep an ownership register with account names, responsible people, renewal dates, and support contacts. Store credentials securely and separately from that register.
Start with the domain and hosting
Record the registrar, domain owner, renewal method, hosting provider, and who manages DNS. A business email address that belongs to the company should receive important account notices. Check that the organization can access its own accounts rather than relying on one person’s memory. This is part of owning the website strategy.
Include the services visitors never see
Forms, transactional email, booking, payment connections, licensed plugins, and image subscriptions may all affect the site. List what each service does and which account pays for it. Mark subscriptions that belong to a developer’s license so the business understands what changes if the support relationship ends.
Define routine and emergency responsibilities
Name the person who edits content, approves changes, checks inquiries, and contacts hosting support. Identify a backup person for absence or departure. The maintenance guide helps connect account ownership with day-to-day care.
Verify the handoff with a small task
Ask the business owner to sign in, find a recent inquiry, and make a harmless content update in the agreed workflow. Confirm where backups are managed and who can restore them. A folder labeled ‘handoff’ is less useful than demonstrated access and clear instructions.
What should stay out of the document?
Do not put passwords, recovery codes, private keys, or payment details into a shared project document. Record where authorized users can obtain access securely instead. Review the register when people or providers change. The build and launch process should end with operational ownership, including a clear route for ongoing help.
