# 3. Assessment Configuration

User Type: **Super Administrator**
Source: *Mi Digital Academy - Education CRM Features Document*

---

## 3. Assessment Configuration

### 3.1 Passing Score Settings
**What it does:** Sets the passing score for an assessment: the minimum score a learner must achieve to pass. The Super Administrator configures the passing score per assessment (or per assessment type), so the pass/fail outcome is defined and applied consistently, and the learner knows the bar they must meet.

**Sub-features:**
- Passing score: the minimum score to pass the assessment
- Per-assessment setting: the passing score set for each assessment
- Default setting: a default passing score for a type of assessment
- Score basis: the passing score as a percentage or a mark threshold
- Outcome application: the pass/fail determined against the passing score
- Learner visibility: the passing score shown to the learner (where appropriate)
- Audit logging of passing score changes

**Super Administrator User Journey:**
1. For an assessment, Super Admin sets the passing score: the minimum score (a percentage or a mark threshold) to pass.
2. For a type of assessment (e.g., all quizzes), sets a default passing score, so the assessments of that type inherit it unless overridden.
3. Saves; the passing score is live, and the pass/fail outcome is determined against it.
4. A learner completes the assessment; the platform determines the outcome (pass/fail) against the passing score and records it.
5. For a learner who fails (below the passing score), the outcome is recorded as a fail, and the retake rule (if set) applies.
6. Confirms the learner visibility: the passing score is shown to the learner (where appropriate), so they know the bar before taking the assessment.
7. For a passing score that needs adjustment (too lenient or too strict, based on the results), Super Admin revises it; the change is recorded and applies to future attempts.
8. The passing score changes are audit-logged with the assessment, the score, and the timestamp.

**Rules & Edge Cases:**
- The passing score is the minimum to pass; it is set per assessment or as a default per type.
- The score basis is explicit (a percentage or a mark threshold); the pass/fail is determined against it.
- A change to the passing score applies to future attempts; a recorded outcome is not retroactively changed.
- The learner visibility is set (the passing score shown where appropriate); the bar is known.
- A fail triggers the retake rule (if set); the outcome and the retake are consistent.
- Passing score changes are audit-logged with the assessment, score, and timestamp.

### 3.2 Retake Rules
**What it does:** Defines the retake rules for an assessment: whether a learner can retake it, how many times, under what conditions (a cooldown, a prerequisite), and how the retake result is recorded (the best score, the last score). The Super Administrator configures the retake rules so the retry policy is explicit and applied consistently.

**Sub-features:**
- Retake allowance: whether a retake is permitted
- Retake limit: the maximum number of retakes
- Retake conditions: the conditions for a retake (a cooldown period, a prerequisite)
- Score recording: how the retake result is recorded (best score, last score)
- Retake tracking: a learner's retakes tracked (the count, the scores)
- Exhaustion: the behavior when the retake limit is reached
- Audit logging of retake rule changes

**Super Administrator User Journey:**
1. For an assessment, Super Admin sets the retake allowance: whether a learner who fails can retake it.
2. Sets the retake limit (the maximum number of retakes) and the conditions (a cooldown period before the next retake, a prerequisite like completing a review).
3. Sets the score recording: the retake result recorded as the best score (the highest across attempts) or the last score (the most recent).
4. Saves; the retake rules are live, and a failing learner is offered the retake per the rules.
5. A learner fails and retakes (within the limit and conditions); the retake is tracked (the count, the score), and the result is recorded per the recording rule.
6. For a learner who reaches the retake limit, the exhaustion behavior applies (no more retakes; the outcome is the recorded score, and a support path is available).
7. Reviews the retake tracking: the retakes per assessment, so the retry pattern is visible (a high retake rate signals a difficulty issue).
8. The retake rule changes are audit-logged with the assessment, the rules, and the timestamp.

**Rules & Edge Cases:**
- The retake allowance, limit, and conditions are explicit; the retry policy is defined, not ad hoc.
- The score recording rule (best or last) is set; it is applied consistently to the retake results.
- A retake is tracked (the count, the scores); the learner's retry history is visible.
- The exhaustion behavior is defined (the limit reached); it is not an ambiguous dead end.
- A high retake rate is a signal (a difficulty issue); it is reviewed, not ignored.
- Retake rule changes are audit-logged with the assessment, rules, and timestamp.

