“The timetable takes three weeks every August, and marks arrive by e-mail.” The Director of Studies’ year, on the screens that do the work — starting with the templates everything is built on.
A division holds its curriculum tracks, a track holds its stages, and every year level has one Curriculum Template — the subjects a cohort is built from. Pick a division and the templates re-render in that curriculum’s own subjects.
© 2026 Commun. All rights reserved.
Mirrors: School Admin → Divisions → Curriculum Tracks · Curriculum Templates · the product’s own chain, Division ▸ Track ▸ Stage → Curriculum Template → Cohort
Secondary (Cambridge) reads Year 7 to Year 11 through Lower Secondary and IGCSE. Pick the National stream and the same matrix reads Bahasa Melayu, Matematik, Sains and Sejarah, Tingkatan 1 to 5. Nothing is translated into a house style: a Head of Year recognises her own year group on the screen.
The template says what each year level studies and which subjects are compulsory. A cohort is created from it, so a family joins a year rather than being added to a dozen classes by hand — and the timetable below is built from those classes.
The product’s own chain: Division ▸ Track ▸ Stage → Curriculum Template → Cohort
Set the rules — how many periods a teacher may take in a day, in a week, in a row — and Generate. The solver places every lesson against your bell schedule while you watch, and lands on a proposal with its seed and score. Tighten a rule too far and it refuses, naming the step to fix.
Each is a hard guarantee — the generator refuses any timetable that would break one. Leave a field blank for no limit. Lessons a teacher already holds in other confirmed timetables (e.g. the other bell schedule) count toward every cap.
A teacher never teaches more than N periods on any one day. A double counts as 2.
Weekly workload ceiling — e.g. 30 keeps every teacher at or under 30 teaching periods a week, support duties included.
A teacher never teaches more than N periods in a row — a break slot or a free period must follow.
Fetch the solver snapshot, run in a background worker, and review the proposal.
© 2026 Commun. All rights reserved.
Mirrors: School Admin → Auto Timetable → Rules · Generate · the proposal · a real run replayed as code — the placements, the seed, the score and the refusal are the engine’s own
A rule is a guarantee. When the search cannot prove a week exists, it says so and names the step that fixes it — here, Teacher availability under Curriculum & Resources — instead of producing a week that breaks one. The refusal above is a real one, replayed word for word.
Every run records its seed and a soft score, so two drafts can be compared instead of argued about. The run above placed 48 periods and improved from 130 to 120 across seven drafts.
The committed week on the board: cohorts down the page, P1 to P13 across, health pills at the top. Click a lesson and the free cells light up — a cell where the teacher is already busy says so before you drop. Apply changes then shows exactly what a move touches, from the date you choose.
© 2026 Commun. All rights reserved.
Mirrors: School Admin → Timetables → Timetable · the board · Apply changes · a cell where the teacher or the room is already taken says so before the drop
Apply changes lists the classes that change and the ones that do not, the dated lessons behind each one, and the first and last date affected. Lessons before the effective date are never touched, and a lesson with attendance is never deleted.
Already have a week elsewhere? Import it from aSc Timetables or from a spreadsheet, and carry on from there. The overall, teacher and cohort views print from the browser.
The teacher marks in a grid on a phone: type a mark, press Enter, and the cursor jumps to the next unmarked student. The framework’s weights compute the percentage and the school’s grade, a comment code comes from the bank, and Finalize locks it. The card is released to parents on the date the school sets.
Scroll horizontally to view all assessments.
Mirrors: Teacher → Gradebook · Teacher → Report Cards → Subject marking · School Admin → Report Card → Student Report Card Preview · Enter jumps to the next unmarked student
Coursework 40, Test 60: the weighting is computed once, the same way for every student in the class. Comment codes come from the school’s own bank, so a report card reads the same whichever teacher wrote it.
Once marks and comments are finalised they cannot be edited over, and the card stays hidden from parents until its release date.
Families read it in the school’s own app, in English, Malay or 中文: see what a parent sees.
A kiosk at the gate rests on a calm screen and wakes on a touch. Everyone it recognises is recorded on sight, with a Not me on every card. In the office, Daily Attendance shows who arrived when, and who was late to their first lesson.
© 2026 Commun. All rights reserved.
Mirrors: Attendance kiosk → the device · School Admin → Insight Centre → Daily Attendance · add-on (Attendance kiosk, class A) · the device screen is English; the frames over the viewfinder are drawn, not photographed
The device records on recognition and checks the student into the lesson in its window — on time or late. A wrong match is one tap to undo, and nothing is recorded.
In class, attendance follows the timetable, lesson by lesson: every period on the board is a lesson a teacher can mark, and a lesson stops accepting edits once it is no longer in progress.
A rule is a guarantee — a week that breaks one is never produced, and the refusal names the step.
Never touches lessons before the effective date, and never deletes a lesson with attendance.
The arithmetic is the framework’s, computed once, the same for every student. Finalised marks lock, and the card stays hidden until the release date.
Records on recognition, with an undo on every card.
Your divisions, your bell schedule, your report card template — a walkthrough of half an hour, shaped around your office.