Subjects, electives and streams mapped to who actually takes them.
Subjects look like the simplest thing a school system has to model, right up until senior secondary. Then a single class contains students taking different combinations, some subjects are core and some are chosen, streams diverge, and one student’s optional third language is another’s computer science. Software that assumes every student in a class sits the same papers handles the first eight years beautifully and then falls apart exactly where the stakes are highest.
- Core and optional subjects per class
- Stream handling for senior secondary
- Bulk assignment of optional subject choices
- Subject-to-teacher mapping
Core and optional subjects, per class
Subjects are defined per class and distinguished between core and optional. A class carries the subjects everyone takes and the pool of options individual students choose from. That distinction is what lets marks entry, results and marksheets be correct later: the system knows which students should have a mark for a given subject and which should not, so a blank in an optional subject is understood rather than flagged as missing data.
Streams that hold their shape at senior secondary
Senior-secondary streams are handled as part of the structure rather than as a naming convention. Science, commerce and humanities students sit within the same class year while following genuinely different subject sets, and the system follows that reality. Results, marksheets and reports read the student’s actual subject combination rather than assuming a uniform class-wide set, which is where generic tools usually require a spreadsheet to be kept alongside.
Assigning optional choices without opening every record
Optional subject choices are assigned in bulk. Collecting elective preferences from a senior-secondary cohort and recording them one student at a time is a week of office work that produces nothing but data entry; doing it as a group operation against the students who chose each option turns it into an afternoon. Choices can be revised the same way when a student changes an option early in the session.
Subjects mapped to the teachers who take them
Subject-to-teacher mapping records who teaches what, to which class. That mapping is what makes the rest of the system behave sensibly for staff — a teacher entering marks sees the subjects and classes that are actually theirs rather than the entire school’s, and the exam coordinator can see which subjects have a teacher assigned and which are still open.
About subjects & streams.
The modules this one leans on.
- Assessment
Examinations
Exam groups, patterns and assessment schemes configured once at the start of the year and reused for every term after it.
Learn more → - Results
Marks & Marksheets
Marks entry as a fast, focused grid instead of a stack of registers — and marksheets that come out of it automatically, in your school’s own chosen design.
Learn more → - People
Staff
Teaching and non-teaching staff records, with the roles and permissions that decide what each person sees when they log in.
Learn more →
See all eight modules on the platform overview.
Spend less time on administration. More on students.
Start with one class and see how the session works end to end — admissions through marksheets — before you commit to anything.
