SkoolBook logoSkoolBook

The academic year rollover checklist most schools do the hard way

6 min read

Academic year rollover is the single most destructive routine event in a school's data. It is also the one most systems handle worst, because it exposes whether the underlying structure was ever designed for a school that has more than one year in it.

Here's what to work through, and the structural question that determines whether it takes an afternoon or a fortnight.

The question that determines everything

Is the academic year a real record in your system, or is it text embedded in other names?

If your sections are called "Class 9-B 2025-26" as a string, rollover is a rename-everything project, and every rename silently detaches last year's history from this year's student. If grade, section and academic year are separate structural records that things are defined *against*, rollover is a structural operation and history stays attached.

You can test this in ten seconds during a demo: ask to see a student's attendance from the previous academic year. If that's awkward, you have your answer.

Promote students without destroying last year

Promotion should create the student's new grade and section association, not overwrite the old one. A student is not "in Class 10" — they were in Class 9 in one year and Class 10 in the next, and both statements need to stay true.

Before promoting: settle retentions and transfers-out first. Promoting a student who has left and then reversing it is far messier than the ten minutes it takes to reconcile the list beforehand.

Re-form sections before anything depends on them

Sections usually get reshuffled. Do this before timetables, before subject allocation, and before fee assignment, because all three hang off section membership. Doing it after means redoing all three.

Version the fee structure, don't edit it

The new year's fees should be a new structure for that academic year, not an edit of last year's. Editing in place destroys your ability to answer what a family was supposed to pay in a previous year — which is exactly the question an audit or a dispute asks.

Carry forward outstanding balances explicitly as their own records rather than folding them into the new year's numbers, or the arrears become invisible within a term.

Staff and access, the step everyone forgets

Class teacher assignments, subject allocations and portal access all change with the year. The common failure is leaving last year's class teacher with access to a section they no longer teach — nobody notices, because nothing breaks.

Make it an explicit checklist item. It's a data-protection issue as much as a housekeeping one.

Do a dry run on last year's data

If your vendor can't offer a way to rehearse this, that itself tells you something. The first time you do a rollover should not be the real one, and any system where rehearsal is impossible is a system where rollover was an afterthought.

The short version

Ask one question of any system you're evaluating: can I see a student's attendance from last academic year? If that's awkward, rollover will be too.

school software for cbse schoolsfee management

More from the blog

What the DPDP Act actually means for your school
India's data protection law treats children's data as a special category. A practical read on what a school is now responsible for — and the questions to put to your software vendor.
RFID, biometrics or the app: how schools should actually mark attendance
An honest comparison of card, biometric and in-app attendance for schools — what each really costs, where each fails, and how to pick without buying hardware you'll abandon.
School bus GPS tracking: how to tell real-time from a position log
Most school transport modules log positions periodically and call it tracking. Here's how to tell the difference during a demo, and what parents actually need.
Book a demo