Academics
Learning Outcomes and Attainment
Adopt CLOs and PLOs gradually, map evidence safely, and publish reproducible attainment reports.
Choose an adoption mode
Learning outcomes are optional. Organizations can introduce them without interrupting grading or transcripts.
| Mode | What you configure | What remains available |
|---|---|---|
| Neither CLO nor PLO | Nothing. | Courses, programs, assessments, grades, GPA, transcripts, progression, and archives continue normally. |
| CLO only | Course Learning Outcomes and optional assessment-to-CLO mappings. | CLO preview and official CLO attainment become available; PLO projection stays omitted. |
| PLO only | Program Learning Outcomes for cataloging and governance. | Program definitions are available, but quantitative PLO attainment waits until compatible CLOs and a published alignment exist. |
| CLO and PLO | Course and program outcomes, assessment mappings, a published CLO-to-PLO alignment, and an optional offering pin. | CLO attainment is calculated first; PLO attainment is projected only when the student and offering context is exact. |
No mandatory setup
Creating or grading an assessment never requires an outcome mapping. Leaving outcomes unconfigured does not block existing academic workflows.
Definitions and revisions
A CLO belongs to one course and a PLO belongs to one program. Editing an outcome creates a new revision instead of rewriting the revision already referenced by mappings, runs, or archives.
- The current revision is used for new authoring.
- Existing assessment mappings continue to reference their exact CLO revision.
- Published program alignments keep exact CLO and PLO revision references.
- Archiving an outcome hides it from normal authoring but does not delete historical evidence.
- Past Records stores the outcome text and alignment context needed to interpret an archived cycle later.
Assessment mapping and locking
- 1Create the course CLOs that describe the evidence the assessment can produce.
- 2Open the assessment and map it to zero, one, or several current CLO revisions.
- 3For quantitative attainment, give every mapping a weight and make the assessment mapping weights total 100%.
- 4Review the outcome preview before releasing grades.
- 5When the first grade is published or finalized, the assessment mapping set locks in the same transaction.
A lock is not a completeness check
An assessment with no mappings can still publish and finalize grades. If mappings exist but are unweighted or do not total 100%, they remain visible as qualitative mappings but are excluded from quantitative attainment.
Program alignment and offering pins
Safe alignment flow
Create a draft for one curriculum version
Map exact course requirement CLO revisions to PLO revisions
Complete outgoing weights where quantitative PLO projection is required
Publish the immutable alignment
Optionally pin it to a compatible program offering
- The same shared course can align differently in different programs or curriculum versions.
- Only published, compatible alignments can be pinned to an offering.
- An offering pin is optional and does not affect offering readiness.
- A pin can change only while the academic cycle is still draft and before linked grades are released.
- Without one exact student program/stage context and one pinned alignment, EduVerse does not guess a PLO projection.
Attainment formulas
| Measure | Calculation |
|---|---|
| Evidence weight | Assessment weight × CLO mapping weight ÷ 100. |
| CLO numerator | Sum of (marks obtained ÷ assessment total marks) × evidence weight for eligible evidence. |
| CLO denominator | Sum of evidence weights that contain eligible, valid grade evidence. |
| CLO attainment | CLO numerator ÷ CLO denominator × 100. |
| Coverage | CLO denominator ÷ total non-exempt weighted opportunity × 100. |
| PLO contribution | Each calculated CLO numerator, denominator, and opportunity is multiplied by its CLO-to-PLO alignment weight ÷ 100. |
| PLO attainment | Sum of weighted CLO numerators ÷ sum of weighted CLO denominators × 100. |
- Missing grades are reported as missing evidence and are not silently treated as zero.
- Exemptions are excluded from the student opportunity.
- Assessments with zero total marks are invalid quantitative evidence.
- Draft or published grades count only if the pinned policy explicitly makes that status eligible; the default official policy uses finalized grades.
- A result receives an attained/not-attained decision only when it meets the policy minimum coverage. Otherwise the decision remains undetermined.
Preview and official runs
| Capability | Preview | Official run |
|---|---|---|
| Persistence | Read-only and not saved. | Stores immutable student CLO/PLO result rows. |
| Purpose | Find missing mappings, coverage gaps, and context issues before reporting. | Create an auditable result for reporting and export. |
| Identity | Shows calculator version and current preview policy. | Pins policy version/snapshot/checksum, source cutoff/checksum, and algorithm version. |
| Repeat action | Calculates current source again. | Reuses an identical ready run; Force recalculation creates a new run that identifies the prior run it supersedes. |
- 1An Org Admin publishes the organization attainment policy.
- 2Staff review section coverage and preview diagnostics.
- 3An Org Admin, Sub Admin, or Manager creates an official run for one section.
- 4Staff open the run to review stored CLO/PLO rows and export CSV.
- 5Use Force recalculation only when a distinct new run is required for audit or correction history.
Independent from grades and transcripts
Outcome attainment never changes marks, grade status, GPA, CGPA, transcript rows, or progression decisions. It is a separate reporting layer over eligible evidence.
Roles and common diagnostics
| Role | Access |
|---|---|
| Org Admin | Organization-wide setup, policy publication, official runs, reports, and exports. |
| Sub Admin | Outcome setup and reports inside department scope; can create official runs but cannot publish organization policy. |
| Manager | Scoped reporting and official run creation inside assigned departments. |
| Teacher | Assigned-section mapping/preview and read-only official reports; cannot publish policy or create official runs. |
| Student and Guardian | No staff analytics access in this version. |
| Diagnostic | What to check |
|---|---|
| No mappings | The section assessments do not map to CLO revisions. This is allowed but produces no attainment. |
| Incomplete weights | Assessment-to-CLO or CLO-to-PLO weights are missing or do not total 100%. |
| No eligible evidence | Grades are missing or their status is not eligible under the selected policy. |
| PLO context not configured | The student enrollment has no exact program, curriculum, stage, and section requirement context. |
| Alignment not pinned | The compatible program offering does not pin a published alignment. |
| Revision mismatch | The pinned alignment references a CLO revision different from the assessment evidence. Review authoring and offering context instead of guessing. |