Academic Settings
Programs and Student Majors
Create provider-owned programs, optionally attach Campus curriculum, relate shared institute cycles for delivery, and preserve student majors.
Programs and cycles stay independent
A program is a provider-owned educational product. In Campus it can be a department-owned qualification or major; in Discover-style contexts it can also be a course, diploma, certificate, workshop, or training product without requiring a Campus organization account. Academic cycles remain independent until a Campus Program Offering connects a curriculum to a shared cycle for actual delivery.
- One department can own many programs.
- One education provider can own many programs and offerings, whether or not it has a Campus organization account.
- One program can have many offerings across institute academic cycles.
- One academic cycle can host many programs, several stages of the same program, and standalone courses.
- The curriculum stage sequence defines progression; it is not a list of calendar periods.
- Completing or archiving a shared cycle does not pause or archive any related program.
Do not duplicate cycles
Create Fall 2026 once for the institute, then create an offering for each program and curriculum delivered in it. A cycle can exist with no program offering.
Answerbook reference and attachments
Each student grade can store an optional answerbook reference number and up to five optional answerbook files. The evidence belongs to that student grade, not to the assessment shared by the whole section.
- 1Open the student grade from the grading form.
- 2Enter the optional answerbook reference exactly as used by the institute.
- 3Save the grade so EduVerse has a stable grade record.
- 4Attach PDF scans or JPG, JPEG, PNG, or WEBP screenshots.
- 5Preview the attachment and confirm it belongs to the correct student before finalizing.
| Rule | Behavior |
|---|---|
| Reference number | Optional, per student grade, maximum 100 characters. |
| Attachments | Optional, maximum five files per grade. |
| Accepted files | PDF, JPG, JPEG, PNG, and WEBP with matching file type. |
| Finalized grade | Reference and attachments can no longer be changed. |
| Archived cycle | Files are locked and remain available only through authorized Past Records downloads. |
Who can see answerbook evidence
- Org Admin can manage evidence across the organization while the grade is writable.
- Sub Admin and Manager access follows department scope.
- Teacher access follows assigned sections.
- Students can view their own evidence only after the grade is published or finalized.
- Guardians can view released evidence only for linked students.
- Draft evidence is not exposed to students or guardians.
No direct storage links
Answerbooks use authenticated download routes. Do not share Cloudinary identifiers or treat a copied storage URL as access permission.
Create a program
- 1Create the owning department and courses. Academic cycles are not required yet.
- 2Open Programs, create the program, and choose its main department.
- 3Choose the structure, progression, and completion rules. Add duration and admissions text where useful.
- 4Add stable curriculum stages in progression order and attach required, elective, or optional courses. Cross-department courses are allowed when policy and permissions permit.
- 5Activate a complete curriculum as the admissions default, then activate the program.
- 6Enable admissions visibility only when the offering should appear to applicants.
| Program state | Meaning |
|---|---|
| Draft | Still being configured; unavailable for new student admission. |
| Active | Available for normal delivery and admission when the curriculum is complete. |
| Paused | Temporarily unavailable for new activity. |
| Teach out | Closed to new admissions while existing students finish. |
| Archived | Historical program identity retained; unavailable for new use. |
Configuration history
Changing activated program structure requires a reason and creates a new immutable configuration revision. Existing student majors keep their pinned revision, curriculum, and historical stage attempts.
Program permissions by department
| Role | Program access |
|---|---|
| Org Admin | Can create, edit, transition, and configure programs in every department. |
| Sub Admin | Can create and change programs only in departments explicitly assigned to that Sub Admin. |
| Manager and Teacher | Can read program context available through their academic scope; cannot change program structure. |
| Student | Can read the program context attached to their own academic record. |
| Guardian and Finance Manager | No program-management access. |
Moving a program
A Sub Admin needs access to both the current and destination departments. A program with student enrollment history cannot move departments.
Map cohorts and sections
Programs describe stable academic structure. Program, stage, and cohort offerings describe cycle-specific delivery. A section is standalone when it has no program mappings.
| Delivery type | Use it when | Required program context |
|---|---|---|
| Standalone | The cohort or class is not part of a defined program. | None. The institute cycle and ordinary course/section fields remain enough. |
| Program mapped | The cohort offering or class delivers part of a program curriculum. | A stage offering; sections also map to the matching stage course requirement. |
- The selected stage offering must use the same institute cycle as the cohort offering or section.
- The selected stable stage must belong to the program offering curriculum.
- The section course must match the mapped stage course requirement.
- Imports and copy-forward preserve the delivery classification instead of guessing from names.
Student major and progression
A student can have one open major program. Assigning it derives the primary department and pins the admitted configuration and curriculum. Actual stage rows are created only when the student is placed into a real stage offering.
- Assign the major during student admission or from Manage Enrollment.
- Optionally choose a stable entry stage at admission; no future cycle is pre-allocated.
- Place the student into an open stage offering and optional cohort offering when delivery is ready.
- Preview finalized grades, course requirements, elective groups, credits, attendance, and eligible next offerings before resolving a stage.
- Record advance, skip, repeat, hold, withdrawal, completion, and transfer decisions with their required reason and immutable evidence snapshot.
- Program transfer preserves the previous enrollment instead of rewriting its history.
Student program lifecycle
Institute cycle status is separate
Activating or completing an institute cycle does not automatically progress every student. Student progression is an explicit enrollment action.
Program passing and optional attendance thresholds are pinned when the student is admitted. Later program edits affect new admissions only. Sequential, credit-accumulation, flexible, and manual programs use their own evaluator, while completion can be based on final stage, requirements, credits, or an explicit manual decision.
Overrides remain auditable
When automatic evidence does not support completion or advancement, an operator must provide an override reason. The original recommendation, evidence, chosen result, actor, and override flag remain on the progression decision and in archived records.
The Progression Workbench previews all in-progress students for one stage offering, supports row-level actions and targets, and returns independent success or failure results. Apply requests use an idempotency key so a retry cannot create duplicate decisions or stage attempts.
A student academic identity always prefers the active major program, then the current cohort, then a current section. The same identity appears in student lists, profiles, transcripts, transcript PDFs, and Copilot context.
Expected graduation
The student Overview uses a recorded graduation date when available. Otherwise, month- or year-based program duration produces an estimate from the start or admission date. Cycle-based duration does not produce a speculative calendar date.
EduVerse Copilot can resolve programs and retrieve permitted program structure, curriculum stages, requirements, offerings, progression policy, duration, and a visible student major summary. Its department and relationship permissions remain identical to the normal application APIs.
Online admission offering contract
The public program-offerings endpoint returns only active, admissions-visible, structurally complete programs for an approved organization slug. It exposes an explicit applicant-safe projection with department, default curriculum, configuration revision, duration, and eligible shared entry cycles.
Applications stay separate until admission
Public applications remain review records until an authorized administrator converts an accepted submission through the normal student admission form. The organization chooses the final student login email during conversion.
Common mistakes
- Creating a separate copy of the same institute cycle for each program.
- Opening an offering before the program and admissions curriculum are ready.
- Changing curriculum structure and expecting existing students to inherit it.
- Editing a student department manually instead of assigning or transferring the major.
- Marking a mapped section as standalone to bypass a missing requirement mapping.