Setting Up a New Academic Year: Promotions, Sections, Fees and Timetables

A disclosure first: Edutris is school software, and we wrote this. The sequence below is not product-specific, though. It is the same on paper, in spreadsheets or in any system, because the dependencies come from how a school works rather than from how software is built. Where Edutris does something specific, we say so, and we say what it does not do.

The short version: the rollover has an order, and the order is the whole story. Sections must exist before students can be promoted into them. Students must be enrolled in the new year before a fee demand can be raised against them. Staff must be allocated before a timetable means anything.

What this guide will not tell you is when your session starts, who may be held back, or what attendance a child needs. Session dates, promotion criteria and attendance minimums vary by state and by board, confirm yours from your own board's circulars and your state's rules. Everything below is about sequence, not the calendar or the regulation.

Why does the order matter more than the effort?

Because almost every step consumes the output of an earlier one, and the failures are silent rather than loud.

A rollover done out of order rarely throws an error. It produces a plausible result that is wrong in a way nobody notices for weeks. Raise fee demands before students are enrolled in the new year and the system dutifully creates nothing, no error, just an empty screen, which reads as "the fees are not showing" rather than "we did step seven before step five". Promote a section before the leavers list is final and children who have left are now inside a strength figure every later number is derived from.

So the discipline is not working harder in the last week. It is refusing to start a step whose inputs are not finished, which means knowing what those inputs are.

What order do you actually do a year-end rollover in?

Twelve steps. The "cannot start until" column is the part worth arguing about with your office before you begin.

#	Step	Cannot start until	If you do it early
0	Create the new academic year; mark it current at the right moment	Nothing	Later records attach to the wrong year, invisibly
1	Close the outgoing year, marks, results, report cards, dues position	Year-end marks entered and checked	Report cards get republished; parents see two versions
2	Decide next year's classes and sections	Expected strength per grade	Safe early, and you should
3	Mark leavers, transfers out and repeaters	Results, plus leaving-certificate requests	Leavers get promoted and inflate the new roll
4	Promote the returning cohort into next year's sections	Steps 0, 2 and 3	Sections and roll numbers get redone by hand
5	Slot new admissions into sections	Step 4	Sections get rebuilt around a still-moving intake
6	Decide and create the new year's fee structures	Whoever approves the amounts	Safe early, the only genuinely parallel step
7	Raise the fee demands against enrolled students	Steps 4, 5 and 6	Zero records created; the enrolments are not there yet
8	Re-apply concessions, sibling and staff-ward discounts	Step 7	Nothing exists to attach them to
9	Assign class teachers and subject teachers	Steps 2 and 4	The timetable is built on guesses
10	Build the timetable, section by section	Step 9	A rebuild after every staffing change
11	Switch scheduled reminders and notifications back on	Steps 7 and 10	Parents get reminded about last year's numbers

Two notes on step 0, the step nobody writes down. In Edutris, academic years are created and marked current at the workspace level by an org admin, and the school-side screens read whichever year is currently marked, so on a trust this is a trust-office action rather than something each principal does separately. And the two things that read the year behave differently, on purpose: promotion asks you which year to promote into, so you can promote into next year while this year is still current, whereas timetable generation uses whichever year is current. That is why the current-year flag has to move before you build the week, and does not have to move before you promote.

What breaks when you do it out of order?

Ordered by how often it actually happens. Each one looks like something else when it lands.

"The fees aren't showing for the new year." Demands raised before the enrolments existed. The demand step resolves the class and the academic year, then creates one pending record per enrolled student, so with no new-year enrolments to find it creates nothing and says so. Promote first, then raise; because re-running does not duplicate existing records, you can safely raise again after each batch of admissions.

Concessions missing from the new dues. Expected, not a fault: a discount sits on a fee record and the new year has new records. Nothing carries them forward, and arguably nothing should: sibling discounts, staff wards and hardship waivers all deserve an annual review. Rebuild last year's list from the audit log, which records fee actions including concessions, then re-apply.

