One student record, from the nursery to youth group.
Moa is WayMark's software for a church's education department. A student's information, attendance, forms, and care follow them from tier to tier — and the rules about custody and access are built into the system, not left to a laminated sheet.
One student. One record. Moa follows them through every stage of your church's education department.
Church education runs on tools that weren't built for it.
A student's information resets every time they move up a tier — a new binder, a new spreadsheet, a new set of contacts.
Custody arrangements, allergies, and who's allowed to pick a child up live in someone's memory or on a printed sheet by the door.
Attendance, consent forms, and fees are tracked in three separate places that don't talk to each other.
What Moa actually does.
Built for a Sunday morning and the week around it — not adapted from a general-purpose database.
Check-in & secure pickup
- A 4-digit claim code is generated at check-in; the parent sees it in their own app and can text it to whoever is actually doing pickup.
- An authorized-pickup list per child that a teacher can check against at the door.
- A ratio guard warns when a room is over its kid-to-adult limit, and logs every override.
- Allergies, medical notes, and emergency contacts surface to the teacher at check-in — and only then.
One record, every tier
- A profile that follows a student from the nursery through youth group instead of restarting each year.
- Multiple households per child, so blended and divorced families both stay current.
- Priority-ordered emergency contacts with tap-to-call.
- Medical records a parent maintains once, shown to a teacher only during check-in.
Attendance & curriculum
- Take attendance for a class in a few taps, with a reason attached to an absence.
- A teacher can hand their class to a substitute for one day — access that expires on its own.
- Lesson plans and resources, memory verses, and per-student progress milestones.
- Make-up flags for students who missed a week.
Safety & compliance
- Custody and access rules are enforced in the database, not just hidden on a screen.
- Background-check tracking that blocks a volunteer role assignment when a check is missing or expired.
- Incident reports visible only to the person who wrote them and the pastor.
- COPPA parental consent for younger students, and an audit trail on every sensitive change.
Forms, fees & events
- A reusable form builder with electronic signature and consent, plus annual renewals.
- A signed form can be required before anyone can RSVP to an event.
- One-off and recurring events with RSVP.
- A fee-status ledger — paid, partial, waived, scholarship — and parent-submitted scholarship requests.
Communication
- Announcements, including scheduled ones, with push notifications.
- Private parent–teacher message threads.
- Prayer requests shared with specific teams or the whole church — with real anonymity, not just a hidden name.
- Group channels and serving schedules.
Four people, one shared source of truth.
Stays in the loop
Sees check-in status and the pickup code, keeps medical info and emergency contacts current, signs forms, and messages a teacher directly.
Runs the room
Opens class with the roster, attendance, allergy flags, and pickup list already in hand — and can hand it all to a sub when away.
Has their own record
One record that grows with them — classes, attendance, memory verses, and progress in a single place, from their first class to their last year.
Sees the whole department
Enrollment, attendance, background-check status, unpaid fees, and missing forms across every tier, from one dashboard.
The safety model is in the foundation, not the interface.
The parts that protect children can't be switched off by a setting or slipped past by a bug.
Each church's data is isolated
Records are separated at the database level. One church's account can never read or query another's.
Access checks run in the database
Custody and permission rules are evaluated on every request by the database itself — a shortcut or a bug in the app can't quietly bypass them.
Sensitive records leave a trail
Changes to attendance, links, incidents, and consent are audited, and sensitive rows are soft-deleted rather than erased.
Your data stays yours
A church can export all of its records if it ever decides to leave, and set its own name, logo, and colors while it stays.
Moa is in early development — not yet available to churches.
We're building in the open and talking with a few churches as we go. If you'd like to follow along or share what your education department actually needs, we'd love to hear from you.
Get in touch