How it works
Your current website and records stay completely untouched until your officers approve the cutover. Nothing is published, imported, or billed without a sign-off.
The process
We review your chapter’s current website, membership process, and governance requirements, then recommend the plan that matches what you actually do today.
We provision your chapter workspace, configure your plan entitlements, and apply your chapter’s branding, colors, and domain.
Members and content are staged for your review and approved by your officers before anything is published. Your existing production site stays untouched throughout.
A guided session covers roster management, communications, events, and — on Professional and above — meetings, eligibility, and voting.
Your public website goes live and your officers begin operating day to day. We stay available through your first full cycle.
Guarantees
Your existing production website stays online and unmodified throughout onboarding. We build yours alongside it and cut over only when your officers say so.
Any member list is staged for officer review. You confirm what is accurate before it becomes active data, and nothing is imported from an existing production database without written authorization.
Dues collection and subscription billing are configuration you enable deliberately. No card is charged and no processor is connected until you approve it.
Quorum, voting eligibility, and balloting rules differ by organization and by governing document. They are configured with you rather than assumed by the software.
Rollout
We publish the phase plan rather than implying everything is finished. If a module appears on this page as Planned, it is not in the product yet and we will not present it as if it were.
Governance and financial modules require explicit approval
Under the hood
ChapterConnect runs on Cloudflare Workers with Cloudflare D1 for relational data and Cloudflare R2 for object storage. There is no server for a chapter to administer, no application to patch, and no single region to fail — requests are served from the location closest to the member making them.
Volunteer officers inherit a system every year or two. A platform with nothing to maintain means a new officer does not inherit an unpatched WordPress install, a lapsed hosting renewal, or a database nobody can restore.
Every tenant-owned record is scoped to a chapter, and every protected operation re-verifies five things on the server: that you are authenticated, that you belong to the chapter you are asking about, that your chapter's plan includes the capability, that your role permits the action, and that you are allowed to see the specific record. Hiding a menu item is never treated as a security control.
ChapterConnect is not a general ledger and will not become one. Where accounting integration is enabled, existing accounting software such as Xero remains the system of record. Figures displayed inside the platform are operational views, not reconciled accounting balances, and they are labelled that way.
Bring your current website, your roster process, and your meeting rules. We will show you exactly how onboarding would work for your chapter.