Home› Groups› Adolescent Health and Wellbeing› Adolescent Health and Wellbeing› What the Webuye 36 should teach us and…

What the Webuye 36 should teach us and what it reveals about our blind spots

Started by Rhoda Nakhosi Sep 19, 2026 11 replies 👁 6 views
Rhoda Nakhosi Admin Community Champion (1,500+ points) Community Champion
Sep 19, 2026 at 4:00 pm
Many of us have seen the news coming out of Bakisa Secondary School in Webuye, Bungoma County: 36 girls pregnant in a single school, with 13 already delivered, 13 currently expectant, and 10 dropped out . Police are investigating, and local leaders are calling for arrests and a dormitory . But I want to raise this here not as a news item, but as a case study for our community. What does it tell us about adolescent wellbeing that we may not be seeing elsewhere?
A few things stand out to me from the reporting:
1. The location matters. Bungoma recorded 10,443 adolescent pregnancies in 2025 among the highest in the country . This is not a one-school problem. It's a regional pattern that this school happened to make visible. How many other schools in high-burden counties have similar numbers that never surface?
2. Only one parent reported to police. A Gender and Child Protection officer noted that of the 36 cases, only one parent had filed an official report . That silence is a data point. What does it tell us about how families, communities, and even school systems are absorbing these cases through informal negotiations, shame, or fear rather than through the protection system designed to respond?
3. The re-entry policy exists, but the girls are still gone. Kenya has a school re-entry policy (strengthened by a 2026 Ministry of Education circular) that guarantees pregnant learners and adolescent mothers the right to return . Yet national estimates suggest nearly 90 percent of teenage mothers never return . The policy is not the problem. The implementation gap is.
4. The proposed solution, a dormitory, addresses exposure, not perpetration. The principal has called for boarding facilities so girls do not walk long distances to school . That may reduce some risk. But the Assistant County Commissioner's own framing is telling: "These girls did not impregnate themselves" . The focus on policing girls' movement, rather than identifying and holding accountable the adults responsible, risks repeating a pattern where the burden falls on the girl.
Questions for this community:
1. What does a case like this look like in the data you work with, does it get counted, or does it disappear into "other"?
2. For those doing direct service work: when 36 cases surface at once, what actually happens to the girls? Are they re-entered, or quietly lost?
3. Where is the line between a "school problem" and a "community protection failure" and does that distinction change who is responsible for fixing it?
4. Is there a version of this story where the data gets better, the reporting improves, and the girls still do not come back?
I do not have clean answers. But I think this case deserves more than a news cycle. It is the kind of event that should force us to ask whether our instruments, our services and our community responses are actually designed for the reality these girls are living in.
Nonvicks Ochieng Member Community Champion (1,500+ points) Community Champion
1 week ago

@Rhoda Nakhosi This case study illustrates a critical breakdown between policy intent, data collection, and frontline service delivery, demonstrating that improved reporting alone does not guarantee better care or protection for adolescent girls. The reality that 36 pregnancies surfaced in a single school while Bungoma County recorded over 10,000 adolescent pregnancies in 2025 highlights how health and protection data typically capture isolated visibility events rather than the full, systemic scope of community harm. The near-total silence of parents, with only one official police report filed out of 36 cases, reveals how informal community negotiations, social stigma, and deep-seated fears bypass formal statutory child protection mechanisms. Furthermore, while Kenya’s 2026 Ministry of Education circulars guarantee a legal right to school re-entry, the reality that nearly 90 percent of teenage mothers never return proves that a policy exists in a vacuum without localized infrastructure, such as childcare, mental health support, and economic relief. Framing this crisis as a "school problem" requiring dormitories dangerously shifts the burden onto restricting girls' mobility rather than holding adult perpetrators accountable for statutory offenses. Ultimately, without redesigning monitoring instruments to directly trigger funded, multi-sectoral care, better data collection will only create a cleaner dashboard of systemic neglect while the girls themselves quietly disappear from the education system.

