This workflow is currently under review and is available for preview only. Central saving, submission and AI analysis are disabled for this module in the current release.
Not a form. An operational review. Understand who left, why, whether it was preventable, and what leadership needs to know.
Progress · Leavers Report
0 of 5 · 0%
Tile 1 of 5
Setup
SetupConfirm identity and select the operational month.
Session identity · read-only
—
Club
—
Session
—
Region
—
Session
—
Authenticated as
—
Session
Operational month · which month are you reporting?
Report the month whose cancellations you're reviewing. Defaults to the most recently completed month.
Tile 2 of 5
Leavers Log
LeaversAnswer whether the club had any leavers this month, then log each one.
Any leavers this month?
Did the club have any cancellations this month?
Privacy: capture Member ID only · no names, addresses, or contact details. Leadership analytics and cross-club insights work exclusively from anonymised IDs.
Zero-leaver month acknowledged. A month with zero cancellations is a real datum — not missing data. Confirming records this month as a preserved zero rather than an omission.
Tile 3 of 5
Summary & Insights
SummaryAuto-derived from the leavers log. Nothing to enter — this is what leadership will see.
This month · at a glance
Reason breakdown
Reason · Count · % of total
Length of stay distribution
Bucket · Count · % of total
Patterns worth leadership attention
Tile 4 of 5
Coaching Brief
CoachingReflect on the month's patterns · optional but valuable for coaching feed + AI trend analysis.
Coaching reflection · optional
What patterns do you want leadership to notice this month?0 / 500
Every reflection becomes durable coaching data. Over time these entries feed pattern discovery across clubs — the Coaching engine and AI insights layer consume them without further transformation.
Tile 5 of 5
Review & Submit
ReviewReview the month · acknowledge any warnings · submit for leadership + Outreach consumption.
What happens next: Submit will persist this report once the backend companion is deployed. The v2 payload bridges to the existing handleLeavers Apps Script handler without schema disruption. Home v1 will surface the report through macarthur_dr_last_leavers in the Platform Integration sprint.
✓
Leavers Report prepared
The frontend flow is complete. This month's report is ready for backend persistence, leadership consumption and future Outreach follow-up routing.