One Big Change Kenya logoOne Big Change™ Kenya
Appendix 6

Risk, Safeguarding, Data Protection & Ethics Framework

The control environment for operating across ten counties, collecting school evidence, interacting with learners and handling public money and external partners - aligned to Kenyan law including the Data Protection Act, the Children Act and NACOSTI research licensing. One Big Change Kenya, September-December 2026.

1. Purpose of this Appendix

This Appendix sets out the proposed framework for identifying, preventing, managing, escalating and reporting:

  • programme risk
  • safeguarding risk
  • child-protection concerns
  • data-protection risk
  • research and evidence ethics
  • financial and procurement risk
  • political and reputational risk
  • fieldwork and travel risk
  • technology and cyber risk
  • partner and conflict-of-interest risk

The objective is to ensure that the One Big Change Kenya Founding Implementation Programme can operate across ten schools and ten counties without exposing learners, educators, schools, Government, partners or programme personnel to unmanaged risk.

Risk management is a core programme function. It is not an administrative exercise carried out after delivery decisions have already been made.

2. Core Principle

The programme will operate according to the principle:

No programme outcome, evidence target, partnership, deadline or financial objective takes precedence over the safety, dignity, rights and lawful treatment of the people participating in the programme.

Where programme delivery and safeguarding conflict:

safeguarding prevails.

Where evidence collection and privacy conflict:

lawful and proportionate data use prevails.

Where speed and proper financial control conflict:

financial control prevails.

4. Risk Management Objective

The programme will maintain a live Risk Register covering:

1strategic risk
2implementation risk
3education-quality risk
4safeguarding risk
5data-protection risk
6research-ethics risk
7financial risk
8procurement risk
9fraud and corruption risk
10people risk
11political risk
12reputational risk
13partner risk
14technology and cyber risk
15travel and fieldwork risk
16school-continuity risk

Every material risk must have:

  • description
  • category
  • cause
  • consequence
  • likelihood
  • impact
  • overall rating
  • mitigation
  • owner
  • review date
  • escalation threshold
5. Risk Rating

Risks will be assessed using likelihood and impact.

Likelihood

1

Rare

Unlikely to occur.

2

Unlikely

Could occur but is not expected.

3

Possible

Realistic possibility.

4

Likely

Expected to occur without mitigation.

5

Almost Certain

Highly likely or already occurring.

Impact

1

Minor

Limited effect on programme delivery.

2

Moderate

Manageable disruption.

3

Significant

Meaningful effect on milestone, school or budget.

4

Major

Threatens major programme objectives, reputation or safety.

5

Critical

Threatens safety, legality, financial integrity or programme continuation.

6. Risk Response

Risk responses may include:

Avoid

Do not undertake the activity.

Reduce

Introduce controls.

Transfer

Use insurance, contract or specialist provider.

Accept

Retain the risk where proportionate and authorised.

Escalate

Refer the decision to a higher authority.

Critical safeguarding, fraud, corruption, serious data-breach and major legal risks may not simply be accepted at operational level.

7. Initial Programme Risk Register

The following represents the initial risk profile.

