Manipur schools run their academic year against two separate examination bodies, and against a registration calendar that has repeatedly been extended rather than fixed. Software chosen for a school here has to survive both.
Two boards, two portals
Secondary and higher secondary examinations in Manipur are not administered by a single body. The Board of Secondary Education, Manipur (BOSEM) handles Class 9 registration, Class 10 enrolment and the High School Leaving Certificate examination. The Council of Higher Secondary Education, Manipur (COHSEM) conducts the higher secondary examination. Results for both are published through manresults.nic.in.
For a school office this means two sets of credentials, two sets of forms, and two sets of deadlines — for the same student, eighteen months apart. Any system that assumes one board per school will force the office back into spreadsheets at exactly the point where accuracy matters most.
Registration and enrolment deadlines that move mid-year
BOSEM’s own notice board records an extension to the registration and enrolment process for Classes IX and X for the academic session, issued on 27 July 2026. This is not an isolated event; extensions are a normal feature of the calendar here.
The practical consequence is that a school cannot treat “registration closed” as a fixed date baked into a process. The office needs to be able to pull a current, accurate list of students by class — with names, dates of birth and parent details as they will appear on the board record — repeatedly, at short notice, without re-keying.
APAAR becomes mandatory from the 2027-28 session
A BOSEM notice dated 1 July 2026 makes APAAR ID generation mandatory for students of BOSEM-recognised institutions from the academic session 2027-28.
Read the date carefully: the requirement is two sessions out, not immediate. That is useful, because the work that actually blocks APAAR generation is record hygiene — a student’s name, date of birth, gender and parent names have to match across the school record, the Aadhaar record and the UDISE+ student record. Schools that spend the current session cleaning those fields will generate IDs in a batch later. Schools that wait will discover the mismatches one rejection at a time.
Be clear-eyed about what software does here. EdunodeX ships a UDISE data export and a rules-based compliance report that flags missing mandatory fields. It does not submit APAAR IDs into UDISE+ on your behalf: that pipeline exists in the backend but runs against mock endpoints until a school supplies its own UDISE+ credentials, and its operator screen is not currently reachable in the application. Anyone selling you automated APAAR submission today should be asked to demonstrate it end to end.
Students who arrive mid-session
BOSEM publishes a separate application form for internally displaced students for Class IX registration and Class X enrolment — a notice dated 2 March 2026 sits alongside the ordinary forms on the board’s portal.
That is a real operational category, not a footnote. A school may admit a student partway through the year with incomplete paperwork, from a school that cannot readily issue a transfer certificate, and still have to place that student on a board register before a deadline. The office needs: an admission path that accepts a partial record and completes it later, a document vault that holds whatever proof did arrive, and a clear view of which students are still missing a mandatory field.
What EdunodeX does for a Manipur school
- Admissions that tolerate incomplete records. The admission wizard accepts a partial student row and lets the office fill gaps later; every uploaded document lands in the document vault regardless of how well it scanned. Bulk CSV/Excel import with guardian de-duplication handles season-start intake.
- One student record, both boards. Demographics, guardians, class history, marks and documents live on a single profile, so producing a board-format list is an export rather than a re-typing exercise.
- Transfer certificates and study/bona-fide certificates with serial numbering, for students moving in or out mid-session.
- Fees. School fees for recognised pre-school to higher-secondary institutions are exempt from GST under Entry 66 of Notification 12/2017-Central Tax (Rate), 28 June 2017 — covering tuition, admission, examination, hostel and transport. For collections, zero MDR on BHIM-UPI person-to-merchant payments has applied universally since January 2020 under section 10A of the Payments and Settlement Systems Act and section 269SU of the Income-tax Act; it is not an education-specific concession. NPCI’s education-specific rule is the ₹5,00,000 per-transaction UPI limit, which matters for annual or term fee payments.
- Offline-tolerant attendance. The native teacher Android app marks attendance offline and syncs when a connection returns; the web app runs as a PWA with an offline banner.
Meitei-language parent communication: what works and what does not
Be precise about this, because vendors are usually vague.
The EdunodeX administrative interface ships in English, Hindi, Tamil and Kannada only. There is no Meitei/Manipuri interface bundle, and we are not going to claim one.
What does work in other languages is the WhatsApp bot: replies are generated in the language the parent wrote in, with the factual content — fee amounts, marks, dates, names — computed in code and passed through verbatim rather than generated by a model. Only the wording is localised. If the language model is unavailable, the reply falls back to English rather than being dropped.
So: a Manipur school gets English or Hindi for its staff-facing screens, and can answer parents in the language they write in over WhatsApp. If a Meitei-script staff interface is a hard requirement, EdunodeX does not meet it today.