Exam Center & reporting
Overview of the Exam Center and Statistics Center — formal module assessment, attempt lifecycle, grading, academic rulesets, and institutional reporting in FuxamCMS.
The Exam Center and Statistics Center in OrgHub are where your institution runs the formal assessment lifecycle and turns exam and enrollment data into reportable evidence. Together they cover defining how exams behave, administering and grading sittings, applying academic policy through rulesets, and exporting statistics for internal decision-making and external authorities.
This is the institutional assessment layer of FuxamCMS — distinct from day-to-day course grading inside FuxamLMS. If you need transcript-relevant module results, attempt history, responsible examiners, or university-wide exports, you work here.
Why it matters
Universities must treat formal assessment as a regulated process, not only as a teaching activity. Examination regulations typically define which formats are allowed, how many times a student may attempt a module, when a resit or reassessment is available, which grade scale applies, and how results feed credit and progression. Staff need one place to schedule sittings, grade submissions, publish outcomes, handle accommodations, and produce the statistics that exam offices and quality units rely on.
Without a shared Exam Center:
- Attempt limits and grading scales drift between modules and cohorts
- Publish timing and examiner responsibility become inconsistent
- Institutional reports (enrollment, examination outcomes, progression) are hard to reconcile with course-level grade books
The Exam Center exists so policy, operations, and reporting stay aligned across modules, curricula, and study programs and cohorts.
Attempt lifecycle — start here for resits and reassessments
If your question is how a student moves from a first sitting to a resit, when attempt 2 needs approval, or how permanent failure is reached, read the dedicated attempt-lifecycle chapter first. It ties together the two policy layers that German examination offices usually separate in regulation text:
| Policy layer | What it supplies in Fuxam | Handbook |
|---|---|---|
| Exam types | Attempt workflow — auto reattempt vs reassessment period | Templates and create / edit |
| Academic rulesets | Numeric passed / failed attempt limits, grading schemas, weights, deadlines | Configure attempt limits |
How this fits into Fuxam
Formal exams sit downstream of academic structure and planning, and alongside — not inside — LMS course grading.
| Layer | Role in assessment | Handbook entry |
|---|---|---|
| Modules and curricula | Define what must be examined and which requirements attach to a version | Modules, Curricula |
| Exam types | Reusable templates for format, rating mode, duration, and attempt workflow | Exam types |
| Academic rulesets | Policy bundles for attempt limits, grading schema, weights, and deadlines | Academic rulesets |
| Attempt lifecycle | How limits and workflows combine into eligibility, tabs, and permanent failure | Attempt lifecycle |
| My Exams | Operational list of exam instances you can plan, grade, and publish | My Exams |
| Grade and manage | Detail tabs for submissions, attempts, requests, and release | Grade and manage an exam |
| Statistics Center | University-wide exports and custom reports | Statistics and reports |
| LMS grading | Course-level grades on learning-journey content blocks | Grading and analytics |
LMS grading vs the CMS Exam Center
Both areas involve assessment, but they serve different scopes:
| Dimension | LMS course grades | CMS Exam Center |
|---|---|---|
| Scope | One course offering and its learning journey | Module-linked formal exams across the institution |
| Where you work | Course → Users → Grades | OrgHub → Exam Center |
| What is graded | Gradable content blocks (hand-ins, in-journey exams, assessments) | Exam submissions with attempt tabs, exam types, and rulesets |
| Typical owner | Teachers and course editors | Exam officers, module organisers, responsible graders |
| Reporting | Course and block analytics | Statistics Center exports and custom reports |
Key concepts
| Concept | Meaning |
|---|---|
| Exam type | A reusable examination requirement template (format, rating mode, attempt workflow) attached to module versions |
| Exam instance | A concrete sitting listed in My Exams — linked to a module, type, cohort or term context, and responsible users |
| Attempt | One counted opportunity for a student to complete a module’s examination requirements. Universities often distinguish first sittings from resits (repeating after failure) and retakes (broader re-enrolment or re-assessment policies). In Fuxam, attempt tabs are generated from resolved max attempts |
| Passed vs failed attempts | Separate caps on how many successful and unsuccessful module attempts are allowed before permanent failure |
| Attempt workflow | Exam-type setting: auto reattempt (eligible students continue under ruleset limits) or reassessment period (at most two attempts; attempt 2 needs reassessment approval; no attempt 3+) |
| Grading scale / rating schema | The set of allowed marks (numeric bands, letter grades, pass/fail, participation). Formal exams inherit scale behavior from exam types and ruleset grading configuration |
| Academic ruleset | A versioned policy bundle that can override defaults for attempt limits, grading schema, grade weights, credit-point requirements, and related deadlines |
| Effective ruleset | The single ruleset resolved for a student via assignment priority (user → cohort → study program → defaults) |
| Publish | The gate between staff-entered grades and student-visible results |
| Exam request | A student-initiated assessment request (for example accommodation or alternative date), handled separately from grading |
| Statistics Center | Institutional reporting: university statistics exports and the custom report builder |
Academic regulation backdrop
Most European and German higher-education frameworks treat module assessment as governed by published examination regulations (Prüfungsordnung and related statutes). Common policy ideas you will map into Fuxam — without inventing product controls beyond what the pages below document — include:
- Attempt economy — Students have a finite number of chances; exceeding failed attempts can mean permanent failure of the module
- Resit / reassessment windows — Later attempts may require approval or a dedicated reassessment period rather than automatic reappearance
- Uniform scales — Comparable grades across programs depend on shared rating schemas and documented rounding (for example German numeric 1.0–5.0, or ECTS letter grades A–F for mobility)
- Counting rules in regulations — Some statutes count the best attempt for the transcript; others count the last. Fuxam records each attempt on its own tab; how your office interprets “the” module grade for certificates is a regulatory and reporting decision — see Attempt lifecycle and Grade and manage an exam
- Rule priority — When program, cohort, and individual exceptions conflict, a clear hierarchy decides which policy applies
Fuxam encodes these ideas primarily through exam types (attempt workflow) and academic rulesets (numeric limits, schemas, weights, deadlines). For the combined lifecycle, use Attempt lifecycle.
In this section
My Exams
Find, create, edit, grade, and publish exams, and handle assessment requests.
Exam types
Define exam types, grading scales, attempt workflows, and custom exam forms.
Academic rulesets
Configure attempt limits and assignment priority rules that override institution defaults.
Grade and manage an exam
Work through an exam’s tabs: details, pending submissions, published grades, and attempt history.
Statistics and reports
Export university-wide statistics and build, run, and share custom reports.
Roles and responsibilities
| Role | Typical focus in this area |
|---|---|
| Exam office / academic administration | Rulesets, exam types, attempt lifecycle policy, publish policy, Statistics Center exports |
| Module organiser / responsible examiner | My Exams configuration, grading, exam requests |
| Grader | Pending and attempt tabs; entering and saving marks before publish |
| Program or cohort lead | Ensuring the correct ruleset is assigned at program or cohort level |
| Teacher (LMS) | Course grades in FuxamLMS — complementary to, not a substitute for, formal Exam Center results |
| Student | Submits work, may raise exam requests, sees published grades |
Where to start
A practical setup and operations order for a new academic year:
- Confirm academic structure — Modules, curricula, and cohorts are in place. See Academic structure and Study programs and cohorts.
- Define exam types — Templates for formats and attempt workflows. See Exam types.
- Configure academic rulesets — Attempt limits, grading schema, weights, and assignments. See Academic rulesets and Configure attempt limits.
- Align the attempt lifecycle — Confirm auto reattempt vs reassessment period against your Prüfungsordnung. See Attempt lifecycle.
- Operate exams — Work from My Exams; grade and publish via Grade and manage an exam.
- Report — Run university statistics or custom reports in Statistics and reports.
Related pages
- Attempt lifecycle — how attempt limits and workflows combine
- OrgHub basics — how CMS navigation and packages fit together
- Permissions, features and visibility — what must be enabled for Exam Center and Statistics Center to appear
- LMS grading and analytics — course-level grades and how they differ from formal exams
- Modules — where examination requirements attach to academic content