PIGEONROCKET / FIELD GUIDE
Website ownership and handoff
Know which accounts, assets, access and instructions your business needs before a website project is finished.
By Stephanie · Published November 21, 2026
Your website can be live, paid for and still difficult to manage without the person who built it. That usually becomes obvious at the least convenient moment: a renewal fails, a form stops arriving or you need to change providers.
A useful handoff explains how the site operates, who controls the important accounts and what your team can do next. Discuss this before the project begins, then test it before calling the project complete.
Separate the parts people call the website
The domain is the address registered through a registrar. Hosting runs the site. A content management system lets people manage content. Email may be provided by another service. Analytics, forms, payments and other integrations can each have their own accounts and responsibilities.
One provider may manage several of these, but they are still separate parts. Ask for a plain-language map of the services, account holders, billing arrangements and renewal dates. Your business should know where each part lives.
For the domain, confirm that the registration and contact details reflect the intended business holder and that the business can recover the account. ICANN's registrant information explains the role and responsibilities of a domain registrant. Domain registration and ownership of the site's design or content are separate questions.
Agree what is transferred and what is licensed
Ask the project agreement to identify the deliverables, usage permissions, editable materials and transfer conditions. A custom design, a licensed typeface and a subscription plugin may have different terms. Paying a project invoice does not explain all of those arrangements by itself.
Request a record of the paid themes, plugins, fonts, imagery and services the finished site relies on. Confirm who renews them, whether a license can transfer and what happens if you stop working with the provider. If a limitation could affect the business, resolve it before approval rather than discovering it during a move.
Keep access useful and secure
Use business-controlled recovery details and individual user accounts where the service supports them. Give collaborators the access their work requires. Avoid passing one shared administrator password around the team. Use multifactor authentication where available and keep recovery information in a secure location your business can access.
Your everyday content editor may not need full administrator permissions. On WordPress, different roles have different capabilities; its roles documentation describes the distinction. Agree who will handle updates, backups, user access and incident response after handoff.
Test the work your team will actually do
A recorded walkthrough or written guide is useful, but it should support real tasks. Ask someone on your team to change a service description, replace an image, publish a draft and locate a form submission using the instructions. Test on the setup you will actually use.
Check that inquiries reach the intended inbox or system, that someone knows where submissions are stored and that there is an owner for checking failures. Confirm how backups are made and who can restore them. A statement that backups exist is different from knowing how recovery will work.
Try this: make a short handoff rehearsal before the final sign-off. Have your team log in with its own account, complete one routine update and trace a clearly labeled test inquiry from the form to its destination. Record anything that still depends on an explanation from the builder.
Keep this handoff checklist
- Domain registrar, intended registrant, recovery details and renewal owner
- Hosting account, billing owner and support contact
- CMS accounts and appropriate access for your team
- Approved design and content files, with agreed usage permissions
- Paid tools and assets, renewal costs and license conditions
- Form destinations, submission storage and someone responsible for checking them
- Analytics and other integrations, with business-controlled access
- Backup, update and recovery responsibilities
- Instructions for routine content changes
- Included support, its end date and the process for further work
- A plan to remove access that is no longer needed
A handoff does not require you to become the developer. It should leave you able to run the business, commission the next piece of work and recover access without a mystery account standing in the way.
Related reading: How to compare creative proposals and How to use your brand files. For an agreed website project or ongoing operational support, explore Web & Digital.
FROM UNDERSTANDING TO DOING
Bring us the question.
Tell us what you’re trying to understand, make or move forward. Messy thoughts welcome.
Start a conversation