Academic Governance
Governance decides what and why. Operations decides when and how. Most systems only run the second one.
A committee agrees a programme requires 120 credits and launches in Fall 2025. That decision lives in a minute, a slide and someone's inbox, while the systems that must honour it keep their own copies. The Academic Governance lifecycle makes the decision itself the record: structure, portfolio, catalog, standards, policy, approvals, accreditation mapping and review, on one governed model the rest of the institution reads directly.
The problem
Software bought a registrar. Nobody bought the committee.
The decision is made properly, by the right people, and then written into a minute. From that moment the institution has two versions of itself: the one that was agreed, and the one its systems enforce.
The gap only shows when it costs something: an accreditor asks which curriculum version a graduating batch was taught under, and gets three answers. Governance was never given a system, so it was given a filing cabinet.
GOVERNANCE OR OPERATIONS
How to tell governance from operations.
Three questions settle who owns any decision. Governance sets the rule; operations runs it.
How often is it decided?
Once, or when policy changes.Every term.Who has standing to decide?
A committee, on the record.A registrar or dean, in the ordinary course of work.Definition or instance?
The rule: what a degree requires.The run: who teaches it, when.Every rule then carries a version and an effective date, so the institution can answer what an accreditor actually asks: what did we approve, who approved it, and which version was this cohort taught.
The lifecycle
One governance model, from structure to review.
Four phases. Nine stages. One shared model, so a click on any stage shows what it feeds downstream.
Capabilities in this lifecycle
Four products. One governance model.
Each is a real product with its own page. Each was built to run as part of one lifecycle, not as a standalone tool you would later try to reconcile.
Programme and course proposals with multi-stage approval, PEOs, programme and course outcomes with Bloom alignment, CO to PO mapping, curriculum plan versioning by regulation year, syllabus and delivery modes, and the catalog that downstream systems read directly.
G01–G02, G07 · AuthoritySchools, departments and reporting lines, programme portfolio with launch, suspend and retire states, degree frameworks and residency rules, enrolment capacity, and committee workflows with stages, delegation, escalation and a recorded signatory.
G05–G06 · RulesGrading schemes, outcome thresholds and assessment standards, term types and academic year structure, add and drop and withdrawal policy, grade submission deadlines, academic standing thresholds, all versioned with effective dates and bound to cohorts.
G08–G09 · AccountabilityStandards and criterion mapping per programme, evidence rules that tell delivery what to capture, review cycles and self-study preparation, institutional KPIs, and portfolio review that reads live enrolment, progression and attainment.
Intelligence in this lifecycle
Intelligence that's earned, not promised.
Data before models. Governance before automation. Assistance before autonomy.
This is the one lifecycle where a machine should never hold the pen. A programme is not launched or retired by a model, and a policy is not amended by a recommendation engine. What AI does here is remove the excuse for a badly informed decision: it reads what delivery actually produced, ranks the portfolio on real signals, finds the incoherence a human eye misses in a 42-course map, and drafts the review pack. The committee still decides, and the record still names them.
Owner: Dean of Science · council item 24/09
Portfolio signals, before the committee meets
Intake trend, progression, attainment, evaluation scores and cost per completion are read against the KPI thresholds governance set, so a viability conversation opens with the institution's own numbers rather than with whoever argues most confidently.
Incoherence in the curriculum map
An outcome no course claims, a course claiming an outcome it never assesses, a prerequisite chain that cannot be completed in the stated duration, a credit total that does not reach the degree rule: each is surfaced with the rule it breaks, while the proposal is still in review.
Standards gaps against the framework
Where a programme is mapped to NBA, ABET, AACSB or MQA criteria, unmapped criteria and thin evidence are flagged against the review cycle date, so a gap is found eighteen months out rather than in the self-study fortnight.
Committee packs drafted from live records
Proposal summaries, change comparisons between policy versions and programme review papers are assembled from the records themselves, so the committee spends its time on the judgement and not on the compilation.
Built for every role
One lifecycle. Six views of the same authority.
Sees the whole portfolio against KPIs, and takes launch and retire decisions on real progression and attainment.
Proposes a programme and watches it move through stages without chasing a single signature.
Owns course definitions and knows the catalog is what delivery will actually enforce.
Reviews coherence with the mapping and the gaps already computed, not read out from a paper.
Publishes the approved version once, and stops maintaining a private copy of the rules.
Shows what was approved, under which standard, with the version and signatory attached.
How it fits the Operating System
Governance sits above all seven other lifecycles.
It has no upstream. Every other lifecycle reads what governance approved: operations schedules the approved catalog, assessment measures the approved outcome framework, records audits the approved degree requirements, quality submits the approved standards mapping. Then delivery answers back, and the portfolio is reviewed on what actually happened.
What academic leadership says about running governance on Creatrix.
Creatrix provides an excellent platform for planning and coordinating teaching activities with a clear line of sight to learning outcomes, assessments, professional competency standards, entrustable professional activities, and graduate attributes.
A bird’s-eye view of our teaching points by course, by faculty, by program and by academic area, right on our dashboards.
Go deeper
From the Creatrix library.
Blogs, whitepapers and case studies for the people who hold the authority: provosts, deans, curriculum committees and quality officers.
Frequently asked
Plain answers about academic governance.
What is the Academic Governance lifecycle?
It decides what the institution teaches and why: organisational structure, programme portfolio, the master course catalog, learning outcomes, assessment standards and grading schemes, academic calendar policy, committee approval workflows, accreditation standards mapping, institutional KPIs and periodic review.
In Creatrix Campus this is one of the institutional lifecycles in the Academic Operating System, and it owns the definitions every other lifecycle reads.
How is this different from Academic Operations?
Governance answers what and why; Operations answers when and how. Governance decides that a BSc in Data Science exists, requires 120 credits and is approved from Fall 2025. Operations decides that in Fall 2025 it runs three sections, with named faculty, in specific rooms, at specific times.
A useful test: if it happens once or rarely and needs a committee, it is governance. If it happens every term and a registrar or scheduler decides it, it is operations.
What does the ownership boundary look like in practice?
Governance owns the master definition of a programme, course or assessment framework: code, credits, prerequisites, outcomes, lifecycle status and accreditation mapping.
Operations references those definitions to create cohorts, sections, exam schedules and grade entry. The operational instance belongs to Operations; the definition it instantiates never does.
How are approvals handled?
Every governance change is a workflow with named stages rather than a document circulated by email. A department proposes, the curriculum committee reviews, the academic council or faculty senate approves, and the registrar publishes.
Comments, revisions, delegation, escalation, status and the approving signatory are recorded, and a policy version is created on approval.
Why does policy need versioning?
Because a rule that changes silently rewrites the past. Degree requirements, grading schemes, calendar policy and academic standing thresholds are versioned with effective dates.
A cohort stays bound to the version in force when it entered, so amending a rule for next year cannot alter the requirements of a student halfway through.
How does governance see whether a programme is working?
Through a feedback loop from operations rather than an annual survey. Enrolment, progression, attainment, course evaluation and cost data flow back against the programme portfolio.
Low demand, poor progression or weak outcome attainment surface as a portfolio review item with an owner, instead of an anecdote at a committee meeting.
What does an accreditor see here?
The approval trail, the policy versions in force, the standards mapping and the review history, alongside the evidence Operations produced while delivering.
Because governance decisions are records rather than minutes, showing that a programme was approved under a stated standard is opening a page, not reconstructing a file.
How does this connect to the other lifecycles?
Academic Operations schedules against the approved catalog. Assessment & Outcomes measures against the approved outcome framework. Student Success & Records audits degrees against the approved requirements. Quality Assurance & Accreditation submits against the approved standards mapping.
Nothing downstream can teach, examine or graduate against something the council never approved.
GET STARTED
Make the decision the record, not the minute.
Tell us how a programme gets approved today, and where the version that was agreed stops matching the version that is taught.