Rhoda Nakhosi Admin Community Champion (1,500+ points) Community Champion
↩ replied to Nonvicks Ochieng 1 week ago

@Nonvicks Ochieng, I agree with almost everything you have written, but I want to isolate one phrase: "better data collection will only create a cleaner dashboard of systemic neglect." I think that is exactly right, and it is also the point at which I would push back on the implicit prescription. The problem you describe is not a data problem at all. It is a linkage problem, the same girl can be fully documented in a health register, invisible in an education record, and absent from a protection file, and every one of those records can be technically accurate. So when we say "better data," are we actually asking for more data, or for the authority and mandate to connect data that already exists? Because those are very different asks, and only one of them is within the researcher's gift.

Nonvicks Ochieng Member Community Champion (1,500+ points) Community Champion
↩ replied to Rhoda Nakhosi 5 days ago

@Rhoda Nakhosi You’ve pinpointed the exact structural blindspot. Calling it a linkage problem rather than a collection problem shifts the burden from "more surveillance" to "interoperable accountability."

The challenge is that data linkage in adolescent protection isn't just a technical integration problem—it’s an institutional authority problem. Here is how I see that breakdown playing out in practice:

  1. Data Silos as Risk-Aversion: Health, Education, and Children’s Services operate under entirely different mandates, performance metrics, and privacy/governance frameworks. A health facility logging an ANC visit for a minor has a confidentiality duty; a school logging a drop-out marks it as a attendance metric; a chief or police officer requires a formal complaint to open a file. Without a legal or administrative mandate forcing a cross-sectoral trigger (e.g., automated mandatory notification mechanisms), the systems are designed not to talk to each other.

  2. The Researcher’s Burden vs. Policy Mandate: Researchers can highlight where the breakages occur, but as you noted, researchers don't have the statutory authority to mandate referral pathways. The ask shouldn't be for researchers to fix linkage, but for inter-ministerial taskforces (Education, Health, Interior, Gender) to establish shared case management frameworks where a single entry point automatically opens a joint care/protection track.

  3. The Danger of Linkage Without Safeguards: The counter-risk we have to acknowledge is that if we link health and police/education data without strong community trust, girls will simply stop seeking prenatal care or formal health services out of fear of legal or social exposure. Linkage must serve care and re-entry first, not just prosecution.

To push this forward: What would a realistic, ethical referral/linkage protocol look like at the county level (e.g., in Bungoma) that connects school re-entry support to health registers without driving vulnerable girls further underground?

Rhoda Nakhosi Admin Community Champion (1,500+ points) Community Champion
↩ replied to Nonvicks Ochieng 3 days ago
@Nonvicks Ochieng, your point that data silos are designed not to talk to each other because each system carries its own mandate, performance metrics and confidentiality duty, is the structural insight this thread needed. The risk aversion framing is what makes it land: institutions are not failing to share out of negligence, they are behaving rationally within their own accountability frameworks. A health facility has a confidentiality duty, a school has an attendance metric, a chief needs a formal complaint. Each is doing its job, and the girl still falls through. But I want to push on the inter-ministerial taskforce proposal, because I think it is the right ask and also the hardest one. Shared case management frameworks require someone to own the case across ministries, and in most county structures, no single office has that mandate. So the question I would put to you: in practice, who convenes that? Is it the County Director of Medical Services, the Children's Services department, or does it require a higher-level directive to make the trigger mandatory rather than discretionary? Because if the cross sectoral trigger remains voluntary, we have built a framework that depends on goodwill and goodwill is exactly what failed the 35 families who stayed silent. And your third point, that linkage without safeguards will drive girls further underground, is the one I keep returning to. That is the risk that could make a well intentioned reform actively worse. I would be keen to hear whether you have seen any county-level protocol that got that balance right.
Dr. Magoba Member Thought Leader (400+ points) Thought Leader
1 week ago

