Run a Sunday Service
How-To Guides
All GuidesRun a Sunday ServiceSet Up Online GivingConfigure Children's Check-InGenerate Tax ReceiptsImport MembersCreate a Small GroupSet Up Volunteer TeamsRecord a Pastoral VisitManage PledgesCreate an Email CampaignSet Up Service PatternsRun a DepositMerge Duplicate DonorsManage Absence AlertsSet Up Prayer GuidesOnboard New MembersManage Join RequestsBuild an Order of ServiceSet Up Worship SetlistsRun a Sunday Service End-to-End
Gather Steward ServeThis guide walks you through a complete Sunday morning workflow: materialising and starting the service, running check-in, recording attendance, completing the service, entering a giving session, and creating a deposit. By the end, your service will be fully documented in SanctuaryOS with both attendance and financial records.
Prerequisites
- At least one Service Pattern configured in Settings → Services (e.g., “Sunday Morning”)
- Funds set up in Settings → Finance → Funds
- Your user account has SUPER_ADMIN, LEAD_PASTOR, or PASTOR role (or a combination of roles covering Gather + Steward access)
Phase 1 — Materialise the Service
Services are generated from Service Patterns. SanctuaryOS automatically materialises upcoming service instances, but you can also trigger it manually from the calendar.
- Navigate to Gather → Calendar
- Locate the upcoming Sunday in the calendar view (month or list view)
- If no service instance exists for today, click “Materialise” to generate it from the service pattern
- The service appears with status SCHEDULED (amber badge)
Phase 2 — Start the Service
- On the Gather → Calendar page, find your service row
- Click the “Start Service” button on the service row
- The status changes from SCHEDULED to ACTIVE (red pulsing badge)
- Check-in is now open for this service across all devices
Phase 3 — Run Check-In
- Navigate to Gather → Check-In
- Select the active service from the service picker — services with the ACTIVE status appear at the top
- The Check-In Console opens with three modes:
- Lookup — search members by name, phone, or email and tap to check in
- Clicker — simple headcount counter (tap “+” to increment)
- Roster — scrollable member list with checkboxes
- Check in members as they arrive. The Headcount and FTV Count update in real time
- To register a first-time visitor, search for them and click “Add as Visitor” when they don't appear in results
Phase 4 — Complete the Service
- When the service ends, return to Gather → Calendar
- Click “Complete Service” on the active service row
- The status changes to COMPLETED (green badge)
- Check-in closes — no further check-ins can be recorded
Phase 5 — Enter the Giving Session
Now switch to the Steward module to record the offering.
- Navigate to Steward → Sessions
- Click “New Session”
- Select the Service (the completed service you just ran) and enter the Session Date
- The Session Entry grid opens. For each giving envelope:
- Type the Envelope # or donor name to look up the donor
- Enter the amount in each Fund column (e.g., General, Missions, Building)
- Set the Payment Method (Cash, Cheque, Card, etc.) — you can type a shortcut key:
cfor Cash,kfor Cheque - For cheques, enter the Cheque #
- Each row auto-saves when you Tab or Enter to the next row
- The running total updates at the bottom of the grid
- When finished, click “Submit” to change the session status from DRAFT to SUBMITTED
Phase 6 — Create a Deposit
- Navigate to Steward → Deposits
- Click “New Deposit”
- Select the session(s) to include in this deposit
- Enter the Bank Amount once you have the deposit receipt from the bank
- SanctuaryOS compares the bank amount to the session total:
- Reconciled — amounts match (green badge)
- Discrepancy — amounts differ (red badge, investigate)
- Pending — bank amount not yet entered (amber badge)
Summary
Your Sunday service is now fully documented: attendance recorded in Gather, giving entered in Steward, and the deposit reconciled against your bank. The cross-module Services page at /services shows the combined view — attendance, giving totals, and volunteer coverage for any service instance.