Calendar.

A school's year shouldn't be published by whoever has the spreadsheet open.

• One calendar per session

  Exams, holidays, activities, administrative dates and term milestones live on a single calendar — typed by category, colour-coded, and kept to exactly one calendar per branch per academic session.

• Year, month and timeline

  Read the session three ways — a year overview of every month at a glance, a month grid you can work in, and a flat timeline — without re-entering a single date.

• Drag to reschedule

  Move a date the way you'd move it on a wall planner — drag an entry to a new day, or drag-select a span for a multi-day event — and the calendar updates the entry underneath.

• Multi-level approval

  Nothing publishes on a whim. A submitted calendar climbs an ordered hierarchy of approval levels — each with its own approver roster — moving Draft → Pending → Approved, level by level.

• Request changes, in thread

  An approver can approve, request changes or reject — with a comment thread between submitter and reviewers, and a rejection comment required when the branch says it must be.

• Delegation when away

  Hand approval authority to a delegate for a fixed window — a leave, a tour — and every action is logged against who really stood in, so the audit trail stays honest.

• Entry notifications

  Schedule an email for an entry — on the day, a day before, a week ahead — to chosen staff and any custom address, with the send time computed in IST from the entry's own date.

• Working-day maths

  The calendar counts itself — working, teaching, holiday and exam days across the whole session and broken down per term — so a planned year is also a counted one.

• 01 / 04

  Kept to one branch, one session. There is exactly one calendar per branch per academic session — so a multi-campus trust plans each campus's year on its own, and last year's calendar stays last year's, never bleeding into this one.

• 02 / 04

  Linked to the records you already keep. Holidays, term milestones and events sync in from the modules that own them — so a date entered once shows up on the calendar, instead of being re-typed and quietly drifting out of step.

• 03 / 04

  On the same web, iOS and Android apps. A coordinator drafts the term from a desk; the principal clears a held event from a phone between classes. One login, one calendar — no separate planning tool to chase.

• 04 / 04

  Within reach of Sol, the AI agent. The same assistant that answers questions across the school can read the calendar too — a quiet way to ask what's coming up or what's still awaiting approval, not a fourth screen to learn.

Why it's built this way

A calendar parents can trust is one nobody could change alone. The approval is the feature.