Academic years, classes, and the calendar every module shares
The academic calendar is the backbone of your school year. Terms, holidays, working days, and events flow into attendance, exams, fees, timetables, and leave, so every team works from the same dates and structure. When the calendar changes, downstream modules should not break. Schoolyi ties classes, subjects, syllabus templates, and session boundaries to one academic model. Coordinators set the year once; teachers, finance, and exam teams inherit consistent dates without maintaining parallel spreadsheets.
Outcomes
Practical results schools report after rolling out this area on the shared calendar and roster.
One source of truth for working days, holidays, and term dates
Timetable, attendance, and exams stay aligned when the calendar shifts
Curriculum and syllabus planning tied to class structure
Less manual reconciliation between academic and operations teams
Product truth
Good school software copy should answer who owns the work, what the handoff produces, and which parts still depend on deployment decisions.
This page describes the supported workflow boundary. Confirm configuration, integrations, data, and policy requirements in a representative pilot before committing to production.
Deep dive
Use these details to turn a product page into an implementation conversation.
When the calendar changes, downstream modules should not break. Schoolyi ties classes, subjects, syllabus templates, and session boundaries to one academic model. Coordinators set the year once; teachers, finance, and exam teams inherit consistent dates without maintaining parallel spreadsheets.
The academic calendar is the backbone of your school year. Terms, holidays, working days, and events flow into attendance, exams, fees, timetables, and leave, so every team works from the same dates and structure. Because Calendar & structure shares roster and calendar data, teams stop reconciling exports between spreadsheets and the parent portal.
Evidence layer
Read the supporting product and implementation material before making a capability claim.
Everything included in this module, from daily workflows to exports your team relies on.
Role-scoped workspaces so each team sees only the tasks they own.
From the blog
One academic calendar - or five reconciliation projects every term
Holidays, working days, and term boundaries must drive attendance, exams, fees, and leave. Stop maintaining parallel date lists.
Read the guide →Focused pages for evaluators comparing specific calendar & structure workflows during an SMS rollout.
Workflow
A typical path from setup through daily use on Schoolyi.
Part of the Calendar & structure workflow on Schoolyi, connected to roster, calendar, and role permissions.
Part of the Calendar & structure workflow on Schoolyi, connected to roster, calendar, and role permissions.
Part of the Calendar & structure workflow on Schoolyi, connected to roster, calendar, and role permissions.
Part of the Calendar & structure workflow on Schoolyi, connected to roster, calendar, and role permissions.
Deep dive
Long-form context for evaluators comparing modules during an SMS rollout.
When the calendar changes, downstream modules should not break. Schoolyi ties classes, subjects, syllabus templates, and session boundaries to one academic model. Coordinators set the year once; teachers, finance, and exam teams inherit consistent dates without maintaining parallel spreadsheets.
The academic calendar is the backbone of your school year. Terms, holidays, working days, and events flow into attendance, exams, fees, timetables, and leave, so every team works from the same dates and structure. Because Calendar & structure shares roster and calendar data, teams stop reconciling exports between spreadsheets and the parent portal.
These areas work closely with calendar & structure and share the same calendar, roster, and role model.
Straightforward answers for visitors evaluating the product.
Academic coordinators, Principals, Admin office run daily workflows in this module while leadership reviews dashboards and exports when needed.
Assign a workflow owner and test it with a representative staff account before the busy part of the term. Verify that approvals, coverage details, and sensitive fields remain within the intended role.
Dates, working days, and class structure flow from the shared calendar so downstream modules do not maintain parallel date lists.
Set the academic calendar before enabling dependent workflows, then test one holiday and one working-day exception against the resulting attendance or exam view. Keep the school’s local policy as the authority for edge cases.
Schools often launch admissions, roster, and fees first, then add this module when the foundation data is stable.
Choose the next phase only after the team has reconciled one complete operating cycle. Record the data, role, calendar, and support dependencies before widening access.
Role-scoped workspaces show only the tasks each team needs. Most schools run a short coordinator session plus self-serve docs.
Assign a workflow owner and test it with a representative staff account before the busy part of the term. Verify that approvals, coverage details, and sensitive fields remain within the intended role.
We'll show how this module fits your school's workflows and which teams benefit first.
Already using Schoolyi? Sign in