RiskPotential ImpactInitial RatingPrincipal Mitigation
Delay in Government contractingSeptember mobilisation delayedHighPre-mobilisation planning, realistic start trigger, revised critical path
Senior Kenya roles not appointedWeak execution capacityHighExecutive search before field deployment, interim accountability
Ten-county logistics become unmanageableMissed school visitsHighRoute planning, local associates, travel contingency
School withdrawalCohort incompleteMedium/HighReadiness screening, reserve school list
Poor school engagementWeak evidenceHighSenior sponsor, champion, participation agreement
Change Lens creates excessive burdenSchool resistanceMediumProportionate methodology and reuse of existing evidence
Programme interpreted as inspectionReduced honestyHighClear communications and confidentiality
Safeguarding incidentHarm to child or adult, legal/reputational impactCriticalSafeguarding policy, trained lead, escalation pathway
Inappropriate collection of learner dataPrivacy/legal harmCriticalData minimisation, DPIA where required, access controls
Cyber/data breachConfidential information exposedCriticalSecurity controls, incident plan, restricted access
Evidence overstatedDecision Gate compromisedHighEvidence QA, independent challenge, limitations reporting
Political captureProgramme credibility damagedHighPolitical neutrality, transparent selection
Procurement conflictFinancial/legal riskHighConflict register, segregation of duties
Fraud or misuse of activation fundsFinancial lossHighControlled release, evidence, procurement controls
Traction Partner influence over findingsEvidence independence compromisedHighWritten partner boundaries
International expertise displaces Kenyan capabilityDependencyMediumKenyan-first expertise and knowledge transfer
Programme costs exceed estimateFinancial pressureMedium/HighMonthly forecasting and contingency controls
Staff turnoverDelivery disruptionMediumDocumentation, deputies, succession arrangements
Research activity begins without appropriate approvalLegal/ethical riskHighResearch-status review before evidence activity
Media disclosure of sensitive school informationReputational/safeguarding harmHighCommunications approval and consent protocols
90-day period insufficient to prove outcomesOverclaimingHighEarly-outcome focus and explicit limitations

The register will be updated throughout implementation.

8. Safeguarding Principle

The programme will adopt a safeguarding approach based on:

Prevention

↓

Identification

↓

Reporting

↓

Response

↓

Learning

Safeguarding applies to:

  • learners
  • staff
  • volunteers
  • contractors
  • guests
  • programme personnel
  • other vulnerable participants
9. Child-Centred Approach

A child is not programme content. A learner's:

  • story
  • photograph
  • video
  • assessment information
  • personal circumstances
  • disability
  • wellbeing information
  • safeguarding experience

must never be used merely because it makes programme communications more compelling. The best interests and welfare of the child will take priority.

This aligns with the Children Act's requirement that the best interests of the child be a primary consideration in actions concerning children. Source: Children Act - Kenya Law.

10. Safeguarding Governance

Before field implementation, the programme will appoint or contract a Safeguarding, Data & Ethics Lead. The role will have authority to:

  • stop an unsafe activity
  • restrict staff access
  • escalate concerns
  • require safeguarding action
  • require consent clarification
  • refer a matter to appropriate authorities where required
  • escalate directly to senior programme leadership

The Safeguarding Lead must not be subordinate to an individual whose programme targets could create a conflict with safeguarding decisions.

11. Safeguarding Policy

The programme will maintain a written safeguarding policy covering:

  • child protection
  • adult safeguarding
  • conduct
  • reporting
  • allegations against programme personnel
  • online interaction
  • photography/video
  • one-to-one contact
  • transport
  • fieldwork
  • school access
  • digital communications
  • whistleblowing
  • retaliation protection
  • escalation
12. Code of Conduct

All programme personnel interacting with schools will follow a Code of Conduct. It will prohibit conduct including:

  • sexual or exploitative relationships with learners
  • harassment
  • discrimination
  • humiliation
  • inappropriate physical contact
  • inappropriate private messaging
  • unauthorised photography
  • gifts intended to influence participation
  • requesting unnecessary personal information
  • being alone with learners in inappropriate circumstances
  • use of programme access for personal commercial activity
13. Safeguarding Screening

Appropriate vetting will be completed for roles involving direct or repeated interaction with children. The precise screening mechanism will be confirmed with Kenyan legal/safeguarding advisers. Screening requirements may differ for:

  • employees
  • contractors
  • volunteers
  • experts
  • photographers
  • event personnel

No individual should be placed in a child-facing role solely because they are known personally to a programme leader.

14. School Safeguarding Interface

