One of the most common website problems I have seen is poor handover.

A website is built. It goes live. Everyone is happy. Then months later, the organization needs to update something, renew hosting, change an email address, fix an issue, or recover access.

That is when they realize they do not have the right information.

They do not know where the domain was bought. They do not know who controls the hosting. They do not know which email address was used to register the account. They do not have admin access. They cannot reach the person who built the website. Sometimes the only person who knew everything has left the organization.

This is a serious risk.

A website belongs to the organization, not the person who built it. But without proper handover, an organization can easily lose control of its own digital asset.

This happens more often than people think.

Sometimes a website is created by a volunteer. Sometimes it is handled by a short-term consultant. Sometimes a staff member manages everything using their personal email. Sometimes the developer keeps all access details and only updates the website when contacted. Sometimes no one documents anything because everyone assumes the information will always be available.

Then life happens. People change jobs. Consultants move on. Emails are lost. Passwords are forgotten. Phone numbers stop working. Hosting renewals are missed.

The organization is left stuck.

Proper handover prevents this.

A good website handover should include domain access, hosting access, WordPress or website admin access, professional email access, backup details, renewal dates, key contacts, and simple instructions for basic updates. It should also explain where important files are stored, what plugins or tools are being used, and what should not be changed without technical support.

This does not have to be complicated. Even a simple handover document is better than having everything in someone’s head.

Organizations should also avoid depending on one person alone. At least two trusted people should know how to access critical website accounts. This does not mean everyone should be an administrator. Access should still be controlled. But the organization should not be helpless if one person is unavailable.

Good handover is also part of accountability.

When an organization pays for a website, it should receive more than a finished design. It should receive the information needed to manage and protect that website. This includes knowing what was built, where it is hosted, when it must be renewed, and how to get support when needed.

For NGOs, civil society organizations, small businesses, and professionals, this is especially important because websites are tied to credibility and continuity. Losing access to a website can affect communication, visibility, fundraising, reporting, and service delivery.

My advice is simple: never accept a website without handover.

Before closing a website project, ask for the access details, documentation, backup information, renewal dates, and basic instructions. Confirm that the website is registered under the organization’s official email where possible. Make sure the organization has ownership of the domain and hosting. Remove unnecessary access from people who no longer need it.

A proper handover may not look exciting, but it can save an organization from serious problems later.

At Drapari Online, I believe website work should include responsible handover because building the site is only one part of the job. The organization must be able to own it, manage it, and continue using it confidently.

A website should not become a mystery after launch.

It should remain in the hands of the people it was built to serve.