Modules & competencies

A module is a building block that can stand in several plans — and stays the same module everywhere, not a copy.

Where to find it: Menu → Plans, select a plan, then tap an entry of kind "Module" in the outline. "Module requirement" then appears below the outline.
How to use it: There you enter the grade levels the module is meant for, and read the competencies it offers.
What it does for you: Because the module is shared, a change here reaches every plan that uses it — the screen says so above the fields.

A module belongs to no single plan

Modules arrive from a package that ships with the app. There is no management screen where you create, rename, or delete a module yourself — which is why its fields hang on the plan, where the module is visible anyway.
A module's title and description cannot be changed here; they come from the package.
"Grade level from" and "Grade level to" form a span. Both ends belong to it; one end alone is not saved, and the lower level must not sit above the upper one.
A span has no gaps: "7 to 9" can be said, "7 and 9 but not 8" cannot.
Change the span and you change it in every plan that uses this module. If something is refused, everything stays as it was.

The competencies offered show what a module can cover. Today they can be read but not edited: Mapidu does not yet keep a competency framework, so a competency appears by its identifier alone and carries no name. Nothing can be entered here.
If a module offers nothing, it reads "This module does not offer a competency yet."
Competency coverage sits in the plan overview, as a pair of numbers: covered out of demanded.
Which competencies a plan demands is likewise not entered on any screen today. On a plan you created yourself it therefore reads "no demand recorded"; while the value is not in yet, "not read yet".
Competency coverage is information. It holds nothing up — neither saving nor rolling out depends on it.