IEMIS Guide for Nepal Schools: How to Prepare and Submit Your Data

It's the third week of Shrawan, and the school's IEMIS coordinator - usually the accountant, sometimes the vice-principal, occasionally whoever complained the least in the staff meeting - has the CEHRD Excel template open in one window and last year's student register open in another.

Name. Date of birth. Grade. Section. Caste/ethnicity category. Ward number. Guardian's phone number. Four hundred rows to go, and it's only Tuesday.

None of this data is actually missing. It's sitting in the admission files, in the fee ledger, in the attendance register, in three different Excel sheets that three different staff members maintain their own way. It's just not sitting in the one format the government needs it in - so someone has to type all of it again, by hand, against a deadline that was announced two weeks ago and is due in one.

If you run a school in Nepal, you already know this week. It's IEMIS season, and it happens every year whether you're ready for it or not.

Some schools finish in a day. Others lose two weeks of the accountant's and the vice-principal's time to it, chasing down teacher certificates, recounting students grade by grade, and estimating fields nobody can find an exact number for. The gap between those two experiences has almost nothing to do with the size of the school, and almost everything to do with what its records looked like on the day the notice arrived.

What IEMIS Actually Is

IEMIS stands for Integrated Educational Management Information System. It's run by the Centre for Education and Human Resource Development (CEHRD), a government body under Nepal's Ministry of Education, Science and Technology, based in Sanothimi, Bhaktapur. CEHRD is the institution responsible for education planning, teacher management, and - through its EMIS section - the annual collection of school-level data from every school in the country.

In plain terms: IEMIS is Nepal's school census. Once a year, every community and institutional school in the country reports detailed data on its students, staff, and facilities to CEHRD. That data becomes the foundation for two national publications, Flash Report I and Flash Report II, which the government uses to plan budgets, allocate teachers, and track progress against national education targets.

The most recent published edition, the Flash I Report 2081 (2024/25), states its purpose plainly in the foreword: "Informed planning requires an effective data system." The report goes on to credit "the support of all schools across Nepal, the 753 Local Governments, the district-based Education Development and Coordination Units (EDCUs), the province-based Ministry of Social Development (MoSD) offices, and the Education Development Directorates (EDDs)" for making the numbers possible. That's the chain your school's Excel file travels through before it becomes a national statistic.

The system itself has existed in electronic form for well over a decade, having grown from a small pilot in a handful of districts to a nationwide rollout covering every district in Nepal. What used to be a paper-based headcount compiled by hand is now, at least in principle, a structured digital dataset covering every school in the country.

Why IEMIS Season Feels Like a Punishment

Here's the part that doesn't show up in any government document: for most schools, filing IEMIS is disproportionately painful relative to how much new information it actually requires.

Almost nothing asked for on the IEMIS form is new information. Your school already knows how many students are enrolled in Grade 6. It already knows which teachers are trained, which aren't, and which classrooms have a working toilet nearby. The form isn't asking you to go find out something you don't know. It's asking you to gather something you already know from six different places and retype it into one place, in a format you didn't choose, under a deadline you didn't set.

That's a data consolidation problem, not a data collection problem - and consolidation is exactly what paper registers and disconnected Excel sheets are worst at.

Consider the scale involved. The Flash Report is compiled from data passing through 753 local governments, dozens of district-level coordination units, and province-level offices before it reaches CEHRD - and every one of those numbers originates from an individual school's own records. School-by-school data is the hardest layer to get right in a system like this, precisely because it depends on hundreds of thousands of individual records being kept correctly, all year, by people whose actual job is teaching or running a school - not data entry.

There's also a staff turnover problem underneath this. The person who filed IEMIS last year is often not the person filing it this year - an accountant moves on, a vice-principal changes, a computer teacher who "was good with Excel" gets handed the job by default. Every handover loses a little institutional memory about which spreadsheet is the real one, which column means what, and which numbers were estimates versus confirmed counts. A school running on scattered files doesn't just lose time to IEMIS - it loses a bit of accuracy every time the person responsible for reconciling those files changes.

So the pain isn't really about IEMIS. It's about what your school's records looked like on the day before the notice arrived.

If your student list, attendance, and staff records live in one clean, current system all year, IEMIS is a formatting exercise. If they live in six places that don't talk to each other, IEMIS is a two-week emergency.

Two Schools, Same Deadline

Picture two schools of roughly the same size - around 450 students, 25 teaching staff - both receiving the same local-level notice in the same week: IEMIS data is due in ten days.

At the first school, student records live in a folder of Excel sheets that has been passed between three different admin staff over three years, each of whom added their own columns and renamed a few others. The attendance register is paper. Staff qualification certificates are in a physical file cabinet, and nobody is entirely sure whether the file for a teacher who joined last term is complete. The head teacher spends the first two days just figuring out which numbers are current - this term's enrollment, or last term's, since a dozen students transferred in and out over the year and nobody updated the master list consistently. Actual data entry into the CEHRD template doesn't start until day four. Two staff members stay late for a week. A few fields get filled in with the head teacher's best estimate, because getting the exact number would mean calling parents to confirm addresses that were never recorded properly in the first place.