The programme does not replace school safeguarding responsibilities. Before activity begins at each school, One Big Change should establish:

  • named school safeguarding contact
  • reporting route
  • emergency contact
  • relevant visitor rules
  • photography/recording rules
  • learner-contact rules
  • incident procedure

Programme staff should know whether a concern must be reported through:

  • the school's safeguarding process
  • One Big Change
  • statutory authority
  • more than one route
15. Safeguarding Concern

A safeguarding concern may include:

  • suspected abuse
  • disclosure of abuse
  • neglect
  • exploitation
  • harassment
  • inappropriate adult behaviour
  • peer abuse
  • self-harm concern
  • online harm
  • unsafe programme activity

Programme personnel should report concerns rather than investigate them personally unless their formal role authorises investigation.

16. Safeguarding Incident Response

The immediate sequence should be:

Protect immediate safety

↓

Listen without unnecessary questioning

↓

Record factual information

↓

Report promptly

↓

Escalate through the safeguarding pathway

↓

Refer externally where legally or professionally required

↓

Protect confidentiality

↓

Review programme implications

17. Confidentiality Limit

Participants must not be promised absolute confidentiality where a safeguarding concern may require escalation. Where appropriate, programme information should explain:

Information will be treated confidentially, but concerns regarding safety or serious harm may need to be shared with the appropriate safeguarding or statutory authority.
18. Learner Participation

Learner voice may add value to the programme. However, learner involvement must be:

  • relevant
  • age appropriate
  • voluntary where applicable
  • ethically designed
  • safeguarded
  • proportionate

A learner should not be disadvantaged because they do not participate in programme evidence or communications.

19. Photography, Video and Media

Photographs, recordings and learner stories require controlled processes. Before use, the programme should establish:

  • lawful basis
  • applicable consent/authorisation
  • intended use
  • platforms on which content may appear
  • retention
  • withdrawal process where applicable
  • safeguarding considerations

Consent to participate in a school activity is not automatically consent to appear in public media.

20. Data-Protection Principle

The programme will seek to collect the minimum personal data necessary to fulfil the defined implementation and evidence purpose.

The Kenyan Data Protection Regulations require processing to be designed around lawful purpose, transparency and appropriate safeguards, including specific protections for children and vulnerable groups. Source: The Data Protection (General) Regulations, 2021 - Kenya Law.

21. Data Governance Roles

Before processing begins, the programme will determine and document:

  • which organisation is the data controller for each activity
  • whether another organisation acts as joint controller
  • which suppliers are data processors
  • which organisations receive shared data
  • contractual responsibilities
  • lawful basis for processing
  • retention arrangements

The programme will also confirm whether registration obligations with the Office of the Data Protection Commissioner apply to relevant entities.

22. Data Inventory

A programme Data Inventory will identify:

  • dataset
  • purpose
  • data subjects
  • personal-data categories
  • sensitivity
  • lawful basis
  • source
  • access
  • sharing
  • storage location
  • retention period
  • deletion/anonymisation approach
23. Data Categories

Potential information may include:

School-Level Information

  • school context
  • staffing
  • facilities
  • implementation information

Staff Information

  • name
  • role
  • contact details
  • questionnaire responses
  • professional-development information

Learner Information

  • Only where genuinely necessary.

Parent Information

  • Only where relevant to the selected intervention.

Programme Personnel Information

  • contracts
  • payment
  • HR
  • contact details
24. Sensitive Data

Particular care should be applied to data relating to:

  • children
  • health
  • disability
  • wellbeing
  • safeguarding
  • ethnicity
  • religion
  • biometric information
  • financial circumstances
  • other sensitive personal information

The programme should avoid collecting sensitive data merely because it might later be interesting.

25. Data Minimisation

Before adding any field to the Change Lens or evidence system, the programme should ask:

1Why do we need this?
2What decision will it support?
3Could we answer the question without personal data?
4Could the information be aggregated?
5Could the information be anonymised?
6What happens if it is disclosed?

