Every part of church administration, on one record.
Church Server is not a set of separate tools that share a login. Membership, giving, services, communication and care all read and write the same records, which is why a single entry never has to be made twice.
One profile per person — not one per spreadsheet.
A member's household, groups, departments, attendance, giving history and pastoral notes live on the same record. When someone transfers branch or joins a department, their history follows them rather than starting over.
- Households and family links, so children and dependants aren't loose records.
- Groups and departments a member can belong to many of at once.
- Attendance history captured per service, not as a running total.
- First-timer journeys with an assigned owner and a response deadline.
- Transfers between branches that carry the full history across.
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.
Friday Night Vigil
Recurring weekly · 21:00–00:00
Set the ladder once — it runs for every recurrence
Set the rhythm once; the reminders follow.
Weekly services, midweek meetings, conventions and one-off programmes are all defined the same way: a schedule, a recurrence, an audience, and a ladder of reminders that fires without anyone remembering to send it.
Recurrence
RSVP & capacity
Attendance capture
Children's check-in
Announcements aimed at a segment, not a group chat.
Write once and send to exactly who it concerns — a department, a branch, everyone who missed the last three services, or every first-timer from Sunday. Each send is recorded against the members who received it.
Templated messages to members who have opted in on your church's number.
SMS
For members without smartphones or data — still the most reliable reach.
Longer notices, statements and receipts, with formatting that survives.
Social channels
Publish the same notice outward with platform-appropriate formatting.
Care that isn't written down is care that depends on one person remembering.
The pastoral side of the record is the part most software leaves out. Church Server treats a welfare request or a hospital visit with the same seriousness as a financial entry: it has an owner, a status, a history, and a deadline someone is accountable to.
Requests & counselling
Follow-up assignments
Medical & emergency notes
Reports that assemble themselves from the record.
Because every branch writes to the same system, a regional or national report is a query rather than a collection exercise. Nobody has to chase twelve spreadsheets with different column headings.
- Attendance, membership growth and giving summarised at any tier you defined.
- Comparisons between branches on the same basis, because the definitions are shared.
- Period-over-period views without rebuilding last quarter's sheet.
- Exports to standard files for auditors, boards and denominational returns.
No one has to be trusted not to look — the scope is enforced
Who holds the keys, and to what.
Church records hold names, addresses, health notes and money. Access has to be deliberate rather than assumed.
Roles & permissions
Audit log
Data export
Multi-branch controls
The shape of the change.
Nothing here is exotic. It is the same church administration you already do, held in a place where it can be found, compared and handed over.
Start with the part that hurts most.
Most churches begin with membership and attendance, then add giving once the record is trusted. Nothing you enter early has to be re-entered later.