Early Alert Utilization (National Conference)
•
0 likes•328 views
The document summarizes a presentation given by Carrie Brimhall and Sarah Rach about an early alert system implemented at their college. The system allows faculty and staff to submit alerts about students who may need additional support. It was created by the college's retention committee to improve retention. The presentation demonstrated the faculty, staff, and data usage components of the system and discussed lessons learned, including the need for feedback, IT support, and addressing faculty privacy concerns. It concluded by asking what resources would be needed to implement a similar system at other colleges.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Early Alert Utilization (National Conference)
Similar to Early Alert Utilization (National Conference) (20)
More from Sarah Rach
More from Sarah Rach (20)
Early Alert Utilization (National Conference)
- 1. 2007 NISOD Conference Carrie Brimhall and Sarah Rach MSCTC Director of Enrollment Management And MSCTC Counselor
- 2. Thoughts for Today… 1. How this project began… 2. Demo of system: 1. Faculty 2. Staff 3. Usage 4. Communication 3. Success Stories 4. Lessons Learned 5. What do you need to make this work at your college? 6. Questions?
- 3. How this project started… • College Retention Committee – Faculty, staff, counselors, etc. – What are we doing well – what can be improved – what should we be doing? • Two issues…same system? – No-show process – and early alert of student issues
- 4. Demo of faculty system…Log in
- 5. List of courses – all locations
- 6. Class list – updated…
- 7. Demo of staff system – log in
- 8. List of student names/alerts
- 9. Demo of usage screen…log in
- 10. List of faculty teaching course(s) at the site.
- 11. Demo of communication system – log in
- 14. Student Response… • Student responses vary… • Surface/academic issues became much more… – “Thank you for your concern. I have had a rough start to the semester starting up school again with all the obligations that come with being nearly 24.” • Success Story – a case study.
- 15. Lessons Learned… • Amazing Response! – Spring semester – 1920 submissions – 171 faculty • Now what? • Feedback is crucial… • You can’t save every student! • What about the repeat student? • IT support is critical. • Faculty concerns with privacy – how much information should I write?
- 16. What do you need to make this work? • Retention Coordinator • Faculty support – include in syllabus? • Early Alert Team • SQL Database • Web Server • REALLY Good Programmer • Patience!