A section holding two sections' worth of children. A promotion run pointed at the wrong target. Compare each new section's strength against its source before you touch fees, because every fee record raised afterwards inherits the error.

Parents reminded about last year's dues. Scheduled reminders in Edutris are per-school and off by default, so whatever you switched on last year is still on through the changeover, with only the old figures to talk about. Switch them off for the rollover window and back on once the new demands are verified.

The timetable is on last year. The current-year flag had not moved when the week was generated. In Edutris, if no year is marked current, timetable generation stops and tells you to set one rather than picking for you, useful, but that only protects you from the "no year" case, not the "wrong year" one. Fix the flag and regenerate, remembering that regeneration replaces that section's existing slots.

Auto-generation refuses to finish. Ask for a week the assigned staff cannot cover and Edutris declines the whole request and names the subject and teacher whose periods it could not place, instead of shipping a half-built week. That reads as a tool failure and is almost always a staffing conflict: the teacher is already committed elsewhere at the only times left.

Roll numbers nobody agrees with. Promotion assigns them in the order students are moved, so promoting in three goes because the leavers list kept changing gives you the order you clicked in. Settle the list, promote once.

A child who left is on the new roll, or a child is missing from it. The first means the leavers list was finalised after the promotion; mark them as left and re-check any demand raised against them. The second is usually a new-session admission who was in no old-year section, so no promotion run could have found them.

Admission numbers that seem to jump. Sequential admission numbers in Edutris are minted per school against a calendar year, not an academic session, so the counter rolls over on 1 January rather than at session start and a February admission carries the earlier year. Gaps and year boundaries are expected, the contract on these numbers is uniqueness, not gaplessness.

Which students do not roll over cleanly?

The bulk cohort is easy. These six groups are where the errors live, and each needs a named list (not an estimate) before you promote anyone.

The final-grade cohort. Leaving, not moving up, and their records still have to stay reachable: certificate and verification requests arrive years later. Mark them as having left rather than removing them.

Transfers out. The trap is timing. TC requests keep arriving during the rollover window, so a list frozen in March is wrong by April: freeze it as late as you can and re-check it against the certificates actually issued.

Repeaters. They stay in the same class, so they are enrolled separately and then explained as a line in your reconciliation. Whether holding a child back is permitted at all in your grade and board is a question for your board's rules, not your software's.

Mid-year joiners. A partial attendance and fee history from the outgoing year, which confuses any like-for-like comparison. They roll over normally; their numbers just will not look like anyone else's.

New-session admissions who were never in the old year. They sit in no source section, so no promotion run can pick them up: they arrive through admissions and are slotted in directly.

Siblings. Family-level discounts can change the moment the eldest leaves: same rule, different input. This is the concession most often re-applied wrongly.

How do you prove the rollover actually worked?

By reconciling in both directions, and writing the numbers down while you still have a source you trust.

Here is a worked reconciliation for a completely made-up school of 612 students. The figures are invented to show the shape of the check; the shape is the deliverable.

Line	Students	Notes
Strength on the last day of the outgoing year	612	From an enrolment export, not from memory
Less: final-grade cohort leaving	−58	Marked as having left, not removed
Less: transfers out with a leaving certificate issued	−11	Named list, checked against certificates actually issued
Less: repeaters staying in the same class	−4	Moved separately, not by the bulk promotion
Expected to be promoted	539	This is the number to check against
Reported as promoted by the promotion runs	535	Four short, do not proceed yet
Reported as skipped, already enrolled in the target year	4	Left over from a partial first attempt; re-running is safe
Accounted for	539	Matches. Every difference now has a cause
Plus: repeaters re-enrolled in the same class	+4	Closes the loop on the −4 above
Plus: new admissions into the entry class	+64
Plus: lateral admissions into existing classes	+9
Opening strength for the new year	616	Must equal the sum of the new year's section strengths

