How exam attempts work
The full exam attempt lifecycle — what an attempt is, module-level completion, passed and failed counters, auto reattempt vs reassessment period, permanent failure, and how German examination-regulation concepts map onto Fuxam policy.
An exam attempt is one formal sitting of a module’s examination requirements under a shared attempt number. Academic rulesets supply the numeric ceilings (how many times a student may pass or fail a module). Exam types supply the procedural path (automatic retry vs reassessment with approval). Together they decide who appears on which attempt tab in the Exam Center — and when a module is permanently failed.
This chapter is the conceptual companion to Configure attempt limits. Read it when you need to explain resit policy to examiners, map a Prüfungsordnung onto Fuxam settings, or reason about edge cases such as withdrawal, no-show, grade improvement, disability exceptions, and final failure.
Why it matters
German and European examination regulations treat attempts as a scarce resource. A wrong ceiling or a mismatched workflow produces the wrong attempt tabs, incorrect permanent-failure decisions, and disputes that exam offices cannot resolve from the UI alone. Understanding the lifecycle — eligibility, registration, grading, counter accrual, next attempt or closure — is what makes ruleset numbers and exam-type workflows operationally coherent.
How it fits
| Building block | Role |
|---|---|
| Academic ruleset | Numeric max passed / max failed (0–10; default 3 / 3) |
| Assignment priority | Which ruleset version applies to each student |
| Exam type | Attempt workflow: auto reattempt or reassessment period |
| My Exams | Attempt tabs and attempt-usage indicators |
| Grading | Entering and publishing outcomes on a sitting |
Key concepts
| Term | Meaning in Fuxam or in regulations |
|---|---|
| Attempt | One formal module sitting under a shared attempt number across required exams |
| Module-level limit | Caps apply across the module’s examination requirements, not as a separate counter per exam |
| Maximum passed attempts | How many times a student can successfully complete the module (default 3; range 0–10) |
| Maximum failed attempts | How many failed module attempts are allowed before permanent failure (default 3; range 0–10) |
| Auto reattempt | Exam-type workflow: eligible students can appear on later attempts while under ruleset limits |
| Reassessment period | Exam-type workflow: at most two attempts; attempt 2 needs reassessment approval; no attempt 3+ |
| Permanent failure | Student has exceeded failed attempts for the module (endgültig nicht bestanden in many statutes) |
| Effective ruleset | The winning policy bundle after user → cohort → study program resolution |
Domain vocabulary (examination regulations)
These terms appear in many German and European examination regulations. They are not separate Fuxam toggles; they describe the legal context that ruleset limits and exam-type workflows help implement.
| Concept | Typical meaning in regulations | How it relates to Fuxam |
|---|---|---|
| Wiederholungsprüfung (resit) | A later sitting after failure | Later attempt tabs under ruleset limits + exam-type workflow |
| Freiversuch (free / early attempt) | An early sitting that may not count as a failed attempt, or may allow grade improvement | Policy decision outside numeric Fuxam fields; map via procedural process and, where needed, individual assignment exceptions |
| Rücktritt (withdrawal) | Leaving an exam before it counts, within a deadline | Rulesets expose a withdrawal deadline (days before withdrawal closes); whether a withdrawal consumes an attempt is a regulatory question — see Appointment and withdrawal deadlines |
| Nichterscheinen (no-show) | Failure to appear without an accepted excuse | Often treated as a failed attempt in regulations; Fuxam’s failed-attempt counter is the ceiling that permanent failure eventually hits |
| Täuschung (cheating / misconduct) | Academic misconduct leading to failure or exclusion | Typically recorded as a failed (or specially sanctioned) outcome; see Academic misconduct |
| Nachteilsausgleich (disability compensation) | Adjusted conditions (extra time, aids, alternative format) | Does not by itself change attempt ceilings; see Disability compensation and hardship |
| Notenverbesserung (grade improvement) | Retaking a passed exam to improve the mark | Relevant to maximum passed attempts and auto reattempt — see Grade improvement |
| Endgültig nicht bestanden (final failure) | No further attempts permitted for the module or examination | Aligns with Fuxam permanent failure when the failed-attempt limit is exceeded |
What counts as an attempt
In Fuxam’s module model:
- A student becomes eligible for an attempt number according to resolved limits and the exam type’s attempt workflow.
- The student is registered or otherwise listed on that attempt tab for the relevant exams.
- The sitting is graded (or otherwise closed) in the Exam Center.
- The outcome contributes to the student’s passed or failed module-attempt economy.
- If the module is not yet complete and limits still allow it, the student may become eligible for the next attempt — or, if failed attempts are exhausted, the module is permanently failed.
Attempt state flow
The following diagram is a conceptual lifecycle. Exact registration and request steps live in My Exams and grading.
| State | Meaning |
|---|---|
| Eligible | Under ruleset limits and workflow rules, the student may sit this attempt number |
| Registered | Listed on the attempt tab / exam roster for that sitting |
| Graded | Outcome recorded for the sitting |
| Passed | Successful module attempt (toward max passed) when the module completes under the same-term / same-attempt rule |
| Failed | Unsuccessful module attempt (toward max failed) |
| NextOrDone / NextOrPermanent | Either continue to a later attempt while under limits and workflow, or stop — including permanent failure when the failed limit is exceeded |
How passed and failed counters interact with limits
On each ruleset version, under Grading configuration:
| Field | Role | Allowed values |
|---|---|---|
| Maximum passed attempts | Ceiling on successful module completions | 0–10; empty resets to 3 |
| Maximum failed attempts | Ceiling on failed module attempts before permanent failure | 0–10; empty resets to 3 |
How they work together:
- Each failed module attempt consumes budget against maximum failed attempts. When that budget is exhausted, the student is marked permanently failed for the module.
- Each successful module completion consumes budget against maximum passed attempts. Under auto reattempt, students who already passed can still appear on later attempts while under ruleset limits — which matters for policies that allow grade improvement.
- The exam-type workflow can narrow what those numbers mean in practice. Reassessment period never offers attempt 3+, even if the ruleset numeric cap is higher.
Override hierarchy (reminder)
When Fuxam calculates max attempts for an exam:
- Academic ruleset (user → cohort → study program)
- Exam type attempt workflow (auto reattempt vs reassessment period)
- Global default (3 passed / 3 failed)
Details: Configure attempt limits.
Auto reattempt vs reassessment period
| Aspect | Auto reattempt | Reassessment period |
|---|---|---|
| Typical use | Standard resit chains under numeric caps | Stricter second-chance / board-gated path |
| Later attempts | Eligible students continue while under ruleset limits | Maximum of two attempts |
| Attempt 2 | Follows normal eligibility under limits | Requires reassessment approval |
| Attempt 3+ | Possible if ruleset limits allow | Not offered |
| Passed students on later attempts | Can appear while under ruleset limits | Constrained by the two-attempt ceiling |
| Relationship to ruleset | Ruleset numbers are the outer ceiling | Ruleset numbers still apply as ceiling, but workflow blocks attempt 3+ |
Worked examples
These examples use only documented Fuxam mechanics. Institutional handling of withdrawal, no-show, or misconduct is noted where regulations usually intervene.
Example 1 — Three failed attempts allowed, pass on the third
Setup: Ruleset Maximum failed attempts = 3, Maximum passed attempts = 3. Exam type workflow = Auto reattempt.
| Sitting | Result | Failed counter | What happens next |
|---|---|---|---|
| Attempt 1 | Fail | 1 of 3 | Student remains eligible for attempt 2 |
| Attempt 2 | Fail | 2 of 3 | Student remains eligible for attempt 3 |
| Attempt 3 | Pass (all required exams pass in the same term at attempt 3) | — | Module complete; passed counter increments |
If attempt 3 had failed instead, the failed limit would be exhausted and the student would be permanently failed for the module.
Example 2 — Reassessment period with approval on attempt 2
Setup: Ruleset Maximum failed attempts = 3 (numeric ceiling). Exam type workflow = Reassessment period.
| Sitting | Result | Notes |
|---|---|---|
| Attempt 1 | Fail | First sitting under the two-attempt workflow |
| Attempt 2 | Requires reassessment approval before the student is eligible | Even though the ruleset would allow a third failure in the abstract, this workflow does not offer attempt 3+ |
| Attempt 2 graded | Pass or fail | End of the operational attempt chain for this exam type |
Example 3 — Module completion across multiple required exams
Setup: Module requires Exam A and Exam B. Limits and workflow allow attempt 1 and attempt 2.
| Scenario | Exam A | Exam B | Module complete? |
|---|---|---|---|
| Aligned pass | Pass, term Winter, attempt 1 | Pass, term Winter, attempt 1 | Yes — same term and attempt number |
| Split attempts | Pass, term Winter, attempt 1 | Pass, term Summer, attempt 2 | No — term and attempt number do not align |
| Retry both | Fail attempt 1 on both | — | Continue under limits; both must later pass together on the same term and attempt |
This is the documented Fuxam completion rule. Plan exam offerings so students can sit the full required set in one aligned window.
Example 4 — Passed limit and grade improvement context
Setup: Ruleset Maximum passed attempts = 2. Workflow = Auto reattempt. In many regulations, Notenverbesserung allows a passed student one chance to improve a grade.
Under auto reattempt, students who passed can appear on later attempts while under ruleset limits. The maximum passed attempts field is the ceiling on how many successful module completions the ruleset allows. Full mapping: Grade improvement.
Example 5 — Withdrawal within deadline vs no-show
Setup: Ruleset Withdrawal deadline = 7 (days before withdrawal closes). Student A withdraws six days before the exam; Student B does not appear and has no accepted excuse.
| Student | Typical regulatory pattern | Fuxam-relevant levers |
|---|---|---|
| A (timely Rücktritt) | Often does not consume a failed attempt | Deadline configured on the version; office applies counting rules when recording the outcome |
| B (Nichterscheinen) | Often counts as failed | Consumes failed-attempt budget toward permanent failure |
See Appointment and withdrawal deadlines.
Withdrawal, no-show, and misconduct — regulation context
Fuxam documents a withdrawal deadline on the ruleset version (days before exam withdrawal closes). How a withdrawal, no-show, or cheating case counts against the failed-attempt budget is defined by your examination regulations and exam-office process.
| Situation | Common regulatory pattern | Where Fuxam fits |
|---|---|---|
| Rücktritt within deadline | Often does not consume an attempt | Set the withdrawal deadline on the ruleset version; apply counting rules consistently when recording outcomes |
| Nichterscheinen without excuse | Often counts as failed | Consumes failed-attempt budget toward permanent failure |
| Täuschung | Failed attempt and/or further sanctions | See Academic misconduct |
| Freiversuch | Special non-counting or improvement rules | Usually handled by process and, if needed, an individual ruleset assignment |
| Nachteilsausgleich | Adjusted sitting conditions | See Disability compensation and hardship |
Permanent failure
When a student exceeds maximum failed attempts for the module, Fuxam marks them as permanently failed. In many German statutes this corresponds to endgültig nicht bestanden: no further ordinary attempts for that module (or examination).
Operational consequences to plan for:
- The student no longer appears as eligible on further attempt tabs for that module under normal limits.
- Exam offices typically need a defined process (notification, transcript entry, counseling, possible appeal) — that process is institutional, not a separate documented Fuxam ruleset field.
- If a board grants an exceptional further attempt, institutions often model the exception with a user-level ruleset assignment that carries different limits — see Assignment priority.
How limits appear day to day
- Attempt tabs (Attempt 1, Attempt 2, …) on an exam are generated from the resolved max attempts for enrolled students.
- The My Exams table shows attempt usage (for example, “2/3 attempts used”) based on the student’s effective limits.
- Day-to-day mark entry on those tabs is covered in Grade and manage an exam.
Best practices
- Write the regulation sentence next to the two numbers — for example, “two failures then final fail” → set Maximum failed attempts to match, then confirm the exam-type workflow.
- Pair every limits change with a workflow check — numeric caps and reassessment gates must tell the same story.
- Teach the same-term / same-attempt completion rule to module organizers so split passes are not mistaken for completion.
- Use versions for new regulation years — do not silently rewrite limits on a version already consuming attempt budgets.
- Sample all three assignment levels (program, cohort, user) before go-live — see Assignment priority.
- Cross-train on companion topics — grade improvement, deadlines, disability exceptions, and misconduct all hang off the same attempt economy.
Common pitfalls
| Pitfall | What goes wrong | Fix |
|---|---|---|
| Thinking limits are per exam | Staff expect three attempts on every exam file independently | Limits are module-level |
| Ignoring reassessment workflow | Ruleset allows 3 failed but attempt 3 never appears | Align exam type workflow |
| Split-term passes | Student passed all exams but module stays incomplete | Require same term and same attempt number |
| Empty limit fields | System resets to default 3 / 3 | Enter explicit values from the regulation |
| Confusing LMS grades with formal attempts | Course marks treated as resits | LMS grading does not consume CMS module attempt budgets |
FAQ
Are attempt limits per exam or per module?
Per module. A module is complete when all required exams pass at the same term and attempt number.
What values are allowed for passed and failed limits?
Between 0 and 10. Empty values reset to the default of 3 for both.
What is the difference between auto reattempt and reassessment period?
Auto reattempt lets eligible students continue onto later attempts while under ruleset limits. Reassessment period allows at most two attempts, requires reassessment approval for attempt 2, and does not offer attempt 3+.
Does a Freiversuch have its own Fuxam setting?
No dedicated Freiversuch toggle is documented. Map free-attempt or early-attempt statutes through your exam-office process, the documented limits and workflows, and individual ruleset assignments when an exception is required.
Does LMS course grading consume these attempts?
No. These limits govern formal CMS Exam Center module attempts. LMS grading is course-level and does not replace ruleset attempt accounting.
Related pages
Configure attempt limits
Set passed and failed ceilings and the override hierarchy.
Assignment priority
Which ruleset version applies to each student.
Grade improvement
Notenverbesserung and best vs last attempt.
Appointment and withdrawal deadlines
Withdrawal windows and appointment lock days.
Exam types
Attempt workflow on templates — auto reattempt vs reassessment.
My Exams
Where attempt tabs and usage indicators appear.
Grade and manage an exam
Working with attempt tabs when grading.
Edit a ruleset
Withdrawal deadline and grading configuration on a version.