Content Lifecycle
Stage 01
Request & Intake
A business owner is named before anything is built. No owner, no build — this is the gate that prevents orphaned content.
Stage 02
Build & Tag
Authored against the shared taxonomy. Topic, audience, business unit, and review interval are set at creation, not retrofitted.
Stage 03
Publish & Enrol
Enrollment rules fire on role, business unit, and completion state. Prerequisites gate what comes next.
Stage 04
Review
Owner is notified at the review date. Confirm, revise, or retire — there is no fourth option and no silent default.
Stage 05
Retire & Archive
Removed from search and enrolment, retained for audit. The catalog stays small enough to trust.
Enrollment Logic
| Trigger | Rule | Result |
|---|---|---|
| Role assigned | Position in HRIS maps to a required learning plan | Learner auto-enrolled on day one; no manager request needed |
| Business unit | Unit membership adds unit-specific requirements on top of the role baseline | Local requirements without a separate catalog per unit |
| Prerequisite met | Completion of a gating path releases the next course — or an external capability | Used to gate Copilot license provisioning on governance training |
| Review date reached | Recurrence interval re-enrols the population | Annual refresh runs itself; no campaign required |
| Role change | Plan recalculates; obsolete requirements drop, new ones attach | Transfers stop carrying stale requirements between units |
Governance Model
Named Owner — Always
Ownership is a field in the system, visible to learners. Currency becomes a property of the content rather than a hope.
Review Date — Always
Set at publication. The system chases the owner; the owner does not have to remember.
One Taxonomy Across Systems
The same topic structure in the LMS and in SharePoint, so a search in either returns the same answer.
Reporting Built for the Decision
Dashboards answer “who is at risk and what expires next” — not “here is everything the platform can measure.”
Sanitized recreation. No tenant configuration, internal URLs, org structure, or employee records are represented.