The operating model
Every lifecycle. One institution underneath.
A lifecycle is how the work actually runs: a chain of decisions, approvals and records that crosses departments. Each one can be fixed on its own. Connected, they stop handing paper to each other, because they read the same record.
Two ways to read the same institution
A lifecycle is the work. A product is what you buy.
Committees think in lifecycles, procurement thinks in products. Both views describe the same records, which is why a purchase in one lifecycle never strands the others.
How the institution runs, end to end
Follow one chain: who proposes, who approves, what gets published, what is owed, what evidence it leaves behind. Own that chain and the seams inside it stop leaking.
- Scoped to a chain of work a committee already recognises
- Measured by cycle time and rework, not licences deployed
Every lifecycle on one record
Run them together and the handoffs disappear. A curriculum change reaches the timetable, a released result reaches the transcript and the accreditation file, an enrolment reaches the ledger.
- No re-entry between recruitment, delivery, assessment and the ledger
- Evidence produced by daily work, not assembled for a visit
Every lifecycle
Start with the chain that is costing you a term.
Filter by the phase of the institution a lifecycle belongs to. Each page shows the stages, the products that serve them and the evidence the chain leaves behind.
Student Recruitment & Enrollment
Enquiry to matriculated, with the agent network, scholarships and offer conditions inside one funnel instead of four spreadsheets.
Academic Governance
Programme and module approval, versioned by regulation year, published as the catalog every downstream system reads.
Academic Operations
Sections, timetables, rooms, faculty load and attendance: the term as it actually runs, not as it was planned.
Assessment & Outcomes
Exam cycles, moderation and grade release, with outcome attainment computed from the results themselves.
Student Success & Records
Registration, advising, intervention and the degree audit behind a transcript that still holds up years later.
Faculty Lifecycle
Recruitment, workload, appraisal, promotion and research output on one faculty record the deans can defend.
Quality Assurance & Accreditation
Standards mapped to evidence the work already produced, so a visit is a review rather than a reconstruction.
Student Financials
Fee structures, invoicing, scholarships, aid and clearance tied to the enrolment that caused them, in the campus currency.
No lifecycle is tagged to that phase yet.
Where institutions lose time
The work is in the seams between lifecycles.
Most institutions do not have a lifecycle problem, they have a handoff problem: the same fact re-entered at every border. These are the borders, and what should cross them without a human retyping it.
The last row is the one that matters most: a quality finding has to reopen governance, or the loop never closes and the same weakness is written up again three years later.
Product coverage
Which products serve which lifecycle.
Several products serve more than one lifecycle, and the platform serves them all. That overlap is the mechanism: the record is shared rather than copied.
Shared foundation
What every lifecycle stands on, whichever one you start with.
The platform is not a separate purchase. It is what makes one lifecycle worth running and the whole set worth governing together.
Platform, Data & AI
Go deeper
From the Creatrix library.
For teams deciding whether to fix one lifecycle or connect the whole operating model.
Frequently asked
Plain answers about starting with one lifecycle, or all of them.
What is a lifecycle, as you use the word?
A chain of work that crosses departments and ends in a record somebody is accountable for: a published catalog, a released result, a cleared fee account, a promotion decision. It is not a module, and it rarely maps to one office.
Do we have to adopt every lifecycle?
No. Institutions almost always start with one, usually the chain that consumed a term of rework. The other seven can stay exactly as they are, because each lifecycle owns its own records and exposes them through documented APIs.
What actually changes when two lifecycles connect?
The handoff between them stops being manual. An approved curriculum version reaches scheduling, a released result reaches the transcript and the accreditation file, an enrolment reaches the fee ledger, without anybody re-entering it.
We already have a system for one of these. Does that block us?
No. A lifecycle you are keeping stays where it is and is integrated at the seam, so the fact crosses the border once. Institutions commonly keep finance or HR and connect them rather than replacing them.
Where does the platform sit?
Underneath every lifecycle. Identity, roles, workflow, integration and the data layer come with every lifecycle, because a lifecycle without them becomes a silo by construction.
START WHERE IT HURTS
Tell us which chain is costing you a term. We will walk that one first.
A tailored proof session walks one lifecycle end to end on your programmes, your calendar and your real approval stages. Leave with a named, dated next step and an honest view of whether one lifecycle or the connected model fits this year.