Find every service a student can use, who delivers it and what it runs on, then check it against the students who need it. The map links five layers: the HERM capability a service supports, the functions it performs, the office that owns it, the service the student actually experiences, and the systems that hold its records. The journey lenses show the demand side.
Sample data: Example State University is fictional. Its offices, services, referral counts and completion rates are illustrative. To run this for real, start from the Student success and early alert play.
{{ tabIntro }}
No services match. Clear a filter to see more.
Numbers count services designed for that group at that stage. Services open to every student are listed when you click a cell but are not counted, because a general service often misses the specific barrier. Barriers come from the Journey builder.
Needs met by two or more offices. Overlap is not always waste, but students should not have to work out which door to use.
Kinds of student record kept in more than one system. Each extra copy is a place where a note or case can be missed.
{{ pop.body }}