Our commitments

What Reduzer is responsible for

We are responsible for the admissions process, the quality of teaching and assessment, the learning environment, student support, and accurate reporting of programme results.

Current programme facts · Reviewed 17 July 2026

Cohort: First cohort in training · Completes August 2026
Programme status: Non-accredited skills training
Qualification: Does not award a diploma or TVET qualification
Employment: Not guaranteed

Why Reduzer runs this programme

Reduzer builds and manages software engineering teams for companies. Through that work, we see the difference between completing a course and being able to contribute to a software team.

We run the programme to address that difference. What we learn from engineering delivery, employers, student work, and cohort results informs the curriculum, projects, assessments, and teaching methods.

Read “Stop Selling Hope to People Who Cannot Afford to Lose It”

The programme

What we commit to

Admissions and expectations
Before enrolment, we explain the cost, workload, entry requirements, programme status, and completion requirements. We assess each applicant against the same entry requirements.
Learning environment and support
We set the timetable, allocate time for instruction and practice, give feedback throughout the programme, and respond when a student asks for help.
Progress and early response
We monitor attendance, submissions, assessments, and practical work. When a student falls behind, we identify the gap, set a recovery plan, and assess progress again.
Teaching and assessment
We teach through practical software work. Assessment covers the software produced, the decisions behind it, and the student’s ability to test, explain, and improve the work.
Curriculum and programme improvement
We review the curriculum, teaching, pacing, assessment, and support using student work, progress data, cohort outcomes, and feedback from students and employers. We record the changes and check their effect on later cohorts.
Reporting
We report results for the whole cohort using the definitions on this page. We include learners who complete, withdraw, are dismissed, do not enter qualifying work, or cannot be reached.

Completion

What a student must demonstrate to complete the programme

Completion is based on assessed work, not attendance alone.

Understand a user or business problem and plan the work.
Design, build, test, deploy, and maintain working software.
Find defects, make changes, and explain technical decisions.
Participate in code review, documentation, deadlines, collaboration, and handover.
Use AI tools while remaining able to explain, test, and correct the resulting work.

Outcomes

How we measure results

The first cohort completes in August 2026, so there is no result to publish yet. The figures below are programme targets, not results or individual guarantees.

Programme target

At least 90%

Completers enter qualifying work within three months

The measure includes every programme completer. Qualifying work is verified, relates to software, and pays at least KSh 45,000 per month. It includes employment, freelance work, self-employment, or a business created by the completer.

Freelance work, self-employment, and business income count only after income meets the threshold for three consecutive months. The first qualifying month must begin within three months of programme completion.

Paid and unpaid internships and apprenticeships do not count. Neither do unstarted offers, freelancer profiles, business registrations, or one-off assignments.

Programme target

No more than 10%

Learners withdraw or are dismissed before completion

The rate is the number of withdrawals and dismissals divided by the number of learners enrolled when the cohort starts. Deferrals and transfers are reported separately.

Reporting cycle

Every 18 months

An independently reviewed outcomes report

We publish the result for each measure, the number of learners in every category, the definitions used, and any gaps in the data. An independent reviewer checks the source records and calculations before publication.

When we miss a target, we say so and report what we change in response.

Why Reduzer runs this programme

Reduzer builds and manages software engineering teams for companies. Through that work, we see the difference between completing a course and being able to contribute to a software team.

Read “Stop Selling Hope to People Who Cannot Afford to Lose It”

What we commit to

Admissions and expectations

Before enrolment, we explain the cost, workload, entry requirements, programme status, and completion requirements. We assess each applicant against the same entry requirements.

Learning environment and support

We set the timetable, allocate time for instruction and practice, give feedback throughout the programme, and respond when a student asks for help.

Progress and early response

We monitor attendance, submissions, assessments, and practical work. When a student falls behind, we identify the gap, set a recovery plan, and assess progress again.

Teaching and assessment

We teach through practical software work. Assessment covers the software produced, the decisions behind it, and the student’s ability to test, explain, and improve the work.

Curriculum and programme improvement

We review the curriculum, teaching, pacing, assessment, and support using student work, progress data, cohort outcomes, and feedback from students and employers. We record the changes and check their effect on later cohorts.

Reporting

We report results for the whole cohort using the definitions on this page. We include learners who complete, withdraw, are dismissed, do not enter qualifying work, or cannot be reached.