Completion-rules pro activity

Which Completion-Einstellungen about welchen Activitystypen passen.

Moodle AFANDI standard Handover-ready documentation reviewed on a regular cycle

Quick overview

This page describes the working standard for Completion-rules pro activity – with a focus on concrete decisions rather than general guidance.

The main focus here is which criteria verpflichtend are and automatisch vs. manuell so that teams apply the same standard.

The standard only becomes traceable through linked evidence such as completion-konfiguration and through documented edge cases/exceptions.

Practical focusTopic-specificVerifiable

When this page helps

Typical situations in which this page adds value as a working document, and where another document is more appropriate.

Typical use cases

when Completion-rules pro activity as a reusable Moodle standard with clear requirements for abschlussregeln pro activity/course should serve
when authors or trainers work inconsistently on which criteria verpflichtend are
when Quality assurance and approvals with completion-konfiguration should be documented in a traceable way
when Support- or course feedback points to a typical pitfall (e.g. regeln are technisch gesetzt, but functional not explained)

Less suitable when

when Completion-rules pro activity only about a one-off individual case without need for standardization applies
when a detailed project ticket or a technical step-by-step guide is the better fit

Recommended process

A pragmatic sequence that works in practice, from scope to review.

Briefly describe the use case and target audience for Completion-rules pro activity briefly describe; from that scope and expected learning outcome derive the scope and expected learning outcome.
standard setup/configuration define, especially which criteria verpflichtend are and automatisch vs. manuell.
Use test users or a reference course to check whether abschlussregeln pro activity/course work in practice.
Quality assurance/approval carry out and link evidence such as completion-konfiguration link.
After Livegang feedback auswerten and error patterns such as „rules are technisch gesetzt, but functional not explained“ as pitfall add.

Decision rules

Note: Gemeinsame documentation-Standards stehen in the guideline. This page keeps only fest, was for Completion-rules pro activity functional or technisch entschieden was. Central guideline.

Completion-rules pro activity is well documented, when rules, Edge cases and Evidence so clearly are, dass teams so that without additional coordination work can.

Entscheidungsrahmen

For Completion-rules pro activity first define the scope clearly: Abschlussregeln pro activity/course.

responsibility

decisions about which criteria verpflichtend are and automatisch vs. manuell not implizit lassen, sondern roles and approvals explicitly benennen.

Abweichungsregeln

Allow exceptions only if they do not dilute the standard; especially relevant here are dependencies between criteria.

review triggers

Verifiable is the rule only, when completion-konfiguration and test runs with beispielnutzern cleanly verlinkt are.

What should be documented

Here only the spezifischen Inhalte about Completion-rules pro activity maintain; general documentation rules remain in the centraln guideline. Central guideline.

The page is good when a substitute can apply or review the standard without first collecting tribal knowledge.

Kontext

terms, scope and boundaries about Completion-rules pro activity specify in concrete terms, including abschlussregeln pro activity/course.

Umsetzungsvorgaben

Den standard so record, dass which criteria verpflichtend are and when zertifikate/approvals ausgelöst be eindeutig entschieden are.

review path

Name and link evidence directly: Completion-Konfiguration, Testläufe with Beispielnutzern, Screenshots/Quality assurance-Protokolle.

Offene Punkte / Exceptions

Aktive Exceptions, the latest change and the next review belong on the page—especially for topics with dependencies between criteria.

Common pitfalls

This section captures real-world pitfalls from Completion-rules pro activity; general guidance belongs in the central guideline. Central guideline.

scope driftet: rules are technisch gesetzt, but functional not explained.
the rule is too abstract: manuelle and automatische criteria kollidieren.
evidence is missing: changes brechen ongoing courses.
the exception gets out of control: Bewertungslogik is functional not explained.

Tip: It is better to document three concrete observations from real cases than to keep a long generic list.

Moodle reference (official docs 5.1)

Kurze Verweise on the offizielle Moodle documentation for Completion-rules pro activity. So remains this Page AFANDI-spezifisch and vermeidet doppelte Grundlagen.

Official references

Documentation focus

Pro activity the Abschlusskriterien document (Ansicht, assessment, manuell) and Exceptions markieren.
UI path, role and test case record explicitly (not only the desired target state).
Mark deviations from AFANDI standards separatelyely so that updates remain easier to review.

Note: Moodle interfaces, paths, and options can vary depending on the version, theme, and enabled plugins. Therefore always include the version, role, and test context on the page.

Review & maintenance

Check this Page gegen reale processes about Completion-rules pro activity – not only gegen the Wortlaut. Entscheidend is, ob standard, Exceptions and Evidence in the Alltag contribute.

Stimmen Completion-rules with learning objective/Prozess?
Are Trigger for Zertifikate getestet?
Were ongoing courses for changes berücksichtigt?
Stimmt the Konfiguration still with the review logic?

Review focus for „Completion-rules pro activity“: activity completion; check especially abschlussregeln pro activity/course.

Useful metrics

A few metrics are enough – what matters is that they trigger decisions or improvements.

For „Completion-rules pro activity“ Kennzahlen directly an which criteria verpflichtend are and the most frequent Praxisrisiken koppeln.

Fehlkonfigurationsfälle

Tickets wegen falscher Completion-Logik

Interval: monthly

Abschlussquote je course

Anteil Lernende with korrekter Completion

Interval: monthly

Quality assurance-Abdeckung Completion

Anteil Courseänderungen with Completion-Test

Interval: monthly

Next steps

Add jetzt the concrete Entscheidung about which criteria verpflichtend are incl. Verantwortlichen, Datum and Verweis on completion-konfiguration.

On „Completion-rules pro activity“ make especially clear as the next step: which abschlussregeln pro activity/course apply in the standard case and which exceptions are time-limited.