Calendar first
Downstream modules inherit dates and should not be reopened until the new calendar is trusted.
Implementation guide
Academic-year rollover checklist
Close the old year, create the next academic context, promote students, and validate downstream calendars before reopening work. See the workflow, ownership, rollout sequence, and boundaries before choosing a school management platform.
At a glance
A useful page should answer the next operational question
Close the old year, create the next academic context, promote students, and validate downstream calendars before reopening work.
Who this is for
- Academic coordinators
- Registrars
- Platform admins
Start with the evidence
Use the linked product and documentation pages to validate the workflow against your school’s data, roles, policies, and deployment.
Read the supporting materialHow it works
Follow the handoffs, not just the feature list
A clear sequence makes ownership, exceptions, and the next system action visible.
- 01
Close
Freeze reporting, exports, outstanding corrections, and old-year changes with a named owner.
- 02
Create
Configure the next year, terms, holidays, grading, classes, subjects, and working days.
- 03
Promote
Move students and assignments with an exception queue for leavers, transfers, and new sections.
- 04
Smoke test
Verify timetable, attendance, fees, exams, portals, and reports against the new year.
Practical artifact
Leave with something your team can use
Copy these checkpoints into a kickoff, vendor demo, or readiness review.
- Rollover owner map
- Calendar freeze checklist
- Promotion exception log
- Post-rollover smoke test
Product truth
What to verify before rollout
Good school software copy should answer who owns the work, what the handoff produces, and which parts still depend on deployment decisions.
Validate for your rollout
Capability status
This page describes the supported workflow boundary. Confirm configuration, integrations, data, and policy requirements in a representative pilot before committing to production.
Teams in the workflow
- Academic coordinators
- Registrars
- Platform admins
Deep dive
Decisions, handoffs, and boundaries
Use these details to turn a product page into an implementation conversation.
Avoid silent changes
Keep an exception log for students, guardians, fee rules, and staffing decisions that need human review.
Evidence layer
Read the supporting product and implementation material before making a capability claim.
Questions, answered
Straightforward answers for visitors evaluating the product.
Can the old year remain available?+
Historical access should be planned by role and reporting need; do not treat rollover as deletion.
What is the minimum smoke test?+
Test one student, one class, one fee, one attendance day, one timetable period, and one family-facing output.
Continue exploring
Related planning and product pages
Follow the next link based on the question your team needs to answer.
Calendar to attendance
Use one academic calendar to decide when school is open, mark attendance accurately, and show families a consistent history.
Read the pageAcademic-year rollover checklist
Prepare a year-end and new-year smoke test covering calendar, promotion, timetable, attendance, fees, exams, and portals.
Read the page
Turn the page into a rollout conversation
We can walk through the workflow with your school’s roles, calendar, data, and first-term priorities.
Already using Schoolyi? Sign in