Higher Ed Enterprise Model Conceptual model Search
Core systems / Admissions CRM functions & features

Admissions and recruitment CRM functions & features

Features of admissions and recruitment CRMs (Slate, Salesforce Education Cloud, Ellucian CRM Recruit, TargetX, Element451), mapped to HERM capabilities. The CRM runs recruitment from first inquiry to deposit: prospects, territories, applications, review and decisions, communications, events and yield. Once a student matriculates, the SIS becomes the system of record; aid, registration and student accounts stay in the SIS and ERP.

Why map to HERM

Shows which parts of the institution the admissions CRM supports, where it overlaps other systems, and where it stops.

Falls within vs related to

A function's main HERM home vs others it touches. Features narrow to one capability.

What it shows

33 HERM capabilities touched, centred on study application management, domestic student recruitment and data management. Over half the features sit in Enabling capabilities.

Three ways in

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) drafted lists, reconciled into one set; source letters show which drafts named each feature. A starting point, not a vendor-verified specification.

Download Excel Download ArchiMate
{{ wheel }}
Crosswalk to HERM v3.2.0

Which HERM capability each function supports

Browse the HERM Business Reference Model →

{{ xwIntro }}

CRM function
Falls within (HERM)
Also related to
{{ row.label }}
{{ row.relNote }}

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.

CRM hierarchy
HERM capability
Definition
{{ tr.hermNote }}
{{ tr.def }}

Admissions is rarely one system. Here the features are mapped to the applications fictional Example State University runs, from vendor core to spreadsheets. Each link records coverage and role; HERM coverage is calculated from the links.

Also see this ecosystem as a capability × application matrix or a HERM-to-application flow.

1 · HERM capabilityWhat the institution does. Stable, vendor-neutral.
2 · Function and featureWhat software can do. The reference list on this page.
3 · ApplicationWhat you run, with coverage and role per feature.
{{ ek.l }}
{{ ecoWheel }}

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).

What the links reveal

Conflicts, gaps and workarounds

{{ fd.n }}{{ fd.title }}

{{ fd.desc }}

Calculated HERM coverage

How well each HERM capability is served

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.

HERM capability
Feature coverage
Applications (system of record first)
{{ er.summary }}
{{ pop.kicker }}

{{ pop.title }}

{{ pop.path }}

{{ pop.body }}

{{ pop.listLabel }}
{{ li.label }}