Multi-site is operationally a different problem
Two campuses isn't two times the work.
It's a different shape of work.
When a church plants its second campus, the operational picture changes in a way most platforms don't handle gracefully. The two campuses share a brand, a doctrine, a leadership board, and a central operations team — but they have their own services, their own volunteer rosters, their own kids ministry rooms, their own bookkeeping flows, and their own pastoral teams. The central team needs to see across both. The campus teams need to run their own campus without stepping on the other one's data.
Most platforms treat multi-campus as a feature flag. You turn it on, you get to tag records with a campus, and the rest is on the staff to coordinate. That breaks when the East Campus volunteer coordinator accidentally schedules a West Campus volunteer, or when a giving report at the elder meeting shows totals nobody can break down by campus.
On TrueConnect+, multi-campus is a first-class data and permission model. Campuses are objects with their own staff, their own service plans, their own volunteer rosters, their own ratios and rooms, and their own dashboards. Staff are scoped to one campus, multiple, or all — campus-scope is granted per staff seat. The central executive admin sees roll-up reports across the whole church. The East Campus admin sees only the East Campus. Members can belong to a primary campus and still attend events at others, with the system tracking attendance by campus regardless of where their primary is.
Every record lives somewhere. The campus is part of the record.
Every service plan, every event, every volunteer assignment, every kids check-in, every gift carries a campus tag. The data model knows that the 9am Sunday service at East Campus is a different record from the 9am Sunday service at West Campus — and the people, rooms, volunteers, and giving attached to one don't bleed into the other.
Reports filter by campus naturally. The East Campus attendance trend shows East Campus only. The West Campus giving total shows West Campus only. The central executive view rolls both up with the option to drill down. Nothing requires manual reconciliation because the data was campus-aware from the moment it was created.
- Campus tag on every operational record (services, events, gifts, volunteers, check-ins)
- Campus-scoped reports filter automatically
- Central roll-up views with drill-down to per-campus detail
- No manual reconciliation; campus-awareness is built into the data model
The East Campus admin sees East. The central admin sees both.
Staff seats can be scoped to one campus, multiple, or all. The East Campus volunteer coordinator is granted campus-scope to East Campus only — she can't accidentally schedule a West Campus volunteer because she literally doesn't see West Campus data. The central operations director is granted campus-scope to all — she sees the whole church. The youth pastor who runs programs at both campuses is granted scope to both.
Permissions stack — a Communications Director with East Campus scope can send broadcasts to East Campus members but not West. A Financial Administrator with all-campus scope can pull giving reports from both. The role permissions and the campus scope work together; neither alone is enough.
- Per-seat campus scope, granted independently of role
- Role permissions and campus scope stack to determine what each staff member sees
- Scope changes are audit-logged
- Owner and Administrator scope to all campuses by default; can be restricted
A member belongs to a campus. But the church is still the church.
Every member has a primary campus — usually the one they attend most often. That primary campus is their default for communications, kids ministry assignments, ministry suggestions, and event recommendations. But the member belongs to the whole church, and the system reflects that. They can attend any campus's service, give to any campus's fund, join a ministry that runs at any campus. Attendance and giving track to the campus where they happened, not just where the member is primary.
This matters for the family that switches their primary campus when they move across town. It matters for the visitor who attends three campuses before deciding which feels like home. It matters for the multi-campus member who volunteers at one campus and attends another.
- Primary campus per member, with attendance tracked at whichever campus the member shows up at
- Cross-campus giving with per-campus fund allocation
- Cross-campus ministry membership
- Member-driven primary campus changes without losing history
The operational details that make it actually work
Multi-site, in operational detail.
Per-campus service plans
Each campus has its own service plans, its own worship sets, its own production teams, its own volunteer rosters. Service templates can be central (a denomination-wide order of service) or campus-specific (East has a contemporary 10am; West has a liturgical 8am).
Per-campus kids rooms
Each campus's kids ministry has its own rooms, its own ratios, its own volunteer team, its own check-in dashboards. Allergies and authorized-pickup lists travel with the child across campuses.
Per-campus giving funds
Campus-specific funds (East Building, West Missions) sit alongside central funds (General Fund, Pastoral Care). Members give to whichever fund matters to them. Bookkeeping sees the campus allocation per gift.
Central public profile, per-campus pages
The church has one main public profile and one page per campus, each with the right service times, location, and team. Members searching for the right campus land on the right page.
Cross-campus volunteer floats
Some volunteers serve at one campus; others float. A volunteer can be scoped to one campus, to a set, or all — with availability windows and conflict detection working across the campuses they're active at.
Roll-up dashboards
The executive dashboard rolls up all campuses with per-campus drill-down. The board meeting shows total attendance, total giving, and campus-by-campus health — the whole church on one screen, with the option to dig.
What a two-campus church looks like, run cleanly.
The East Campus pastor opens his Monday morning dashboard and sees East Campus only — 312 in attendance yesterday, $18,400 in giving, two prayer requests still open from the prayer team, four new visitors from the welcome card. The West Campus pastor sees the same view for West Campus — 178 in attendance, $9,100 in giving, six new visitors. Each is running his campus.
The executive operations director opens her dashboard and sees the whole church — 490 in attendance, $27,500 in giving, ten new visitors across both campuses, with the option to drill into either. She notices East Campus had a sharper drop in 3rd-5th grade attendance over the last month. The data points to a kids ministry leader who's been out sick for three weeks. She makes a note to check in.
On the elder board call that night, the chair opens the central giving and engagement dashboard. Total giving up 8% year-over-year. East Campus growing in young families. West Campus stable in attendance but climbing in volunteer hours. The board sees the church. Neither campus sees the other's confidential data. The platform respects both the autonomy of each campus and the integrity of the church as a whole.