- CollectApplications, LMS, SIS, card swipes, surveys
TechnologyCollect only what serves a stated student success purpose
- Store & integrateWarehouses, CRMs, vendor platforms
TechnologyDefine ownership, access roles, and shared definitions
- Analyze & modelDashboards, predictive models, AI
TechnologyDocument variables, test for bias, record approvals
- ActOutreach, alerts, holds, advising
TechnologyName who acts, how, and how students can respond
- Retain & disposeArchives, vendor contract end
TechnologySet retention limits and verify deletion
Map one student success tool through all five stages. Gaps usually appear at “Act” and “Retain & dispose.”
Common failure points
- Data collected for one purpose, such as card access, is reused for another, such as engagement scoring, without review.
- Vendor contracts do not specify data ownership, secondary use, or deletion.
- Model inputs change upstream and no one tells the team using the scores.
- Students have no way to see or correct data used to flag them.
In the Campus Enterprise Model
Where this work sits in campus systems, capabilities, and data.