Module groups

Group related modules for catalog organization and curricula planning — and how module groups differ from curriculum elective groups.

A module group is a named collection of related modules in your institution’s academic catalog — for example, “Core Modules,” “Quantitative Methods,” or “Language Electives Pool.” Groups help staff organize the module catalog and support curricula planning by attaching modules that belong together conceptually.

Module groups sit alongside individual modules: modules remain the units of study with versioned ECTS and exams; groups are an organizational layer on top.

Why it matters

Large institutions maintain hundreds of modules. Without groupings, catalogs and planning views become flat lists that are hard to navigate. Module groups let program offices:

• Cluster related modules (core, methods, languages, specialization pools) under a shared name and code.
• Reuse those clusters when building or reviewing curricula.
• Give planners a clearer map of which modules belong together — before deciding which are required and which are electable in a specific program.

In examination regulations and module handbooks, universities often already speak in “areas,” “pools,” or “module packages.” Module groups are the catalog counterpart to that thinking.

How it fits

Module groups vs elective groups

These names sound similar; they solve different problems:

Key concepts

What you can do with module groups

Institutions manage module groups through campus management operations (including integrations that sync academic structure). In plain terms, you can:

Create and manage module groups

Create a group

Update membership or details

Update a group when the catalog changes: rename for clarity, adjust description after a handbook revision, or attach/detach modules as offerings move in or out of the pool. Prefer updating the group over creating near-duplicate groups with overlapping membership.

Delete a group

Deleting a module group permanently removes the group record. Before deleting, confirm that curricula planning and staff workflows no longer rely on that grouping. Deleting a group does not delete the underlying modules or their versions — only the organizational grouping.

Worked example — core vs elective pool

Institution catalog

Curriculum use

1. Both groups help the program office see which catalog modules belong together.
2. In the B.A. curriculum, ECON101 and GEN100 are placed as required items (no elective group).
3. STAT110 and ECON210 are placed as optional items inside a curriculum elective group with “Select until Credit Points = 12.”
4. When Statistics moves from 5 to 6 ECTS, you version the module and update the default — the Quantitative Methods module group still points at Statistics as a catalog member, while curricula and courses pick the correct version explicitly.

Best practices

• Name groups after handbook language your faculty already uses (core, Wahlpflicht pool, methods area).
• Keep codes short and stable for reporting and integrations.
• Attach modules only after each has a sensible default version with correct ECTS.
• Do not use module groups as a substitute for elective groups when students must choose under credit or count rules.
• Review group membership when you archive modules so retired units do not remain in pools that look current.

Common pitfalls

• Confusing module groups with elective groups — one organizes the catalog; the other governs student election inside a curriculum.
• Attaching modules before setting the intended default version — membership resolves to defaults.
• Creating overlapping groups with nearly identical membership — prefer one clear pool per purpose.
• Expecting a module group to set ECTS or exams — those always live on the module version.

FAQ

Related pages