Shipped
Running in production on the East Tennessee Nazarene District today.
Naz.tools Events
Shipped Event registration core
Household-aware booking, person and family records, multi-day events, live ticket-availability validation, cancellations and full/partial refunds.
Shipped Stripe payments with per-entity routing
Per-event payee picker, KMS-encrypted per-entity Stripe key vault, webhook receiver with signature verification and idempotent processing.
Shipped Waivers with HIPAA-aligned storage
E-signature capture per booking, per-event waiver templates, S3 Object Lock + KMS storage, three-year PHI retention with Glacier Deep Archive transition.
Shipped Tablet kiosk check-in
PIN-protected kiosk mode, QR-code scan check-in/out, multi-day "Day N of M" tracking, CSV roster export, undo with audit trail.
Shipped Member self-service ("My Events" tabs)
My Registrations, My Household, My Events (for staff), in-tab profile editor, password change with current-password verification.
Shipped Full event RBAC
Event creation, edit/delete scoped by payee, admin list filtering, composable role framework (event admin, kiosk operator, waiver admin, payee).
Naz.tools Attendance
Shipped Monthly attendance reporting workflow
Per-church reporters submit monthly counts via a structured form. Reporting deadline configurable per district (default: the 8th).
Shipped Twilio SMS + email reminders
Automated SMS reminders on the 1st and 8th of each month for delinquent reporters. Email reminders alongside.
Shipped District rollup dashboard
District-admin view of who's reported, who's delinquent, attendance trends over time, and per-church history.
Shipped Modern Events Calendar venue sync
Each church syncs as a MEC venue so church admins can create events tied to their own location, sharing one source of church data.
Shipped Reporter RBAC
District admin / church admin / reporter / viewer roles. Reporters can only edit their assigned church's data.
Naz.tools Directory
Shipped Public church finder with phone-verified gating
Map-based church directory, local-events listing per church, phone-verification form before contact details surface.
Shipped Leadership & committee registry
People records with photo, role, term-end, contact, committee. Bulk import + bulk priority update tools.
Naz.tools Team
Shipped Native Elementor team-display widget
Responsive grid (1–6 columns), live search, committee filter, click-to-reveal contact obfuscation, multi-instance per page.
In progress
In progress Kiosk PWA — installable to iPad/Android home screen
Web app manifest, service worker, iOS-specific meta tags so the kiosk can be installed as a home-screen app on a registration tablet. Explicitly not an offline-queue feature — that's a separate, larger project.
In progress Multi-district readiness
Documentation, white-glove onboarding runbook, deploy automation, and the parts of the codebase that still hard-code "ETNDI"-shaped assumptions need generalizing before any second district is migrated.
In progress Naz.tools rebrand of the CAR/Directory/Team plugins
The attendance, directory, and team plugins are being renamed and unified under the Naz.tools brand, with shared assumptions and one upgrade path.
Planned — suite-wide
Planned Two-factor authentication
Built-in 2FA for admin roles across the suite, not just via WordPress plugins. Higher priority for districts handling minors' data.
Planned Unified district calendar
One unified calendar of district events, member-church events, and camps. Aggregation across the four district ministries.
Planned Cross-component leadership dashboard
Attendance trends, ministry-level revenue summaries, waiver-compliance status, reporter-delinquency, and credentialing status — one place the District Superintendent can open without asking the IT volunteer.
Future tools — coming after the core suite stabilizes
These are the next products beyond the four already shipping. Order and timing are negotiable based on beta-district feedback.
Future Naz.tools Voting
District Assembly delegate voting and church board elections, with eligibility validated against the directory, audit trail per ballot, and roll-up tallies for the District Secretary. Replaces the paper-ballot-plus-spreadsheet workflow most districts run today.
Future Naz.tools Credentialing
Track ministerial credentials — license, ordination, retirement, transfer — with renewal reminders, document storage, and a District Board of Ministry workflow. Surfaces credential status in the directory so what's published is always accurate.
Future Naz.tools Jobs
Pastoral and staff job board for the district, with applicant intake, search-committee permissions, and visibility scoped to the district (not a public-internet posting). Pulls from the directory so postings can be tied to specific churches.
Future Naz.tools UMF Payments
One Stripe account, three clean streams, every transaction tagged at the source — designed around how Nazarene district money actually moves.
- UMF (Unified Ministry Allocation) — churches to district. ACH only, capped at $5 per transaction regardless of amount. A church sending $3,000/month pays $5, not $87.
- Event Registration — for the district's auxiliaries. Cards, debit, and ACH on the same Stripe Checkout. Each auxiliary reconciles to its own treasury.
- Donations — district-level giving. All methods, including Apple/Google Pay. Receipts auto-generated.
Per-church Stripe Checkout landing pages — branded, pre-populated with the church's name, tied to the same church record that drives attendance and the directory. The treasurer visits one page; the platform tracks who's paid and who's behind. The merchant relationship is the district's, not a middleman's.
Future Naz.tools District Treasurer Dashboard
One unified financial view for the District Treasurer — every dollar in, categorized, reconciled, and tied back to the church or auxiliary that sent it.
- UMF receipts by church, with a live delinquency view
- Event revenue by auxiliary (Inspire, NMI camps, NYI, etc.) — separate ledgers
- Donation totals across the district
- Per-church running balances alongside attendance reporting status — one page, not two
- Audit-ready transaction history with timestamped, ECFA-aligned audit trail
- Export to your existing accounting system (Aplos, QuickBooks, Wave) — the platform doesn't replace your general ledger, it feeds it
Considering
On the long list. Beta-district feedback will move these up or off.
- Recurring giving / pledge campaigns (separate from event payments)
- Volunteer scheduling for camps and conferences
- Group / small-group registration patterns
- Native mobile app for staff (probably not — PWA is the plan)
- SOC 2 Type I report
If something on this list would change your district's decision to join the beta — let us know. Roadmap order is heavily influenced by what beta districts actually need.