Ideas + Insights

Insights

Practical thinking on website design, development, branding, marketing, SEO, accessibility and AI - created to help businesses make better digital decisions.

The Website Handover Question Nobody Asks: Who Maintains All of This?

Website projects naturally build towards launch.

There is a final content review, forms are tested, redirects are checked and the new site becomes public. Everyone involved can see the result, which makes launch feel like the finish line.

The following morning, the website becomes an operating system the organisation needs to own.

Software requires updates. Content becomes outdated. Staff change, third-party services evolve and small decisions accumulate. A website can launch in excellent condition and still become fragile when nobody knows who is responsible for what happens next.

Handover should define ownership, not just access

Providing an administrator login is not the same as transferring operational responsibility.

The organisation should know who owns content accuracy, who approves changes, who manages technical maintenance and who responds when something stops working.

For a small business, one person may coordinate several of those responsibilities. Larger organisations may divide them across marketing, IT, communications and external providers.

The important part is that the boundaries are visible before an urgent issue forces everyone to work them out.

Know where the website actually lives

Domain registration, DNS, hosting, email and website software are related but separate responsibilities.

The organisation needs to know which accounts control them, whose name they are registered in, when they renew and what access is available. A developer should not be the only person capable of proving ownership of the domain.

Dependable website hosting and domain management includes backups, monitoring, renewal processes and a recovery path, not simply server space.

Updates need a process

Content management systems, frameworks, plugins and dependencies change after launch.

Updates can address security, compatibility and defects. Applying them without testing can introduce problems, while ignoring them indefinitely increases risk.

A maintenance plan should define how updates are reviewed, where they are tested and how the website can be restored if something fails. More complex sites may require separate development, staging and production environments.

WordPress websites particularly benefit from disciplined plugin and theme management because several independent components may need to remain compatible.

Those maintenance responsibilities also inform the initial platform choice; compare the trade-offs between WordPress and bespoke development.

Custom systems need durable knowledge

A bespoke website or application contains decisions that may not be obvious from the interface.

Documentation should explain how to set up the project, its architecture, important integrations, scheduled tasks, deployment process and unusual business rules. Source code belongs in a controlled repository with a clear history.

Bespoke development creates value through tailored behaviour. That value becomes a liability if the knowledge exists only in one person’s memory.

Backups need to be recoverable

A backup existing somewhere is reassuring. A backup that can be located, restored and verified is useful.

Determine what is covered: database, uploaded files, application code, configuration and external data may have different backup paths. Retention should reflect how quickly a problem might be discovered.

Recovery also needs ownership. Who notices the failure, who decides to restore and what happens to data created after the selected backup?

Monitoring should identify actionable problems

A website can remain technically online while important parts fail.

The contact form may stop delivering, a payment integration may reject transactions or a scheduled import may silently stop. Basic uptime monitoring will still report success.

Monitoring should reflect critical journeys as well as server availability. Alerts need a recipient who understands what they mean and has authority to respond.

Content ownership matters just as much

Service information changes, staff profiles become outdated and temporary announcements remain live long after their relevance has passed.

Editors need guidance on headings, links, images, accessibility and metadata. Templates should make routine publishing safe without allowing every page to drift into a different design.

A content review schedule can prioritise the pages that most affect customers and search visibility rather than attempting to review the entire website at once.

Performance can decline gradually

New tracking scripts, embedded tools, campaign code and oversized images accumulate over time.

The site may feel only slightly slower after each addition until the combined effect becomes substantial. Periodic website performance checks provide a baseline and help identify deterioration before it becomes accepted as normal.

Plan for improvement as well as maintenance

Maintenance keeps the website dependable. Improvement asks whether it is still doing the right job.

Analytics, search data, enquiries and customer feedback can show where content or journeys need refinement. Small, evidence-based changes often create more value than waiting several years for the next complete rebuild.

A handover should therefore include the measures and tools needed to learn from the live website.

A website is finished only as a project

Launch marks the completion of a defined body of work. It does not freeze the technology, organisation or audience around it.

A good handover leaves the business with access, documentation, clear responsibilities and a practical support path.

The question “Who maintains all of this?” should not arrive after something breaks.

It belongs in the project while there is still time to design a proper answer.

  • Strong search visibility comes from useful content, sound technical foundations and a clear understanding of what your customers are actually looking for.

  • See how ideas become working solutions

    Explore how strategy, design and development come together across websites, brands, digital platforms, marketing and search projects.