IEMIS Student Data: What to Keep Ready All Year

Most schools experience IEMIS as a reporting problem. It is usually a records problem wearing a reporting costume. The forms are only hard to fill when the numbers they ask for do not exist anywhere in a form you can trust, and have to be reconstructed from registers, memory and a spreadsheet somebody kept privately.

This guide is about the layer underneath the submission: the student records themselves. What they need to hold, where each figure should be traceable to, and the specific faults that quietly accumulate during the year and then surface as errors under deadline. For the submission process itself, see the step-by-step reporting guide. As always, the authoritative list of indicators for any given cycle comes from CEHRD or your local education office, not from here.

The rule that makes everything else easier

If a number cannot be traced to a register, a payroll record or a physical count, it is an estimate. Estimates are what get questioned.

Every figure a school reports should have a source you could point at if someone asked. Not a recollection, not last year's number adjusted by feel. When the school can answer "where did this come from?" for each line, the reporting step becomes transcription. When it cannot, reporting becomes negotiation, and reviewers can tell.

The student records worth keeping current

The exact indicators change between cycles, but the underlying records that feed them are stable. These are the ones that repay being kept accurate as the year runs rather than assembled at the end.

Identity and enrollment

• Full name as it should officially appear, recorded once and used consistently, rather than a slightly different spelling in each register.
• Date of birth, with a clear note of whether it is recorded in Bikram Sambat or Gregorian. Mixing the two silently is one of the most common sources of nonsense ages in a dataset.
• Gender, grade and section, kept current as students move rather than corrected in bulk at year end.
• Date of admission, and the class the student was admitted into.
• Whether the student is repeating the grade, which is reported separately from new enrollment in most cycles.

Movement in and out

• Transfers in, with the date and, where you have it, the previous school.
• Transfers out and dropouts, with the date and the reason as far as the school knows it. A dropout recorded without a date cannot be attributed to the right reporting period.
• Readmissions, which are easy to double-count as new enrollment if the earlier record was never closed.

Support and category data

• Scholarship or stipend recipients, with the category and the period covered.
• Any disability or special-needs information the current cycle asks for, recorded with care and shared only with staff who need it.
• Guardian details, kept as a proper relationship rather than a name scribbled in a margin, so a student with two guardians or a guardian with three children is represented correctly.

The faults that cause rework

These are the ones that survive a casual look and only surface when the totals refuse to reconcile.

1. 1The same student entered twice, usually because the name was spelled differently the second time, or because a readmission created a fresh record instead of reopening the old one.
2. 2Mixed BS and AD dates in the same column, which produces students who are apparently forty years old or not yet born.
3. 3Section changes made in one register and not another, so grade totals and section totals disagree.
4. 4Dropouts and transfers recorded without a date, which makes them impossible to assign to a reporting period.
5. 5Guardians duplicated once per child, so a family of three appears as three unrelated guardians and any count of families is wrong.
6. 6A student who left months ago still counted as enrolled because nobody closed the record.

Checking without waiting for the deadline

A short, boring review once a term catches nearly all of the above while it is still cheap to fix.

• Reconcile the grade totals against the section totals. They should agree exactly; if they do not, something moved in one place and not the other.
• Sort by date of birth and look at both ends. Impossible ages are almost always a calendar-system mix-up.
• Sort by name and scan for near-duplicates. Two students one line apart with nearly the same name is usually one student.
• List students with no recorded guardian, and students whose admission date is missing. Both are small lists, and both cause problems later.
• Compare this term's enrollment against last term's, and be able to explain every movement in the difference.

Where software helps, and where it does not

Software cannot make a school's data true. What it can do is make the faults above hard to create in the first place: one record per student rather than one per register, guardians stored as relationships and de-duplicated on import, dates held in a single calendar system with the Nepali one as a display choice, and movements recorded with dates because the system asks for them.

That is the honest claim to make about school software and IEMIS. It does not submit for you, and no software should tell you it does. It changes how ready your numbers are when you sit down to report.