That last line is the one people skip, and the one that catches a wrongly-targeted promotion run. If the section strengths sum to 616 but one section holds sixty children and another twelve, you have promoted two sections into one target.

Then the same for money, because a mismatch here reaches parents:

Line	Amount (₹)
Annual demand raised across all classes	1,84,80,000
Less: concessions and waivers re-applied	−6,20,000
Expected net demand for the new year	1,78,60,000
Net demand in the system	1,78,60,000

Invented numbers again. The check that matters is per class rather than in total: a class's demand should be its strength times the sum of that class's heads, and any class where that does not divide cleanly has a student on the wrong fee structure. Totalling everything hides exactly that error. Keep the outgoing year's arrears tracked separately rather than folded into the new demand, or you lose the ability to answer "what does this family owe us, and for which year".

For raw material, export the enrolment and fee CSVs before you start and again when you finish. Edutris has filtered attendance, fee-collection and enrolment CSV exports on the analytics side, and two exports either side of the rollover beat any screenshot. Promotions and fee actions are written to the audit log, so "who moved this section, and when" does not depend on anyone remembering.

How much work is this at your school's size?

Same method everywhere. Very different amount of clicking.

A 200-student school, one section per grade, one person in the office. Sections already exist and rarely change, so step 2 is a five-minute review, and the risk sits almost entirely in the leavers list and the demand raising. Do the fee decision earlier, in a separate sitting, so amounts are not being settled by the same person on the day they are promoting children. The constraint here is attention, not data: the one person who knows everything is also the one being interrupted all day.

A 900-student school, three sections a grade, a separate accountant and an exam in-charge. Promotion runs per section, so this is thirty-odd runs rather than ten, but the actual work is section rebalancing, a pedagogical conversation disguised as an administrative one. Three people have to agree before anyone clicks: the exam in-charge owns who is eligible to move up, the accountant owns the concession list, the office runs the promotions. Expect the concession review to be the long pole.

A trust running three schools. One at a time, smallest first, treating the first as the rehearsal. Each school has its own academic year record, classes, sections, fee structures and admission-number counter: nothing is shared, which is what you want at audit time and a chore at rollover. The decision to make once, at the top, is naming: if three schools call the same grade three different things, every trust-level comparison next year is manual.

Where software helps, and where it genuinely cannot

Worth being precise about, because the difference is where schools waste a week.

What it carries: promotion as a repeatable, recorded action rather than a hand-edited list, with promoted and skipped counts to reconcile; fee structures scoped to a year and a class, so a cohort lands on the right amounts without per-student entry; a timetable grid editor with auto-generation and printing; report-card and hall-ticket release controlled per section, so you can close the outgoing year grade by grade; certificates issued per student for the children leaving; and CSV exports on both sides of the rollover. On a Professional plan or above with AI switched on, some of the writing (report-card remarks, a reply to a parent) can be AI-drafted, and it is always a draft a human reviews and approves before it goes anywhere.

What it will not do: decide who repeats, who is eligible to move up, or when your session starts. Those are your board's rules and your school's judgement. Copy last year's fee structures forward, because in Edutris they are created fresh each year on purpose. Tick individual children out of a bulk promotion, because the wizard moves a source section at a time: precisely why the leavers list has to be settled first. Or notice that your reconciliation does not balance. That last one is why the tables above exist: software will hold a wrong number very neatly.

The honest bottom line

The rollover is not difficult work. It is dependent work, and the dependencies are unforgiving in one direction only: every step done early produces a result that looks fine and is not.

So: create the year, close the old one, fix the sections, name everyone who is not moving up, promote, admit, raise the money against a roll you have already reconciled, then staff, then the timetable, then switch the reminders back on. Do that and the first week of the session is about children rather than corrections.

If you'd like to see promotion, academic-year fee structures and section timetabling run end to end on a demo school, book a walkthrough or start a 30-day guided pilot and we'll do your first rollover alongside you.