C
CampusOS
Enhancement Recommendations
Document: CampusOS Enhancement Recommendation
System: Moodle Feature Set
Version: 1.0  |  Date: August 30, 2026

CampusOS Enhancement Recommendation

What the LMS Needs to Support US College Grading

Five Moodle gradebook capabilities beyond basic categories and weights — and why each one needs to be configured, not just technically available, before CampusOS is ready to sell into an accreditation-seeking US college.

The Grading Setup SOP covers categories, aggregation, and letter boundaries — enough to run a course. This document covers five additional Moodle features that most US colleges expect but that don't get set up by accident: Outcomes, Scales, grade point precision, Advanced grading methods, and Grade penalties.

Audience: CampusOS engineering (what needs to be built or configured platform-wide) and academic administrators (why each item is worth the setup time). For how a course's categories and weights actually combine into one grade, see the grade flow diagram.

Setting Up a Discussion and Grading It in Moodle

A short screen-recorded walkthrough of the actual Moodle UI: creating a graded discussion forum, choosing a grading method, and entering grades. Useful alongside the written steps here and in the companion Discussion Grading brief.

Watch on Vimeo →

Live Moodle environment available on request. UMF runs a live Moodle LMS instance. If the CampusOS team wants hands-on access to review the environment directly — not just the video — UMF can provide reviewer access upon request.

Accreditation is the sales conversation, not a formality

Most US colleges CampusOS is marketing to are themselves accountable to a regional or program accreditor, and accreditors require documented evidence that courses map to stated learning outcomes and that assessment data shows students actually met them. That evidence has to come from somewhere — and if the LMS can't tag grade items to outcomes and produce a report on them, the school has no automated way to produce it.

!

This surfaces in the first sales conversation, not later. An academic dean or accreditation liaison evaluating CampusOS will ask, directly, "can this show us outcome attainment data for a program review?" A gradebook that only does categories and weights cannot answer that question. Outcomes support is what makes it answerable.

The other four items in this document exist for a related reason: they're the specific features that let a US college's actual grading practice — standardized scales, defensible rubric-based grading, automated late-work policy — run on the platform without instructors improvising workarounds per course.

Tagging grades to learning outcomes, not just to a category

An outcome is a specific description of what a student should be able to demonstrate — rated on its own scale, separate from the numeric grade. Any activity with an outcome attached gets its own extra column in the gradebook, so a single assignment can report both a grade and how well it demonstrated a specific competency.

In Moodle's own framing, outcomes are "similar to sub components of a grade" — a course still gets one overall grade, but each activity can also carry statements about specific competencies, rated on their own scale, alongside it.

Outcomes exist at two levels: course-level outcomes defined by an instructor for one course, and standard outcomes defined once by an admin (Site administration → Grades → Outcomes) and available to every course on the tenant. Moodle also supports bulk setup natively — outcomes (and their scales) can be exported and imported as a CSV, so a program's full outcome set can be defined once and imported as standard outcomes rather than re-entered course by course.

!

Outcomes lock in once used. An outcome can't be removed from an activity once it's been graded, and its associated scale can't be changed while it's attached to any graded activity. Get the program's standard outcome set and scales right before the first course goes live — not after instructors start grading against them.

Outcomes are not the same as Moodle's "Competencies" framework. Moodle's own docs describe Competencies as "an alternative to outcomes" built around learning plans. Outcomes are the gradebook-native option, reportable per activity via the Outcomes report (Course → Grades → Outcomes report, six columns: short name, course average, site-wide flag, activities used, per-activity average, and number of grades given). For accreditation evidence tied to actual grades, Outcomes is the relevant feature — don't build against Competencies expecting gradebook data.

CampusOS action
  • Enable Outcomes site-wide during tenant setup (Site administration → Advanced features → Enable outcomes — off by default).
  • Build the program's outcome set once as a CSV (outcome name, short name, description, scale name, scale items) and import it as standard outcomes, rather than leaving instructors to define their own per course.
  • Surface the Outcomes report to academic admins, not just instructors, so it can be pulled directly as program-review evidence.

Standard scales vs. one-off scales per course

Beyond point grades, a grade item can use a scale — an ordered word list (e.g. Fail, Pass) instead of a number, usable on Forums, Glossaries, and Assignments. Administrators create standard scales available across the whole site (Site administration → Grades → Scales); teachers can create scales scoped to just their own course. Items must be entered in increasing order of value — a Fail, Pass scale is entered as Fail,Pass, not the reverse.

This is the mechanism the Grading Setup SOP's Part 1, step 3 pointed to for non-numeric outcomes like Incomplete, Withdrawal, or Audit — those need to exist as a scale, since there's no native numeric slot for them.

!

A scale doesn't map onto percentages the way you'd expect. Moodle turns an n-item scale into a 0/n–n/n range for aggregation, and Moodle's own docs warn that combining or averaging a non-numeric custom scale into a percentage is "unpredictable" — recommending the standard 100% numeric scale wherever an aggregate matters. That's a real argument for keeping an I/W/AU scale as a status flag outside the aggregated course total, rather than as a graded item that feeds into it.

