The church runs on records, not memory.
Who joined last month, which branch they belong to, what was given and to which fund, who is still waiting on a visit. Church Server holds all of it in one authoritative record — for a single congregation or a network of hundreds.
- 0
- Modules
- 0
- Per-branch fees
- 0
- Day trial
Grace Adeyemi
MBR-00418
Bound records
Every action anywhere in the platform writes back to the person it concerns. Nothing lives in a side spreadsheet.
Members
One profile per person, with family, history and care in the same place.
Structure
Your own branches, tiers and offices — not a denomination's template.
Giving
Funds, causes and transfers with a proof trail at every level.
Services
Programmes, attendance and reminders that run on schedule.
Most churches don't lack care. They lack a record of it — so the same questions get asked twice and the person in need falls through the gap.
The attendance sheet is in one book, giving in a second, the WhatsApp group in a third, and the follow-up list in someone's head. Every report becomes an archaeology project, and every handover loses history.
One write, everywhere true
History that outlives the handover
Answers without a data hunt
What actually changes.
Not a feature list — the five questions a church asks every week, and how each one goes depending on whether the answer was written down.
Who visited for the first time on Sunday?
A paper slip, if the usher remembered to hand it over.
A record with an owner and a 24-hour response deadline.
Has anyone followed them up?
Ask around on Wednesday and hope someone did.
Visible on the board, with who is doing it and by when.
What did the building fund receive last month?
Wait for the treasurer to rebuild the spreadsheet.
Read it off the fund, with every entry behind it.
Which branches haven't reported?
Email all of them and count the replies.
A list, already sorted by how late they are.
The pastor who knew everyone has moved on.
The history moves on with them.
The record stays; the role is reassigned.
Eight parts of church life, kept in one ledger.
Adopt them in any order. Each part writes to the same record, so switching one on never means re-entering what you already have.
Membership & households
Profiles, families, groups, departments, attendance history and first-timer journeys.
Organisation structure
Define your own levels — campus, region, diocese, ministry, office — to any depth, with permissions that inherit down the tree.
Giving & stewardship
Tithes, offerings, pledges, causes and inter-branch remittance, each with proof of payment.
Services & events
Recurring programmes, RSVPs, attendance capture and a staged reminder sequence per event.
Communication
Segmented announcements across WhatsApp, SMS and email, with the full send history on record.
Pastoral care
Welfare requests, counselling notes, follow-up assignments and response deadlines your team can actually see.
Assistant
Ask operational questions in plain language, read uploaded documents, and draft messages from real church data.
Administration
Roles, permissions, audit logs, reporting and platform controls for whoever holds the keys.
A board of what the church needs a person for.
Not a wall of totals. The first screen after signing in is the work itself — newcomers to visit, welfare waiting on a decision, reports overdue — each with an owner and a deadline, moving left to right as it gets done.
Amara Bello
due 6hFirst visit on Sunday
Westgate branch
12h lateMarch report outstanding
Ngozi Eze
due 20hAsked to speak with a pastor
Daniel Okon
due 2dNo attendance for six weeks
Tunde Ogun
due 2dHome visit arranged
Emeka Nwosu
Visited Saturday
Model your church as it actually is.
Most church software ships one hierarchy and asks you to bend into it. Church Server lets you declare your own levels and name them in your own language — then aggregates every report up the tree you defined.
- Name your tiers: region, zone, diocese, parish, campus, ministry, office — or something only your church uses.
- Keep separate structures for locations, leadership offices, departments and ministries.
- Permissions inherit downward, so a zonal pastor sees their zone and nothing beyond it.
- One subscription covers the whole tree — branches are never billed per location.
Asked
Which branches haven't submitted last month's report?
Answered from your records
Three branches are outstanding: Harbour Assembly, Westgate and Lakeview. Harbour Assembly has missed two consecutive months.
Scoped to the asker's permissions — never beyond them
Ask the record a question.
The assistant reads your own data — not the open internet. It answers operational questions, summarises uploaded documents, and drafts the message you were about to write by hand, always inside the permissions of whoever is asking.
Operational answers
Document reading
Drafting
Members on WhatsApp
Money that can be accounted for, at every level.
Giving is the part of church administration that most needs a record and most often lacks one. Church Server treats every amount as a traceable entry from the moment it is received to the moment it is remitted.
01
The branch records what came in
Tithes, offerings, pledges and cause donations, each posted against a fund and a giver where one is known.
02
Your rules divide it
Finance defines the splits, percentages and reporting deadlines once per tier. The system applies them from then on.
03
It moves up the tree with proof
Branch to zone to central office. Every transfer carries a proof-of-payment record, so no figure arrives unexplained.
The first fortnight.
No implementation project, no consultant, no six-week onboarding call series. You can do the whole of this inside the trial.
Describe your structure
Name your tiers and place your branches. Fifteen minutes for a single church; an afternoon for a network.
Bring your people in
Import members from a spreadsheet or an export from your current system. Columns are mapped, then validated before anything is written.
Start with one habit
Most churches begin with attendance and newcomers. Giving follows once the record is trusted.
Add the rest as you need it
Care, communication, remittance and reporting all read the same records — switching one on never means re-entering anything.
What we commit to, plainly.
Church records hold names, addresses, health notes and money. We'd rather tell you exactly how they're handled than print a badge.
Permissions, not honour systems
An audit log you can read
Your data leaves when you do
One subscription, every branch
Before you ask.
The five things churches raise most often, answered without hedging.
We're one congregation, not a denomination. Is this too much?
No. A single church declares one tier and never sees the rest of the hierarchy machinery. The same record works whether you have one location or three hundred.
Our structure doesn't match any standard hierarchy.
That's the case Church Server was built for. You declare your own tiers and name them yourself, so a diocese stays a diocese and a circuit stays a circuit.
What happens to our data if we leave?
It leaves with you. Members, giving and attendance export to standard files, and that export is available on cancellation rather than withheld as leverage.
Who can see pastoral and financial records?
Only the roles you grant. Scope is resolved from the tier a role is held at, and counselling and welfare notes can be restricted more tightly than the tier itself.
Does the assistant read our members' data?
It answers from your records, inside the permissions of whoever is asking, and it drafts rather than sends. It does not answer from the open internet.
One subscription. The whole tree.
Church Server is priced per church, not per location or per member record you happen to keep. The paying church covers every branch, zone and office beneath it.
Put the church on one record.
Start with your members and your structure. Add giving, services and care as you go — nothing to migrate twice.