Case Study · Onboarding & Implementation
Five high school programs in three states started the same Monday. I set the start dates, sent the welcomes, and checked every team the next morning, so no program launched to an empty roster and stayed that way.
The challenge
Every program has the same moving parts: a coach registers the team, a start date gets set, a welcome goes out, and athletes join and take a baseline. Miss one piece and a team "launches" with nobody on it. With five going live on one Monday, the steps had to be the same every time.
The week before
Monday
Day 2 to day 29
What happened
I gave coaches a day to share the camp with their athletes, then reran the launch report on Tuesday morning. Three teams already had athletes joined and assessed. Two hadn't started at all, so they went straight onto the follow-up list with the join link, instead of being found weeks later.
The system behind onboarding
For our bundle program, I built a tracker where the stage updates from real events instead of someone remembering to change a dropdown. A payment date moves a school to Paid. A sent welcome email moves it to Onboarding scheduled. It only moves forward, and "Onboarded" stays a human call.
| Program | What happened | Stage |
|---|---|---|
| Lakeview High School | Payment date entered | Paid |
| Riverside High School | Welcome email sent | Onboarding scheduled |
| Cedar Ridge High School | Coach confirmed athletes are training | Onboarded |
| Pine Valley High School | Payment link sent | Link sent |
| North Shore High School | Replied "interested" | Interested |
Sample rows with made-up schools. The real tracker holds client data.
Skills