Church Website Handover Checklist for Staff and Volunteers
Hand over your church website with an account inventory, update instructions, renewal ownership, and a practical rehearsal for the next volunteer.
Key takeaways
- +Transfer knowledge and access while the outgoing editor is still available.
- +Document the few recurring website tasks your church actually performs.
- +Rehearse an update and a recovery process before declaring the handover complete.
Free AI makeover
Build a free first draft of your church homepage.
Paste your church's web address, create a free account, and confirm your details. Review your homepage draft, then request the remaining pages free. Pay only when you publish.
Free makeover · Saved securely · No credit card required · No website yet? Start fresh
By Nils Smith · LinkedIn · Editorial responsibility: ChurchPress Editorial
01
What belongs in a church website handover?
A church website handover should identify who owns the accounts, who pays for renewals, how routine updates are made, who approves sensitive changes, and where to get help. It is complete when the incoming editor can carry out the church's normal tasks using their own authorized access. Sending a password and a folder of logos is only a starting point.
Volunteer transitions expose knowledge that often lives in one person's memory: which calendar feeds the homepage, why a giving button opens another service, or who receives the contact form. Capture those relationships before the current editor leaves. This guide covers handing over an existing site; changing platforms requires a separate migration plan.
02
Create an account and responsibility inventory
Record the website platform, domain registrar, DNS provider, media host, form service, and any connected tools the church actually uses. Several of these may be managed in one place. For each entry, note its purpose, the authorized account owner, billing contact, renewal date if applicable, and support route. Keep payment details and account recovery secrets out of the general handover document.
Use a church-controlled recovery address where the service supports it and ensure the responsible leaders can access it. Invite the incoming editor with an appropriate individual account when available. Test that invitation before changing the outgoing editor's access. Avoid putting shared passwords in ordinary email or a publicly accessible document; use the church's approved credential-sharing process.
Inventory template: “Service: [name]. Purpose: [what depends on it]. Authorized owner: [role]. Billing responsibility: [role]. Renewal: [date or arrangement]. Access instructions: [approved location]. Help: [support route].” A domain and website subscription can have different renewal owners, so verify both instead of assuming one invoice covers everything.
03
Write instructions for the five tasks you repeat
Choose tasks from the church's actual workload: correcting a gathering time, publishing an event, adding a sermon, updating a staff page, or processing a website inquiry. For each task, document the source of the approved information, where the edit happens, how to preview it, who approves it, and how to verify the result. Use the interface your editor will actually see.
Task template: “When [trigger], get confirmed details from [owner]. Update [page or record]. Preview [relevant screens]. Obtain [required approval]. Publish through [actual process]. Check [public page and dependent destination]. If something goes wrong, [documented recovery or support step].” A short screen recording can supplement these instructions, but keep a written version that is easy to search.
Show dependencies explicitly. Editing an event in an external calendar may update the website automatically, while changing homepage text might not change a separate visit page. The new editor needs to know which source controls each visible detail. Document this once instead of relying on repeated corrections after Sunday announcements.
04
Protect existing links during the transition
Save a list of important public URLs, including the visit page, giving destination, sermon archive, and pages used on printed materials. Explain which URLs must stay stable and where redirects are managed if a move becomes necessary. A change of editor is not a reason to rename every page or rebuild the navigation.
Document who can review search reporting and where the site's existing SEO settings are managed. Titles, descriptions, and redirects should not be reset just to make the new editor's workspace feel tidy. When a page genuinely needs changing, review its role and existing links first. The related ownership and content-governance guides can help separate editorial responsibility from account administration.
05
Run a handover rehearsal
Have the incoming editor use their own account to preview a harmless draft change, check it on a phone, and locate the procedure for restoring the previous version or contacting support. If the platform has no draft mode, choose a real, approved correction and supervise the update. Do not experiment on payment destinations, account recovery settings, or live service times merely to prove access.
Send a test inquiry through the public contact form and confirm its destination with the assigned recipient. Check billing responsibility and the next renewal together. Only after the replacement access works should the authorized administrator remove access that the outgoing person no longer needs. Record the handover date and the next review date so the document does not become another abandoned file.
- Inventory website services, authorized owners, and renewal responsibilities
- Verify the incoming editor's individual access through the approved process
- Document five recurring updates and their approval owners
- Rehearse a draft or approved correction and check the public contact route
- Review outgoing access after the new owner confirms the handover works
Put it into practice
Your action plan
- 1Transfer knowledge and access while the outgoing editor is still available.
- 2Document the few recurring website tasks your church actually performs.
- 3Rehearse an update and a recovery process before declaring the handover complete.
- 4Inventory website services, authorized owners, and renewal responsibilities.
- 5Verify the incoming editor's individual access through the approved process.
How to know it worked
The message has a named audience, owner, channel, next action, and review date—and the team can sustain the rhythm.
Frequently asked questions
Quick answers
Who should own the church website account?
Account control should follow the church's approved governance, with recovery and billing responsibility accessible to authorized church leaders. It should not depend solely on a departing volunteer's personal inbox.
Do we need to change website platforms when a volunteer leaves?
Not automatically. First test whether the next editor can perform the required work with clear instructions and appropriate access. Treat a platform change as a separate decision.
What if the outgoing editor is already unavailable?
Start with authorized church records for billing, account ownership, and recovery contacts. Use each provider's account-recovery process and document dependencies as they are confirmed rather than guessing or changing settings blindly.
Sources and further reading
1 · Use the resource
Run the free website audit
Open →2 · Find the gaps
Run the free website audit
Score your site →3 · Build your website
Let ChurchPress build your new church website—free.
Share your current website and ChurchPress will create a polished new version for your church. Build it, preview it, and refine it before you decide whether to publish.
No credit card required