Your church's structure, not a vendor's assumption.
Church software usually ships one hierarchy — often the one its first customer had — and asks everyone else to bend. Church Server has no built-in denomination. You declare the levels, name them in your own language, and everything else follows that definition.
A diocese is not a zone. A circuit is not a campus. Software that flattens the difference makes every report slightly wrong.
The words a church uses for its structure carry real meaning — canonical, historical, sometimes constitutional. Church Server stores your labels as data, so the interface, the reports and the permissions all speak the language your leadership already uses.
Pentecostal network
National office → Region → Zone → Branch
Anglican / Catholic
Province → Diocese → Archdeaconry → Parish
Methodist
Conference → District → Circuit → Society
Baptist union
Union → Association → Local church
Multi-site church
Central → Campus → Congregation
Single congregation
Church → Department
You define the tree; the product adapts to it.
There is no migration to a fixed schema and no request to a vendor to add your denomination. Tier depth, tier names and unit placement are all configuration you control.
Name your levels
Create the tiers your constitution recognises, in order, with the labels your leaders say out loud. Two levels or nine.
Place your units
Add each real branch, parish, campus or office under its parent. Move one later and its children move with it.
Attach people and offices
Assign leadership at whichever tier holds the office, and members at the unit they belong to.
A church is not one tree. It is several, overlaid.
Where a member worships, who they report to, which department they serve in and which ministry they belong to are four different questions. Collapsing them into a single hierarchy is what forces churches back into spreadsheets.
Locations
Leadership offices
Departments
Ministries
Authority flows down the tree you drew.
Grant someone oversight of a region and they see that region and everything beneath it — automatically, including branches added next year. Nothing above or beside their scope is visible, and no one has to remember to restrict it.
- A new branch inherits the permission rules of its parent the moment it is created.
- Moving a unit moves who can see it, with no separate permission clean-up.
- Pastoral notes and finance records can be restricted more tightly than the tier itself.
- Roles map to real offices, so a handover is a reassignment rather than a rebuild.
Derived from the tree — never hand-maintained per person
Every tier gets its own view of the same truth.
Attendance, membership and giving aggregate upward along the location tree automatically. A branch sees its own numbers; a zone sees the sum of its branches; the national office sees the whole, and can open any level beneath it to ask why.
Because every branch is entering data against shared definitions, the comparison between two branches is meaningful — which is rarely true of two spreadsheets.
Aggregate, then drill
Consistent definitions
Reporting deadlines
Adding a branch adds records, not an invoice.
Per-location pricing punishes exactly the growth church software should support. The subscribing church covers its whole tree — every zone, parish, campus and office beneath it.
Describe your church once.
Set up your tiers on the trial and see your own vocabulary throughout the product — before you commit a single member record.