ModulesEvents
Overview
Run attendance operations and service-plan workflows from one grouped events section.
Events groups the live service and event operations that teams usually need together.
This section is built for the reality of church operations: upcoming services need planning, live services need fast check-in tools, and finished events still need clean records that leadership can review later.
In This Section
Attendance
Run live check-ins, manage attendee records, and review turnout for active events.
Order of Service
Prepare reusable service-plan structure and run finalized plans in live view.
Why this grouping makes sense
Attendance handles the who-is-here side of live events, while Order of Service handles the what-happens-next side of the service plan.
What Teams Usually Use Events For
- Prepare service-day structure before the event begins.
- Run check-in and attendance workflows while the event is active.
- Review turnout, member versus visitor mix, and service-level activity afterward.
- Keep repeatable service planning in one place so the same work does not need to be rebuilt every week.
Practical Flow
- Confirm the correct event exists with the right date, time, category, and recurrence settings.
- Use Order of Service to organize the plan, sequence, and reusable service components when needed.
- Use Attendance during the live event for staff-assisted check-in, self check-in, or review.
- Review the attendance summary after the event so leaders know what actually happened.
What Makes This Section Operationally Important
- It keeps live-service tasks close to the planning surfaces that support them.
- It helps teams work quickly during busy arrival windows.
- It gives leadership a clearer record of turnout without building a separate reporting process first.
- It supports recurring rhythms, which matters for weekly church life.
Set Up This Section Well By Doing These First
- Create the main recurring and one-off events your branch actually runs.
- Check service times, event categories, and location rules before a live weekend.
- Decide whether your team will use manual check-in, QR/self check-in, or both.
- Build a simple Order of Service template for the most common service pattern.
Questions This Section Helps Answer
- Which event is active right now?
- How many people attended?
- Was attendance mostly members, visitors, or families?
- Is the service plan ready for the team running the event?
- Are the event rules, timing, and attendance controls set the way we expect?
Last updated on
Was this helpful?