Pastors change. The address, and its history, should stay with the church.
Ask a small congregation where its email lives and the honest answer is usually a personal account. The pastor’s, or the one a volunteer set up in 2011 with a password that three people know. It has the church’s name in it somewhere, and that seems like enough.
It is enough until the pastor takes a call to another church, or the volunteer moves away, or someone needs the message the building committee sent to the contractor last spring.
The problem is ownership, not appearance
Churches are unusual organisations. Leadership changes on a timescale of years, the people doing the administration are volunteers, and the correspondence matters for a long time: baptismal records requested decades later, decisions recorded in an email thread rather than minutes, agreements with a denomination or a lender.
When that correspondence lives in an account that belongs to a person, the church does not own its own history. Recovery goes to the person’s phone. Access ends when their involvement ends. And nobody thinks about this until the transition is already happening and everyone is being gracious about it.
A domain the church owns, with addresses on it, changes that. The pastor uses pastor@ while they serve, and hands it to the next pastor. The treasurer uses treasurer@. When people change, the addresses and their history stay with the body.
A small church needs four or five addresses
There is no reason to over-build this. For most congregations:
- office@ or info@ for general enquiries, matching what is on the sign and the website
- pastor@ for pastoral correspondence
- treasurer@ or giving@ for finance
- elders@ or council@ as a shared address for the leadership body
- individual addresses for staff, if there are any
The leadership address is the one most churches skip and most churches need. Correspondence about property, disputes, or denominational matters should not live in one elder’s personal inbox.
Pastoral confidentiality
There is a reason beyond continuity, and it is the more serious one.
Pastoral email contains things people would not want read by anyone else: a marriage in trouble, a diagnosis, a struggle with faith, a request for financial help. When that arrives at a personal account, it sits alongside everything else in that person’s life, on devices shared with family, backed up wherever personal backups go.
A dedicated custom email domain for the church, with the pastor’s address on it, at least puts that correspondence in a container the church controls, with its own password and its own access rules. It is not a complete answer to confidentiality. It is the minimum.
The Cybersecurity and Infrastructure Security Agency publishes guidance for non-profits and small organisations on the basics: unique passwords, two-factor authentication, removing access when someone leaves. All of it applies to a church office.
The transition document
The most useful thing a church administrator can produce is one page: where the domain is registered and who holds the login, where mail is hosted and who holds that login, which addresses exist, who has access to each, and what happens when someone steps down.
Make sure the domain and the mail account are registered to the church, not to a person. A church domain sitting in a departed volunteer’s personal account is a genuine problem, and one that is awkward to raise with someone who served faithfully for a decade.
Why this is worth an evening
None of this is theology and none of it is ministry. It is the kind of thing that, done well, nobody ever notices.
But a congregation that can hand its correspondence from one pastor to the next without loss, keep pastoral conversations in a place it controls, and answer a question about a decision made years ago, is a congregation that has taken its own continuity seriously. That is worth an evening’s work.
