False absences
Holiday mornings still trigger parent SMS because attendance does not know the calendar.
One institutional calendar — terms, holidays, exams, and events
Academic Calendar is the master timeline every module respects: working days for attendance, exam windows, holidays for fees/reminders, and events parents can see.
Year
and term structures per campus
Holidays
that stop false absence alerts
Windows
for exams and key events
The problem
Why a PDF calendar is not an operating calendar
When dates live in a circular only, attendance, exams, and transport still assume every weekday is a working day.
Exam collisions
Units tests land on sports day because planners use different sheets.
Trust drift
Multi-campus groups cannot share one holiday master with local exceptions.
Parent confusion
Families miss term start or PTM dates buried in long circulars.
Capabilities
What this module actually does
Operational depth your team will use every cycle — not a shallow feature list.
Academic year & terms
Define year boundaries, terms, and working-day patterns.
Holiday master
National, regional, and campus-specific holidays in one place.
Exam windows
Block date ranges that Examination Management and timetables consume.
Event scheduling
PTMs, sports days, and orientations with portal visibility.
Working-day rules
Drive attendance expectations and reminder suppression.
Multi-campus variants
Share a trust calendar with local overrides.
Portal publish
Show key dates to parents, students, and staff.
Downstream hooks
Feed timetable, exams, fees reminders, and transport planning.
Operating loop
How it works end to end
A clear path your staff and parents can follow without training manuals.
-
01
Define
Set the academic year, terms, and weekly working pattern.
-
02
Populate
Add holidays, exam windows, and major events.
-
03
Publish
Release the calendar to portals and dependent modules.
-
04
Adjust
Push mid-year changes once — attendance and alerts follow.
Who uses it
Role-aware access for every stakeholder
The right people see the right slice of the pipeline.
Admin / Principal office
Owns year setup, holidays, and publish authority.
Exam controller
Aligns seating and papers to reserved date ranges.
Teacher
Plans lessons against real working days.
Parent
Sees holidays, PTMs, and term boundaries in the portal.
Connected stack
Works with the modules you already need
Each module is an edge in the campus operating graph — not a silo.
Outcomes
What changes after go-live
Measurable ops wins institutions report once this module runs inside ScholarERP.
Fewer
holiday-morning absence false alarms
Aligned
exams, events, and teaching days
One
publish for the whole campus community
“We stopped printing the calendar twice a year. One publish updates portals, attendance rules, and exam planning together.”
FAQ
Questions teams ask before buying
Straight answers for setup, integrations, and day-two operations.
Can different campuses have different holidays?
Yes. Start from a trust master calendar and apply campus-level overrides where needed.
Does the calendar stop attendance alerts on holidays?
When working-day rules are published, Attendance Management and Alerts can suppress absence noise on non-working days.
How do exam windows interact with Examination Management?
Reserved windows give exam controllers a date fence for sessions, seating, and publish planning.
Can parents download an ICS calendar?
Portal visibility of key dates is standard; ICS export can be enabled where your deployment supports it.
Map your next academic year in the demo
Bring term dates and holidays — we will show publish impact on attendance and exams.