What the 2027 deadline actually means
I teach and coordinate e-learning at Makerere University Business School, Faculty of Computing and Informatics. I also sit on CBET conversations through MUBASA and our faculty steering work. When people ask what the National Council for Higher Education (NCHE) 2027 mandate will change, I do not start with slogans. I start with a course outline.
From the 2027/2028 academic year, higher education institutions in Uganda are expected to admit first-year students only to programmes aligned with a Competence-Based Education (CBE) framework. NCHE’s direction is clear: programmes must show what graduates can do, not only what content was covered.
Listing nine focus areas is not enough for a lecturer who must rewrite a module before accreditation. This post is practical: what changes on an Applied Computing outline, in the lab, and in how we grade.
Where the policy comes from
NCHE hosted a stakeholders validation meeting on 23 January 2026 to review draft minimum standards for CBE in higher education. The Executive Director, Prof. Mary J. N. Okwakol, reminded institutions that the Minister of Education and Sports directed HEIs to review programmes and align them with CBE. She also stated that from 2027/2028, admission would be limited to CBE-aligned programmes. Read NCHE’s summary: NCHE consultative meeting on CBE reforms.
Dr. David Musiimaami outlined nine areas in those draft standards: Curriculum Design; Teaching and Learning Approaches; Assessment; Faculty Training and Support; Student Support Services; Quality Assurance Systems; Industry and Community Linkages; Monitoring and Evaluation; and Gender and Equity Mainstreaming. NCHE later published a public page for the Minimum standards for implementing Competence Based Education and Training in Uganda (March 2026). I cite the institution and the published direction carefully. I will not invent clause numbers or fake document titles.
The Monitor (April 2026) also places the reform under a Ministry of Education and Sports directive for tertiary institutions to adopt Competence-Based Education and Training (CBET) by 2027/2028. Universities are revising programmes, training staff, and waiting on NCHE processes.
Why 2027 is not a random year
Uganda’s lower secondary system already moved. Through the National Curriculum Development Centre (NCDC), the Ministry of Education and Sports rolled out a competency-based Lower Secondary Curriculum to Senior One in January 2020. NCDC documents that rollout here: Lower Secondary Curriculum Embraced. Those learners grow into university entrants. If we keep pure content-and-exam modules, we waste the habits they already built: projects, continuous tasks, and applied work.
Related reading on this site:
What I change first on a computing course outline
Take a familiar Applied Computing mix: Unix fundamentals, basic routing, and information security. Under the old pattern, the outline lists topics and contact hours. Week 3 is “Introduction to cryptography.” Week 5 is “Routing protocols overview.” Students sit a midterm and a final. Many can define confidentiality. Fewer can show a hardened host.
Under CBE, I rewrite the same credit load around observable outcomes. The module still covers Unix, routing, and security. The difference is the promise on page one:
Outcome A: Configure a baseline-secure Linux host (users, SSH policy, host firewall, basic audit trail) and demonstrate it live.
Outcome B: Map common campus threats to controls, and justify choices in plain language.
Outcome C: Apply simple routing and access-list rules, then verify traffic behaviour with a checklist.
Outcome D: Run a short incident response drill for phishing or malware on a lab VLAN and produce a one-page report.
Each outcome needs evidence. Evidence is not “attended lecture.” Evidence is a lab demo, a config dump with annotations, a peer-reviewed report, or a short viva on design trade-offs.
Unix lab: from commands covered to host secured
Old lab sheet: a list of commands. chmod, useradd, ufw, journalctl. Students copy them. They pass if the worksheet is filled.
CBE lab sheet: a scenario. “You inherit a student project server. Root login over SSH is open. Guest accounts exist. No firewall. Logs are not checked.” The competence is restoring a minimum safe baseline. I watch them work with a checklist: invalid users removed, SSH restricted, firewall rules explained, log proof attached. If a student cannot explain why a rule exists, they have not met the outcome yet. They get another attempt with clear feedback. That is formative work, not charity.
Routing: from definitions to verification
In networking weeks, I used to ask for definitions of static routes and ACLs. Now the task is smaller and sharper. Build a three-router lab path. Block one subnet from reaching a services VLAN. Show the before and after with a ping or traceroute capture and a short note of intent. The competence is verification under constraints, which is what junior network roles actually need.
Information security: theory that must survive a drill
Security still needs concepts: CIA triad, threat versus vulnerability, authentication versus authorization. CBE does not delete theory. It refuses theory with no performance. After a phishing tabletop, students submit an incident timeline: detect, contain, eradicate, recover, lessons. They may use notes. They may not invent evidence. The grade follows the quality of the response and the honesty of the log trail.
Assessment: what competence-heavy looks like
NCHE’s published direction pushes assessment redesign. Exact weightings sit inside institutional policies and the approved standards document, so I will not invent a mandatory national percentage. Public reporting and campus practice show continuous demonstration rising. The Monitor notes Makerere programmes that already run around 60% coursework and 40% final exam in places, and other universities proposing closer splits. For computing modules I teach or co-design, the workable pattern is:
Observed labs with checklists (hard to fully outsource to generative AI).
Short design vivas (five to eight minutes) on why a control or route was chosen.
Capstone scenario that stitches Unix, routing, and security into one ticket.
A written paper that still checks conceptual clarity, but no longer carries the whole story.
If your only assessment is a take-home essay, generative tools win easily. If assessment is a live lab plus a viva, the student must still think. Related: AI as a catalyst, not a crutch, in university assessment.
What faculty actually have to retool
Faculty Training and Support is one of NCHE’s nine areas for a reason. You cannot facilitate competence if your only muscle memory is chalkboard transmission. At MUBS computing, the retooling list is concrete:
Rewrite ILOs as verbs a lab can observe (configure, verify, contain, document).
Build rubrics that separate “ran the command” from “can explain the risk.”
Schedule lab time as teaching time, not optional extras after theory.
Invite industry guests for one module outcome, not a ceremonial career talk.
Agree how incomplete competence is remediated before resit culture becomes chaos.
Industry linkages stop being a brochure line when a SOC analyst co-reviews an incident rubric, or an ISP engineer checks whether ACL tasks match field tickets.
Constraints we should name honestly
CBE fails quietly when labs have dead machines, unstable power, or forty students sharing eight working PCs. NCHE’s Saul Waigolo has publicly noted infrastructure, equipment, staffing, and funding as live challenges while training rolls out. Programme teams should plan for offline VMs and paper checklists that still prove competence when the LMS is down. Gender and Equity Mainstreaming is not a footer. It is whether evening students, students with disabilities, and students without personal laptops can still reach the same outcomes.
Quality Assurance will ask whether outcomes map to credits, assessors are calibrated, and support exists when continuous load rises. Monitoring means we collect evidence each semester and fix what failed.
A simple next step for a computing department
If your faculty is stuck at slogan level, pick one module. Rewrite four outcomes. Attach one evidence type to each. Pilot one observed lab with a checklist this semester. Share the rubric with two colleagues and one industry contact. Then scale. That is how CBET becomes teaching practice rather than a PDF on a shared drive.
The 2027 mandate is a hard admissions gate. For me as a teaching assistant and CBET committee member, it is also a chance to make Applied Computing honest: Unix that secures, routing that verifies, security that survives a drill. Universities do not need prettier topic lists. We need graduates who can show the work.