Branch Management
Headquarters over regions over districts over assemblies, each keeping its own register, with figures that roll up.
In the app: Branches
A circuit, a district, a presbytery or a diocese is not one church with a bigger register. It is many churches, each keeping its own records, answering upward.
Fold models that directly, to any depth, rather than flattening it into one congregation with groups.
What it does
- Create branches beneath a church, to any depth.
- Let every branch keep its own register, giving and attendance.
- Give leadership above a read-only view of everything beneath them.
- Sum members, attendance and giving across every church beneath a given point.
- Transfer a member from one branch to another.
What is different about ours
Oversight is read only, deliberately
A regional overseer sees every assembly beneath them and cannot write into one. A district office correcting an assembly's register without the assembly knowing is how trust in a system is lost, so the ability simply does not exist.
Depth is not capped
Headquarters over regions over districts over assemblies, or whatever your denomination calls those layers. Nothing here assumes two levels.
Roll-ups obey the same rules as everything else
A total is summed from the churches you are actually entitled to see. If a figure looks short, somebody lacks oversight, and that is the answer rather than a number to be forced.
Questions churches ask
- Can headquarters edit a branch's records?
- No. Oversight from above is read only by design. A branch's own leadership is the only one that can change its records.
- How many levels of branch can we have?
- As many as your denomination has. Branches go to any depth.
- Does each branch see only its own data?
- Yes, plus anything beneath it if its leadership oversees other branches.
Further reading
See it with your own register
Thirty days free, no card, and nothing to cancel. Bring the register you already keep and we will help you move it across.