CHOS for your church
CHOS is not ready for multi-site use
The current first-pilot boundary is one campus, fewer than 300 people, one weekly service pattern, and a trusted small staff team.
Multi-site operation requires campus isolation, location-aware permissions, local teams, cross-campus reporting, and carefully separated check-in workflows. Those capabilities are not launch-proven in CHOS.
Do not use the current release as a shared multi-campus workspace. Keep your existing multi-site system active and evaluate CHOS only for a separate, one-campus pilot if that boundary is operationally safe for your church.
Why multi-site is not ready
Current pilot boundary
One campus, fewer than 300 people, one weekly service pattern, and a trusted small staff team.
No campus isolation
Per-campus access boundaries and location-scoped teams are not launch-proven.
No cross-campus reporting
Campus rollups and trustworthy location comparisons are not part of the current pilot.
Keep your current system
Continue using your established multi-site platform until CHOS explicitly releases and verifies multi-campus support.
Frequently asked questions
Can CHOS manage multiple church campuses?
No. CHOS is not launch-ready for multi-site or multi-campus use. The current first pilot is limited to one campus, fewer than 300 people, one weekly service pattern, and a trusted small staff team.
Does CHOS support per-campus dashboards or reporting?
No. Per-campus permissions, team scoping, dashboards, and cross-campus rollups are not part of the current release. Keep your existing multi-site system active.
Learn more
Keep your multi-site system active
CHOS is not launch-ready for multi-campus operation. Evaluate it only as a separate one-campus pilot when that boundary is safe.