Application domains
The eight pillars cover what to build, and the Strategic Compass covers how to choose. The four domains show where AI applies across a campus. They are defined by what the work does and who it serves, not by reporting lines, so they hold up at any institution.
Teaching, Learning & Student Success
Supports every learner, credit and non-credit, from first inquiry through completion and career transition.
Teaching & Learning
Faculty-governed; raises pedagogy and academic integrity questions.Enrollment & Academic Records
AI informs high-stakes decisions about individuals; heavily regulated.Student Experience & Success
Holistic support; sensitive health and personal data.Research & Innovation
Creates, protects, and transfers new knowledge.
Operations & Infrastructure
Runs and safeguards the institution; the home for anything that fits nowhere else.
Advancement & Public Service
Builds external relationships and delivers public benefit.
Clinical Care & Health Services Optional
Patient care and clinical services under health-system governance. Use it only where a campus operates a health system; otherwise it is out of scope.
Medical education stays in Teaching, Learning & Student Success, and clinical research stays in Research & Innovation.
Community engagement is a view, not a domain
In higher education, community engagement means reciprocal, mutually beneficial partnership between an institution and its communities, rooted in teaching and research (the Carnegie test). Service learning and community-engaged research keep their academic home and carry community engagement as a cross-cutting tag. Fundraising, alumni relations, and marketing sit in Advancement & Public Service.
Placement rules
- Function, not reporting lines. Domains are defined by what the work does and who it serves.
- Test by who benefits, in order. A learner's progress goes to Teaching, Learning & Student Success; new knowledge goes to Research & Innovation; an external party or public benefit goes to Advancement & Public Service; everything else goes to Operations & Infrastructure.
- Classify by direct outcome. Recruitment campaigns serve enrollment, gift requests serve advancement, and student account collections serve finance.
- Place capabilities, never offices. One office can work in several domains.
- One primary domain per capability. Secondary tags support search and shared work but never count in rollups. Count each initiative and its spend once.
- Keep the HERM reference. Record the HERM code, version, and parent for every capability (current release v3.2.0).
- Record each platform once. Link each use of a platform to its own outcome and risk review.
- Tag every use case. Give it a risk tier and name the people affected: applicant, student, employee, research subject, patient, or public.
- Community engagement is a cross-cutting view. It is determined by Carnegie's test of reciprocal, mutually beneficial partnership, not by a domain.
Edge cases
Reading the domains as a leader
- Roll up by sub-portfolio as well as by domain, so a large student domain does not hide where investment and risk actually sit.
- Expect offices to span domains. That is by design: capabilities are placed, not offices.
- Pair domain views with risk views. A domain shows where value is expected; the risk tier shows where review and monitoring are needed.
Capability blueprint adapted from the Campus AI Framework, Domains & Capabilities by Joe Sabado, designed to apply across community colleges, regional publics, private colleges, R1s, and minority-serving institutions.