Why a generator helps
The same dependent modules are easy to forget when each team plans rollover separately.
Free planning tool
Academic-year rollover checklist
Prepare a year-end and new-year smoke test covering calendar, promotion, timetable, attendance, fees, exams, and portals. 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
Prepare a year-end and new-year smoke test covering calendar, promotion, timetable, attendance, fees, exams, and portals.
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 the year
Record reports, corrections, outstanding approvals, and archive decisions.
- 02
Build the next year
List terms, holidays, classes, subjects, grading, and fee dates.
- 03
Promote carefully
Mark expected moves and exceptions for leavers, transfers, and new sections.
- 04
Test outputs
Check one full student journey before reopening all staff and family workflows.
Practical artifact
Leave with something your team can use
Copy these checkpoints into a kickoff, vendor demo, or readiness review.
- Close-down tasks
- New-year setup
- Promotion exceptions
- Smoke-test matrix
Build your copyable checklist
This tool stores nothing and is for planning only. Do not enter student or family data.
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.
Available now
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.
Keep evidence
Attach screenshots or exports from the smoke test to the change record.
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 checklist be customised?+
Yes. Treat the generated tasks as a baseline and add board, campus, and policy-specific checks.
Should families be invited immediately?+
Wait until guardian links, calendar, fees, and published content pass the school’s smoke test.
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 pageStudent records software for registrars
Keep one student record current across admissions, class placement, guardians, certificates, fees, and academic history.
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