CampusOS action
  • Pre-build the program's standard scales (I/W/AU, and a general Pass/Fail) as site-wide scales during tenant setup.
  • Don't let instructors create their own one-off scales per course — inconsistent scale names and orderings across a catalog make the Outcomes report and transcript exports unreliable.
  • Decide whether I/W/AU should even be a graded scale item at all, given the aggregation caveat above — a non-aggregated status field (Moodle-side or on the Gibbon side) may be the safer default.

Scale, Point, or None — and who controls the ceiling

Every activity's Grade setting is one of three types: Scale (see above), Point (a plain numeric maximum), or None (not graded). When a teacher picks Point, they set a Maximum points value for that activity — but they're capped by a site-wide ceiling: if they enter a number higher than the administrator-set maximum, Moodle shows a warning and won't let them save it. The administrator sets both that ceiling and the default point value new activities start with, at Site administration → Grades → General settings.

!

Maximum grade locks once any grade has been entered against an item. Changing the point scale of an assignment mid-term isn't a simple edit after that — fixing a wrong point total requires unlocking or recreating the item, not something to discover after a class has started submitting work.

CampusOS action
  • Set a sensible tenant-wide maximum and default point value at tenant setup — this is a platform-level ceiling, not a per-course setting, so it needs to be right before the first program is configured.
  • Warn admins at course-template creation time that Maximum Grade locks after first use — surface this in onboarding, not just in Moodle's own UI.
  • Keep the tenant's point ceiling comfortably above anything a real syllabus needs (e.g. 1000+), so instructors never hit the warning while building a category like the 100-point Final in the Points & Weighting examples.

Rubrics and marking guides, for the categories that need judgment

Moodle's advanced grading applies to Assignment and Forum activities — meaning both Assignments and Discussions (graded via Forum) can use it, not just Assignments. There are two advanced methods, on top of the default:

MethodWhat it isBest for
Simple direct gradingOne score plus optional feedback. The default when advanced grading isn't used.Quizzes, short checks — anything objective.
Marking guideA list of criteria, each worth points up to a set maximum, with optional justification text per criterion — no fixed performance levels.Assignments where feedback matters but a full rubric is overkill.
RubricCriteria × performance levels, each level worth fixed points — the most structured option.Discussions and group projects, where grading is inherently subjective and needs to be defensible.

This matters most for exactly the categories that carry the most weight and the most subjectivity in the standard model: Assignments (50–60%) and Discussions (10%). A rubric turns "why did I get an 85" into a criterion-by-criterion answer, and keeps grading consistent across sections taught by different instructors.

Reuse is already native — use it. A grading form can be saved as a shared template at the site level (gated by the moodle/grade:sharegradingforms capability, granted to managers by default), and any instructor can then start a new rubric or marking guide from that template instead of building one from scratch. Each activity still gets its own independent copy once created, so editing one course's rubric never silently changes another's.

CampusOS action
  • Grant the shared-template capability to a small "curriculum design" role, and seed the site with a starter set (discussion participation, written assignment, group project) instead of leaving every instructor to build their own.
  • Encourage rubric use specifically on Discussions and Assignments during course-template setup — the two categories most likely to draw a grade dispute without one.

A centrally-set penalty, not a per-instructor formula

Grade penalties let admins set a late-submission penalty that teachers can then apply — but only apply. Set up is admin-only:

  1. Enable the penalty plugin Toggle late-submission penalties on for the site. Site administration → Grades → Manage penalty plugins
  2. Set the penalty as a percentage E.g. entering 10 reduces a late grade by 10%. Optional rules can escalate the penalty for submissions overdue by a specified time.
  3. Choose which activities support penalties Assignment is enabled by default; other activity types can be enabled here too, depending on what penalty plugins are installed. Site administration → Grades → Manage supported activities

A teacher's only control is a Yes/No toggle on the individual assignment (Grade section → Grade penalties → Yes) — they cannot edit the penalty amount itself. A grade with a penalty applied is flagged with a red triangle icon and tooltip on the submissions page and in the grader report.

This is actually the argument in CampusOS's favor, not a limitation. Because the penalty percentage is locked to admin control (Manage grade penalty rules, manager role only by default), a school's late-work policy is enforced identically in every course — no instructor can quietly go easier or harder than the syllabus states.

CampusOS action
  • Set the tenant's standard late-penalty percentage (and any overdue-escalation rules) once, centrally, during onboarding — don't leave it as a per-course teacher decision.
  • If a school's syllabus needs the late policy applied beyond Assignments (e.g. Quizzes, Forums), confirm what other activity types have a penalty plugin available and enable them in Manage supported activities — verify this per Moodle version deployed, since activity coverage here is plugin-dependent.
  • Restrict the "Manage grade penalty rules" capability to admins only, matching Moodle's own default, so instructors can't override tenant-wide policy.

Tenant readiness for a US college sale

RequirementMoodle featureStatus
Learning outcomes mapped and reportableOutcomes + Outcomes reportNot started
Standard scales pre-built (I/W/AU, Pass/Fail)ScalesNot started
Tenant-wide point ceiling and default setGrade pointsNot started
Shared rubric & marking guide templates seededAdvanced grading methodsNot started
Late-penalty percentage set centrally, activities enabledGrade penaltiesNot started