Grade improvement
How Notenverbesserung and related improvement policies map onto maximum passed attempts, auto reattempt, and best-vs-last attempt counting in Fuxam.
Grade improvement (Notenverbesserung in many German examination regulations) is the idea that a student who has already passed may sit again to improve the mark. Fuxam does not ship a separate “Notenverbesserung” toggle. Instead, improvement policy is expressed through documented levers: Maximum passed attempts on the ruleset, the exam type’s Auto reattempt workflow (passed students can appear on later attempts while under ruleset limits), and your office’s rule for whether the best or last published attempt counts on transcripts.
This chapter connects those levers so exam offices can implement improvement statutes without inventing UI that does not exist.
Why it matters
Improvement rights are politically and legally sensitive. Students plan careers around whether a 3.0 can become a 2.0; examiners need clear attempt tabs; transcript officers need a single authoritative mark. If passed ceilings, workflows, and “best vs last” practice disagree, you get duplicate marks, disputed averages, and incorrect grade weighting inputs.
How it fits
| Building block | Role for improvement |
|---|---|
| Maximum passed attempts | Ceiling on successful module completions on the ruleset version |
| Auto reattempt | Exam-type workflow that can let passed students appear on later attempts |
| Reassessment period | At most two attempts; not the usual path for open-ended improvement chains |
| Attempt tabs | Each sitting graded separately in My Exams / grading |
| Best vs last (domain) | Office rule for which published result enters certificates and weighted averages |
Key concepts
| Term | Meaning |
|---|---|
| Notenverbesserung (domain) | Retaking a passed examination to improve the grade |
| Freiversuch (domain) | Early / free attempt that may combine with improvement or non-counting failure — no dedicated Fuxam toggle |
| Maximum passed attempts | Ruleset ceiling on successful module completions (0–10; empty resets to 3) |
| Auto reattempt | Workflow allowing eligible students (including those who passed) onto later attempts under limits |
| Best-attempt counting (domain) | Transcript keeps the better of the original and improvement marks |
| Last-attempt counting (domain) | Transcript keeps the most recent published sitting, even if worse |
Map regulation text to Fuxam levers
| Regulation idea | Typical Fuxam mapping |
|---|---|
| One improvement sitting after a pass | Maximum passed attempts at least 2; exam type Auto reattempt; office process for eligibility |
| No improvement after pass | Maximum passed attempts = 1 (or procedural refusal to place passed students on later tabs) |
| Improvement only within a time window | Process / scheduling — not a separate documented ruleset date field for improvement |
| Best mark counts | Institutional transcript rule; both attempts remain on their tabs |
| Last mark counts (risk of worsening) | Institutional transcript rule; communicate clearly to students |
| Free attempt that also allows improvement | Process + possibly a user assignment; no Freiversuch toggle |
Best vs last — decision guidance
Fuxam stores each attempt separately. Your examination regulations (or exam-office standard) must state which published result is authoritative:
| Rule | Pros | Cons | Handbook note |
|---|---|---|---|
| Best attempt | Student-friendly; common for Notenverbesserung | Requires clear selection for averages and weights | Document which tab feeds certificates |
| Last attempt | Simple “most recent wins” | Student can worsen the mark | Communicate risk before the retake |
| First attempt only (no improvement) | Simplest | Not available if statute grants improvement | Align max passed and workflow accordingly |
Worked examples
Example 1 — One improvement allowed
Setup: Ruleset Maximum passed attempts = 2. Exam type = Auto reattempt. Statute: one Notenverbesserung; best mark counts.
| Sitting | Result | Notes |
|---|---|---|
| Attempt 1 | Pass, 3.0 | Module complete under same-term / same-attempt rule |
| Attempt 2 (improvement) | Pass, 2.3 | Allowed while under max passed and auto reattempt |
| Transcript | 2.3 | Office applies best rule |
If attempt 2 had scored 3.3, a best rule would keep 3.0; a last rule would keep 3.3.
Example 2 — Improvement blocked by reassessment workflow
Setup: Ruleset max passed = 3. Exam type = Reassessment period.
Operational attempts stop at two, and attempt 2 needs reassessment approval. Do not assume open improvement chains on this exam type — raise the passed ceiling alone does not create attempt 3+. See How exam attempts work.
Example 3 — No improvement track
Setup: Certificate program, Maximum passed attempts = 1, Auto reattempt or a process that does not place passed students on later tabs. First pass closes the module for grading purposes; further sittings are not offered for mark shopping.
Example 4 — Weights after improvement
Module weight 70% / final weight 30%. The module component used in the blend must be the mark your best-vs-last rule selected. Changing the rule after grades are published creates audit pain — lock the rule before the improvement window opens. See Grade weighting.
Example 5 — Individual exception
A board grants a second improvement sitting beyond the cohort rule. Model the higher Maximum passed attempts on a user-level ruleset version, assign it at user priority, and remove it when the exception expires.
How to configure for grade improvement
Read the improvement clause in the Prüfungsordnung (how many retakes, best vs last, time limits).
On the ruleset version, set Maximum passed attempts to match the number of successful completions the statute allows.
Confirm linked exam types use Auto reattempt when passed students must appear on later attempts. Avoid expecting long improvement chains under Reassessment period.
Document the institutional best vs last rule for transcripts and weighted averages.
Spot-check attempt tabs for a passed sample student in My Exams before the improvement window.
Best practices
- Pair numbers with workflow — max passed without auto reattempt (or with reassessment-only types) will not behave like an open improvement statute.
- Publish best vs last early — students should know whether a retake can hurt them.
- Prefer new versions when improvement rights change for a new PO year.
- Do not confuse failed and passed ceilings — resits after failure use Maximum failed attempts; improvement after pass uses Maximum passed attempts.
- Keep Freiversuch in process — no dedicated Fuxam Freiversuch field is documented.
Common pitfalls
| Pitfall | What goes wrong | Fix |
|---|---|---|
| Raising max failed for improvement | Wrong ceiling — improvement is a passed story | Adjust Maximum passed attempts |
| Expecting improvement under reassessment period | Attempt 3+ never appears | Align exam-type workflow |
| No best-vs-last SOP | Transcript and weighting disagree | Document the rule before publishing |
| Editing max passed mid-term on a live version | Eligibility shifts under students who already passed | New version + validity dates |
| Treating LMS retakes as Notenverbesserung | Informal course marks enter formal policy | Formal improvement uses CMS attempt tabs |
FAQ
Is there a Notenverbesserung button in Fuxam?
No dedicated toggle is documented. Use Maximum passed attempts, the exam-type attempt workflow, attempt tabs, and your office’s best-vs-last rule.
Can passed students appear on later attempts?
Under Auto reattempt, yes — while they remain under ruleset limits. See Configure attempt limits.
Does Fuxam automatically pick the best grade?
Fuxam stores each attempt on its tab. Selecting best vs last for certificates and weighted averages is an institutional rule you apply consistently.
How does Freiversuch relate?
Freiversuch is a regulatory concept (early / free attempt). There is no dedicated Freiversuch setting; map it through process, documented limits/workflows, and user assignments when needed.
Related pages
- Configure attempt limits — passed and failed ceilings
- How exam attempts work — lifecycle and workflows
- Grade weighting — which mark enters combined grades
- Grade and manage an exam — attempt tabs and publishing
- Assignment priority — individual improvement exceptions
- Academic rulesets — section overview