Phase G ships the mobile experience. This document shows what the web dashboards look like β the side church staff, mentors, pastors, coordinators, and admins live in every day. Ten screens chosen to cover the actual delegation reality: pastors monitor coordinators; coordinators run their domain; every activity reports its estimated vs. actual attendance and what the SRS said about it; new members are tracked through the welcome funnel with a dedicated Welcome Pulse instrument; small groups are measured by their GSRS engagement score; clinical mentors who bill see their session revenue and Stripe Connect payouts.
This v3 fills two gaps v2 still had: "are we actually welcoming new people?" (new Welcome Pulse instrument + scorecard dashboard) and "are our small groups engaging?" (GSRS applied to small groups with per-group cards showing trend + retention + invitation conversion). Both are MEP applied to onboarding β the moment a person first encounters the church is where future engagement is decided.
v4 adds Missional Vital Signs (MVS) β the measurement layer that operationalizes the ministry renewal movement's Genesis Compass. Four new screens: the pastor's overview, an indicator drill-down for Culture of Prayer, the Ministry Coach view foregrounding momentum and trade-offs, and the first-week "indicative" empty state before the Ministry Coach sets church targets. MVS is designed to be the tool ministry coaches adopt rather than reject β Level + Momentum twin axes (the REVEAL antidote), church-as-its-own-control (no leaderboards), and clinical PHI walled off from the measurement layer entirely.
Intersections with existing code: these mockups intentionally align with already-shipped patterns in gracesteps-server β the StatCard pattern from FacilitatorReportsPage, the 7/30/90-day window selector, the MentorLoadIndicator capacity bar (becomes Coordinator Load Indicator for church), mentors-oversight-table (becomes Coordinators Oversight), mentor-change-approval-card (church access requests reuse the same approval pattern). The church attendance API at /api/attendance/check-in already records kiosk + manual + self-dashboard sources; the activity report just visualizes what's already collected. This isn't building from scratch β it's surfacing data that already flows.
Each browser frame is a real workflow that a real persona uses. Captions explain the strategic intent and the existing code primitives the screen builds on, so engineering doesn't read this as a from-scratch ask. Screens 11β14 introduce Missional Vital Signs (MVS) β the operational measurement layer designed for ministry renewal churches. Three-key rollup (Culture of Prayer / Evangelization / Shared Leadership) + a North Star (Vision) gauge, each indicator reporting Level + Momentum + Confidence so the dashboard cannot be misread as a scorecard. v1 ships from passive operational exhaust only β zero new survey burden on the church.
MentorLoadIndicator component from src/components/org-dashboard/mentor-load-indicator.tsx β same green/amber/red logic at 75/90% thresholds. The oversight table is the church analog of mentors-oversight-table.tsx. The "Check in" thread reuses the existing conversations machinery. Net-new work is the data wiring + the per-coordinator pulse rollup query.FacilitatorReportsPage. The "Hours needing attention" table reuses the load-bar component. Sub-coordination integrates with the existing prayer broadcast system at /api/broadcasts. New work is per-coordinator role-based view permissions β the church role pack from the consolidated baseline already defines prayer_ministry_coordinator, so the RBAC gate is in place. Just need to wire the coordinator-scope filter on the existing queries.members, and thenβ¦ nothing measures whether anyone reached out, whether they were invited to a group, whether they feel they belong. This dashboard fixes that. Four KPIs at top measure conversion through the welcome funnel: signed up β personally contacted β invited to a group β active in a ministry. The gold callout is the new Welcome Pulse instrument β a 4-item VAS scored at 7 / 30 / 90 days post-join asking "have you felt welcomed," "have you found connection," "is this becoming your spiritual home." The lowest-scoring dimension surfaces the action ("Found connection" 6.4 β invitation gap β prioritize group invites). The per-member table flags people who haven't been contacted (rose background) β Emily Butler 42 days in without a single personal outreach is the kind of failure the system makes visible.members table exists in the Prayer Ministry consolidated baseline. measurement_subject_kind already includes 'member' as a value. The Welcome Pulse is a new built-in instrument to seed in a follow-up migration (14th instrument, joining the 13 already seeded). Trigger pattern reuses the alliance-hooks model from Phase F: on members INSERT, schedule pulse_invitations at +7d, +30d, +90d (same shape as `prayer_request_received` etc.). Per-member outreach tracking joins conversations + messages on member.profile_id; group invitations join church_membership_extras + group memberships. Net-new is the instrument seed + the report UI.helper_encounters with subject_kind='group_session'. What's net-new is the per-group rollup query (group GSRS over time, retention, invitation conversion) and the leader-by-leader visibility. The CGSRS branch is automatic β children's groups already use the children's variant of the instrument. Cross-org groups (Campus Fellowship at Grace Campus House) work because helper_encounters.organization_id identifies which org owns the group, and the dashboard filters by visible orgs for the viewer./api/attendance/check-in, /api/attendance/visitor, /api/attendance/current-hour. SRS-per-service is the existing helper_encounters/measurements infrastructure pivoted by subject_kind='sermon_mass'. The per-team breakdown joins ministry_assignments Γ measurements with the same service subject_id. Net-new is the dashboard UI itself β every underlying datum is already collected.connectService.ts, stripe_connect_account_id on organizations, 5 endpoints under /api/organizations/[id]/stripe-connect/*). Per-mentor revenue reporting is the org-level /dashboard/super-admin/financials page pivoted by mentor.user_id instead of organization_id. The window selector and stat-tile pattern come from FacilitatorReportsPage. Net-new is the per-mentor scope and the tax export β both queries-and-UI, not new infrastructure.Reading the screens above as user journeys β what each persona does in 60 seconds when they sit down. The product's strategic argument is measured delegation: it works for the pastor, for each coordinator, for the mentor, the billing clinician, AND for the new member whose welcome experience now gets visibly tracked.
Pastor Mike opens the dashboard at 7 AM. The Delegation Health table shows him in 5 seconds that Joseph's work-orders backlog (3 open Β· 2 overdue) is dragging that ministry's pulse down to 6.9. Maria's prayer ministry is on track (87% covered), Patricia's prayer-wall queue is healthy, David needs help filling 8 ministry slots for Sunday 12 PM. Pastor Mike opens a thread with Joseph to check in, broadcasts the open ministry slots, and signs off. The dashboard is fundamentally about delegation health, not the pastor's personal to-do list.
Maria the Prayer Ministry Coordinator opens her dashboard. She sees the same shape as Pastor Mike β KPIs, attention list, hours-needing-attention table β but scoped to her one ministry. Her dashboard has the church's prayer ministry hours and only those. The shape is consistent so coordinators trained on one ministry can lead another with minimal re-onboarding. This is how church staff scale.
The pastor or coordinator opens any specific activity (Sunday 10 AM Worship Service, Thursday's prayer team meeting, Saturday's prayer hour). The Activity Report tells them: coordinator estimated 320, kiosk + greeters + mobile logged 287 actual, the SRS for THAT specific activity averaged 7.4 with cantor flagged 6.4 (consistent with comment "music felt rushed"). This is operational visibility no church CRM provides β most churches still track worship attendance in a paper notebook.
Sarah Chen sees Anna's ORS trending up after a hard month and remembers Anna's grandmother passed. She opens the thread, drafts a thoughtful note, and attaches a prayer request from Anna's home church (Crossroads). One click sends it. The prayer request is scheduled server-side, lands in Anna's mobile inbox, and Crossroads church staff sees it appear in their queue with Sarah's note attached. The clinical and church surfaces become one motion.
Sarah β an LCSW billing through GraceSteps Connect β opens her Billing dashboard at month's end. $3,420 gross, $3,146 net, $1,580 hitting her account Thursday, $320 outstanding (one card declined that needs follow-up). Each session line item includes the ORS and SRS scores β clinical outcomes adjacent to billing means the clinician isn't choosing between "do good work" and "get paid for it" as separate concerns. Tax export button regenerates a 1099-ready CSV. This is the report counselors, coaches, and psychologists need to actually use the platform as their billing infrastructure.
Maria the deacon (or whoever owns welcome) opens the Welcome Scorecard. She sees 24 new members over the last 90 days, 19 personally contacted, 12 invited to a group, 8 active in a ministry. The Welcome Pulse instrument (4-item VAS at 7/30/90 days) tells her the lowest-scoring dimension is "Found connection" (6.4 / 10) β the invitation gap is the bottleneck, not the warmth of the church. She filters to "no contact yet" and sees Emily Butler (42 days), Jasmine Kang (19 days Β· welcome email only), Thomas Murphy (8 days Β· nothing). Three personal phone calls and three group invitations later, those flags clear. The church stops losing new members to silence.
The pastor opens Small Group Engagement. Nine groups, 142 total members, avg GSRS 8.1. Most groups healthy. Three flagged: Young Adults Bible Study (GSRS 6.8, dropping; lost 3 members; low invitation conversion β John needs help), Thursday Lectio Group (GSRS 5.9, lost 4 of 10 members; bleeding β rethink format), Campus Fellowship at Grace Campus House (cross-org, healthy at 8.4 β Anna's peer-led college group is a model). The pastor walks down to John's office on his way to lunch. Group engagement measurement is the missing layer in every other church platform β the GSRS instrument already lives in the schema; this is the surface that makes it actionable.
A clinical platform and a church CRM each compete in saturated markets. The unified platform competes in a market with no other product. The Delegation Health table is the demo. The Activity Report with estimated-vs-actual is the demo. The mentor's prayer request attachment is the demo. The clinician's billing report with ORS/SRS inline is the demo. Each demo is invisible to any competitor because building it requires owning both surfaces.