What should be in a church media handoff document?

Four categories: account access (logins or who holds them), the weekly rhythm of what happens and by when, a short contact list for support and reliable volunteers, and a record of the reasoning behind non-obvious decisions. It should be the minimum a capable stranger needs to keep things running, not a full training manual.

How do you document a church volunteer role before they leave?

Write it down while the role is still active, ideally right after someone has been trained into it, rather than waiting until the person announces they are leaving. Focus on account access, the weekly sequence of tasks, who to contact for common problems, and why any non-obvious choices were made.

Where should church account passwords be stored?

In a password manager the church itself controls, tied to a church account rather than a personal one, so access does not leave with the volunteer who set it up. If that is not yet in place, keep at minimum a written record of what accounts exist and who currently holds access.

How often should a church update its media handoff document?

Twice a year is usually enough to keep it accurate without it becoming a burden. An outdated handoff document that describes an abandoned workflow is worse than no document at all, because it actively misleads whoever relies on it next.

Who should be responsible for the church media handoff document?

The role, not the individual — typically whoever leads the media team structurally, such as a comms director. Assigning it to a named role rather than a specific volunteer means the document survives the exact staff or volunteer turnover it is meant to protect against.

What is the biggest risk when a church media volunteer leaves suddenly?

Losing access to accounts — a locked streaming channel, a domain login, a scheduling tool tied to a personal email — is usually the most disruptive gap, because it is often undiscoverable without the person who set it up. That risk is the strongest single reason to keep account access documented in advance.

Should a church media handoff document include the reasoning behind decisions, or just the steps?

Both. Steps alone let a successor follow the process, but without the reasoning behind non-obvious choices — why a post goes out on a certain day, why one platform gets more focus — they may reverse a decision that was actually deliberate, or blindly repeat one without understanding why.

Writing the Church Media Handoff Document

October 21, 20268 min read

The volunteer who ran your media for three years just left, and nobody knows the password to the YouTube account. A handoff document is how you avoid that twice.

The person who has run your church's media for the last few years knows things nobody else does: which login gets into the streaming account, why the Tuesday post always goes out at that specific time, which volunteer actually shows up and which one needs a reminder text. None of it is written anywhere. It lives in their head, and it works exactly as long as they stay.

Then they move, or take a new job, or simply need a season off, and the church discovers all at once how much depended on one person's memory. Passwords get reset through a support form. A posting schedule quietly stops. Someone spends a week rebuilding a workflow that already existed and was simply never written down.

A handoff document fixes this before it becomes a crisis, and it takes a fraction of the time the recovery does.

What actually belongs in a handoff document

A good handoff document is not a manual for how to do the job well — that is what training is for. It is the minimum a reasonably capable stranger would need to keep the lights on for a few weeks without the person who used to do it. Four categories cover almost everything.

Category	What it includes	Why it gets missed
Access	Logins, or who holds them; which accounts exist and where	Feels obvious to the person who already knows it
Weekly rhythm	What happens each week, in what order, by when	Lives entirely as habit, never as a list
Contacts	Who to call for what — hosting, streaming platform support, key volunteers	Only needed rarely, so it is never top of mind
Decisions	The whys behind non-obvious choices, so a successor does not undo something on purpose	Nobody thinks to record a decision once it feels settled

Access: the category that causes actual emergencies

Missing access is the single most disruptive gap in a handoff, because it is often not discoverable at all without the outgoing person — a locked YouTube channel, a domain registrar login, a scheduling tool tied to a personal email address that leaves with the volunteer. Use a password manager the church itself controls, not a personal one, for anything account-level. If that is not realistic yet, at minimum keep a written, access-controlled list of what accounts exist and who currently holds the credentials, even if the credentials themselves live elsewhere.

The weekly rhythm, written as a list a stranger could follow

Write down what actually happens between Sunday and the following Sunday, in order, with rough timing. This is the part of a handoff most likely to already exist informally — as habit — and least likely to be written anywhere a successor could find it.

Sunday: what gets captured

How the service is recorded, where the file lands, who is responsible for getting it there.

Monday–Tuesday: what gets made from it

What content is produced from the sermon — clips, a highlight, a quote graphic — and by what process.

Midweek: what gets posted, and when

Which platforms, in what order, at roughly what times, and who has final approval before it goes live.

Ongoing: what gets checked

