Ownership and workflow
Who should own church website updates?
The right answer is not always “the pastor,” “the volunteer who built it,” or “the website company.” A dependable public pathway needs several responsibilities named clearly—even when one qualified person holds more than one role.
Start with six responsibilities
- Authoritative source owner: knows which calendar, document, person, or system contains the approved answer.
- Accountable website owner: makes sure the public route remains current.
- Approver: confirms the content is accurate and appropriate before publication when approval is required.
- Response owner: receives the public form, email, call, or registration response.
- Backup: can perform the essential task when the primary owner is unavailable.
- Escalation owner: decides what happens when the normal workflow fails or the issue exceeds the team's authority.
One person may hold several roles—but the roles still matter
A small church may have one administrator who receives information, updates the website, approves routine facts, and responds to public inquiries. Writing the roles down is still useful because it reveals what must be transferred when that person is away, changes jobs, or no longer has access.
Do not confuse access with authority
The person who has the password may not be authorized to change a service time, children’s process, giving instruction, pastoral-care statement, or legal notice. The person authorized to approve a change may not know how to publish it. A responsible workflow connects authority, access, publication, response, and recovery.
Create an ownership card
Record one public pathway
- Public question:
- Authoritative source:
- Accountable owner:
- Approver:
- Publisher:
- Response owner:
- Backup:
- Escalation route:
- Normal review date:
- Next re-test date:
Add a review rhythm
Some information should be rechecked weekly, some monthly, and some only after a defined event. Tie the review rhythm to the risk and frequency of change. Service times, holiday schedules, current events, staff changes, forms, giving links, and emergency notices should not depend on someone remembering to look.
Know when to stop
Stop and seek the responsible authority when the change involves child safety, confidential information, finances, pastoral care, legal or accessibility conclusions, security, account recovery, or a claim the team cannot verify.
The backup needs current permission, usable access, enough training to perform the bounded task, and a recovery route that does not depend on the unavailable primary owner.
Next step
Use the facts-versus-assumptions method before making the next change, or see the complete ownership and re-test worksheets.