Skip to content
Docs
English
Esc
navigateopen⌘Jpreview
On this page

Exams

Orient yourself in My Exams — the Exam Center cockpit for planning, grading, and publishing formal module exams under module-level attempt rules.

My Exams is the landing page of the Exam Center in OrgHub. It lists every formal exam instance you have access to based on your role — typically exams where you are a responsible examiner, or exams you can see because you hold organization-wide exam access.

An exam instance here is not a one-off quiz inside a course shell. It is the operational record of a module examination requirement for a cohort and term: who is responsible, when it is scheduled, which attempt students are on, what has been submitted, and which grades have been published. Attempt tabs and usage counters you see here are the day-to-day expression of policy configured in academic rulesets and explained in depth in How exam attempts work.

If you need the broader Exam Center context (exam types, academic rulesets, statistics), start from Exam Center and reporting.

Why it matters

Universities separate day-to-day course work from formal assessment for good reason. Module exams feed transcripts, attempt counters, credit recognition, and institutional reporting. Staff need one place to:

  • See which exams they own for the current term
  • Plan sittings and deadlines without hunting through individual courses
  • Grade and publish under attempt rules that match examination regulations
  • Handle accommodations and alternative-date requests before results go out
  • Read at a glance how many attempts a student has used (for example, 2/3)

My Exams is that operational cockpit. Without it, examiners lose track of who is on which attempt, pending submissions pile up invisibly, and grade publication becomes inconsistent across modules.

How this fits into Fuxam

My Exams sits at the center of the CMS assessment lifecycle. Configuration lives elsewhere; execution happens here.

Related area How it connects
Exam types Templates that define submission format, rating mode, duration, scheduling mode, and attempt workflow (auto reattempt vs reassessment period)
Academic rulesets Policy that sets module-level max passed and failed attempts and the effective rating schema per student
How exam attempts work How attempts are consumed, when a module completes, and how resit / reassessment map onto Fuxam tabs
Configure attempt limits Where numeric attempt ceilings are set on a ruleset version
Grade and manage an exam Conceptual tour of the same detail tabs you open from this list
Statistics and reports Institutional exports and custom reports after grades exist
Module Catalog Where students elect modules (and early or alternative exam options); elections feed enrollment into exam-bearing modules
LMS grading Course-level grades inside a learning journey — different system, different purpose (see below)

CMS exams vs LMS course grades

My Exams (CMS) LMS course grades
Scope Formal module exams across cohorts and terms Gradable content blocks inside one course
Where OrgHub → Exam Center → My Exams Course → Users → Grades
Rules Exam types, attempt tabs, academic rulesets Block setup and course grade publication
Attempt ledger Module-level passed / failed limits Not the Exam Center attempt counter
Typical owners Exam officers, module organisers, designated examiners Teachers and course editors

Use My Exams for official sittings that count toward module completion and institutional reporting. Use LMS grading for formative or course-internal marks. A module may have both; your exam office decides which record is authoritative for transcripts.

Key concepts

Term Meaning
Exam instance A concrete exam for a module, cohort, and term, listed in My Exams — derived from a module examination requirement
Exam type The reusable examination requirement template (file upload, exam, digital exam, presentation, or custom form)
Attempt A numbered sitting (Attempt 1, Attempt 2, …) generated from resolved max attempts
Module-level attempt limits Caps on how many times a student may pass or fail the module across its exams — not a separate counter per exam file
Attempt usage Indicator such as 2/3 (or 2/3 attempts used) based on the student’s effective limits
Attempt workflow Exam-type setting: auto reattempt (eligible students continue under limits) or reassessment period (at most two attempts; attempt 2 needs reassessment approval)
Module completion A module is complete when all required exams pass at the same term and attempt number
Responsible users Primary and secondary examiners assigned on the Details tab
Pending / Published Lifecycle views of submissions before and after grade release
Exam request A student-initiated ask for accommodation, alternative date, early assessment, reassessment, and similar — handled separately from grading
My access Your permission level on a row: full, grade, plan, or view

Open My Exams

Go to OrgHub → Exam Center → My Exams. The table lists exams with key information such as exam name, module, exam type, cohort, term, scheduled date, and your access level. Depending on your view and filters, you may also see attempt usage for enrolled students (for example, 2/3).

Search and filter exams

