Different persona, different shape from the parish pastor. The chaplain at a Catholic college runs a small high-leverage team, not a sprawling parish, and the academic semester drives the rhythm — not the liturgical year. He has visibility into students that no parish ever has (academic schedule, year-in-school, formation cohorts), and an explicit measurement need around spiritual multipliers — students who go from being mentored to becoming mentors.
The persona for this gallery:
Active reach: ~280 students engaged out of ~600 Catholic students on campus. Spring 2026 · week 12 of 15. The mockups below show six dashboards: the chaplain's daily landing, FOCUS missionary oversight (with the federated-reporting nuance called out), the student roster with engagement signals, Bible studies health (16 studies running this semester), one FOCUS missionary's personal dashboard, and a major-event manager for the upcoming spring break mission.
Intersections with existing code: the underlying schema needs no new tables. organizations.org_type = 'university' plus parish_org_settings.org_subtype = 'newman_center' identifies a campus center. Bible studies are helper_encounters with subject_kind = 'group_session'; 1-on-1 discipleship is the same with subject_kind = 'direct_session'. FOCUS missionaries get a custom_role_slug = 'focus_missionary' via organization_custom_roles; staff coordinators get 'coordinator'. The federated-reporting to FOCUS HQ is a separate downstream export, not a different data model.
Captions explain what's different from the parish version and what existing code primitives each screen builds on.
parish_membership_extras.based_on_role transitions + helper_encounters where the student moved from group_session.subject to group_session.leader. The federated export is the existing broadcasts/email_logs machinery applied to a system-to-system integration.parishioners table stores student records; year-in-school + RCIA status live in parish_membership_extras.allowed_modules + a new student_year text column on the same sidecar. The wellbeing index is a server-side rollup over attendance_records, helper_encounters, and measurements — same pattern as the parish activity report, scoped by student.helper_encounters with subject_kind = 'group_session'. The student-led tag is derived from helper_encounters.leader_user_id existing in organization_custom_roles with slug = 'student_leader' vs 'focus_missionary'. GSRS measurements are the existing Phase 2 instrument seed.helper_encounters where leader_user_id = anna.id and subject_kind = 'direct_session'. Working-on notes are session-note attachments. The shepherding pipeline calculation joins disciples with parish_membership_extras.based_on_role showing the upcoming role transition.special_events in the consolidated baseline. Registration is signup_form_signups with the event's form. Fundraising integrates with Stripe Connect for donations. Pre/post pulses are the existing pulse_invitations primitive with two new instruments — Pre-Mission Readiness and Post-Mission Impact — added to the seeded set.Reading the screens as user journeys — what each persona does in 60 seconds at Holy Cross.
Fr. Patrick opens Today and sees 6 people he can see by name (2 staff + 4 FOCUS) plus a small group of urgent items. John is over capacity. The mission is short of registrations. Two RCIA candidates are waiting on James. The whole team table fits on one screen. He clicks "Help John" — opens a conversation. Total time: 90 seconds. The same time on a parish dashboard would have shown him a list 10× longer; a chaplain's team is smaller and that's the design.
The FOCUS Oversight screen is the structurally novel piece. FOCUS missionaries report to both the chaplain locally and FOCUS regional leadership nationally. The dashboard supports this honestly: the chaplain sees his 4 missionaries' work, the multiplier metric FOCUS cares about, and a status indicator showing the latest data export to FOCUS HQ. This is the federated-org pattern — one user belongs to two reporting structures. The product doesn't pretend they don't; it handles them.
The roster gives Fr. Patrick (and Megan, and the FOCUS team) a per-student wellbeing trend. Jacob Nguyen's sparkline crashed three weeks ago — the system can flag it. Emma Walsh's sparkline cratered around her uncle's death. Sarah Edwards's sparkline rises through her senior year as she becomes a multiplier. The roster surfaces names that need attention before the next semester reveals that nobody noticed. On a parish dashboard the same view would show 2000 rows; here it shows 284, and that's its own form of intimacy.
16 studies running. 9 of them student-led — that's the multiplier engine. Two flagged this week: John's struggling sophomore men, Ben's faith-seekers group with retention dropped to 38%. The chaplain knows in 10 seconds which ones need a check-in. The GSRS is the same instrument that runs on parish small groups — campus context is just denser. The student-led ratio is the campus-specific KPI: a higher percentage means the multiplier engine is working.
Spring break mission isn't a one-time event — it's an anchor that reshapes a student's spiritual trajectory. The Mission Manager dashboard plans the pulse cadence accordingly: pre-departure readiness, day-0 post-return, day-7, day-30, day-90 (the long tail of impact). The multiplier-impact survey on a chosen subset asks the strategic question — "did this mission shift your willingness to lead?" That's how the chaplain knows two months out whether the $12,000 he raised converted into next year's student-led Bible study leaders.
FOCUS HQ has their own reporting tools. Most Catholic colleges use spreadsheets. Mindspirit has clinical software. None of them measure spiritual multipliers as the core engagement metric while ALSO tracking individual student wellbeing while ALSO supporting the federated FOCUS-and-college reporting structure. The unified product is the only place a chaplain can run his ministry from one dashboard and have it speak both languages.