---
title: Manage course load for a planned module
description: >-
  Connect delivery courses to a planned module version, distribute cohort
  members and individual users across courses, set Access status, and save the
  load from Module planning.
sidebar:
  order: 6
---

**Course load management** is the Campus Management detail view for one planned module version in a term. Open it from [Module planning](/docs/fuxam-web/cms/programs-and-planning/module-planning) by selecting a module name in the planning table. Use it to connect delivery courses, distribute cohort members and individual users across those courses, set each course's Access status, and save the distribution so enrollments match your plan.

:::tip
Plan the module into a [term](/docs/fuxam-web/cms/academic-structure/chronology) first. Course load management is scoped to a module version and optional organization term — the same module in two terms opens as two separate load pages.
:::

## Why it matters

Module planning answers *what runs this term* and *who organizes it*. Course load management answers *which courses deliver that module* and *how students are split across those courses*. Without it, planners often create courses and enrollments by hand, so capacity, Access, and study-plan visibility drift apart.

## Before you start

| Requirement | Detail |
|---|---|
| **Planning feature** | The institution Planning package must be enabled (otherwise the page is unavailable). |
| **Permission** | You need **read:course-modules** (or equivalent module access) to open the page; saving distribution and Access changes also requires write access for the affected modules and cohorts. |
| **Module planned in a term** | Open from **Campus Management → Planning → Module planning** (or a cohort's **Module planning** tab) after the module sits in a Chronology term. |
| **Courses** | Use existing connected courses, or create new courses from the module version in this view before you distribute members. |

## Open course load management

1. Go to **Campus Management → Planning → Module planning** (institution-wide), or open a study program cohort and select the **Module planning** tab.

2. In the planning table, select the **module name** for the row you want to configure. Fuxam opens Course load management for that module version and term, and keeps your planning filters in a return link so you can go back to the same table.

3. Confirm the header shows the module name, **Members** count, source/cohort count, **Individual users** count, and the **current study period** tag when a term is attached.

## Understand the page

The page has two main tabs:

| Tab | What you do there |
|---|---|
| **Details** | Overview fields for the planning object (status, expected users, quota, tags, planning dates) plus the load canvas and sidebar sections. |
| **Connected courses** | Review courses already linked to this module version for the term. |

On **Details**, the sidebar (or sections list) typically includes:

| Section | Purpose |
|---|---|
| **Cohorts** | Cohort sources that contribute members to this planned offering. |
| **Courses** | Courses that will receive those members; create or select courses here. |
| **Individual users** | Users on the module who are not covered only by the cohort sources (shown when present). |

A flow chart visualizes how member groups connect to courses. You can open a fullscreen layout when you need more space.

## Distribute members across courses

Use this flow when one planned module should run as several parallel courses (for example, multiple seminar groups).

1. Open Course load management for the module version and term.

2. In **Courses**, select existing connected courses and/or create new courses from this module version so every parallel group has a course row.

3. Choose a **distribution method** for each cohort source. Supported methods in the product are:
    - **Split evenly** — divide members as evenly as possible across the selected courses.
    - **Split every** — place a fixed number of members into each course (you set the count).
    - **Split cohorts** — keep cohort membership aligned when splitting across courses.
    - **Pass all** — send all members of the source into the selected courses without splitting by count.

4. For each course, set **Access** (course connection status). Behavior from the product:
    - **NO_ACCESS** — hidden; no course-layer access granted.
    - **ORGANIZERS_ONLY** — only assigned organizers receive course access.
    - **BOOKABLE** — appears in course booking; students gain access when they book.
    - **FULL_ACCESS** — students receive course access automatically.

5. Review the flow chart and member counts so the total matches the header **Members** figure.

6. Select **Save** (and **Reset** if you need to discard unsaved sidebar changes). Saving runs a progress operation that writes the distribution and refreshes the module planning row's connected courses.

:::warning
Statuses that grant organizer access require organizers to have roles on the course. If Access needs organizer roles and they are missing, Fuxam blocks the status change with an error toast — assign organizers/roles first (see [Assign a module organizer](/docs/fuxam-web/cms/programs-and-planning/assign-a-module-organizer)).
:::

## Adjust overview settings

On the **Details** tab you can update planning-object overview fields when you have edit permission:

| Field | Use |
|---|---|
| **Status** | Planning lifecycle: not planned, in planning, planned, or archived. |
| **Expected users** | Planned headcount for capacity and monitoring context. |
| **Quota** | Percentage when user quotas are enabled for the institution. |
| **Tags** | Module tags associated with this planning object. |
| **Planning dates** | Allowed date selection for the offering. |

Save overview changes together with your course distribution when you finish the pass.

## Best practices

- **Finish module placement and organizers before heavy distribution** — Access modes like organizers-only depend on who is attached.
- **Prefer one clear distribution method per cohort** — mixing ad-hoc enrollments outside this view makes the flow chart and monitoring harder to trust.
- **Create the parallel courses here** when they do not exist yet, so connections stay tied to the module version and term.
- **Return via the planning link** after saving so filters and term grouping stay intact.

## Common pitfalls

| Symptom | Likely cause | What to try |
|---|---|---|
| Page not found / unavailable | Planning feature off, or missing module read permission | Enable Planning; check [roles and permissions](/docs/fuxam-web/base/user-management/roles-and-permissions) |
| No useful term in the header | Module not placed in a Chronology term | Assign a term in [Module planning](/docs/fuxam-web/cms/programs-and-planning/module-planning) |
| Cannot set Access that needs organizers | Organizers lack course roles | Assign organizers/roles, then retry Access |
| Save fails mid-progress | Validation or permission error on distribute | Read the error toast; confirm cohort write access and course connections |
| Member totals look wrong after save | Stale planning table | Re-open Module planning (the save marks the table for refresh) |

## FAQ

**Is this the same as Course planning?**

No. **Course load management** is the per-module detail you open from a Module planning row to connect courses and distribute members. Institution **Planning** tabs focus on Module planning, Monitoring (when quotas are on), and SmartPlan. Older Course planning routes may still exist in the product, but this guide covers the load view linked from Module planning.

**Do I need a cohort?**

Cohort sources appear when the planned offering has cohort membership. Individual users can still show when people are attached outside those sources. Continuing-education or non-cohort setups may lean more on individual users and selected courses.

**Does saving enroll students immediately?**

Saving the distribution writes course connections and membership according to your Access settings and distribution method. Modes like **BOOKABLE** still require students to book; **FULL_ACCESS** grants course access as part of the enrollment update path.

## Related pages

**[Module planning](/docs/fuxam-web/cms/programs-and-planning/module-planning)**

Place modules into terms before opening course load.

**[Assign a module organizer](/docs/fuxam-web/cms/programs-and-planning/assign-a-module-organizer)**

Staff attachment required for organizers-only Access.

**[Planning monitoring](/docs/fuxam-web/cms/programs-and-planning/planning-monitoring)**

Check quotas after you set expected users and load.

**[Course management](/docs/fuxam-web/cms/courses-management)**

Institution course catalog and enrollments.

**[Link module to course](/docs/fuxam-web/cms/academic-structure/modules/link-module-to-course)**

How module versions connect to delivery courses.

**[Chronology](/docs/fuxam-web/cms/academic-structure/chronology)**

Terms that scope each course load page.