If there is no credible use, the field should not be collected.

26. Data Protection Impact Assessment

The programme will conduct a Data Protection Impact Assessment where required by law or where processing presents high risk.

Kenya's Data Protection Regulations identify processing involving children's data, vulnerable groups, large-scale personal-data processing, sensitive data, linked datasets and certain innovative technologies among activities that may require a DPIA. Source: The Data Protection (General) Regulations, 2021 - Kenya Law.

The founding programme should therefore complete an initial programme-level DPIA before large-scale evidence collection involving learners begins. Additional DPIAs may be required for particular tools or processing activities.

27. Data-Protection by Design

Data protection must be built into the programme before collection starts. This includes:

  • minimum-access design
  • secure defaults
  • clear privacy notices
  • collection limitation
  • role-based permissions
  • secure sharing
  • retention controls
  • logging
  • deletion/anonymisation

Kenya's Data Protection Regulations expressly require data protection by design or default. Source: The Data Protection (General) Regulations - Kenya Law.

28. Basic Education Data Infrastructure

The programme must obtain specialist Kenyan data-protection advice regarding the hosting architecture for any personal data used in basic education.

Current Kenyan Data Protection Regulations include basic education within specified processing of strategic interest and contain requirements concerning processing through Kenyan servers/data centres or maintaining a serving copy in Kenya. Source: The Data Protection (General) Regulations, 2021 - Kenya Law.

Therefore, the technology architecture must be legally reviewed before learner-level personal data is placed into cloud systems.

29. Cloud Services

Before using a cloud provider, the programme should assess:

  • location of data
  • sub-processors
  • encryption
  • authentication
  • access controls
  • backup
  • breach notification
  • deletion
  • cross-border transfer
  • contractual protection

Convenience will not determine the choice of system.

30. Data Access

Data will follow least-access principles. A person should only have access where required for their role. Possible access levels include:

School

Own school information.

Field Team

Assigned school records.

Evidence Team

Required programme evidence.

Executive Team

Aggregated programme information and controlled underlying access.

Government

Contractually agreed reports/data.

Traction Partners

Only information required for the agreed resource relationship.

Traction Partners should not receive unrestricted Change Lens data.

31. Data Sharing

Personal data will not be shared informally because two organisations happen to be programme partners. Where sharing is required:

  • purpose must be defined
  • lawful basis confirmed
  • minimum data identified
  • security confirmed
  • responsibilities documented
  • applicable agreement completed

Kenya's Data Protection Regulations include requirements concerning data-sharing arrangements and data-controller/data-processor contracts. Source: The Data Protection (General) Regulations, 2021 - Kenya Law.

33. Children's Data

Where children's personal data is processed, enhanced safeguards will apply. The programme will:

  • establish a clear necessity
  • minimise collection
  • use child-appropriate explanations where relevant
  • confirm appropriate parent/guardian processes where required
  • restrict access
  • consider DPIA requirements
  • avoid direct marketing or inappropriate profiling

Current Kenyan regulations specifically address the exercise of data rights involving children and require attention to the risks and safeguards associated with children's data. Source: The Data Protection (General) Regulations, 2021 - Kenya Law.

34. Anonymisation and Aggregation

Where individual identification is unnecessary, programme reporting should use aggregated information, anonymised data, and pseudonymised data where appropriate.

The Ministry does not need the identity of an individual learner to understand that a particular implementation barrier exists.

35. Retention

The programme will establish a Data Retention Schedule. For each dataset it will specify:

  • purpose
  • retention period
  • review point
  • deletion
  • anonymisation
  • archive requirement

Kenyan Data Protection Regulations require retention to be linked to the lawful purpose and provide for retention schedules and deletion, anonymisation or pseudonymisation when the purpose has ended. Source: The Data Protection (General) Regulations, 2021 - Kenya Law.

36. Data-Subject Rights

