Loading
Features
One system, not a suite of things that share a login
The difference shows up on an ordinary Tuesday: you build a serving team once, and it is already an audience you can email, a register you can take attendance against, and a pool the scheduler can draw from. Nothing has to be re-entered, because nothing was duplicated in the first place.
The six primitives
What every module is built out of
If a module ever needs its own version of one of these, that is treated as a design fault and the primitive gets extended instead. It is an unusual rule to hold to, and it is the reason the pieces fit.
- Person
- Collective and membership
- Schedulable and assignment
- Attendance
- The communication pipeline
- Files
Person
One directory record per human being. Every roster, assignment, check-in and message resolves to it, so no module keeps its own copy of a phone number to go stale.
Collective and membership
Teams, small groups, Bible classes and mailing lists are one thing with a type. Build a roster once and it is an audience, a class register and a scheduling pool.
Schedulable and assignment
One scheduling engine. A position on a service plan, a seat on a class rota and a slot at an event all invite, accept, decline and swap through the same flow.
Attendance
A record in its own right, not a by-product of a kiosk. A check-in station writes it, and so does a teacher marking a register or an usher counting heads.
The communication pipeline
Audience, template, channel, delivery log — in that order, every time. The in-app inbox is a channel on the same pipeline rather than a second system.
Files
One file service with real permissions, inherited from whatever the file is attached to. A background-check document is not readable by everyone who can see a lesson plan.
Module by module
Every module, and whether it is built yet
All 13 of these read real data today. Availability chips are still read from the same list the app uses to explain its own empty pages — so if a module ever deferred again, this page would say so with the deploy rather than a hand edit.
People and households
Available nowThe directory, with the family structures churches actually have — including a child who belongs to two households. Per-person privacy, duplicate detection, and a merge tool that repoints everything.
Groups, classes and lists
Available nowRosters for small groups and Bible classes, plus smart lists: a saved filter that stays current instead of a hand-picked list that rots. "Members, has kids under five, joined this year" is one list, always right.
Serving teams
Available nowPositions, qualifications, and each volunteer’s own availability and blockout dates — the facts the scheduler needs before it can ask anyone anything.
Services and scheduling
Available nowService types, plans, and the order of service. Assignments go out, volunteers accept or decline from a link with no login, and auto-fill respects blockouts, conflicts, and whose turn it is. The live orchestrator keeps the service moving from the booth.
Events and registration
Available nowRecurring events that survive daylight saving — nine in the morning stays nine in the morning — with room booking, capacity and waitlists, and registration through a public form link anyone can open.
Calendars and feeds
Available nowMinistry and room calendars, and a personal “my schedule” feed each volunteer subscribes to once in Apple or Google Calendar. Their commitments turn up where they already look.
Check-in and attendance
Available nowStation-based check-in with kids security codes, guardian pickup matching, classroom companion mode, parent pages on presenter screens, guest signup, and per-station questions — built so Sunday morning keeps moving.
Digital signage
Available nowDisplays, playlists and stream URLs you configure on the web today, ready for foyer screens and the Apple TV app. Parent-page overlays reuse the same kids security codes check-in already minted.
Giving
Available nowFunds, batches and contributions on an offline ledger — envelope entry, soft credits, anonymous gifts — with person as the donor of record and household as the statement unit. Year-end tax statements come next on the same ledger.
Bible classes and curriculum
Available nowClass rosters, a versioned curriculum library, lesson schedules, and Promotion Sunday that previews every grade move before anyone clicks execute — including remapping children onto their next classroom.
Locations and floor plans
Available nowBuilding addresses, room configuration, and floor-plan maps you draw once — then check-in stations and digital signage show parents where to go.
Forms
Available nowA builder with conditional fields, public fill links protected by Turnstile, and submissions that match to existing people for review rather than silently creating duplicates. The same forms bind as check-in questions on a station.
Communications
Available nowTemplated email to any roster or smart list, with a delivery log that says what arrived. Scheduling requests and newsletters are handled differently, because the law treats them differently.
Check-in on Sunday
From the foyer glass to the classroom door
Station search, household selection, security codes, classroom confirmation, and pickup matching — one path, drawn the way a volunteer explains it with their hands.
Find the household
Search by name or phone at the station. Lookup stays fast even when the foyer is full.
Choose who’s checking in
Select family members and their destinations — today’s service, a class session, or an event.
Answer station questions
When the station binds a form, allergies and first-time visitor notes are asked before anyone is written in.
Keep the security code
Kids mode mints a household code on the confirmation screen. Parent-facing surfaces show the code, not the child’s room.
Classroom confirms arrival
Teachers mark kids Here on the companion clipboard. Admins can move a child between rooms without re-checking them in.
Match at pickup
Checkout matches the code to an authorised adult — or a self-checkout authorisation — and soft-denies a mismatch on self stations.
Questions
The things churches ask second
After “does it do scheduling”, these are the questions that decide it.
- Can a volunteer accept a Sunday without making an account?
- Yes. Assignment requests carry a signed, single-use link with a narrow scope and an expiry, so accepting, declining or asking for a swap takes one tap from the email. Most people in a church directory never log in at all, and the data model is built around that: a Person is the identity, and a User is only a way to sign in as one.
- Do children get accounts?
- No. Nobody under thirteen is ever a User — their records are managed by a guardian. Teens between thirteen and seventeen are optional per church, with a guardian consent flag. Kids check-in data such as allergies and authorised pickups is treated as a sensitive field, which means it needs an explicit grant to read and the reading is itself recorded.
- What happens when the church Wi-Fi drops on a Sunday morning?
- Check-in is designed around that rather than despite it: stations mint their own check-in ids and the live counts are a polled projection of D1, so an offline drain can catch up without inventing a second book of record. The web kiosk’s service-worker queue is still on the Phase 3 list; the native iPad app is what will drive thermal label printers when Wi-Fi flakes.
- Does a recurring event survive daylight saving?
- Yes, and it is worth asking, because naive repeating events are where most calendars break. Times are stored in UTC alongside the church’s own timezone, and recurrence resolves in local time — nine in the morning stays nine in the morning across the change, and an exception to one week does not rewrite the rest.
- Can we move our directory across from Planning Center or Breeze?
- That is what the CSV importer is for, with column mappings for Planning Center, Breeze and Elvanto, a dry run that shows you exactly which rows would merge before anything is written, and duplicate detection that gives a reason rather than a score. Every row is staged before anything is written, so the preview can say “31 of these look like people you already have” without having created one — and the pairs it is unsure about go to a review queue that remembers what you decided.
- Can we use our own domain and branding?
- Yes: set your colours, logo, and banners under Settings → Branding, and email layouts pick them up automatically. Custom hostnames provision through Cloudflare for SaaS from Settings Domains, with managed certificates, and email already goes out under your church’s display name. SMS sending still waits on a Messaging Service being wired.
See whether it fits your Sunday
Tell us what your week looks like and what you are running now. If this is not ready for your church yet, we would rather say so than sell you a migration.