Student onboarding
The first weeks of an enrolled student in one place: accounts handed over, orientation, placement and the 30 and 90 day checkpoints, with deadlines counted from the start date. The time to first engagement is measured from real signals and shows "no measurement" when there is none. Part of the Education vertical, optional and off until an administrator turns it on.
The Education screen gains the Student onboarding block: the checklist of the first weeks for each enrolled student, with the deadlines, the accounts already handed over and the time it took the student to actually show up.
It comes from the enrollment
Nobody creates an onboarding by hand. When a student is enrolled, the onboarding opens by itself, one per enrollment. Opening it again, by the button or by the system, never creates a second one.
The start date is taken from the enrollment: the start date it declares, or the moment it was recorded, or the first day of classes of the term. The screen always says which of the three it used. If none of them exists, there is no start date, and without a start date there are no deadlines, so the state reads "no measurement" instead of pretending everything is fine.
Milestones with a deadline counted from the start
Every onboarding starts with five milestones: accounts handed over, orientation, placement, the 30 day checkpoint and the 90 day checkpoint. Each one carries a number of days, and the deadline is that number counted from the start date. Your school can change the list, and changing it never erases work already done: a milestone that was already completed keeps its status.
A milestone with no deadline is never late. An unknown deadline does not become a complaint.
Time to first engagement is measured, never estimated
This is the number the block exists for, and it only comes from facts that were recorded with a date: an attendance check-in, an orientation the student attended, or a signal the staff records with the day it happened. The system picks the earliest of them and counts the days from the start.
When there is no signal at all, the screen says "no measurement". It does not show zero, it does not show an average and it does not guess. The overview counts measured and not measured separately, and the averages are calculated only over the students who have a real signal, so a student nobody has seen yet never drags the number down as a zero.
What the system never does
An overdue milestone raises a heads-up for the team, once per student. Nothing is blocked, no enrollment is cancelled and no student is labelled. Following up is a human decision.
The list of accounts handed over stores the name of the account, the channel and when it was handed over. Passwords and tokens never go into the CRM: there is no field for them.