This case should be understood not simply as an episode of adolescent pregnancy within one school, but as a potential sentinel event revealing weaknesses across the adolescent health, education, safeguarding, and community protection systems.

From an epidemiological perspective, the first question is not only “How many girls became pregnant?” but “What population-level processes produced these pregnancies, who was exposed to risk, what protective factors failed, and what happened after identification?” A cluster of 36 pregnancies in one school warrants a structured, ethically conducted investigation rather than assumptions about causation. The analysis should establish the girls’ ages at conception and identification, school attendance patterns, distance and mode of travel to school, socioeconomic circumstances, access to adolescent-responsive health services, contraceptive and SRH information, relationships with partners, and any indicators of coercion, exploitation, abuse or other safeguarding concerns. These data should be collected with strict confidentiality and child-protection safeguards, particularly because some affected learners may be minors.

1. The denominator is as important as the headline number

The figure of 36 is highly visible, but epidemiologically it is only meaningful when placed against an appropriate denominator. We would want to know the number of female learners at risk, age distribution, person-time or school-year exposure where appropriate, and whether similar schools in the same sub-county demonstrate comparable patterns.

Likewise, the reported county figure should not automatically be interpreted as evidence that every school faces the same magnitude of risk. County-level aggregates can conceal substantial geographical, socioeconomic and age-specific heterogeneity. A useful surveillance system should therefore allow disaggregation by age, school, ward/sub-county, pregnancy outcome, school status, and referral/service outcome, while protecting individual identities.

This is where the event becomes particularly valuable for public-health learning: a highly visible school cluster may be a sentinel event rather than an isolated phenomenon.

2. The reporting gap is itself an epidemiological signal

The fact that only one parent reportedly made a formal police report should not automatically be interpreted as parental indifference or acceptance. Non-reporting can arise from multiple mechanisms: stigma, fear of retaliation, economic dependence, family pressure, lack of knowledge about reporting pathways, distrust of institutions, informal dispute resolution, or concerns about exposing the child to further trauma.

Consequently, surveillance data need to distinguish between absence of reporting and absence of harm. A case that does not enter the police or child-protection database may nevertheless appear in school, health-facility, community-health-worker or social-service records—or disappear from all formal systems.

This creates an important data linkage problem. If education, health, child protection and justice systems operate as separate silos, the same child can become simultaneously visible in one dataset and invisible in another.

3. Better reporting is necessary—but it is not the endpoint

I strongly agree with the concern that improved reporting does not automatically translate into improved outcomes.

A stronger monitoring framework should follow the entire continuum of care and protection, for example:

Identification → safeguarding assessment → clinical care → psychosocial support → protection/legal response where indicated → school re-entry → retention → completion.

For each stage, we should be asking:

  • Was the learner identified?

  • Was a safeguarding assessment completed?

  • Was appropriate clinical care provided?

  • Was psychosocial support offered?

  • Was referral completed rather than merely issued?

  • Was the learner able to return to school?

  • Did she remain in school after re-entry?

  • Did she complete the academic year?

  • Was childcare or social support available where necessary?

  • Were protection concerns appropriately investigated?

  • What happened to learners who did not return?

These are substantially more informative indicators than pregnancy counts alone.

4. School re-entry should be measured as retention, not merely admission

A learner technically being allowed to return to school is not equivalent to successful educational reintegration.

A meaningful programme indicator would therefore move beyond:

“Number of pregnant learners who returned to school.”

It should include:

return within a defined period → attendance after return → retention at 3/6/12 months → grade progression → completion.

The system should also capture why learners do not return. Possible barriers include childcare responsibilities, financial constraints, stigma, family circumstances, health complications, lack of psychosocial support, school-level discrimination, transportation difficulties and fear of returning to peers.

This distinction matters because a policy can be formally correct while implementation remains incomplete.

5. The proposed dormitory needs to be evaluated as an intervention, not assumed to be a solution