At the second school, student records, attendance, fee status, and staff details have been kept in one system all year, updated as things actually happen rather than reconstructed afterward - a new admission entered the day it happens, a teacher's training certificate uploaded when it's issued, a transfer logged the week it occurs. When the IEMIS notice arrives, the head teacher doesn't need a week to find out how many students are currently enrolled in Grade 8, broken down by gender, or how many teachers have completed in-service training this year. Those numbers are already sitting in a dashboard, current as of that morning. The work that remains is real but bounded: pull the current figures, map them onto the government's specific field definitions and categories (which don't always match a school's internal terms one-to-one), and enter them into the CEHRD portal. It's a day of focused work, not a week of archaeology.

The difference between those two schools isn't effort, and it isn't which one cares more about accuracy. It's that one of them was doing data entry all year in small pieces, and the other tried to do a year's worth of data entry in one sitting, under deadline pressure, from memory and scattered paper.

Why This Data Actually Matters

It's easy to file IEMIS as one more bureaucratic requirement and move on. It's worth understanding what it's actually for, because that context changes how seriously a school treats the accuracy of what it submits.

Nepal's education budget, teacher deployment, and infrastructure investment decisions are made using this data. When CEHRD or a province-level education office decides which local levels need additional teachers, which schools qualify for scholarship disbursements, or where school infrastructure grants should go next, IEMIS numbers are a primary input. A Tech News Nepal report on the system quotes Nepal's education minister making this connection directly - that precise, timely school data supports policy formulation at the federal, provincial, and local level, resource distribution including funding and training, and even emergency preparedness planning for schools.

The Flash Report itself makes this concrete. It isn't just a headcount - it tracks Gross and Net Enrollment Ratios by gender, survival rates to Grade 10 and Grade 12, the share of Dalit and Janajati students enrolled, the share of students with disabilities, the percentage of teachers who've completed professional development training, and whether a school has the minimum physical facilities - toilets, a library, science and IT labs - to be considered functional. Every one of those figures is compared against national targets set under Nepal's School Education Sector Plan.

That has a direct, if indirect, consequence for your school. If your school under-reports enrollment because nobody had time to reconcile the transfer students, or over-reports because last year's number got copy-pasted without checking, that error doesn't stay local. It becomes part of a province-level or national figure that shapes budget allocation the following year - for your school and every school reporting alongside you.

This is also why data quality complaints about IEMIS aren't new. Independent reviews of Nepal's education management data have noted a recurring pattern: enrollment figures reported through EMIS-style systems tend to run higher than what independent household surveys find, a gap researchers generally attribute to schools carrying inactive or transferred students on their rolls longer than they should. That's not a technology failure. It's what happens when a school's "official" numbers are reconstructed once a year under deadline pressure instead of maintained continuously.

What Data Does IEMIS Actually Ask For?

The scope is broader than most people expect going in. Based on CEHRD's published Flash Reports, the categories a school is generally expected to report on include:

• Student enrollment, broken down by grade, gender, age, and caste/ethnicity category, including students from Dalit, Janajati, and other disadvantaged communities
• Students with disabilities, tracked separately at each grade band
• Internal efficiency, meaning promotion, repetition, dropout, and survival rates from one grade to the next
• Teacher and staff details, including qualifications, years of experience, employment type (government-approved, privately hired, grant-supported, or volunteer), and completed training
• Physical infrastructure, covering classrooms, toilets (including separate facilities where applicable), drinking water, library access, and science and IT labs
• School governance, including whether the school has a current School Improvement Plan and completed social or financial audits
• Scholarships and support programs, including pro-poor targeted scholarships by grade
• Early Childhood Education and Development (ECED) enrollment where applicable, for schools that run a preschool-level class

That's not a form you fill in from memory. It's a form that assumes your school has been keeping structured, disaggregated records on all of the above throughout the year - which, for most schools, is precisely the assumption that doesn't hold.

What Happens to Your Data After You Submit It?

Once a school's IEMIS data is uploaded, it doesn't stay at the school level. It moves up through the local level education office, gets aggregated at the district and province level by the EDCUs and MoSD offices mentioned above, and eventually feeds into the national Flash Report I and Flash Report II publications CEHRD releases each year.

Those reports aren't filed away and forgotten. They're the reference documents used to set the following year's targets under Nepal's School Education Sector Plan, to decide where teacher positions get approved, and to track equity indicators - gender parity, Dalit and Janajati enrollment share, disability inclusion - against national goals. A province education office deciding where to prioritize a scholarship program or a school infrastructure grant is working from numbers that trace back to exactly this kind of school-level submission.

That's also part of why data quality checks exist at the local level before figures are finalized - numbers that look implausible compared to the previous year, or fields left blank, are the kind of thing a reviewing office is likely to flag and send back. Schools with clean, consistent records are less likely to trigger that kind of follow-up. Schools reconstructing numbers under deadline pressure, with a few estimated fields mixed in, are more likely to.

