← Back to work

Case Study · Onboarding & Implementation

5 programs. One Monday.

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.

Client

The AEA Institute

Program

A 28-day mental training camp for high school teams

My role

Launch scheduling, onboarding, day-two follow-up

Launch day

Monday, November 16, 2026

5
high school programs launched the same Monday
3
states, one launch checklist
28
day camp, with the retake on day 29
Day 2
launch report on every team, before anyone follows up

The challenge

Five launches, five chances for a quiet start

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

Set up

  • Coach registers the team and picks a start Monday
  • I set the start date in the admin tool
  • Welcome email goes out with the join steps
  • Athletes join and take their baseline

Monday

Go live

  • Camp opens for every team at once
  • Coaches get a day to share it with their athletes

Day 2 to day 29

Check and follow up

  • Rerun the launch report: joined and assessed, by team
  • Draft follow-ups for any team that hasn't started
  • Retake on day 29 to show the change

What happened

Three teams joined fast. Two needed a nudge.

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

A pipeline that moves itself forward

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.

ProgramWhat happenedStage
Lakeview High SchoolPayment date enteredPaid
Riverside High SchoolWelcome email sentOnboarding scheduled
Cedar Ridge High SchoolCoach confirmed athletes are trainingOnboarded
Pine Valley High SchoolPayment link sentLink sent
North Shore High SchoolReplied "interested"Interested

Sample rows with made-up schools. The real tracker holds client data.

Events move itPaid date and welcome email advance the stage automatically.
Forward onlyA stage never slides backward on its own.
People decide "Onboarded"Free, comped, and not-moving-forward rows never change on their own either.

Skills

Onboarding that doesn't depend on memory

Contact

Let's talk.

Download résumé More work