Every school in Nepal runs on a calendar that almost no off-the-shelf software understands. The year starts in Baisakh, not January. Terms are bounded by Dashain and Tihar, which move against the Gregorian calendar every year. Exams sit in Chaitra and Baisakh. And in 2083 the whole thing was compressed by two government decisions at once - a later session start and a five-day school week - which pushed a lot of schools into rebuilding their annual plan from scratch.
This is a guide to how the Nepali school year actually runs, what changed for the 2083 session, and why the calendar is the single deepest localization requirement in school software. It is also the reason "we support multiple date formats" is not the same claim as "we support Bikram Sambat", and the reason the first question on any software demo checklist should be about dates.
The Year Runs Baisakh to Chaitra
Nepal's official calendar is Bikram Sambat, which runs roughly 56 years and 8 months ahead of the Gregorian calendar and starts its year in Baisakh, around mid-April. The school year follows it. A Nepali academic session opens in Baisakh and closes in Chaitra, the twelfth month, which lands in March or early April.
That single fact has consequences that ripple through every system a school runs:
- The academic year and the financial year do not align with anything a global product assumes. A platform hard-coded to a September or January intake does not just display the wrong month name; its promotion logic, its year-end rollover, and its report headers are all keyed to the wrong boundary.
- BS month lengths are not fixed. Unlike Gregorian months, the number of days in a Bikram Sambat month varies from year to year and is published rather than computed from a simple rule. Software that "converts" by adding a fixed offset will drift.
- Every printed artifact carries a BS date. Report cards, fee receipts, transfer certificates, attendance registers, and character certificates are all read by parents and by government offices in BS. A system that stores dates correctly but prints Gregorian is producing documents your office has to re-type.
The technically correct approach is to store dates in AD and convert only for display. That keeps sorting, date arithmetic, and interoperability sane while giving every human-facing surface the calendar it expects. What you should be wary of is the opposite: a system that stores a BS string as text. Those cannot be sorted or compared reliably, and the damage shows up months later in a report that puts Mangsir before Kartik.
What Changed for the 2083 Session
Two things moved at once, and together they are the biggest calendar disruption Nepali schools have absorbed in years.
In a circular issued to all local levels and schools, the Education and Human Resource Development Center (CEHRD) set out the schedule for the 2083 session following a Council of Ministers decision. Per CEHRD's announced schedule, the shape of the opening weeks is:
- Baisakh 2 - administrative and creative preparations begin, including teacher training and school improvement planning.
- Baisakh 15 - the student admission campaign formally opens.
- Baisakh 21 - regular classroom teaching and learning begins.
The second change is larger in its effects: the government moved all educational institutions to a two-day weekend, Saturday and Sunday. CEHRD integrated that policy into the same circular, requiring schools to restructure their annual calendars and instructional plans so curriculum requirements are still met inside a five-day week.
The published dates are not perfectly consistent across sources, and this matters if you are building a plan around them. CEHRD's circular puts the admission campaign at Baisakh 15 and teaching at Baisakh 21. The National PABSAN directive to member schools describes new admissions starting Baisakh 2 with regular teaching from Baisakh 15. Treat both as indicative and confirm the operative dates with your local level education office before you print anything or lock a term structure into software.
The 220-Day Floor Is the Real Constraint
The teaching-day requirement is what turns a calendar change into an operational problem. For the 2083 session, schools are directed to manage Dashain, Tihar, winter and summer vacations, and all other breaks so that a minimum of 220 teaching days is still achieved.
National PABSAN, which represents private and boarding schools, circulated the government's decision to its members while registering serious concern about it. Its arithmetic is worth quoting in substance: introducing Saturday and Sunday as weekly holidays adds roughly 40 extra holidays a year, and shifting the session start from Baisakh 1 to Baisakh 15 squeezes an already tight calendar further. The association's position is that this makes completing the prescribed curriculum on time genuinely difficult, even as it directs members to comply fully.
Alongside the day count, the same directive asks schools to:
- Manage school hours carefully so the compression does not simply become a longer day for students.
- Integrate more ICT into teaching and learning to recover instructional capacity.
- Move trainings, workshops, competitions, parent days and PTA meetings onto Saturdays or Sundays, keeping weekdays for teaching.
- Collect fees strictly per Chapter 25 of the Education Act 2072 - monthly fees monthly, annual fees once a year, admission fees once from new students only, and additional fees only against specific services provided.
That last point is a fee-policy rule that happens to arrive in a calendar circular, which is exactly the kind of cross-cutting requirement that gets missed when the academic calendar and the fee ledger live in different systems.
The practical consequence for planning: with 220 days as a floor and roughly 40 more weekend days as a ceiling on available time, the slack that used to absorb an unplanned closure is largely gone. A school that loses a week to a strike, a local election, or a monsoon disruption no longer has an obvious place to recover it. Knowing your actual teaching-day count at any moment, rather than estimating it in Chaitra, stops being administrative hygiene and becomes a planning necessity.
Where the Exams Sit
The examination calendar is set nationally by the National Examination Board and anchors the end of the year.
SEE (Grade 10) falls at the close of the session, in Chaitra. The SEE routine for 2082 ran from Chaitra 19 to Chaitra 29, 2082 - April 2 to April 12, 2026 - with papers from 8:00 AM to 11:00 AM and 1,972 examination centres designated nationwide.
Grade 12 sits slightly later and crosses the year boundary. Per the NEB academic calendar for grades 11 and 12, the Grade 12 annual examinations for 2083 are scheduled from Baisakh 14 to Baisakh 27.
That crossover is worth noticing. Grade 12 exams for one cohort are being sat while the next session is already opening for everyone else, which means a school running grades 11 and 12 has two academic years live in the building at the same time. Any system that models "the current academic year" as a single global setting will represent that badly.
Internally, most schools then layer their own terminal examinations between these fixed points - commonly a first terminal, a second terminal, and a final - with results feeding report cards at each. If you have ever wondered why report cards take a week, part of the answer is that each of those checkpoints requires collecting marks from every teacher, computing NEB letter grades and GPA, and producing a printed document, three times a year, against a calendar that has no spare days in it.
The Dashain and Tihar Hole
The largest single feature of the Nepali school calendar is the festival break in the middle of it. Dashain and Tihar together remove a substantial block from roughly September to November, and because they are set by the lunar calendar they move relative to both AD and BS dates each year.
This is not a holiday that can be planned once and reused. It has to be re-derived annually, and everything downstream shifts with it: the second terminal examination window, fee due dates that fall inside the break, attendance percentage denominators, and any automated reminder that would otherwise fire while the school is closed.
The failure mode here is specific and common. A fee reminder scheduled by a fixed day-of-month rule will send during Tihar. An attendance report that divides by calendar days rather than teaching days will show every student at catastrophic absence rates for the month. Neither is a display bug - both are the system applying a Gregorian assumption to a calendar that does not work that way. This is the same class of error as treating missing attendance data as a zero rather than as "not marked".
Why Software Gets This Wrong
Almost every school platform sold into Nepal claims calendar support. The claims differ enormously in what they actually mean, and the differences are invisible on a slide.
Level one: a date picker that shows BS. The system stores and reasons in Gregorian, and a widget converts for input. Reports print AD. This is the most common form of "BS support" and it solves almost nothing, because the documents your office hands to parents and to the education office are still wrong.
Level two: BS on printed output. Report cards and receipts carry BS dates. Better, and it covers the visible surface. But the academic year boundary, term structure, and any date arithmetic still run on a Gregorian model underneath, so year-end rollover and promotion happen against the wrong boundary.
Level three: the calendar is the model. The academic session is defined in BS, terms are bounded by real festival dates for that specific year, teaching days are counted rather than assumed, and every human-facing surface renders BS while storage stays AD for correctness. This is the level at which a system can answer "how many teaching days have we actually delivered" without someone counting on paper.
The gap between level one and level three is not a feature checkbox. It is an architectural decision made early, and it is very hard to retrofit - which is why asking a vendor to generate a real report card with BS dates live on screen, rather than showing you a slide, separates the three levels in about thirty seconds.
What to Check in Your Own System
Whether you are evaluating something new or auditing what you already run, these are the questions that expose the difference:
- Generate a report card and an attendance report with BS dates, right now. Not a mockup, not a settings screen. The printed artifact is the test.
- Ask what the system thinks the academic year boundary is. If it is January or September, or if it is a single global value with grades 11 and 12 running a different year, the model is wrong.
- Set up a fee reminder and check where it lands during Dashain. A system that fires reminders into a two-week closure will train parents to ignore them.
- Ask how attendance percentage is calculated. Teaching days or calendar days? The two produce very different numbers, and only one of them is meaningful.
- Ask it for your teaching-day count so far this session. With a 220-day floor, this is now a number a principal needs on demand, not one to reconstruct in Chaitra.
- Check that the festival dates are per-year data, not hard-coded. Ask what happens next year when Dashain moves.
A system that handles all six is doing the calendar properly. One that handles the first two and fails the rest is doing BS display over a Gregorian engine, which will hold up right until the year-end rollover.
The Bottom Line
The Nepali school year runs Baisakh to Chaitra, is bounded by exams NEB sets nationally, is interrupted by a festival break that moves every year, and for the 2083 session has to fit at least 220 teaching days into a five-day week that started two weeks later than it used to. Nothing about that is exotic - it is simply the calendar the country runs on - but it is different enough from the Gregorian assumptions baked into imported software that the mismatch shows up in printed documents, absence percentages, fee reminders, and year-end rollover.
The schools that find this easy are the ones whose systems treat the calendar as the model rather than as a formatting option. The ones that find it painful are usually running something that converts dates at the edges and hopes the middle works out. Because the official dates for a session can and do shift, and because published sources are not always consistent with one another, confirm the operative calendar with your local level education office each year rather than carrying last year's assumptions forward.
Gurukul is built on the Bikram Sambat calendar rather than converted into it: academic sessions, terms, teaching-day counts and every printed document run in BS, with dates stored in AD so the arithmetic stays correct. See the platform or book a free demo.
