KEMIS and Your Learner Roster: Keeping Ministry Data Clean Without Retyping It
Every school administrator who worked through NEMIS has a story. The portal that would not load in the last week before a deadline. The learner whose birth certificate number did not match. The transfer that never arrived because the previous school had not released the record. The capitation figure that seemed to depend on how many learners the system believed the school had, rather than how many were in the classrooms.
The Ministry of Education is now moving schools from NEMIS to KEMIS, the Kenya Education Management Information System. The new system is meant to be a single national record for learners across early years, basic education, TVET and university, linked to civil registration so that each learner carries a Unique Personal Identifier from early in life. Reporting in 2026 has also made clear that the transition is not finished: news coverage in September 2026 described delays, funding constraints and technical problems, including difficulties that affected Grade 10 selection.
Whatever happens with the national system, one thing is in the school's control: the quality of its own learner records. A school whose roster is accurate, complete and in one place spends hours on a Ministry submission. A school whose data is scattered spends weeks. This article is about being the first kind of school.
What is changing, and what is not yet clear
The broad direction is public. KEMIS is intended to replace NEMIS, cover learners across the education system, and connect to national registration records. The Ministry has said it aims to use it to track learners accurately and remove ghost learners from the count, which matters because capitation and other allocations depend on enrolment figures.
What is less clear, as of October 2026, is the detail of how and when every function will work for every school. Reports have described the system going live at the start of 2026 and, later in the year, as not yet fully implemented. Schools should follow official Ministry of Education communication and their sub-county and county education offices for current instructions, rather than relying on summaries, including this one.
What has not changed is the information the Ministry needs about each learner: who they are, their identifiers, their date of birth and sex, the school and class they are in, their status, and who their parent or guardian is. Those facts have to be right in the school's records before they can be right anywhere else.
No national system can be more accurate than the school records it is built from.
The UPI is the key that must not be lost
The Unique Personal Identifier is the number that follows a learner from school to school. When it is correct, a transfer is a matter of moving a known record. When it is missing or wrong, the learner effectively appears as a stranger, and the receiving school starts again from paper.
Every school should know, at any moment, which of its learners have a UPI recorded and which do not. That list is the school's to-do list for Ministry compliance. New admissions, particularly in January, are the usual source of gaps: a learner arrives without documents, or with a UPI written on a transfer letter that nobody enters. A clear rule helps: the UPI is entered at admission, or the learner is flagged until it is.
It also helps to record the UPI in the same place as the learner's other details, rather than in a separate spreadsheet kept for the Ministry. Two copies of the same fact drift apart. One copy, used for everything, stays right.
Clean data is a habit, not a project
Most data problems in Ministry submissions come from a handful of causes, and each has a simple habit that prevents it.
Spelling and name order differ between the birth certificate, the admission form and the class list. Fix this by entering names exactly as they appear on the official document at admission, with first, middle and last name in separate fields. Dates of birth are entered in different formats, or guessed. Fix this by requiring the date from a document, not from memory. Learners who have left remain on the roll. Fix this by recording every exit, whether transfer, withdrawal or completion, on the day it happens, with the date and reason. Guardian contacts go stale. Fix this by checking them at the start of each year, which also helps every other communication the school sends.
None of these is difficult on its own. They fail because they are left to the week before a deadline. A school that applies them daily never has a catch-up exercise.
The roster as a file, in the right shape
Schools are often asked to provide learner lists in a particular layout, whether for upload to a portal, a county exercise, or a verification visit. Producing that list by hand from a class register is slow and error prone.
The better approach is to keep the learner record complete and produce the roster from it whenever needed, as a file with one row per learner and the columns the Ministry asks for. Learners without a UPI should appear on that file with the field blank, rather than being dropped, because the purpose of the exercise is often to find exactly those learners. Before any upload, compare the file's column order and headings with the template your county or the portal currently requires, since templates can change.
Treat the roster as sensitive
A full learner roster is every child in the school, with dates of birth and a parent's phone number, in a single file. It is the most useful file a school holds for a legitimate Ministry exercise, and also the most attractive one to anyone who should not have it.
Under the Data Protection Act, 2019, children's data needs particular care, and the school, as data controller, is responsible for how it is shared. Practical rules follow. Limit who can produce the full roster to a small number of named staff. Require strong sign-in for that action. Keep a record of each time it is produced and by whom. Do not send it through personal WhatsApp or email accounts, and delete copies from desktops and phones once the upload is done. For more on the school's role as controller, see who owns your school's data.
The roster is the file a school needs a few times a year and an attacker would want every day. Treat it accordingly.
Transfers in and out
Transfers are where national data most often breaks. A learner leaves one school and arrives at another, and the national record has to follow. Under NEMIS, schools grew used to transfers that stalled because the releasing school had not acted. Whatever process KEMIS settles on, the school can protect itself on both sides.
When a learner leaves, record the exit on the day, with the date, the reason and the receiving school if known, so the learner does not linger on your roll and your enrolment count is correct. When a learner arrives, record their UPI from the transfer documents at admission, and flag them if it is missing. A transfer recorded promptly on both sides is one less discrepancy for the Ministry, and one less learner whose records are lost between schools.
Where Opero fits
Opero holds each learner's details, including the UPI, admission number, names, sex, date of birth, class, curriculum, status and linked guardians, in one record. It produces a Ministry roster as a CSV file with one row per learner: UPI, admission number, first, middle and last name, sex, date of birth, class, curriculum, status, and a guardian's name and phone. Learners without a UPI are included with the field blank, and Opero reports how many are missing so the office can chase them.
Producing the roster requires the export permission, two-step sign-in, is rate limited, and is recorded in the audit trail, because it is every child in the school in one download. Opero does not connect to KEMIS or upload anything to it; as far as we know, KEMIS does not offer an integration interface for school systems, and the school uploads or enters data through the Ministry's own channels. Check the file's columns against the current template before you upload. What Opero removes is the retyping, as part of the learner records the school already keeps.
Key takeaways
- KEMIS is replacing NEMIS, but reporting in 2026 shows the transition is incomplete; follow official Ministry and county instructions.
- The UPI is the learner's key across schools. Record it at admission and keep a list of who is missing one.
- Prevent data errors daily: names as on documents, real dates of birth, exits recorded on the day, guardian contacts checked yearly.
- Produce the roster from the learner record when needed, rather than maintaining a separate spreadsheet.
- Treat the full roster as sensitive: limit, record and clean up every export.
Frequently asked questions
Has KEMIS fully replaced NEMIS? It is intended to. Reporting through 2026 described a go-live early in the year and later said implementation was incomplete because of funding and technical issues. Check with your sub-county education office for the current position.
What should we do about learners without a UPI? Keep a list, follow the Ministry's current process for obtaining or confirming UPIs, and enter each one in the learner record as soon as it is known. Do not drop those learners from rosters.
Can a school system upload directly to KEMIS? Not that we are aware of. We have not found a published integration interface for school systems. Schools use the Ministry's own portal or upload process as instructed.
Who in the school should be allowed to export the full learner list? As few people as practical, typically the head and one named administrator, with strong sign-in and a record of each export.
See your own roster
The quickest test is to load your learners and see how many are missing a UPI before the next Ministry request arrives.
Book a demo and we will show how a school's learner records turn into a Ministry-shaped roster, and how the missing UPIs become a list you can work through.