Higher Ed Enterprise Model Conceptual model Search
Step 1 · Shape

What the institution must answer to

“A new rule lands. What does it touch, and can we meet it?”

Some priorities are chosen; others arrive from outside. Drivers are the external forces the institution must answer to. Recording each one against the capabilities and systems it affects turns a compliance scramble into a known list of changes.

1Step 1 of 5 · Shape — context & drivers
Driver types

Six sources of outside pressure

Accreditation

Institutional and programmatic accreditors, and the evidence they ask for in self-studies and reviews.

Why it matters: Evidence lives across curriculum, assessment and reporting systems that rarely share data.

Federal regulation

Student aid, privacy, safety and accessibility rules, for example Title IV, FERPA, Title IX, Clery, GLBA and ADA web accessibility.

Why it matters: Each rule maps to specific data, processes and systems, and audits ask for proof.

State mandates

Performance funding metrics, reporting requirements, system-office directives.

Why it matters: Often tied to funding, so a weak data flow has a direct cost.

Funder terms

Grant conditions, cost-accounting rules and research-security requirements from sponsors.

Why it matters: Research administration and identity systems carry most of the load.

Market and demographics

Enrollment trends, competition, employer demand, student expectations.

Why it matters: Shapes which capabilities need investment before any rule requires it.

Technology shifts

Vendor end of support, forced SaaS migrations, licensing changes.

Why it matters: Sets deadlines the institution did not choose, often for core systems.

The trace

From a driver to the systems that must change

Sample traces for Example State University. Status shows whether today’s capabilities and systems can meet the driver.

DriverCapabilities affectedSystems involvedStatus
Web accessibility rule (public institutions)Teaching delivery, digital content, communicationsLMS, web CMS, library platform, student mobile appPartial: LMS content not yet audited
GLBA safeguards for student aid dataFinancial aid administration, information securityFinancial aid system, IAM, SISMet: reviewed annually
Research-security requirements from federal sponsorsResearch administration, identity, trainingResearch admin system, IAM, HRMPartial: training records split across two systems
State performance-funding metricsStudent progression, completion reportingSIS, reporting and analyticsPartial: metric definitions differ by college
Programmatic accreditation self-studyCurriculum management, assessment, quality assuranceCurriculum system, LMS, reportingGap: assessment evidence held in spreadsheets
Vendor end of support for on-premises HR systemWorkforce administration, payrollHRM, Finance ERP, IAMGap: no funded migration plan
Recording a driver

One record per driver

  1. 1Name and source. The rule, standard or pressure, and who imposes it.
  2. 2Owner. The person who answers for meeting it, usually a compliance or division lead.
  3. 3Capabilities affected. The HERM capabilities it touches, at level 1 or 2.
  4. 4Evidence systems. The systems that hold the data or run the process the driver asks about. These become driver_refs on each system record.
  5. 5Deadline and review cycle. When it takes effect and how often it is checked.
  6. 6Status. Met, partial or gap. A partial or gap feeds straight into levers.
Related
Institutional context →Outcomes & value →Answer audit and board questions →Policies & decision rights →