If you are evaluating school management software in Nepal, at some point a vendor will tell you their system is IEMIS-ready. It is worth knowing what that can honestly mean, because the phrase covers everything from a genuinely useful set of features to nothing at all.
Start here
No private software submits your data to IEMIS for you. Submission runs through official CEHRD and local education office channels, using your school's own credentials. Any vendor who implies otherwise is either confused about the process or hoping you are.
What IEMIS-ready can honestly mean
Set aside submission, and there is still a real and useful meaning. A system that helps with IEMIS is one where the data you are asked to report is data the system already holds, correctly, without a reconstruction exercise first.
- It holds the fields the reporting cycle asks about, rather than a generic international schema that omits half of them.
- It keeps enrollment current as students move, so a grade total is a lookup rather than a count.
- It records movements with dates, so transfers and dropouts can be attributed to the right period.
- It handles Bikram Sambat dates properly rather than leaving staff to convert by hand.
- It can get your numbers out — on screen, printed, or exported — in a form a person can read alongside the form they are filling.
- It resists the data faults that cause rework: duplicate students, duplicated guardians, records left open after a student has left.
Questions worth asking
Ask these in a demo, and ask to see the answer rather than hear it. A vendor who cannot show you within the product is telling you something.
- Show me where a student's date of birth is stored, and how the system knows whether that is BS or AD.
- Show me this class's current enrollment, broken down by gender, as of today.
- A student transferred out last month. Show me how that was recorded, and show me that they no longer count as enrolled.
- Two guardians in your system are the same person entered twice. What happens when I import a list where that occurs?
- Can I get the underlying data out of your system, in a readable form, without asking you to do it for me?
- If we leave you in three years, what exactly do we take with us, and in what format?
- Which of the fields our local education office asks about does your system not hold?
The last two matter most
Export and exit are the questions vendors are least prepared for, and the ones that cost the most if the answer turns out to be bad. A school's records should never be hostage to a subscription. Ask early, while you still have leverage.
Claims that should slow you down
- “We submit to IEMIS automatically.” No private system does. At best they mean they prepare a file for you to use.
- “We are approved by CEHRD” or similar, offered without documentation. Ask to see it, in writing, and check what it actually covers.
- “Government-integrated.” This can mean almost anything. Ask precisely what integrates with what, and what happens when the government side changes.
- Pricing that only appears after a meeting. It is not a scandal, but transparency here tends to predict transparency elsewhere.
- No answer to the export question, or an answer that involves a support ticket and a fee.
Where we stand
For the sake of being held to the same standard: NepEdu does not submit anything to IEMIS, and will not claim to. What it does is hold student and staff records with the Nepal-specific fields schools are asked to report, keep them current as the year runs, handle BS dates throughout, de-duplicate guardians on import, and let a school get its data out.
That is a smaller claim than “IEMIS-integrated”, and it is the one that is true. If another vendor makes a larger claim, the questions above are a reasonable way to find out whether it survives a demo.
Judge us by the same questions. Ask us any of them and we will show you rather than tell you.
Talk to us