Units in order
A unit has a title, goals, the number of lessons the plan allows for, and a note. Order is data, not sorting: arrows in the row menu move a unit, and the list holds a hundred of them.
All modules
Teaching
Course programme
The syllabus used to live in someone else's document or in the teacher's head, so a substitute had no idea where the group had stopped. Here the programme is a school record: a list of units, an assignment to a group, and a note of which unit each lesson covered.
English File Intermediate
6 Travel and transport 2 lessons
7 Reported speech Where we are 3 lessons
8 Conditionals 2 lessons
9 Writing: an email 2 lessons
Angielski B1 7/12
Course programme
What this module does
100
units in one programme
1
programme per group, and that is a decision
4
unit fields: title, goals, lessons, note
6
levels to choose from, A1 to C2
One programme per group
A group follows a single programme, and that is a decision rather than a gap: with two of them the question “where are we” would have no single answer. One programme can carry any number of groups.
The unit on a lesson
In the group's journal, next to the plan and the topic, you pick the unit the lesson covered and add a note such as “up to exercise 3”. The topic stays a topic and sits beside it.
Where we are
Each group shows the unit from its last lesson that actually took place and was not cancelled. A substitute sees exactly what the regular teacher sees, and has nobody to call about it.
Progress of every group
The programme screen lists every group that follows it: how many units are covered out of all of them, how many lessons have been held, and where the group stands now. Duplicating turns a programme into a variant for the next term.
Who sees what
A module is a permission, and which records may be touched is settled on write, not in the menu.
| Role | Sees | Changes |
|---|---|---|
| Owner | Every programme in the school and the progress of every group. | Everything. Deleting a programme belongs to them and to the methodologist alone. |
| Methodologist | The same as the owner: every programme and every group. | Everything. The syllabus is their job outright, deletion included. |
| Teacher | Programmes and progress of all groups, because a substitute has to know where the group stopped. | Creates and edits programmes and units. No deleting, and the unit on a lesson only on their own lessons. |
| Student | Nothing. The module is not theirs and cannot be granted to them. | Nothing. A programme is a tool of the school, not a plan shown to the student. |
The details nobody asks about during a demo
The things that only surface in the third week of working with the module.
What this module does not do
- lesson dates and times - when a group meets is told by the Schedule
- the lesson topic - that stays in the Journal, with the unit beside it
- materials and exercises - a unit points to no file and no section today
- grades - progress is units covered, not a student's result
In what it answers. The topic says what happened in that lesson (“Present Perfect, exercises 3-5”), the unit says which part of the programme it covered (“Unit 7”). Both sit side by side on the same lesson and neither replaces the other; the topic stays journal data and loses nothing.
Whoever teaches that lesson, by the same rule as for the topic and attendance. A teacher reads programmes and progress across the whole school, but marks the unit only on their own lessons. The owner and the methodologist can do it anywhere, so a later correction always has someone to make it.
Nothing on its own. The programme screen gives the numbers for each group: units covered out of all, lessons held, and the conclusion is drawn by a person. There is deliberately no “behind schedule” tile on the dashboard, because nobody has yet said how much delay counts as delay, and a false alarm every Monday stops being read within a month.
By duplicating. The copy goes through in one transaction, with the full set of units, and always comes out with no groups, so it cannot attach itself where the original already sits. Groups are added afterwards, and the old programme goes to the archive and frees space in the limit.
No, and this is not a backlog item. Twenty units are typed once a term, while a file format has to be maintained forever. A new unit is born as a row at the end of the list, with no dialog and no form, so the whole syllabus is one column of titles and as many Enter presses as there are units.
Coverage goes with the unit, and the gap in the order closes itself. A programme can only be deleted when no group follows it; otherwise the system refuses and says how many groups have to be detached first. The archive is the default route: a programme from two years ago stays readable and stops taking up space.
Not today. Files live in E-learning and DocHub, sets to solve live in Exercises, and a pointer from a unit to a folder or a section is separate work and a separate decision. The programme says what there is to cover and where the group stands; what to cover it with is said by those modules.
As many as the plan says: twenty on Pro and sixty on the School plan, with a negotiated number available on request. Active programmes are what counts, so an archived term frees space. Units have no limit at all: a hundred per programme is a readability boundary, not space a school buys.
See Cerium from the inside.
14 days on your groups and instalments. No card, no strings.