Processes will be established for applicable requests relating to:

  • access
  • correction
  • objection/restriction
  • erasure
  • portability
  • other rights provided under applicable law

Requests involving children will follow the applicable safeguards.

37. Data Security

Minimum security controls should include:

  • multifactor authentication where available
  • strong authentication
  • role-based access
  • encryption in transit
  • appropriate encryption at rest
  • secure device management
  • patching
  • backups
  • audit logs
  • secure password practices
  • controlled file sharing

Personal data should not routinely be stored in personal WhatsApp accounts, uncontrolled spreadsheets or personal email accounts.

38. Field Data Security

Field teams should receive clear rules concerning:

  • devices
  • paper records
  • photographs
  • recordings
  • file transfer
  • lost devices
  • public Wi-Fi
  • deletion after secure upload

Paper records containing sensitive information must not be left in vehicles, hotels or public spaces.

39. Data-Breach Response

The programme will maintain a Data Breach Response Procedure covering:

identify

↓

contain

↓

preserve evidence

↓

assess affected information

↓

assess harm

↓

escalate

↓

notify required authorities/data subjects where applicable

↓

remediate

↓

document

↓

learn

Applicable statutory notification requirements will be confirmed by the Data Lead and Kenyan counsel.

40. Cyber Incident Response

Cyber incidents may include:

  • compromised credentials
  • malware
  • phishing
  • unauthorised access
  • data exfiltration
  • ransomware
  • device theft

Critical incidents will be escalated immediately.

41. Research vs Programme Monitoring

Not every evidence activity is automatically academic research. The programme will distinguish between:

Routine Programme Monitoring

Information necessary to manage and evaluate delivery.

Evaluation

Structured analysis of programme effectiveness.

Research

Activity intended to generate generalisable or publishable knowledge and falling within applicable research requirements.

The programme will obtain specialist advice rather than self-declare an activity exempt where the distinction is uncertain.

42. NACOSTI and Research Licensing

If One Big Change, a university or another partner undertakes activity that constitutes research in Kenya, the appropriate research licensing route must be confirmed before that research commences.

NACOSTI currently states that persons intending to undertake research in Kenya must apply for a Research Licence. Source: NACOSTI FAQs.

Research activity will not commence on the assumption that the Government programme contract itself replaces research licensing.

43. Ethics Review

Where research involves human participants or otherwise requires ethical review, the programme will seek the appropriate review through a NACOSTI-accredited Institutional Ethics Review Committee or other applicable route before research begins.

NACOSTI provides information on accredited ethical-review arrangements and research licensing. Source: Kenya - National Science and Ethical Committee (NSEC).

No university's participation will be treated as automatic ethical approval.

45. Evidence Integrity

The programme will prohibit:

  • fabricated evidence
  • selective deletion of negative findings
  • retrospective manipulation of baselines
  • changing indicators after seeing results without disclosure
  • presenting estimates as observed outcomes
  • presenting partner intentions as commitments
  • counting the same beneficiary repeatedly without disclosure
46. Publication Ethics

Research papers, reports, case studies and communications must distinguish:

  • confirmed result
  • preliminary result
  • inference
  • limitation
  • future hypothesis

Publication should not disclose confidential school information merely because the programme owns the underlying report.

47. Artificial Intelligence and Automation

Where AI tools are used to support:

  • analysis
  • transcription
  • summarisation
  • categorisation
  • matching
  • reporting

the programme will establish controls concerning:

  • personal-data exposure
  • accuracy
  • bias
  • human review
  • vendor terms
  • data retention
  • security

AI-generated analysis will not constitute final professional judgement without human review.

Automated decisions with significant effects require particular care under Kenya's data-protection framework. Source: The Data Protection (General) Regulations, 2021 - Kenya Law.

48. AI and Children

AI will not be used to generate consequential individual judgements about learners without an appropriate lawful, ethical and professionally validated basis.

One Big Change's purpose is implementation support. It is not building an automated learner-ranking system.