A boarding facility may address some structural barriers—for example, long commuting distances, unsafe routes or excessive travel time. However, it should be evaluated against the specific mechanism through which it is expected to reduce risk.

If the causal pathway is:

long distance → unsafe journey → increased exposure → pregnancy risk,

then reducing travel distance may plausibly address one component.

But if important contributors include sexual exploitation, coercion, poverty, transactional relationships, inadequate access to SRH services, gender-based violence, weak safeguarding or community-level vulnerabilities, a dormitory alone cannot address those pathways.

Therefore, the intervention should be accompanied by a theory of change and measurable indicators, rather than being adopted simply because it is a visible infrastructure response.

6. Accountability must be evidence-based and child-centred

The statement that “these girls did not impregnate themselves” appropriately draws attention to the need to examine the role of adult men and other potential perpetrators. However, the response should avoid assuming that every pregnancy resulted from the same mechanism.

The appropriate public-health approach is to establish, through confidential safeguarding and investigation processes, who was involved, whether coercion or exploitation occurred, whether there were age-related legal concerns, and what protection response was required in each case.

Where offences are identified, accountability should follow the applicable child-protection and criminal-justice mechanisms. At the same time, the health and education response should not be delayed while investigations proceed.

The affected girls are first and foremost children and learners requiring protection and support, rather than merely cases in a pregnancy statistic.

7. We also need to examine the denominator of the “missing girls”

One of the most important questions is what happens after the headline event disappears.

If 36 pregnancies are identified but only a proportion subsequently appear in school-re-entry records, health-service records or child-protection follow-up, then we have a potentially important loss-to-follow-up problem.

A programme dashboard could therefore include:

  • pregnancies identified;

  • learners receiving initial assessment;

  • safeguarding referrals;

  • completed referrals;

  • clinical care received;

  • psychosocial support received;

  • learners returning to school;

  • learners retained at 3, 6 and 12 months;

  • learners completing the academic year;

  • learners lost to follow-up;

  • documented reasons for non-return.

That would transform the data from a descriptive statistic into an accountability and programme-improvement instrument.

8. This should trigger a multi-sectoral investigation and response

The case sits at the intersection of several systems:

Education: attendance, re-entry, retention, school environment and safeguarding.

Health: adolescent-responsive SRH services, antenatal/postnatal care, HIV/STI services, mental-health and psychosocial support.

Child protection: identification, referral, protection planning and follow-up.

Justice/security: investigation of suspected offences where applicable.

Community systems: parents, community health promoters, chiefs, religious/community leaders and local organisations.

Social protection: poverty-related barriers, childcare and household vulnerability.

The response therefore should not be owned exclusively by the school or education department.

9. There is also an important surveillance-system question

This event provides an opportunity to ask whether Kenya's existing information systems can actually connect the relevant pieces of the story.

For example, can a programme identify that:

Learner A → pregnancy identified → health facility attended → safeguarding referral made → referral completed → school re-entry → retained after six months?

If the answer is no, then the problem is not simply inadequate data collection. It is a continuum-of-care information architecture problem.

However, any linkage system must use appropriate privacy protections. Personally identifiable information should not be casually merged across platforms merely for surveillance purposes. Unique identifiers, role-based access, minimum necessary data, secure referral mechanisms and clear governance arrangements would be essential.

10. Finally, we should avoid turning the girls into surveillance objects

Better data should ultimately improve the lives of the people represented by the data.

The most important question after collecting information is therefore:

“What action does this indicator trigger?”

If a pregnancy is recorded but no service follows, the indicator has limited practical value. If a safeguarding concern is identified but referral is not completed, the system has detected risk without providing protection. If school re-entry is recorded but the learner subsequently drops out, the programme may report success while the learner experiences failure.

For me, the central lesson from the Bakisa case is therefore this:

We should move from counting events to tracking pathways, from reporting outcomes to understanding causes, and from documenting referrals to measuring completed care and protection.

