Higher Ed Enterprise Model Conceptual model Search
Step 2 · Run · Business layer

The rules that govern the work, and who decides

“Why can’t we just change this?”

Most change is blocked or enabled by a rule or a person, not a system. This page adds two things to the business layer: an inventory of policies linked to the work they govern, and decision rights that say who must agree before anything changes.

2Step 2 of 5 · Run — business layer
Policy inventory

Each policy, linked to the work it governs

A policy record names the processes, data and systems it applies to, so a policy change shows what it touches, and a process change shows which rules stand in the way. Sample records for Example State University:

PolicyGovernsOwnerReview
Data classificationAll data topics; every system’s classification fieldCIO with the data governance councilAnnual
Records retentionStudent, HR and finance records; archive and deletion jobsUniversity records managerEvery 3 years
Acceptable use of technologyIdentity and access, all user-facing systemsCIOEvery 2 years
Course withdrawal and late dropEnrolment and registration process; SIS rulesAcademic senate with the registrarEvery 3 years
Procurement thresholdsPurchasing process; Finance ERP approval workflowsCFOAnnual
Electronic signaturesForms and approval workflows across unitsGeneral counselEvery 3 years

On each system record, policy_refs lists the policies that apply. Read the other way, it is the list of systems a policy change would touch.

Decision rights

Who decides, who must agree, who is consulted

Decision rights are recorded per kind of change, not per system. The decision_owner on a system record points to the row that applies.

Kind of changeDecidesMust agreeConsultedInformed
Replace a core systemCabinet, on the CIO’s recommendationCFO; owning vice presidentAcademic senate; affected units; IT architecture reviewCampus community
Change a shared data definitionData governance councilData owner for the topicData stewards; institutional researchSystem owners
Change an academic policyAcademic senateProvostRegistrar; student affairsStudents and advisors
Retire a serviceOwning vice presidentCIO if technology is involvedService users; help deskCampus community
Adopt an AI agent that acts on recordsAI governance groupData owner; system ownerSecurity; legal; affected staffUsers of the process
Where change gets stuck

Four patterns to look for

No owner

A policy nobody reviews, or a decision with no named decider. Changes stall waiting for someone to say yes.

Too many vetoes

Every unit must agree, so the default answer is no.

Rule outlives its reason

A policy written for a paper process now forces a workaround in a digital one.

Hidden rule

A practice everyone follows that is not written anywhere, so it cannot be changed on purpose.

Each pattern points to a lever: change the policy, or reorganize who decides. See levers.

Related
Org units & services →Process architecture →Data governance (DAMA) →COBIT IT governance →Levers →