Most church websites are built and maintained by one person — often a volunteer with a particular interest in web design, who quietly becomes the only person who understands how the site actually works. It runs well for years. Then that person moves away, steps back, or simply isn’t available anymore, and the church discovers it doesn’t have the login, doesn’t know who the hosting provider is, and has no idea how to update a single page.
This is one of the most common — and most avoidable — crises in church website management. Here’s how to hand things over properly, whether you’re the volunteer stepping back or the church leader picking up the pieces.
Why This Catches Churches Out So Often
A volunteer webmaster usually takes on the role informally. There’s rarely a written agreement about who owns what, and because the site “just works,” nobody thinks to ask questions until the person is no longer there to answer them. By that point, the church may not know:
- Who registered the domain name, and under whose personal account or email it sits
- Which hosting provider the site is on, or when the hosting is next due for renewal
- The login details for the website’s admin area
- Which plugins, themes, or paid tools the site depends on to keep running
None of this is anyone’s fault — it’s simply what happens when a website is treated as one person’s project rather than the church’s asset. Similar problems come up around domain ownership specifically, and it’s worth reading alongside our guide on GDPR and data protection for church websites, since a badly handled handover is often also a data protection gap — old form submissions, admin accounts, and contact details can be sitting in a system nobody’s actively responsible for.
Start With an Access Audit
Before anything else, get a complete list of everything the outgoing webmaster has access to. This should include:
- Domain registrar — where the domain (e.g. yourchurch.org.uk) is registered, and the login for that account
- Hosting provider — where the website’s files actually live
- Website admin login — WordPress, Squarespace, Wix, or whatever platform the site runs on
- Email accounts connected to the website (a “webmaster@” or “admin@” address, if one exists)
- Third-party tools — online giving platforms, event booking systems, newsletter software, analytics
- Any paid subscriptions tied to the site, and who’s currently paying for them
If the volunteer is still contactable, this conversation is far easier while they’re still around than after they’ve gone. If they’ve already left and access has been lost, most hosting providers and domain registrars have a recovery process, but it can take days or weeks and usually needs proof the church is the legitimate account holder — another reason this is worth sorting out before it becomes urgent.
Get Everything Into the Church’s Name, Not a Person’s
The single most important long-term fix is making sure the domain, hosting, and any paid tools are registered to the church itself — using a church email address and, ideally, an account that more than one person can access — rather than to one individual’s personal name and email. This is exactly the same principle covered in our piece on choosing the right website platform for your church: a platform decision made by one person, for one person’s convenience, tends to become a liability the moment that person isn’t available.
Decide Who Takes Over — And Whether That’s the Right Long-Term Plan
Once you’ve secured access, the real decision is what happens next. There are broadly three options:
- Find another volunteer with the time and technical confidence to take it on — which solves the immediate gap but leaves the church exposed to exactly the same risk again in a few years
- Split the responsibility across a small team, so no single person is a point of failure
- Move to a managed service, where hosting, updates, and support are handled professionally and ongoing changes don’t depend on one volunteer’s availability
There’s no universally right answer — a small church with modest needs may be perfectly well served by a capable volunteer with proper documentation in place. But for many churches, this moment (losing the person who built and understood the site) is exactly when it becomes worth asking whether relying on volunteer availability is sustainable at all. Our overview of essential features every UK church website needs is a useful benchmark either way, since it’s worth checking the site still covers the basics regardless of who ends up managing it.
Document Everything, Regardless of Who Takes Over
Whatever you decide, write it down. A simple handover document should cover:
- Domain and hosting account details, and renewal dates
- Login credentials, stored securely (a password manager shared with church leadership, not a sticky note or a single person’s inbox)
- A plain-English explanation of how to make basic updates — changing service times, adding an event, updating a sermon
- Who to contact if something breaks
This document should sit with the church’s leadership or administration, not with whoever happens to be doing the website work at the time. That way, the next transition — and there will be one — is a formality rather than an emergency.
The Bottom Line
Losing a volunteer webmaster is inevitable eventually; every volunteer role turns over at some point. What determines whether it’s a minor inconvenience or a genuine crisis is whether the church ever had proper ownership of its own website in the first place. Getting access, ownership, and documentation sorted now — while there’s no pressure — is far easier than trying to reconstruct it after the fact.
If your church is dealing with this right now, or wants to avoid facing it again, UKChurches provides fully hosted, managed websites for UK churches — find out more about how we work or get in touch for a free website audit.