A faithful volunteer says they need to step back from the website. The church thanks them, finds a replacement, and discovers a month later that the domain renewal notice went to the former volunteer’s personal inbox.
The pages were handed over. The responsibility was not quite handed over with them.
A good transition gives the new editor enough knowledge to act and the departing volunteer permission to be finished. Begin while there is time to practice together, rather than treating their last week as a password exchange.
Record ownership and recovery
Create a short inventory in a church-controlled location:
- Domain — Registrar, renewal owner, and recovery route.
- Website — Provider, billing contact, and administrator accounts.
- Content — Where page text, photographs, and templates are stored.
- Backups or exports — What exists, who can retrieve it, and how recovery works.
- Related services — Forms, email delivery, analytics, and integrations the site relies on.
Do not put passwords into a general handoff document. Use the church's approved password manager and access process. Give authorized editors individual accounts where the provider supports them.
Confirm that renewal and recovery messages reach a monitored church contact, rather than relying entirely on the departing person's private inbox.
Teach the next editor three real jobs
Have the backup editor update a service time, add or remove an event, and correct a contact page. Include previewing, publishing, and checking the result on a phone.
Let them perform the steps while the current volunteer observes. Record where they need help. A short written guide or screen recording can cover those exact points.
For the second attempt, let the new editor work from the guide alone. Ask the former volunteer to observe without rescuing each hesitation. The places where the instructions fail are exactly the places worth improving.
Include an unglamorous task such as removing an expired notice. A church website needs ordinary maintenance far more often than it needs a redesign.
Explain where the information comes from
A website can contain both live data and manually written text. Identify the source for the calendar, service times, sermon list, and contact details.
For example, TimelyChurch Website Studio can display eligible public events from the church's event records through a dynamic Events section. The new editor should know to correct those records. An uploaded flyer or a sentence typed on a page remains a separate copy to check.
With the appropriate website permissions, a church can give an editor website responsibilities without granting unrelated financial access. Test the actual role before the handoff is complete.
Write the recovery page
Include the person to contact if publishing fails, how to remove an incorrect public item, and what to do if the main editor is unavailable. State which changes require review, especially sensitive personal information or major service changes.
Ask the provider about backups or recovery where the current process is unclear. Do not let an assumed backup become the only emergency plan.
Decide whether a platform change is necessary
A handoff may reveal missing documentation, unsuitable permissions, or a difficult editor. It may also reveal that the present site works well once a second person is trained.
Fix the specific problem before committing to a redesign. Changing platforms creates its own migration and training work.
Finish with a rehearsal: the backup editor completes a routine update, another person checks the public result, and the former volunteer does not need to intervene. Keep that shared responsibility active with occasional real edits.
If the transition reveals that routine edits are too difficult for the people available, look at TimelyChurch’s Website Studio. Have the incoming editor try a public event update and a page correction. The right choice will let them take responsibility confidently—and let the previous volunteer step away without remaining the emergency help desk.