- Student needWho, and what is happening?
TechnologyCommuting students miss labs in weeks 2–4
- MechanismWhich theory explains it?
TechnologyInvolvement drops; belonging is fragile (Astin; Strayhorn)
- Institutional responseWhat will people do?
TechnologyProactive advisor contact and lab scheduling options
- Technology functionWhat does the tool do?
TechnologyFlags missed labs and routes the case to an advisor
- Workflow ownerWho acts, by when?
TechnologyNamed advisor, contact within 48 hours
- Process measureDid the response happen?
TechnologyShare of flagged students reached by a person within 48 hours
- Student outcomeDid it help?
TechnologyLab completion, course pass rate, belonging score
- EvaluationFor whom, compared with what?
TechnologyComparison group; results by attendance pattern and race
If a link has no answer, the tool is not ready. Most early-alert projects stop at the technology function.
Judge early alert by support, not alerts
- Time from flag to human contact
- Share of flagged students reached by a person
- Share who received a referral that fit the problem
- Outcomes compared with similar students who were not flagged
- All of the above by student group
- Alert volume is a workload measure, not a success measure.
Template: fill one line per link
- For [student group] experiencing [need],
- we expect [mechanism] to matter.
- [Office] will [response],
- supported by [technology function].
- [Named role] acts within [time].
- We will track [process measure]
- and expect change in [outcome],
- evaluated by [comparison] for [groups].