Lernfortschritt und Prüfungen

Learning progress and assessment

When to use

When progress, attempts, grades or completion determine learner outcomes. Inspect the actual LMS and assessment engine rather than a generic percentage-complete field.

Workflow

1. Inspect course/assessment versions, grading, event producers, retries and gradebook. Identify owners of submissions, assessment decisions, progress, completion and certificates, including any external provider and installed versions.
2. Obtain the owner's rules for required activities, passing, attempt limits, late submissions, best/latest grade, manual review, resubmission, appeals, exemptions and imported credits. Keep submitted, awaiting assessment, assessed, passed and completed distinct; pending human review is not a pass.
3. Preserve reconstructable attempts: learner, activity/question versions, answers, submission time, rubric and authorized assessor. Corrections/regrades reference prior decisions, reason and actor without replacing evidence. Do not log unnecessary answers or learner data.
4. Make progress ingestion idempotent using the source's stable event identity within the learner/course context. Persist acceptance and the state transition atomically or through the existing durable queue pattern. Replayed events must not add time twice, create extra attempts or issue duplicate certificates. Define how delayed events and explicit corrections affect the projection; arrival order alone must not overwrite newer authoritative state.
5. Evaluate completion against the learner's assigned course version and policy version. Keep completion and certificate issuance separate, with an idempotency boundary for each. A revoked or expired certificate is a lifecycle event with its own reason; it must not erase the original assessment history. Define the effect of a regrade before changing already-issued outcomes.
6. Implement accommodations as authorized, scoped policy overrides: extra time, alternate accessible format, adjusted availability or permitted attempt extensions. Keep effective dates and an audit trail without exposing medical details. Apply the override consistently to the server deadline, interface and external assessment engine; a visual timer alone is insufficient.

For requested certificates, define the output (such as a downloadable document), issuer, learner display data, stable identifier, issue date and completion/course/policy references. Open the generated artifact and check its text. Verification shows authoritative valid/expired/revoked status; regeneration and retries retain issuance identity. Minimize public verification data and authorize private downloads. Course completion does not establish accreditation.

Evidence and verification

Deliver the assessment policy decision record, state transitions and evidence for one complete learner journey. Include a manual assessment still pending, a failed attempt followed by a permitted retry, a regrade, an exempt activity and an accommodated deadline.

Test duplicate and concurrent submissions, offline events arriving after a newer state, a stale course version, an expired enrolment, unauthorized grade changes and a retry after certificate issuance. Download and inspect the certificate, verify its identifier, then check revocation without erasing assessment history. Verify keyboard and assistive-technology access to the actual question/feedback controls and timeout handling. Report unresolved provider or policy behavior explicitly rather than manufacturing a passing grade.

Boundaries

• A qualified human owns consequential assessment rules and contested assessment decisions. AI assistance may draft feedback or identify missing evidence within the authorized task; it must not silently become the final assessor.
• Time spent, a video reaching its end or a guessed engagement score does not establish mastery unless the approved policy explicitly uses that evidence for that limited purpose.
• Do not impose new identity checks, proctoring or surveillance to solve a progress bug. Work within the agreed learning and privacy requirements.

Primary references

Check the relevant release and the exact assessment specification before claiming support:

• https://moodledev.io/docs/5.0/apis/subsystems/enrol
• https://standards.1edtech.org/