Skip to content
All articles
Web Development7 min read

Education management information system: the KUSOED case

What a university's education management information system has to record, from first application to result, with the KUSOED EMIS we built as the case.

EK

EK Ra Sunya team

EK Ra Sunya Inc.

An education management information system (EMIS) for a university has to record a student's whole path in one place: the application, the admission decision, the student record and batch, every fee paid, and every result. At Kathmandu University School of Education (KUSOED), that is what EMIS does. It also enforces the rules between departments, such as no result before the fee is verified.

That second part is where most of the value is. Storing records is easy. Making the finance office, the exam department and the admissions team agree on one set of facts is the actual job.

Why did KUSOED need an EMIS?

KUSOED is one of the country's leading education faculties. Before EMIS, it managed student records, academic performance and institutional reporting across disconnected tools and spreadsheets. Leadership had no single, reliable view of the school's own data, and routine reporting was slow and manual.

A spreadsheet can hold a student list. It can't stop a result being released to someone who hasn't paid, and it can't tell you which of two copies of the fee sheet is the true one. If your school is in the same place, the question isn't "which software" yet. It's "which rules do we keep breaking because nothing enforces them".

We built EMIS as one system for the school: a web app and an API, with a Flutter mobile app alongside. It has been live since 2025 and is still in active development. The EMIS project page has the summary.

What should an education management information system record?

Here is what KUSOED's EMIS covers, taken from the project page, with what each part means for anyone planning their own.

AreaWhat EMIS does at KUSOEDWhat to decide if you're planning one
AdmissionsApplicants apply and are tracked through admissionsWhich stages an application passes through, and who moves it on
Student recordsAdmitted applicants become student records, organised by batchWhat a batch means for you (intake year, programme, both)
ResultsPublished only after fees are verifiedWhich department's "yes" a result waits for
PaymentsKhalti payments reconciled with university revenueWho owns reconciliation, and what counts as paid
NotificationsEmail and SMS keep applicants and students informedWhich events trigger a message, and to whom
FinanceA secure finance integration API serves the finance teamWhich system is the source of truth for money
AccessRole-based access for 10+ roles, from applicants to the exam departmentWho can see and change each record
ReportingEnrolment analyticsWhich numbers leadership asks for every term

The table reads like a feature list, but each row is really a decision someone at the university has to make. Software can enforce a rule. It can't choose it for you.

Why should an applicant become a student record, not a new entry?

At KUSOED, applicants are tracked through admissions and then become student records organised by batch. The applicant and the student are the same person in the same system.

Our advice: insist on this in any EMIS you buy or commission. If admissions lives in one tool and student records in another, someone re-types names, dates of birth and contact details at the point of enrolment. Every re-typed field is a chance for two versions of one person.

Batches matter for the same reason. Most of what a faculty does (timetables, exams, results, fee schedules) happens to a group of students at once. A system that organises records by batch lets staff act on the group without exporting a list to a spreadsheet first, which is exactly the habit an EMIS is meant to end.

What happens to the records you already have?

About 5,700 existing student records were migrated into EMIS at KUSOED. It is why admissions, records, results, fees and enrolment analytics now sit in one system, rather than the new system covering only new intakes.

If you're planning an EMIS, treat migration as its own piece of work, with its own owner, not as a step at the end. Some advice for that planning:

  • Decide early whether old records come in at all. A system that starts empty leaves staff checking two places for years.
  • Agree what a clean record looks like before anyone starts moving data, so the old files can be checked against it.
  • Expect the old data to disagree with itself. Plan for spreadsheets kept by different offices not matching. Someone with authority has to decide which version wins.
  • Test with real records, not samples. Our user acceptance testing checklist covers how to have staff sign off on what they actually use.

Student records are also personal data under Nepal law. The Privacy Act, 2075 (2018), often called the Individual Privacy Act, lists a person's education or academic qualification as personal information, and section 12 says data collected with consent is to be used only for the purpose it was collected for. Read the Act itself, and take your own legal advice on what it means for your institution.

How many user roles does a university EMIS need?

KUSOED's EMIS has more than ten, from applicants at one end to the exam department at the other. That range is the point. An applicant should see their own application and nothing else. The exam department needs results across a batch. The finance team needs payments, not grades.

When you list roles for your own system, start from people and what they must never see, not from screens. A short list of "this role can't change that" usually tells a developer more than a long list of permissions.

Why publish results only after fees are verified?

This is the rule we'd point to if someone asked what makes EMIS a university system rather than a database. At KUSOED, results are published only after fees are verified, and Khalti payments are reconciled with university revenue.

The rule only works if "verified" means something exact. For online payments, the gateway's own documentation should define it. Khalti's ePayment docs tell merchants to use the lookup API for final validation of a transaction, and to treat only a "Completed" status as a successful payment. Pending payments are to be held, not treated as paid.

Our advice for anyone planning a fee-gated result:

  1. Write down what "fee verified" means for each way a student can pay, online and otherwise.
  2. Make the gate automatic. If a person has to remember to check, the rule will be broken in the busiest week of the year.
  3. Give the finance team its own view. At KUSOED, a secure finance integration API serves the finance team, so money is checked where money is managed.
  4. Decide who can override the gate, and make sure the system records who did it.

Does a university EMIS need a mobile app?

Not always. KUSOED's EMIS runs as a web app and an API, with a Flutter mobile app alongside.

Flutter builds mobile, web, desktop and embedded apps from a single codebase. If you're weighing a mobile app, a single codebase is worth asking about, because it is one less thing for a small IT office to maintain. We compared it with the main alternative in Flutter vs React Native. The web side is built with Next.js, React, TypeScript, Node.js, Express and PostgreSQL.

Email and SMS notifications sit alongside both, so an applicant doesn't need to open either app to learn something changed.

Frequently asked questions

Is an EMIS the same as a student information system?

The terms overlap. A student information system usually means student records. At KUSOED, EMIS also covers admissions, fee-gated results, payment reconciliation, a finance integration and enrolment analytics, so it runs more of the school than records alone.

Is EMIS finished?

No. It has been live since 2025 and is still in active development. A university's rules change every year, so plan for a system that changes with them.

Can an EMIS take online fee payments in Nepal?

KUSOED's does, through Khalti, with payments reconciled against university revenue. Whichever gateway you use, follow its own documentation on how to confirm a payment before treating it as paid.

Do we have to move all our old records?

You decide. KUSOED migrated about 5,700 existing student records so that one system holds the full picture. Leaving them out is possible, but then staff have to check two places whenever they need an older student's history.

Planning an EMIS for your school or university

We build web apps, APIs and Flutter apps for education and admissions work. See how that looks in education and admissions, or read about our web development work. If you're scoping an EMIS, tell us what your school needs to record.

Have a project in mind?

Let us help you build something scalable, fast, and built to last.

Start a conversation