A genuinely responsive adolescent-health system should be capable of answering not only “How many pregnancies occurred?”, but also “Who was affected, what circumstances contributed, what protection was provided, what services were received, whether the learner returned and remained in school, and what happened next?”

That is where epidemiology, surveillance, implementation science and community protection intersect. The value of this case study will ultimately depend not on how prominently the 36 pregnancies are reported, but on whether the event produces better detection, stronger safeguarding, more responsive services, improved educational retention, and measurable prevention of recurrence—without placing additional blame or burden on the girls themselves.

Rhoda Nakhosi Admin Community Champion (1,500+ points) Community Champion
↩ replied to Dr. Magoba 1 week ago

@Henry Magoba, your continuum of identification → safeguarding assessment → clinical care → psychosocial support → protection/legal response → re-entry → retention → completion — is the clearest articulation of the accountability pathway I have seen in this discussion. But I want to put a hard question to it. The moment you build that pathway into a monitoring instrument, you create a record that follows an identified child across systems. For a 14-year old whose pregnancy may be the result of a statutory offence, that record is also evidence. How do you reconcile the monitoring function, which needs the pathway to be traceable with the safeguarding function, which may require that the identity of the child not be traceable across systems at all? You mentioned unique identifiers and role based access, but I am not sure that resolves the tension so much as it names it. Is there a version of this pathway that does not require the child to become legible to the state in order to be protected by it?

Dr. Magoba Member Thought Leader (400+ points) Thought Leader
↩ replied to Rhoda Nakhosi 1 week ago

Rhoda, thank you for pushing this to the level where the real safeguarding tension becomes visible. I agree that a pathway designed for accountability can unintentionally become a pathway for surveillance if “traceability” means that the child’s identity follows her across every system.

I would therefore distinguish traceability of the safeguarding event from traceability of the child’s identity. The monitoring instrument does not necessarily need to make the child personally identifiable to every actor. A strong model could use a minimum-data, purpose-limited architecture: the frontline safeguarding/clinical team retains the identifiable record where legally and clinically necessary, while the monitoring layer uses a protected unique case identifier, role-based access, data minimisation and aggregated or de-identified information for actors who do not require identity. The system should also have explicit rules for when information can and cannot be shared, with safeguarding and legal obligations taking precedence over routine programme reporting.

So, to your final question: yes, I think there is a version of the pathway where the child does not have to become universally “legible to the state” in order to be protected by it. What needs to be legible is the protection need and the response pathway, not the child’s identity to every institution. The challenge is designing the governance architecture so that confidentiality does not become an excuse for institutional inaction, while accountability does not become a justification for unnecessary disclosure.

That distinction— “traceable protection, not universal traceability”—may be the critical design principle for such a monitoring framework.

Rhoda Nakhosi Admin Community Champion (1,500+ points) Community Champion
↩ replied to Dr. Magoba 3 days ago
@henry Magoba, your distinction between traceability of the safeguarding event and traceability of the identity of the child is, I think, the design principle this whole discussion has been reaching for "traceable protection, not universal traceability." It resolves the tension I raised, at least at the level of principle. Where I am still pushing is on implementation. You noted that confidentiality must not become an excuse for institutional inaction, and that accountability must not become a justification for unnecessary disclosure. I agree entirely but those two failure modes are guarded by different actors with different incentives. The confidentiality safeguard is enforced by data protection officers and legal frameworks; the "no inaction" safeguard is enforced by... what, exactly? In Bungoma, the system had every legal basis to act and still didn't. So the governance architecture you are describing needs an enforcement mechanism for the duty to follow through, not just a restriction on who can see what. Which is why I would add one item to your continuum: alongside identification → safeguarding assessment → clinical care → psychosocial support → protection → re-entry → retention → completion, there needs to be a named accountable owner at each transition, and a trigger that fires when a transition does not happen. Otherwise the pathway documents the drop off rather than preventing it. Curious whether you think that is a governance question or a data-architecture question because I suspect it is the former, and that is the harder one to design.
Charles Member Expert (800+ points) Expert
4 days ago