Use the toolbar to narrow the list:

  • Search — filter by exam name, module name, responsible users, curricula, or cohort.
  • Exam type — filter by submission format (file upload, exam, digital exam, presentation, or custom form).
  • Term — show only exams in selected academic terms.
  • Scheduled date — filter by scheduled date or cohort date range.
  • Status — filter by exam lifecycle status for enrolled students.
  • Attempt number — filter by attempt (1, 2, …).
  • My access — filter by your permission level on each exam (full, grade, plan, or view).

Organization-wide administrators also see a student name filter to find exams for a specific enrolled student.

Open an exam

Select an exam row to open its detail page. The detail page is organized into tabs:

Tab What you do here
Details Manage exam responsibles and per-student examiner assignments
Pending Review submissions that have been received but not yet graded
Published See submissions whose grades have been published to students
Exam Requests Handle student assessment requests (accommodations, alternative dates, reassessment, and related requests)
Attempt 1, Attempt 2, … Grade submissions, schedule dates, and manage each attempt separately

Attempt tabs are generated dynamically based on the maximum number of attempts allowed for the exam — resolved from the student’s effective academic ruleset and the exam type’s attempt workflow. For a walkthrough of the same tabs from a grading-first angle, see Grade and manage an exam.

Submission and grade states (staff view)

State Where you see it Meaning for staff
Pending Pending tab (and ungraded rows on attempt tabs) Work received; not yet graded
Graded unpublished Attempt tab after save Mark exists for staff only; students do not see it yet
Published Published tab Result released; notes and grades on that attempt typically become read-only
Request open Exam Requests tab Individual circumstances pending decision — resolve before publishing when the request would change timing or conditions

Attempt scenarios you will recognize

These worked examples use documented Fuxam mechanics. Domain terms such as resit and reassessment are framed in general examination-regulation language and connected to what you see in My Exams. For the authoritative attempt model, see How exam attempts work.

Scenario A — First sitting (Attempt 1)

A cohort sits the module’s written exam in the winter term. You open Attempt 1, set the appointment or deadline, grade on that tab, then publish. Students who pass contribute toward module completion only if every other required exam for the module also passes in the same term at the same attempt number.

Scenario B — Resit after failure (auto reattempt)

A student fails Attempt 1. Under an auto reattempt exam type, and while still under the ruleset’s failed-attempt ceiling, they become eligible for Attempt 2. My Exams may show attempt usage such as 1/3 after the first sitting is consumed, then 2/3 after the resit is used. You schedule and grade on the Attempt 2 tab — do not overwrite Attempt 1.

Scenario C — Reassessment period (approval-gated Attempt 2)

The exam type uses reassessment period: at most two attempts, and Attempt 2 requires reassessment approval (often via Exam Requests). There is no Attempt 3+. Even if the ruleset allows a higher numeric failed limit, the workflow caps the operational path at two sittings with an approval gate.

Scenario D — Multi-exam module completion

A module requires a written exam and a presentation. Both must pass in the same term at the same attempt number for the module to complete. Passing only the written exam on Attempt 1 while the presentation remains open does not close the module — examiners should coordinate attempt numbers across related exam instances. How marks combine is covered in Module grade calculation.

Scenario E — Permanent failure

When a student exceeds the ruleset’s maximum failed attempts for the module, they are marked permanently failed. Further attempt tabs are not an operational path for that student. Exam offices typically need a defined regulatory process after this outcome appears.

Roles and responsibilities

Role Typical work in My Exams
Exam officer / administrator Sees institution-wide lists, uses student-name filters, publishes grades, triages Exam Requests across modules, interprets attempt usage and permanent failure
Primary responsible Owns planning, responsibles, scheduling, and oversight for one exam instance
Secondary responsible / examiner Grades assigned students; may have limited plan access
Module organiser Often becomes a responsible via course or module planning; coordinates with examiners so related exams share coherent attempt timing
Student Does not use My Exams; submits work and sees published results through curriculum and module views, and elects modules in the Module Catalog

Where to start

A practical order for a new sitting:

  1. Confirm the exam appears after module requirements and enrollment are in place — Create an exam and Exam registration and deregistration.
  2. Assign responsibles and, if needed, per-student examiners — Edit an exam / Manage examiners.
  3. Schedule the sitting (and rooms as needed) — Schedule exam sittings.
  4. Resolve open requests before grading closes — Handle exam requests.
  5. Grade on the correct attempt tab — Grade submissions.
  6. Publish only when the set is verified — Publish grades.
  7. Plan resits and interpret module outcomes — Exam results and resits and Module grade calculation.

For policy questions (why Attempt 2 exists, how 2/3 is calculated, when a module completes), open How exam attempts work before changing operational schedules.

In this section

Last updated on July 20, 2026

Was this page helpful?