How Academic Year Promotion Should Work in Modern School Software

Every school does this once a year: move students up a grade, decide who repeats, who graduates, who leaves. It's a simple idea that's surprisingly easy to get wrong in software.

The core design decision

The right model treats a student as a permanent identity and their yearly enrollment as a separate, closable record. Promotion doesn't edit last year's data to say "now in Grade 6" - it closes last year's enrollment exactly as it was, and opens a new one for the new year. This single decision is what makes a student's full history trustworthy years later.

What should never happen during promotion

• Last year's attendance or grades should never be edited or deleted.
• A repeating student's two years in the same grade should never blend into one record.
• Fee records from the year that just ended should stay exactly as they were billed.
• A parent's account and relationship to the student should carry over automatically, without needing to be relinked.

What a good promotion workflow gives you

A real preview before anything is committed, a decision per student (not just a blanket "promote everyone"), and warnings - not blocks - when something looks unusual, like a student with very low attendance being promoted anyway. The software's job is to inform the decision, not make it.