Comments to monitor, messages to respond to, anything that needs a weekly glance even on a quiet week.

If your team already has a defined church media workflow, the handoff document can largely point to it rather than duplicate it — the handoff's job is to fill the gaps that workflow document leaves for someone who has never done the role before.

Contacts: who to call before it becomes urgent

A short contact list, kept current, saves real time in a moment of actual need: who to contact for streaming platform issues, who manages the church website if the video embed breaks, and which volunteers have historically been reliable for a last-minute ask. This list is short by design — five to ten names and one line each on what they help with — not a full team directory.

If the ongoing weekly step is turning the sermon into clips, that part of the handoff gets much shorter to write — see how the process works so the document only needs to cover reviewing and posting, not the technical cutting steps.

Try it on your next sermon — 2 free

Recording decisions, not just steps

The category most handoff documents skip entirely is the reasoning behind non-obvious choices — why posts go out on Tuesday and Thursday specifically, why one platform gets more attention than another, why a particular graphic style was chosen. Without this, a successor either repeats a choice blindly without understanding it, or reverses a decision that was actually made deliberately, for reasons that made sense at the time and might still. A single paragraph per major decision is enough; it does not need to be a defence, just a record.

Keep it current, or it becomes worse than nothing

A handoff document from three years ago that describes a workflow the team abandoned a year in is actively misleading — it sends a successor down a path that no longer exists. Set a recurring reminder, twice a year is enough, to open the document and update anything that has changed. This is a smaller task than writing it the first time and it is the difference between a document that gets trusted and one that gets ignored.

The best moment to actually write or update this document is not during a crisis, when the person who has the knowledge has already left — it is during a calm season, ideally right after a role has been freshly trained (see training a media volunteer in one afternoon), while the process is still fresh enough to write down accurately.

Who should own the handoff document

Ownership should sit with a role, not a person — usually the comms director or whoever leads the media team structurally, rather than whichever individual volunteer happens to be doing the work today. That way the document survives the exact turnover it exists to protect against. Church media team roles is a useful companion here, since a clearly defined role structure makes it obvious whose job it is to keep this document current.

Frequently asked questions

What should be in a church media handoff document?: Four categories: account access (logins or who holds them), the weekly rhythm of what happens and by when, a short contact list for support and reliable volunteers, and a record of the reasoning behind non-obvious decisions. It should be the minimum a capable stranger needs to keep things running, not a full training manual.
How do you document a church volunteer role before they leave?: Write it down while the role is still active, ideally right after someone has been trained into it, rather than waiting until the person announces they are leaving. Focus on account access, the weekly sequence of tasks, who to contact for common problems, and why any non-obvious choices were made.
Where should church account passwords be stored?: In a password manager the church itself controls, tied to a church account rather than a personal one, so access does not leave with the volunteer who set it up. If that is not yet in place, keep at minimum a written record of what accounts exist and who currently holds access.
How often should a church update its media handoff document?: Twice a year is usually enough to keep it accurate without it becoming a burden. An outdated handoff document that describes an abandoned workflow is worse than no document at all, because it actively misleads whoever relies on it next.
Who should be responsible for the church media handoff document?: The role, not the individual — typically whoever leads the media team structurally, such as a comms director. Assigning it to a named role rather than a specific volunteer means the document survives the exact staff or volunteer turnover it is meant to protect against.
What is the biggest risk when a church media volunteer leaves suddenly?: Losing access to accounts — a locked streaming channel, a domain login, a scheduling tool tied to a personal email — is usually the most disruptive gap, because it is often undiscoverable without the person who set it up. That risk is the strongest single reason to keep account access documented in advance.
Should a church media handoff document include the reasoning behind decisions, or just the steps?: Both. Steps alone let a successor follow the process, but without the reasoning behind non-obvious choices — why a post goes out on a certain day, why one platform gets more focus — they may reverse a decision that was actually deliberate, or blindly repeat one without understanding why.

Church Video Tips, Weekly

Join 1,000+ church communicators getting actionable strategies for growing your congregation's digital presence. Every week, free.

No spam, ever. Unsubscribe anytime.

Keep reading

Training a Media Volunteer in One Afternoon

Part of

Church Media Workflow and Team

How church media actually gets done: the Sunday-to-Monday workflow, volunteer systems, recruiting and training, gear that matters, and how to keep it running when one person leaves.

All articles