Dadra and Nagar Haveli and Daman and Diu is administered as one Union Territory, but it does not behave like one place. Its three districts do not touch each other: Dadra and Nagar Haveli sits inland with Silvassa at its centre, Daman is a coastal enclave, and Diu is an island off the Saurashtra coast. Between them lie Gujarat and Maharashtra.
For a school administrator, that geography is the whole story. Every assumption a school management system makes about “one campus, one office, one language” has to be checked here.
One territory, three districts, no shared border
According to the UT administration’s own portal, Dadra and Nagar Haveli covers about 491 square kilometres across 72 villages with a population of roughly 3.44 lakh; Daman covers about 72 square kilometres with roughly 1.91 lakh people; and Diu covers about 40 square kilometres with roughly 52,000 people.
School education across all three is administered by the Directorate of Education of the UT Administration, headquartered at Shiksha Sadan, behind the Collectorate, Moti Daman.
The practical consequence is that a trust or an administration running institutions in more than one district is running them at real distance, without shared staff and often without shared infrastructure. Software chosen here has to work for a school office that cannot walk down the corridor to ask.
Four languages in a very small school system
PARAKH Rashtriya Sarvekshan 2024, the NCERT national assessment conducted under the Department of School Education and Literacy, administered its survey in this territory in four languages: English, Gujarati, Hindi and Marathi. The UT’s own official portal operates in English, Hindi and Gujarati.
The scale is genuinely small. In the same survey, 65 schools participated at Grade 3, 71 at Grade 6 and 76 at Grade 9, with 157, 208 and 299 participating teachers respectively. The survey covered state government, government-aided, private and central government schools.
Four languages across a system that size is unusual, and it points at the real communication problem: a single circular in a single language will not reach the parent body. The right architecture separates the staff console language — which staff are trained on and which can reasonably be one or two languages — from the language a parent actually receives a message in, which should follow the parent.
Central mandates apply in full
A Union Territory does not get a lighter compliance load. The Right of Children to Free and Compulsory Education Act, 2009 applies, including the Section 12(1)(c) reservation of twenty-five per cent of entry-level seats in private unaided schools for children from weaker sections and disadvantaged groups, and free education for them to Class 8. UDISE+ reporting applies. Board affiliations bring their own record-keeping requirements, and national assessments such as PARAKH reach schools here as they do anywhere else.
What differs is capacity. A small directorate and small school offices mean the same obligations are met by fewer people. That is an argument for systems that produce required reports as a by-product of daily work, rather than requiring a data-collection exercise every time a return falls due.
What software has to do differently here
Five things worth testing specifically:
- District separation with a territory-level view. Each school’s data should be genuinely isolated, with its own users and its own books, and any consolidated view built from those rather than maintained alongside them.
- Multiple mediums in the same institution. A school with Gujarati-medium and English-medium sections needs subject sets and report card templates that differ per section, drawing from one marks store.
- Parent messaging that follows the parent. Not a language setting on the school, a language that follows the person you are writing to.
- Low-bandwidth reality. Check what the parent-facing experience is on a modest handset over a patchy connection, not on the demo laptop.
- Reports as a by-product. Ask to see attendance summaries, enrolment counts and fee status produced from live data without a preparation step.
How EdunodeX handles a multi-district territory
- Each school is its own tenant. Every school gets an isolated database schema and its own subdomain, with its own users, academic years, fee heads and grading systems. A user for one school is not a user for another.
- Fees in one ledger per student. Fee items with categories and recurrence, class-level fee plans, installment schedules, transport and hostel as recurring subscriptions, grace days and late-fee formulas, concessions written to the affected installments with an audit record and reversible, waivers, write-offs, settlements and reversals. Amounts are stored as integers in paise, and receipt numbers come from a database sequence in the form
RCP-YYYYMMDD-XXXXX. - Collection that works at a small counter. Cash, UPI, bank transfer and cheque with a running tally of who collected what today. Partial payment is a school-level setting; when enabled, an amount below the selected total is allocated oldest-due-first. Online payments run through the school’s own Razorpay or Cashfree account, with secrets encrypted and each school’s webhook verified with that school’s own secret.
- Parent messaging in the parent’s language. WhatsApp through Meta Cloud API or MSG91. Replies come back in the language the parent wrote in — Gujarati, Hindi and Marathi included — with amounts, dates and names computed in code and preserved verbatim rather than regenerated by a model. Business-initiated messages use Meta-approved templates only, per-guardian opt-in is recorded, and STOP and START keywords toggle it in real time. The staff console ships in English and Hindi, alongside Tamil and Kannada.
- Academics per section, not per school. Classes carry stage and capacity, sections carry a class teacher and room, subjects are defined per class with electives, and grading systems for CBSE, ICSE and state patterns coexist. Report card templates are configurable.
- Attendance with consent where it involves biometrics. Face and biometric attendance require a recorded consent status before the data is accessible, and the check sits inside the query rather than only at enrolment.
- Reporting that already exists. A rules-driven compliance engine with state-specific overrides re-evaluates weekly and produces a per-category report with CSV export, and there is a UDISE export for government reporting.
Practical checks before you choose
- Ask for two schools in two districts set up in the same account, and confirm a user for one cannot open the other.
- Send a fee reminder to a test number and look at what arrives, in Gujarati.
- Ask what happens when the internet drops mid-collection — specifically, whether a receipt can be issued twice.
- Ask how you export all of your own data, in what format, and how long it takes.
- Ask what support looks like from a district that is not on the vendor’s usual travel route. Remote onboarding is the norm here, not a fallback.
On tax: fees for education up to higher secondary at a recognised institution are exempt from GST under Entry 66 of Notification No. 12/2017-Central Tax (Rate) dated 28 June 2017, covering tuition, admission, examination, hostel and transport supplied to its own students. Your fee system should not be adding GST to those heads.