Rhoda, thank you for framing this as a case study
rather than a headline — that distinction matters, and your four observations
(regional pattern, the single police report, the re-entry gap, the
dormitory-as-partial-answer) are exactly the right ones to sit with.

 

From peer-led prevention work, point 2 is the one
I'd push on hardest. The silence you're describing — one parent reporting out
of 36 — is not an absence of harm, it's evidence that communities have built
informal systems to absorb these cases before they ever reach a protection
system. In our own district-level work, we see the same pattern with addiction:
families and communities develop quiet coping mechanisms — shame management,
informal settlements, relocation — precisely because the formal system feels
distant, slow, or punitive. Those informal systems aren't failures of
awareness. They're rational adaptations to a protection system communities
don't trust to help them.

 

That reframes your question 3 for me: this isn't
only a "school problem" vs. "community protection failure"
binary. It's a trust problem. Until families believe reporting leads to protection
and accountability rather than exposure and stigma, the data will keep
disappearing into "other" — not because it isn't being generated, but
because no one is bringing it forward.

 

The dormitory addresses proximity. It won't touch
the trust deficit that's keeping 35 of 36 families silent.

Charles Member Expert (800+ points) Expert
4 days ago

Nonvicks, Rhoda, Dr. Magoba — this exchange on linkage vs. surveillance is
the most important turn in the thread. "Traceable protection, not
universal traceability" is a strong principle, but I want to offer a
different layer to the solution, alongside the data-architecture one.

The tension you've identified is that any system
traceable enough to coordinate care is also traceable enough to expose the
child. But the reason families avoid formal systems in the first place — what I
called the trust deficit earlier — is precisely that formal systems feel
state-facing, not community-facing. A protected unique identifier still sits
inside an institutional architecture families have learned to distrust.

In our peer-led recovery work, the referral
bridge that actually gets used is human, not technical: a trained community
peer who already has standing trust, who can walk a family toward formal
services without the family's first point of contact being an institution. That
person doesn't need — and shouldn't have — full case-file access. Their role is
narrower: recognize the need, accompany the family to the right door, and stay
present through the handoff.

Applied here, that suggests a hybrid worth testing at county level: pair Dr.
Magoba's minimum-data protected-identifier architecture with a trained
community-based referral layer — peer navigators who carry trust but not data —
so the "traceable protection" isn't only a technical safeguard but a
relational one the community already believes in before the system ever needs
to be legible to anyone.

Rhoda Nakhosi Admin Community Champion (1,500+ points) Community Champion
↩ replied to Charles 3 days ago
@Charles Bawate, your hybrid proposal on Dr. Magoba's minimum data protected identifier architecture paired with a trained community based referral layer of peer navigators who carry trust but not data is the most concrete thing to come out of this thread. It also raises two questions I woud like your thinking on. First, who protects the navigator? In recovery work, peer navigators often carry lived experience, and that is part of their credibility. Here, a community peer accompanying a family toward a protection referral may face the same pressure, stigma, or retaliation that kept the case quiet in the first place. What supervision, support, and protection does that role need and who funds it sustainably? Second, what is the navigator authorised to promise? Trust is built on whether what's promised actually happens. If a navigator walks a family to a system that then fails them referral issued but not completed, re-entry recorded but not sustained the navigator's credibility is spent, and the next family won't come forward. So the navigator model only works if the formal system behind them can demonstrate completed care, not just entry. Which makes me wonder whether the sequencing is wrong. We are designing the referral bridge and the data architecture at the same time, but maybe trust has to be rebuilt before the architecture matters meaning the first investment is not in linkage at all, but in proving, in one county, that a girl who comes forward is still in school twelve months later. If we cannot yet demonstrate that, does the architecture just make the failure more legible? Would value your read on that, given how the recovery model handles the same chicken and egg problem.