49. Financial Risk

Financial risk includes:

  • unauthorised expenditure
  • duplicate payment
  • supplier fraud
  • false invoicing
  • unsupported expenses
  • activation-fund misuse
  • undisclosed conflicts
  • contingency misuse

Controls are detailed further in Appendix 9.

50. School Activation Fund Risk

The School Implementation Activation Fund is particularly sensitive. Controls must include:

  • evidence of need
  • approved implementation plan
  • budget
  • authorised expenditure
  • procurement evidence
  • confirmation of receipt
  • asset identification where relevant
  • implementation evidence
  • variance review

No participating school or individual is automatically entitled to KSh 1.5 million in cash.

51. Fraud and Corruption

One Big Change will adopt zero tolerance for:

  • bribery
  • kickbacks
  • facilitation payments
  • procurement manipulation
  • false expenses
  • supplier collusion
  • payments for political access
  • inducements linked to Government decisions

Programme staff and partners must be able to report concerns through an appropriate whistleblowing mechanism.

52. Gifts and Hospitality

A Gifts and Hospitality Register should be maintained. Programme personnel should not accept or provide gifts that could reasonably be interpreted as seeking to influence:

  • procurement
  • school selection
  • partner appointment
  • Government decision
  • LocaeAwards selection
  • employment
53. Conflict of Interest

Relevant personnel will declare interests including:

  • companies
  • suppliers
  • schools
  • relatives
  • investments
  • consultancy relationships
  • public office/political interests

A declared conflict does not automatically imply misconduct. An undisclosed material conflict is a governance concern.

54. Procurement Risk

Supplier selection should be based on:

  • need
  • specification
  • competence
  • value
  • due diligence
  • appropriate competition where required
  • documented approval

The fact that a supplier is known to a programme director is not sufficient justification for appointment.

55. Traction Partner Risk

Traction Partners may provide substantial value. Potential risks include:

  • commercial influence
  • brand capture
  • inappropriate access to schools
  • sales pressure
  • data access
  • inappropriate learner marketing
  • resource dependency
  • inflated valuation of in-kind support

Every significant partnership should therefore define:

  • contribution
  • restrictions
  • data access
  • branding
  • safeguarding
  • reporting
  • conflict provisions
  • exit
56. Political Risk

The founding programme may operate during a politically sensitive period. Risks include:

  • perceived party alignment
  • programme launches becoming political events
  • county selection being interpreted politically
  • educational evidence being used selectively
  • pressure to accelerate unsupported claims

The programme will maintain political neutrality.

57. Election-Period Safeguard

One Big Change may communicate educational outcomes. It should not:

  • endorse candidates
  • provide campaign resources
  • condition school support on political affiliation
  • target programme expenditure for electoral advantage
  • alter evidence for campaign messaging

The programme should be able to continue under any lawful future administration.

58. Reputational Risk

Reputational risks may arise from:

  • inaccurate claims
  • safeguarding failure
  • financial misuse
  • weak delivery
  • inappropriate partner
  • premature announcement
  • misrepresentation of university relationships
  • political perception

Programme communications require evidence discipline.

59. Partner Representation

Organisations will be described accurately. The programme will distinguish:

  • confirmed contracted partner
  • memorandum/discussion
  • exploratory relationship
  • potential partner

No organisation should appear under "Partners" solely because a conversation took place.

60. School Reputation

Participation should not expose a school to public humiliation. The programme should not publish headlines such as:

"School X fails CBA readiness."

Instead, public learning should normally use aggregated evidence, anonymised examples, consented case studies, and strengths and learning.

61. Fieldwork Risk

Fieldwork across ten counties creates risks including:

  • road accidents
  • fatigue
  • weather
  • security
  • delayed transport
  • unsafe accommodation
  • lost equipment
  • staff isolation

