Exam results, transcripts, and resits
After grades are published — student-facing results, transcript context, resit and reassessment sittings, attempt usage, and permanent failure.
Once staff publish grades, exam results become visible to students in their curriculum and module views, and submissions appear on the exam Published tab. Later sittings — resits after failure, or reassessment under an approval-gated workflow — are scheduled and graded on subsequent Attempt tabs. How many chances remain is governed by academic rulesets and the exam type’s attempt workflow.
This chapter is the post-release companion to grading: what students see, how offices talk about transcripts, and how to run the next sitting without overwriting Attempt 1. Deep policy: How exam attempts work.
Why it matters
Release and resit are where examination regulations become personal for students. Institutions must:
- Disclose results on a controlled timeline
- Offer resits or reassessment within documented limits
- Explain attempt usage (for example 2/3) without confusing LMS course marks
- Process permanent failure as a regulatory outcome, not only a label
- Keep transcript practice (best vs last attempt) consistent across modules
My Exams is the operational cockpit for that story after configuration is done.
How it fits
| Related area | Relationship |
|---|---|
| Publish grades | Controlled release and locking |
| How exam attempts work | Auto reattempt vs reassessment; counters; permanent failure |
| Schedule exam sittings | Date and room for Attempt 2+ |
| Handle exam requests | Reassessment approval and accommodations |
| Module grade calculation | How marks combine once required exams pass |
| Statistics and reports | Institutional exports after results exist |
Key concepts
| Term | Meaning |
|---|---|
| Published result | Grade released to the student; staff see it on the Published tab |
| Attempt usage | Indicator such as 2/3 based on the student’s effective limits |
| Resit (Wiederholungsprüfung) | Later sitting after failure — often Attempt 2 under auto reattempt |
| Reassessment period | Exam-type workflow: at most two attempts; Attempt 2 needs approval; no Attempt 3+ |
| Module completion | All required exams pass at the same term and attempt number |
| Permanent failure | Failed-attempt limit exceeded (endgültig nicht bestanden in many statutes) |
| Best vs last attempt (domain) | Which published sitting your office treats as authoritative on certificates |
What students see after publish
Students do not use My Exams. After publish, they see results in curriculum and module views. Staff verify release on the exam Published tab (for example 3/25 Results Published).
Saving a grade without publishing leaves the mark staff-only. LMS Publish all Grades does not release Exam Center results — see LMS grading.
Transcripts and certificates (domain framing)
Fuxam stores each attempt separately and publishes what staff release. Your exam office decides:
- Whether the best or last published sitting appears on the transcript
- How weighted module results are printed — see Module grade calculation
- How permanent failure is worded on official documents
Institutional statistics and smart documents may support exports and certificates; treat Exam Center published marks as the usual administrative source of truth unless your office documents otherwise.
Resit sittings under auto reattempt
When the exam type uses auto reattempt and the student is still under the ruleset’s failed-attempt ceiling:
Publish Attempt 1 results so attempt accounting and student visibility are clear.
Confirm eligibility and attempt usage on My Exams (for example 1/3 after the first consumed sitting).
Schedule Attempt 2 on that attempt tab — do not overwrite Attempt 1. See Schedule exam sittings.
Grade on Attempt 2, then publish Attempt 2 as its own coherent batch.
Students may still need exam requests for accommodations or alternative dates, but the workflow itself does not require a reassessment gate for every Attempt 2.
Reassessment-gated Attempt 2
When the exam type uses reassessment period:
| Step | Action |
|---|---|
| 1 | Publish Attempt 1 (typically fails that need a second chance) |
| 2 | Student registers / requests within term reassessment registration windows when enabled — see Exam registration and deregistration |
| 3 | Staff Approve the reassessment request |
| 4 | Schedule and grade Attempt 2 only |
| 5 | No Attempt 3+ under this workflow — even if the ruleset numeric failed cap is higher |
Worked scenarios
Scenario A — Pass on Attempt 1, module with one exam
Publish the pass. If it is the only required exam, module completion can follow for that term and attempt. Attempt usage reflects a successful path under max passed limits when relevant.
Scenario B — Fail, then resit (auto reattempt)
Attempt 1 published as fail. Usage moves toward the failed ceiling. Staff schedule Attempt 2, grade, publish. If Attempt 2 fails and the ceiling allows Attempt 3, continue on Attempt 3 — never by editing Attempt 1.
Scenario C — Multi-exam module after partial pass
Written exam passed on Attempt 1; presentation still open. Module is not complete. Coordinate the presentation sitting for the same term and attempt number before telling students the module is finished.
Scenario D — Permanent failure
Failed attempts for the module are exhausted. The student is permanently failed. Further ordinary attempt tabs are not an operational path. Exam offices typically need notification, transcript entry, counseling, and appeal processes — institutional, not a separate ruleset field. Exceptional further attempts are often modeled with a user-level ruleset assignment — see Assignment priority.
Scenario E — Grade improvement context
Under auto reattempt, students who already passed can appear on later attempts while under ruleset maximum passed attempts — relevant where regulations allow Notenverbesserung. Map your statute to that ceiling; do not invent extra Fuxam switches. See How exam attempts work.
Best practices
- Communicate release and resit windows together so students know what publish means for their next chance.
- Keep attempt history intact — never “fix” Attempt 1 by entering the resit mark there.
- Document best vs last attempt for certificates before contested cases arise.
- Use the Published tab as a checklist against enrollment counts.
- Escalate permanent failure through the exam office process immediately after it appears.
Common pitfalls
| Situation | Likely cause | What to do |
|---|---|---|
| Student cannot see a result | Grade saved but not published | Confirm Published tab |
| Resit mark on wrong tab | Graded Attempt 1 again | Use Attempt 2+ |
| Expecting Attempt 3 under reassessment period | Workflow cap | Align with exam type |
| Module still open after a pass | Sibling exam misaligned | Same term and attempt number |
| Mixed-attempt publish surprise | Confirmation warning ignored | Publish one attempt number at a time |
FAQ
Where do published results appear for students?
In curriculum and module views — not in My Exams. Staff use the Published tab.
Does Fuxam pick best or last attempt for the transcript?
Fuxam stores and publishes each attempt; your exam office decides which sitting is authoritative for certificates.
When is a reassessment request required?
When the exam type uses reassessment period, Attempt 2 needs reassessment approval. Under auto reattempt, eligible students continue under ruleset limits without that same gate.
Can I unpublish a wrong result?
Some institutions allow unpublish when no downstream module grade is locked. Ask your administrator. Prevention is the primary control.
Related pages
How exam attempts work
Full attempt lifecycle, workflows, and permanent failure.
Publish grades
Release step before results and resits.
Schedule exam sittings
Date and room for later sittings.
Module grade calculation
How marks combine once exams pass.
Handle exam requests
Reassessment and accommodation approvals.
Statistics and reports
Institutional exports after results exist.