The functions and features most commonly offered by admissions and recruitment CRM platforms (Slate, Salesforce Education Cloud, Ellucian CRM Recruit, TargetX and Element451), and the HERM business capability each one supports. The CRM covers the pre-enrollment journey from first inquiry to deposit: lead capture and the prospect record, recruiter territories, application intake and checklists, review and decision, communications and journeys, events and visits, yield and deposit, funnel reporting, and integration, security and operations. The SIS becomes the system of record once an admitted student matriculates; financial aid packaging, registration and the student account stay there and in the ERP. Test-score and transcript vendors appear only as feeds.
Shows which parts of the institution the admissions CRM supports, where it overlaps other systems, and where it stops.
A function's main HERM home vs others it touches. Features narrow to one capability.
33 HERM capabilities touched, centred on study application management, domestic student recruitment and data management. Over half the features sit in Enabling capabilities.
Wheel to explore, tree to scan every mapping, CSV or JSON to reuse it.
How this was compiled: three AI assistants (Claude, Perplexity and Grok) were each asked to identify the core functions and features of the major higher education admissions and recruitment CRM platforms. Their lists were reconciled into this single set, using the Claude draft’s structure; source letters on each feature show which drafts named it. Treat it as a starting point, not a vendor-verified specification.
{{ xwIntro }}
The full hierarchy: areas, functional areas, functions and features, each with its HERM mapping and definition. Select any HERM capability or feature to see its full definition.
Admissions is rarely one system. Here the same functions and features are mapped to the applications a fictional Example State University actually runs: a vendor core, add-on modules, third-party products, homegrown tools and spreadsheets. Each link records how well the application covers the feature and its role. HERM coverage is then calculated from those links, not mapped by hand.
Also see this ecosystem as a capability × application matrix or a HERM-to-application flow.
Inner rings: area and functional area. Outer ring: one slice per feature, split into bands when more than one application provides it. Marks outside the ring flag gaps (red) and competing systems of record (violet).
{{ fd.desc }}
The executive view. Each bar is the capability’s features, coloured by the best coverage any application gives them. Select a capability for its HERM definition, or an application to see its footprint.
{{ pop.body }}