### 3.3 Adaptive Testing Configuration (Real-Time Difficulty Adjustment)
**What it does:** Configures adaptive testing: the assessment adjusts the question difficulty in real time based on the learner's responses, so the test calibrates to the learner's level (easier questions after incorrect answers, harder after correct ones). The Super Administrator enables and configures the adaptive behavior (the adjustment logic, the bounds) so the assessment is a fair, level-calibrated measure.

**Sub-features:**
- Adaptive enablement: the adaptive behavior enabled per assessment
- Adjustment logic: the difficulty adjusted in real time based on the responses
- Difficulty bounds: the minimum and maximum difficulty the test can reach
- Calibration: the test calibrates to the learner's demonstrated level
- Question selection: the next question selected per the current difficulty level
- Result interpretation: the adaptive result interpreted as a level estimate
- Audit logging of adaptive configuration changes

**Super Administrator User Journey:**
1. For an assessment, Super Admin enables the adaptive testing: the difficulty adjusts in real time based on the learner's responses.
2. Sets the adjustment logic: the difficulty increases after correct answers and decreases after incorrect ones (the calibration rule).
3. Sets the difficulty bounds: the minimum and maximum difficulty the test can reach (so it does not go below the floor or above the ceiling).
4. Saves; the adaptive assessment is live, and the question selection follows the current difficulty level.
5. A learner takes the adaptive test: the questions get harder as they answer correctly and easier as they answer incorrectly, calibrating to their level.
6. The result is interpreted as a level estimate (the learner's demonstrated level), not just a raw score; the estimate is recorded.
7. Reviews the adaptive configuration: the logic, the bounds, and the question pool per difficulty level (adequate coverage at each level).
8. The adaptive configuration changes are audit-logged with the assessment, the configuration, and the timestamp.

**Rules & Edge Cases:**
- The adaptive behavior is enabled per assessment; it is not the default for all assessments.
- The adjustment logic is explicit (the calibration rule); the difficulty moves in response to the responses.
- The difficulty bounds are set (the floor and ceiling); the test stays within them.
- The question pool must have adequate coverage at each difficulty level; a gap (no questions at a level) is a configuration problem.
- The adaptive result is a level estimate; it is interpreted as such, not a raw score.
- Adaptive configuration changes are audit-logged with the assessment, configuration, and timestamp.

### 3.4 Exam Pattern Configuration (Question Counts, Marks, Duration)
**What it does:** Defines the exam pattern: the structure of the assessment in terms of the question counts (how many questions, and per section/type), the marks (the weight of each question/section), and the duration (the time allowed). The Super Administrator configures the exam pattern so the assessment's structure is defined and consistent, and the scoring is well-defined.

**Sub-features:**
- Question counts: the number of questions, and per section/type
- Marks: the weight of each question/section (the scoring)
- Duration: the time allowed for the assessment
- Section structure: the assessment organized into sections (where applicable)
- Pattern consistency: the pattern applied consistently to the assessment
- Pattern preview: the pattern reviewed before it goes live
- Audit logging of pattern changes

**Super Administrator User Journey:**
1. For an exam, Super Admin configures the pattern: the question counts (the total, and per section/type), the marks (the weight per question/section), and the duration (the time allowed).
2. For a multi-section exam, sets the section structure: the sections, the questions per section, and the marks per section.
3. Previews the pattern: the structure reviewed (the counts, the marks, the duration) before it goes live, so the exam is as intended.
4. Saves; the pattern is live, and the exam is structured per the configuration.
5. A learner takes the exam: the questions are presented per the pattern (the sections, the counts), and the scoring is per the marks.
6. For a pattern that needs adjustment (a section too long, a mark weight off), Super Admin revises it; the change is recorded and applies to future attempts.
7. Reviews the pattern consistency: the exam's structure is as configured, and the scoring is well-defined (the total marks, the duration).
8. The pattern changes are audit-logged with the exam, the pattern, and the timestamp.

**Rules & Edge Cases:**
- The exam pattern defines the structure: the question counts, the marks, and the duration; it is explicit.
- The section structure (where applicable) is set; the sections, counts, and marks are defined.
- The pattern is previewed before going live; a structural issue is caught before the exam is taken.
- A pattern change applies to future attempts; a recorded attempt is not retroactively re-scored.
- The scoring is well-defined (the total marks, the weight per question/section); there is no ambiguity.
- Pattern changes are audit-logged with the exam, pattern, and timestamp.