A fieldwork protocol should address:

  • journey planning
  • approved transport
  • emergency contacts
  • check-in
  • accommodation
  • insurance
  • lone working
  • incident reporting
62. Travel Authorisation

Field travel should require:

  • approved purpose
  • itinerary
  • traveller details
  • school contact
  • emergency information
  • cost authorisation

High-risk travel may require additional assessment.

63. People Risk

Programme people risks include:

  • slow recruitment
  • poor performance
  • burnout
  • inappropriate conduct
  • unclear accountability
  • excessive dependency on volunteers
  • conflict within leadership

Mitigation includes:

  • clear roles
  • performance expectations
  • onboarding
  • supervision
  • succession
  • wellbeing
  • disciplinary procedures
64. Volunteer Risk

Volunteers add capacity but cannot substitute for professional accountability. Volunteers should not independently undertake:

  • safeguarding decisions
  • financial approvals
  • legal decisions
  • sensitive interviews
  • high-risk data processing
  • clinical or specialist interventions

unless appropriately qualified and formally authorised.

65. School Burden Risk

A poorly designed programme could consume school time without improving implementation. The programme will monitor:

  • meeting volume
  • reporting burden
  • data requests
  • teacher time
  • event attendance

Where burden exceeds value, the programme should simplify.

66. Intervention Harm

Even well-intended interventions can create unintended effects. Examples include:

  • increased teacher workload
  • inequitable access
  • technology without support
  • equipment without maintenance
  • public labelling
  • diversion from existing priorities

Each school implementation plan should consider unintended consequences.

67. Resource Sustainability Risk

Before deploying equipment or technology, the programme should consider:

  • ownership
  • maintenance
  • licence renewal
  • connectivity
  • electricity
  • staff competence
  • replacement
  • ongoing cost

A resource that cannot be maintained may create dependency rather than capability.

68. Technology Risk

Before national scale, technology must be tested for:

  • reliability
  • usability
  • offline/low-connectivity environments
  • security
  • scalability
  • support
  • cost
  • interoperability
  • vendor dependency

Technology should not become a condition of participation where infrastructure makes its use unrealistic.

69. Evidence Risk

The greatest evidence risks include:

  • confirmation bias
  • positive-story bias
  • incomplete baseline
  • weak comparator
  • short implementation window
  • attribution error
  • selective reporting

Appendix 5 establishes controls to mitigate these risks.

70. Scale Risk

A successful ten-school programme does not automatically prove that a 6,000-school network will succeed. Scale creates different risks:

  • diluted quality
  • workforce shortage
  • weak Hub leadership
  • inconsistent evidence
  • excessive centralisation
  • fragmented governance
  • technology load
  • financial control

These will form part of the December scale-readiness assessment.

71. LocaeHub Safeguarding

Before a school takes on a future Hub role, the programme must assess:

  • leadership capability
  • safeguarding readiness
  • data practices
  • capacity
  • governance
  • peer-support boundaries

Hub status does not permit one school to access unnecessary confidential data from another school.

72. LocaeAwards Risk

Awards create incentives. Poorly designed incentives can produce:

  • gaming
  • exaggerated evidence
  • popularity voting
  • resource inequality
  • political influence
  • sponsor influence

LocaeAwards criteria should therefore reward:

  • evidenced improvement
  • implementation quality
  • learning
  • inclusion
  • sustainability
  • sharing practice
73. LocaeFest Risk

LocaeFest may involve learners, public figures, media, sponsors and schools. It will require separate planning covering:

  • safeguarding
  • photography
  • crowd management
  • travel
  • insurance
  • data
  • sponsorship
  • political neutrality
74. Whistleblowing

The programme should establish a confidential mechanism through which:

  • staff
  • volunteers
  • schools
  • suppliers
  • partners

can raise concerns regarding:

  • safeguarding
  • fraud
  • corruption
  • harassment
  • unethical conduct
  • retaliation

Reports should be assessed by an appropriate independent or senior function.