What "Clean and Continuous" Records Actually Look Like

The schools that treat IEMIS as a non-event share one habit: they don't think of it as "the government form we fill out in Shrawan." They think of student and staff records as something maintained every day, and IEMIS as one of several things that record eventually gets used for.

In practice, that means a few specific things are true year-round, not just during filing season:

Every student has one current record, not several. When a student transfers in, is admitted, or leaves, that's updated once, in one place - not in the admission register, then separately in the class teacher's Excel sheet, then separately again in the fee ledger. A proper student information system keeps one profile per student that every other module - attendance, fees, exams - reads from, instead of each department keeping its own copy that drifts out of sync with the others.

Attendance and demographic data are captured as structured fields, not free text. "Dalit" typed three different ways across three sheets isn't a structured field, it's a data cleanup project waiting to happen. When categories like caste/ethnicity, disability status, and address are entered once into defined fields, they're already in a form that maps cleanly to a government census category later. This is sensitive data by definition, which is also a reason it belongs in a system with proper access controls rather than a shared spreadsheet anyone with the file can open - the same student data privacy concerns that apply to attendance and fee records apply just as much to the demographic fields IEMIS asks for.

Staff records are kept current, not reconstructed. Teacher qualifications, training completions, and employment type change during the year - a new certificate, a training course finished, a transfer. If those are logged when they happen, the school always has an accurate answer to "how many of our teachers have completed in-service training this year," instead of needing to dig through a filing cabinet to reconstruct it in Shrawan.

Reports can be generated on demand, not compiled by hand. A school that can pull "current enrollment by grade and gender" or "attendance rate for the year" as a report in a few clicks has already done most of the mapping work IEMIS requires. A school that has to manually count from paper or reconcile five spreadsheets hasn't - no matter how accurate the underlying records actually are.

None of this is specific to IEMIS. It's the same discipline that makes a digital attendance system or a proper school management platform worth adopting in the first place. IEMIS just happens to be the one deadline every school in Nepal shares, which makes it a good forcing function for noticing whether your school's records are actually in order the other 364 days of the year.

Can School Software Fill Out IEMIS For You?

It's worth being honest about what school management software does and doesn't solve here, because this is where a lot of vendor claims get ahead of reality.

No school management platform, Gurukul included, has a literal one-click button that submits data directly into CEHRD's IEMIS portal. IEMIS is a government system with its own template, its own field definitions, and its own upload process, and it isn't open to third-party software integrations. That submission step - entering figures into the government's format and uploading through the official portal - stays a manual, human task, done by whoever is designated as your school's IEMIS focal person.

What good school management software does change is everything upstream of that step. If your student records, staff records, and attendance data live in one continuously updated system instead of six disconnected ones, the work of finding the correct current numbers - which is where most of the two weeks of IEMIS pain actually goes - shrinks from days to minutes. You're no longer reconciling three versions of a spreadsheet or guessing whether last term's transfer got recorded. You're reading a number off a dashboard, checking it against the government's category, and typing it into the CEHRD form.

That's a meaningfully smaller job. It's not "IEMIS in one click." It's "IEMIS without the archaeology" - which, if you've lived through a bad IEMIS week, is most of what actually hurts.

Where a system like Gurukul does help directly is in producing the underlying figures fast: current enrollment by grade and section, attendance summaries, teacher rosters with training and qualification status, all available as reports rather than as something someone has to manually tally. Getting from "here's our data" to "here's our data in the government's format" is still a manual mapping step. Getting from "let me check five places" to "here's our data" doesn't have to be.

How to Prepare for This Year's IEMIS Submission

If your school's IEMIS week has historically looked like the first school in the comparison above, a few concrete changes make the difference before the notice even arrives:

1. Designate one IEMIS focal person, and give them access to everything. Attendance, fees, and student records shouldn't be split across three staff members' personal files when the deadline hits. One person should be able to pull every category CEHRD asks for without needing to track down colleagues.

2. Reconcile your enrollment list quarterly, not annually. Transfers, dropouts, and new admissions should be updated in your master student list as they happen. Waiting until IEMIS season to figure out who's actually still enrolled is where most of the delay comes from.

3. Keep staff qualification and training records in one place, updated as they change. A teacher completing a training course or submitting a new certificate should be logged that week, not chased down months later.

4. Standardize your categories now. Caste/ethnicity, disability status, and address fields should use one consistent format across every record your school keeps - not three different conventions across three different spreadsheets. This alone removes a large share of the manual cleanup that eats into IEMIS week.

5. Do a dry run before the deadline. A week or two before your local level's IEMIS notice typically arrives, pull the numbers CEHRD will ask for and see how long it takes. If it's still slow, you know exactly which records need attention before the real deadline lands.

None of these require new software to start doing. They require treating your school's data as something that's maintained continuously, which is a habit - not a purchase. Software makes that habit easier to keep, but it doesn't replace the decision to keep it.

Gurukul keeps your student records, attendance, staff details, and reports current year-round, so when IEMIS season arrives, you're pulling numbers instead of reconstructing them. Book a free demo →