Bewertungsrelevante activities

which activities benotet be should and such as sie in the Gradebook landen.

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

Quick overview

This page describes the working standard for Bewertungsrelevante activities – with a focus on concrete decisions rather than general guidance.

The main focus here is aggregationstypen and umgang with fehlenden versuchen so that teams apply the same standard.

The standard only becomes traceable through linked evidence such as gradebook-konfig 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 Bewertungsrelevante activities as a reusable Moodle standard with clear requirements for bewertungskategorien and aggregation should serve
when authors or trainers work inconsistently on aggregationstypen
when Quality assurance and approvals with gradebook-konfig should be documented in a traceable way
when Support- or course feedback points to a typical pitfall (e.g. gewichtungen are not traceable)

Less suitable when

when Bewertungsrelevante activities 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 Bewertungsrelevante activities briefly describe; from that scope and expected learning outcome derive the scope and expected learning outcome.
standard setup/configuration define, especially aggregationstypen and umgang with fehlenden versuchen.
Use test users or a reference course to check whether bewertungskategorien and aggregation work in practice.
Quality assurance/approval carry out and link evidence such as gradebook-konfig link.
After Livegang feedback auswerten and error patterns such as „Gewichtungen are not traceable“ as pitfall add.

Decision rules

Note: The general documentation rules remain central. On this Page dokumentierst du only decisions, the Bewertungsrelevante activities clearly steuern. Central guideline.

Bewertungsrelevante activities is well documented, when rules, Edge cases and Evidence so clearly are, dass teams so that without additional coordination work can.

scope & Wirkung

For Bewertungsrelevante activities first define the scope clearly: Bewertungskategorien and Aggregation.

approvalregel

decisions about aggregationstypen and umgang with fehlenden versuchen not implizit lassen, sondern roles and approvals explicitly benennen.

Exceptions cleanly halten

Allow exceptions only if they do not dilute the standard; especially relevant here are gewichtungen, skalen and sichtbarkeit.

Verifiablekeit

Verifiable is the rule only, when gradebook-konfig and beispielrechnungen cleanly verlinkt are.

What should be documented

Here only the spezifischen Inhalte about Bewertungsrelevante activities 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.

scope

terms, scope and boundaries about Bewertungsrelevante activities specify in concrete terms, including bewertungskategorien and aggregation.

Concrete Parameter/rules

Den standard so record, dass aggregationstypen and approval the notenansicht eindeutig entschieden are.

evidence

Name and link evidence directly: Gradebook-Konfig, Beispielrechnungen, Quality assurance-approval.

Versionierung

Aktive Exceptions, the latest change and the next review belong on the page—especially for topics with gewichtungen, skalen and sichtbarkeit.

Common pitfalls

This section captures real-world pitfalls from Bewertungsrelevante activities; general guidance belongs in the central guideline. Central guideline.

scope driftet: Gewichtungen are not traceable.
the rule is too abstract: Skalen mischen sich with Prozentwerten.
evidence is missing: changes wirken rückwirkend unerwartet.
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 Bewertungsrelevante activities. So remains this Page AFANDI-spezifisch and vermeidet doppelte Grundlagen.

Official references

Documentation focus

Pro benoteter activity Bewertungsskala, Feedback-Modus and Exportbedarf document.
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 Bewertungsrelevante activities – not only gegen the Wortlaut. Entscheidend is, ob standard, Exceptions and Evidence in the Alltag contribute.

Ist the Notenberechnung transparent?
Passen categories to the Prüfungsordnung?
Were Beispielrechnungen updated?
Stimmt the Konfiguration still with the review logic?

Review focus for „Bewertungsrelevante activities“: Bewertungen; check especially bewertungskategorien and aggregation.

Useful metrics

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

For „Bewertungsrelevante activities“ Kennzahlen directly an aggregationstypen and the most frequent Praxisrisiken koppeln.

Noten-Korrekturen

Subsequent Korrekturen wegen Konfigfehlern

Interval: monthly

Quality assurance-Bestandene courses

Anteil Courseprüfungen with bestandenem Gradebook-Check

Interval: monthly

review-time Gradebook

time to approval the Bewertungslogik

Interval: pro course

Next steps

Add jetzt the concrete Entscheidung about aggregationstypen incl. Verantwortlichen, Datum and Verweis on gradebook-konfig.

On „Bewertungsrelevante activities“ make especially clear as the next step: which bewertungskategorien and aggregation apply in the standard case and which exceptions are time-limited.