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

Appointment and withdrawal deadlines

Configure exam appointment selection and withdrawal deadlines on academic rulesets — lock windows, Rücktritt context, and how deadlines relate to attempt counting.

Academic ruleset versions carry two deadline fields that shape exam logistics: the Exam appointment selection deadline (days before an alternative date becomes locked) and the Withdrawal deadline (days before exam withdrawal closes). Both live under Grading configuration on the version and apply through the student’s effective ruleset.

In German examination-regulation language, these settings support appointment / registration timing and Rücktritt (withdrawal) windows. This page explains what the fields do, how they relate to attempt counting, and how to version them safely when regulations change.

Why it matters

Examinations fail operationally when students can change appointments or withdraw at unpredictable times. Regulations usually close those windows a fixed number of days before the sitting. Encoding the windows on the ruleset:

  • Gives every program (or cohort) a documented lead time
  • Keeps examiners from arguing over informal “last minute” exceptions
  • Separates timely withdrawal from no-show, which regulations often treat differently for attempt consumption

How it fits

Deadlines are resolved with the rest of the effective ruleset — via assignment priority — and sit beside attempt limits, weights, and credit requirements on the same version. Day-to-day appointment and request handling appears in My Exams and Handle exam requests.

Key concepts

Term Meaning
Exam appointment selection deadline Days before an alternative date becomes locked
Withdrawal deadline Days before exam withdrawal closes
Rücktritt (domain) Formal withdrawal from an examination within an allowed window
Nichterscheinen (domain) No-show without accepted excuse — often counted as failed
Registration / appointment window (domain) Period when students may pick or change an exam date

Settings reference

On Settings → OrgHub → Academic Rulesets → [ruleset] → [version]Grading configuration:

Field Meaning
Exam appointment selection deadline Number of days before an alternative date becomes locked
Withdrawal deadline Number of days before exam withdrawal closes

Configure both from the regulation text (or exam-office standard operating procedure). Prefer explicit values on each active version so intakes do not silently inherit outdated windows.

Domain framing — withdrawal vs no-show

Situation Common regulatory pattern Fuxam-relevant levers
Withdrawal within the deadline Often does not consume a failed attempt Withdrawal deadline on the version; office records the outcome accordingly
Withdrawal after the deadline Often refused or treated as failed / no-show Deadline already closed; process may route through requests or sanctions
No-show without excuse Often counts as a failed attempt Consumes failed-attempt budget toward permanent failure
Medical / hardship excuse May allow non-counting withdrawal outside the normal window Institutional process; limit exceptions may use user assignments
Appointment change before lock Usually allowed while the selection window is open Exam appointment selection deadline

Worked examples

Example A — Seven-day withdrawal window

PO text: “Withdrawal is possible until seven days before the examination date.” Set Withdrawal deadline = 7 on the ruleset version. Train staff that day 6 still allows Rücktritt; day 5 does not (counting from your office’s calendar convention — document that convention locally).

Example B — Appointment lock three days before

Students may choose an alternative date until three days before the sitting. Set Exam appointment selection deadline = 3. After the lock, route genuine hardship cases through exam requests rather than silently reopening the window for everyone.

Example C — New intake, tighter windows

PO 2025 shortens withdrawal from 7 to 3 days. Create a new version, set Withdrawal deadline = 3, assign it to the new cohort, and leave older cohorts on the previous version so mid-program students keep the window they enrolled under.

Example D — Withdrawal vs attempt counter

Student withdraws five days before an exam under a 7-day deadline. The office records a timely withdrawal and — under that institution’s statute — does not increment the failed counter. Another student misses the exam without excuse; the failed counter increments toward permanent failure. Same ruleset deadline field; different recorded outcomes.

Example E — User exception for medical leave

A board allows a late withdrawal that would normally be closed. That is typically a case-file decision, not a rewrite of the program deadline. Keep the cohort ruleset unchanged; handle the exception in process (and, if attempt limits also change, via a user-level ruleset).

How to configure deadlines

Open the ruleset version under Settings → OrgHub → Academic Rulesets.

Under Grading configuration, set Exam appointment selection deadline (days before an alternative date locks).

Set Withdrawal deadline (days before withdrawal closes) from the regulation text.

Save and confirm connections so the intended students resolve to this version.

Brief examiners and study advisors on how timely withdrawal differs from no-show for attempt counting — see How exam attempts work.

Decision table — change the deadline or keep it?

Situation Prefer
Same PO, same day counts Keep fields; no new version needed for deadlines alone
PO revises the day counts New version + reassignment for affected intakes
One student needs a late withdrawal Case process / exam request — not a silent program deadline change
Continuing-education cohort needs a shorter lock Cohort ruleset assignment with different deadline values

Best practices

  • Quote the PO sentence next to the number in internal SOPs (for example “7 days before → Withdrawal deadline = 7”).
  • Version when windows change — protect students still under older intakes.
  • Separate logistics from sanctions — deadlines close windows; misconduct is a different chapter (Academic misconduct).
  • Align My Exams practice — staff who handle exam requests should know the lock and withdrawal day counts.
  • Document calendar counting — whether “7 days before” includes weekends/holidays is institutional; pick one convention and stick to it.

Common pitfalls

Pitfall Impact Fix
Changing deadlines mid-term on a live version Students lose or gain windows unexpectedly New version + validity dates
Assuming withdrawal never counts as failed Attempt budgets wrong Apply statute consistently when recording outcomes
Confusing appointment lock with withdrawal Wrong field updated Selection deadline locks alternative dates; withdrawal deadline closes Rücktritt
Ignoring priority Program deadlines ignored for cohort overrides Check assignment priority
Grading withdrawn students Invalid marks on closed sittings Follow grade submissions rules

FAQ

Where are these deadlines set?

On the academic ruleset version under Grading configuration: Exam appointment selection deadline and Withdrawal deadline. See Edit a ruleset.

Does a timely withdrawal always spare the failed attempt?

Not automatically as a universal Fuxam rule. Many regulations treat timely Rücktritt as non-counting, but your office must apply the statute when recording the outcome. The ruleset field defines the window, not the counting policy.

What happens if a student misses the exam without withdrawing?

That is typically a no-show situation. Regulations often count it as failed, which consumes failed-attempt budget toward permanent failure. See How exam attempts work.

Can deadlines differ by cohort?

Yes. Assign different ruleset versions at cohort (or user) priority so intakes can keep different day counts. See Assignment priority.

Last updated on July 20, 2026

Was this page helpful?