75. Non-Retaliation

No participant should suffer retaliation because they raise a genuine concern in good faith.

Malicious complaints may be addressed separately, but fear of retaliation must not suppress legitimate reporting.

76. Complaints

A programme complaints process should cover:

  • schools
  • staff
  • parents
  • partners
  • suppliers
  • other affected stakeholders

The process should specify:

  • route
  • acknowledgement
  • review
  • escalation
  • response
  • record

Statutory complaints rights remain unaffected.

77. Incident Classification

Incidents may be classified:

Level 1 - Minor

Local issue, no serious harm.

Level 2 - Significant

Requires programme-level management.

Level 3 - Major

Potential legal, financial, safeguarding or reputational impact.

Level 4 - Critical

Immediate serious risk or harm requiring senior/external escalation.

78. Critical Incident Management

For critical incidents:

protect safety

↓

activate responsible lead

↓

preserve evidence

↓

notify relevant executive

↓

seek legal/specialist advice

↓

notify authorities where required

↓

communicate carefully

↓

document actions

↓

conduct post-incident review

79. Business Continuity

Potential disruption scenarios include:

  • political unrest
  • transport disruption
  • health emergency
  • school closure
  • cyber incident
  • senior staff absence
  • partner withdrawal

The programme should define:

  • alternative delivery
  • remote capability
  • replacement personnel
  • backup records
  • communication routes
  • revised milestones
80. Stop / Pause Authority

The programme should define who can pause:

  • a school activity
  • a data collection activity
  • a supplier
  • an event
  • a partner activation
  • the whole programme

A Safeguarding Lead must be able to pause unsafe activity without waiting for a commercial decision.

81. Monthly Risk Reporting

The Ministry programme report should include:

  • top ten risks
  • new risks
  • closed risks
  • significant incidents
  • mitigation progress
  • safeguarding status
  • data-protection status
  • financial-control status

Sensitive information may require restricted reporting.

82. Decision Gate Risk Report

The December Decision Gate should receive a consolidated risk assessment covering:

  • founding risks realised
  • effectiveness of controls
  • unresolved risks
  • Year 1 risks
  • Hub-specific risks
  • data/cyber readiness
  • safeguarding readiness
  • financial-control readiness
83. Conditions Before National Scale

National expansion should not proceed unless there is sufficient evidence that:

  • safeguarding architecture can scale
  • data infrastructure is lawful and secure
  • programme governance can handle scale
  • financial controls can handle Hub-level activity
  • field workforce can be supervised
  • evidence quality can be maintained
  • political neutrality can be protected
  • complaints and whistleblowing can operate nationally
84. Pre-Mobilisation Control Gate

Before school-facing implementation begins, the Kenya Managing Director should confirm completion of:

1legal review
2programme insurance
3safeguarding policy
4Code of Conduct
5safeguarding reporting mechanism
6data inventory
7privacy notices
8Data Protection Impact Assessment where required
9technology-security review
10research-status determination
11ethics/research licensing pathway where applicable
12financial controls
13conflict register
14whistleblowing route
15travel/fieldwork procedure
16school participation documentation

Field implementation should not begin merely because the launch date has arrived.

85. Accountability

Overall executive accountability

Kenya Managing Director / CEO

Operational risk coordination

Chief of Staff & Operations

Safeguarding, data and ethics

Safeguarding, Data & Ethics Lead

Educational implementation

Education & Implementation Director

Evidence integrity

Evidence, Research & Learning Lead

Finance

Designated Finance Function

Corporate governance

One Big Change Board / Governance Structure

Government retains responsibility for its own statutory and contractual oversight.

86. Core Risk Promise
One Big Change Kenya will not pursue scale at the expense of safety, evidence integrity, lawful data use, financial accountability or school trust.

The founding phase is intended not only to prove that the implementation model can work. It must also prove that the model can be governed responsibly.