
Academic years that roll over
Set up the year, its grades and its sections once. Opening the next year copies the structure across rather than making somebody rebuild it, and the year you are looking at is always explicit.
Loading…The academic year, classes and sections, the timetable, the daily register, homework, syllabus progress and promotion. One lifecycle in one system, so a student's history survives the year rolling over instead of being copied into next year's register by hand.
Most of an institution's administrative pain is concentrated into two weeks, and it is the same two weeks every year.
Next year's registers are written out by hand from this year's, which is where names, dates of birth and IEMIS details quietly diverge.
A student's history stops at the year boundary, so answering a question about Grade 6 means finding the Grade 6 register.
The timetable lives in a spreadsheet on one computer, and the version on the noticeboard is a photograph of an older one.
Homework is set in a copy, so nobody except the class knows what was given or when it is due.
Syllabus progress is a conversation in the staff room rather than something anyone can look at.
The parts you actually touch every day, built so they refer to the same records rather than describing each other.

Set up the year, its grades and its sections once. Opening the next year copies the structure across rather than making somebody rebuild it, and the year you are looking at is always explicit.

A student is enrolled into a section for a year, so class lists are derived from enrolment rather than maintained separately. Move a student and every list that mentions them updates, because there is only one list.

Define period, break and assembly slots, then build the routine per class and per teacher. A one-off change is recorded as an override rather than by editing the timetable, and teachers, students and parents can each see their own day.

Attendance is captured against the student, not a sheet of paper, so a term's attendance for one child is a question you ask rather than a count you do. Teachers see the classes they actually take, enforced on the server.

Homework is set against a class and a subject where students and parents can see it. Syllabus units are marked off as they are covered, so how far a class has actually got is visible without asking.

Move a whole year group up in one action. Each student's record carries forward rather than being recreated empty, so last year is still there to look at after the roll over.
Promotion is the single most destructive action in a student system, so it is built to be inspected before it happens and undone after it.
Open next year and copy this year's grades and sections into it.
Preview the promotion. Every student is listed with where they would land, before anything moves.
Read the blockers. Students with something outstanding are flagged rather than swept along, and you decide case by case.
Commit. The year group moves up together, with each student's history attached.
If it was wrong, undo it. A promotion run can be reversed rather than unpicked student by student.
Show us how your institution works today, registers, spreadsheets or another system, and we will show you what moving across actually looks like. No pressure, and a straight answer on price.