Operations
·
·
⏱ 2 min read
·
👁 25
Holiday & festival calendar handling for Indian schools
No two states in India share the same school holiday calendar. A management system that ships only Republic Day and Independence Day is hostile to every regional school. Here is how to model a calendar that handles 50+ holidays across boards, states, religions.
T
Technokrits
Technokrits team
📖
A school in Kerala observes Onam. A school in Punjab observes Lohri. A Muslim-minority school observes Eid-ul-Fitr AND Eid-ul-Adha. A board school follows CBSE's revised calendar. A state-board school follows the state Government Order. Each of these is right; a one-size-fits-all calendar is wrong.
How to model this:
1. Three layers — national (gazetted), state (Government Order), school (PTA decision). Schools tick which ones apply.
2. Religious holidays sourced from a maintained list, not a code constant. Eid-ul-Fitr and Diwali change date every year; hard-coding "October 21" breaks next year.
3. Half-day support — Saturdays in many CBSE schools, day before exam in others. The attendance system must allow expected-hours-of-school to be configurable per day.
4. Working day exceptions — special workdays announced after a sudden closure (rain holiday made up the next Saturday). The calendar must allow this without code change.
5. Bell schedule shifts on shortened days. A 4-period day after holidays needs its own bell config.
6. Auto-reminder for parents — SMS the evening before "Tomorrow is closed due to Diwali, school re-opens Tuesday." The single missed-reminder ruins a parent's morning.
The right approach is a database table of (date, type, scope, working_status) that the timetable, attendance, and SMS modules all read from. Hard-coding any of this is a mistake you only make once.
How to model this:
1. Three layers — national (gazetted), state (Government Order), school (PTA decision). Schools tick which ones apply.
2. Religious holidays sourced from a maintained list, not a code constant. Eid-ul-Fitr and Diwali change date every year; hard-coding "October 21" breaks next year.
3. Half-day support — Saturdays in many CBSE schools, day before exam in others. The attendance system must allow expected-hours-of-school to be configurable per day.
4. Working day exceptions — special workdays announced after a sudden closure (rain holiday made up the next Saturday). The calendar must allow this without code change.
5. Bell schedule shifts on shortened days. A 4-period day after holidays needs its own bell config.
6. Auto-reminder for parents — SMS the evening before "Tomorrow is closed due to Diwali, school re-opens Tuesday." The single missed-reminder ruins a parent's morning.
The right approach is a database table of (date, type, scope, working_status) that the timetable, attendance, and SMS modules all read from. Hard-coding any of this is a mistake you only make once.
T
Technokrits
Technokrits team — building software for Indian schools.
Try it in your school today