Financial Controls, Procurement & Value for Money
The financial-management, procurement, expenditure-control, audit, reporting and value-for-money architecture for One Big Change Kenya - carefully distinguishing the Government's procurement of One Big Change from One Big Change's management of programme funds after contracting. One Big Change Kenya, 2026.
This Appendix sets out the proposed financial-management, procurement, expenditure-control, audit, reporting and value-for-money architecture for the One Big Change Kenya programme.
Its purpose is to establish how programme resources will be:
- authorised
- received
- budgeted
- committed
- procured
- spent
- documented
- monitored
- reconciled
- reported
- audited
- protected from misuse
- connected to contracted outputs and outcomes
The framework applies first to the proposed 90-day Founding Implementation Programme and establishes the controls that would need to mature further before any Year 1 national programme is commissioned.
Money follows an approved purpose, an authorised budget, an evidenced need, an accountable owner and a verifiable result.
No programme expenditure should exist simply because budget remains available.
Every material expenditure should be capable of answering:
Two financial-control environments must be distinguished.
Stage A
Government Procurement of One Big Change
The relevant Government/public entity determines the lawful procurement and contracting mechanism. Its responsibilities include matters such as:
- approved budget
- procurement planning
- procurement method
- tender/RFP documentation
- evaluation
- award
- contract execution
- contract management
- payment approval
One Big Change must not determine Government's procurement route for Government.
Stage B
One Big Change Programme Financial Management
Once a lawful contract is in force, One Big Change becomes responsible for delivering the contracted programme according to:
- the signed contract
- approved budget
- agreed deliverables
- applicable law
- programme financial controls
- supplier and subcontractor requirements
- audit and reporting obligations
The precise treatment of programme funds, subcontracting obligations and any additional public-sector requirements will be confirmed in the final Government contract and through Kenyan legal and financial advice.
Approval of this proposal does not by itself constitute authority for expenditure. Funding can only be drawn through the lawful Government process and the executed contract.
The programme therefore distinguishes:
Proposal approval
↓
procurement award
↓
contract execution
↓
milestone acceptance
↓
payment authorisation
↓
cash receipt
Where the relevant public entity procures the programme, the applicable Kenyan public-procurement framework applies. The current PPADA framework gives effect to the constitutional requirement for public procurement to operate through a system that is fair, equitable, transparent, competitive and cost-effective.
One Big Change's proposal will therefore be structured so that its:
- scope
- deliverables
- evaluation criteria
- milestones
- costs
- reporting
- acceptance criteria
can be converted into a formal procurement and contract-management structure if required.
This proposal does not prescribe the procurement method Government must use. The appropriate route will be determined by the relevant public entity based on:
- applicable law
- procurement plan
- approved budget
- nature of the requirement
- value
- timing
- technical characteristics
- lawful procurement method
One Big Change will provide the technical and commercial information necessary to support that process.
The Government-facing programme should be capable of being translated into an identifiable procurement requirement. The procurement requirement should specify:
- programme objective
- implementation period
- technical scope
- geographic scope
- deliverables
- performance measures
- evidence requirements
- reporting
- budget
- payment milestones
- contract-management requirements
Programme requirements must not be artificially divided for the purpose of avoiding an applicable procurement process or threshold.
The programme should be packaged according to genuine operational need rather than an artificial attempt to circumvent procurement requirements.
Following contract award, One Big Change will maintain its own Programme Procurement Plan. The plan should identify expected procurement such as:
- technology
- travel
- venues
- research/evaluation
- expert services
- equipment
- communications
- legal services
- insurance
- field services
- implementation resources
- events
For each planned procurement it should record:
- requirement
- budget
- expected date
- procurement approach
- approving authority
- responsible person
Programme purchases should be categorised into:
Goods
Physical items and equipment.
Professional Services
Specialist professional capability.
Non-Consulting Services
Operational or routine services.
Technology
Software, platforms, hosting and technical services.
Works
Any physical works or installations, if applicable.
Travel and Logistics
Transport, accommodation and field operations.
School Implementation Resources
Goods or services required under approved school implementation plans.
Classification helps determine the appropriate procurement process.
The programme will maintain separation between critical financial functions. Where practicable, different people should undertake:
Request
↓
Approval
↓
Procurement
↓
Receipt confirmation
↓
Payment
↓
Reconciliation
The programme should maintain the following functions.
Budget Holder
Responsible for the relevant budget.
Requester
Identifies the legitimate programme need.
Procurement / Sourcing Function
Conducts the sourcing process.
Approver
Approves commitment/expenditure within delegated authority.
Receiver / Technical Verifier
Confirms the good or service has been received satisfactorily.
Finance Function
Processes payment and maintains accounting records.
Reviewer / Reconciler
Checks transactions and reconciliations.
No single person should control the entire transaction cycle for material expenditure.
Before mobilisation, a formal Delegated Financial Authority Schedule will be approved. It should specify who can approve:
- recruitment
- consultancy
- supplier engagement
- purchase orders
- travel
- school activation expenditure
- contract variations
- contingency use
- asset purchases
- payments
Authority should increase with seniority and transaction value.
A person's seniority does not provide unlimited spending authority. The Founder, Kenya CEO, directors and programme staff remain subject to the approved financial-control framework.
No individual should approve their own:
- invoice
- expense claim
- consultancy payment
- supplier relationship
- reimbursement
The indicative founding budget is:
| Category | Amount |
|---|---|
| Personnel & Programme Leadership | KSh 23,700,000 |
| Governance, Legal & Assurance | KSh 5,500,000 |
| Direct School Implementation | KSh 20,500,000 |
| Travel & Field Logistics | KSh 6,800,000 |
| Change Lens, Research & Evidence | KSh 5,500,000 |
| Technology & Data | KSh 2,500,000 |
| Traction Partner Mobilisation | KSh 1,500,000 |
| Engagement, Materials & Reporting | KSh 4,700,000 |
| Year 1 Scale Readiness | KSh 6,000,000 |
| Subtotal | KSh 76,700,000 |
| Programme Contingency | KSh 7,670,000 |
| Total | KSh 84,370,000 |
This budget remains subject to validation during contracting.
Every expenditure must map to an approved:
- programme
- workstream
- budget line
- cost centre
- activity
The finance system should permit reporting by:
- category
- workstream
- school
- county
- supplier
- Hub where applicable
- funding source
Finance will produce a monthly Budget Versus Actual report. The report should show:
- approved budget
- spend to date
- committed spend
- remaining budget
- forecast final cost
- variance
- variance explanation
Material unexplained variance should trigger review.
Programme management should not treat unspent bank cash as available simply because an invoice has not yet been paid. The programme should track:
Paid
Already disbursed.
Committed
Contractually committed but unpaid.
Forecast
Expected future expenditure.
Available
Budget genuinely available after commitments.
This prevents accidental overspending.
The programme should maintain a rolling cash-flow forecast covering at least:
- payroll
- contracted suppliers
- school implementation
- travel
- tax
- technology
- events
- professional services
- contingency
Cash-flow pressure must not be solved by using restricted programme money for unrelated purposes.
Where appropriate to the final contracting model, programme funds should be identifiable through:
dedicated project account
clearly segregated project ledger/cost centre
The final approach will depend on contract terms, legal structure, banking arrangements and accounting requirements.
The overriding requirement is traceability.
The proposed founding payment structure remains:
| Payment | Trigger | % | Amount |
|---|---|---|---|
| 1 | Contract effectiveness and accepted inception/mobilisation requirements | 35% | KSh 29,529,500 |
| 2 | 10 schools onboarded and baseline deliverables accepted | 30% | KSh 25,311,000 |
| 3 | Implementation cycles active and interim evidence accepted | 20% | KSh 16,874,000 |
| 4 | Final deliverables and Decision Gate pack accepted | 15% | KSh 12,655,500 |
| Total | 100% | KSh 84,370,000 |
The final contract may vary this schedule.
Payment should not depend solely on the passage of time. Each contractual milestone should identify:
- deliverable
- completion standard
- evidence
- submission date
- Government review period
- acceptance
- correction mechanism
- invoice point
For example:
Activity
Visit ten schools.
This alone should not trigger acceptance.
Deliverable
Ten quality-assured Change Lens baselines meeting the agreed standard.
That is capable of contractual verification.
Financial milestones should therefore follow deliverables rather than activity counts wherever practical.
Before an invoice is submitted to Government, One Big Change should confirm:
- milestone achieved
- required deliverables submitted
- acceptance evidence available
- invoice matches contract
- taxes treated correctly
- supporting information complete
The final financial proposal should state clearly whether figures are:
- inclusive of applicable taxes
- exclusive of applicable taxes
- subject to withholding or other statutory treatment
The precise Kenyan tax treatment must be validated before contract signature by appropriately qualified Kenyan tax/accounting advisers.
The KSh 84.37 million figure should therefore not be represented as a final tax-inclusive contractual amount until this validation has occurred.
Before material payment to a supplier, the programme should normally hold:
- legal name
- registration details
- tax information where required
- bank details
- contact details
- contract/purchase order
- ownership/beneficial ownership information where appropriate
- conflict declaration where relevant
Due diligence should be proportionate to:
- value
- risk
- school access
- child contact
- data access
- reputation
- financial exposure
Higher-risk suppliers require deeper checks.
Where appropriate, the programme should compare more than one credible supplier. Comparison may consider:
- price
- quality
- delivery
- expertise
- sustainability
- total cost
- school suitability
- safeguarding
- data security
Lowest price alone does not necessarily represent best value.
Where only one provider is realistically suitable, the file should record:
- reason
- market evidence
- uniqueness
- price justification
- conflict review
- approval
Convenience is not in itself sufficient justification.
For significant purchases, the programme should obtain reasonable evidence that cost is appropriate. This may include:
- quotations
- market research
- benchmark pricing
- historic comparable cost
- independent estimate
Material expenditure should not routinely proceed on a retrospective basis. The intended sequence is:
Need
↓
Approval
↓
Supplier selection
↓
Purchase order / contract
↓
Delivery
↓
Verification
↓
Invoice
↓
Payment
Where appropriate, payment should require matching:
Purchase Order / Contract
Proof of Receipt / Acceptance
Supplier Invoice
Material discrepancies must be resolved before payment.
Physical goods should be verified for:
- quantity
- specification
- condition
- delivery location
- serial/asset number where relevant
Receipt should be recorded by a person independent of the supplier.
Professional or contracted services should be accepted against:
- agreed scope
- deliverable
- timescale
- quality standard
- evidence of completion
A consultant's invoice is not itself evidence that the work was delivered.
The proposed founding programme contains:
KSh 15,000,000
School Implementation Activation
Up to KSh 1.5m
Per founding school (average)
This is an average planning envelope but is not an automatic unrestricted transfer.
Expenditure should require:
One founding school may require:
KSh 500,000
One school
KSh 1.4 million
Another school
Expert support
Rather than equipment
The portfolio budget must therefore remain needs-led rather than forcing equal expenditure.
Unused school activation funding remains programme funding.
It should not be spent merely to ensure that every school's theoretical allocation is exhausted.
Where practical, the programme may procure required goods/services directly rather than transferring cash to schools.
Where cash transfer is appropriate, additional controls should specify:
- purpose
- amount
- account
- authorised recipient
- reporting
- evidence
- return of unspent funds
- audit rights
The lawful mechanism must be agreed before use.
Where significant assets are acquired, records should identify:
- description
- serial number
- value
- funding source
- date
- location
- custodian
- ownership
- maintenance responsibility
Programme documents must distinguish between:
Ownership should never be inferred merely from physical possession.
Where assets are formally transferred to a school or public institution, the transfer should be documented. The documentation should establish:
- asset
- condition
- value
- receiving organisation
- responsible officer
- maintenance expectations
Travel expenditure should require:
- programme purpose
- approved itinerary
- traveller
- county/school
- cost estimate
- authorisation
Travel should be consolidated where possible to reduce cost.
The ten-county founding design increases logistics costs. The programme should therefore track:
- cost per field mission
- cost per county
- cost per school
- team size
- number of useful programme outputs per visit
This evidence will determine the Year 1 mix of:
- national travel
- cluster delivery
- Hub delivery
- digital delivery
Expense claims should normally require:
- business purpose
- date
- amount
- receipt/evidence
- cost centre
- approver
Personal expenditure is not reimbursable merely because it occurred during programme travel.
Programme personnel expenditure should distinguish:
- employees
- contractors
- consultants
- advisers
- volunteers
Each paid role should have:
- contract
- role
- remuneration
- time requirement where relevant
- deliverables/accountability
- approval
Where a founding director receives a programme retainer:
- the programme role must be defined
- deliverables must be identifiable
- remuneration must relate to actual programme responsibility
- invoices/payroll treatment must be appropriate
- conflicts must be disclosed
Nobody is paid from Government programme funding simply because they hold equity, founder status or an advisory title.
Share ownership, options, vesting or other equity arrangements are separate corporate matters.
They should not be charged to the Government programme as delivery expenditure.
Volunteer support may legitimately include reasonable:
- meals
- travel
- materials
- safeguarding
- training
Such expenditure should be recorded separately from employment compensation.
The founding budget includes:
KSh 7,670,000
Programme contingency
The contingency is not an unallocated discretionary fund.
Use should require:
- description of unexpected need
- reason it was not reasonably budgeted
- amount
- programme impact
- alternative considered
- appropriate approval
- updated forecast
Contingency should not routinely finance:
- new programmes
- unrelated events
- unapproved hiring
- discretionary branding
- personal expenditure
Material scope change requires contractual and budget review.
A budget variation may be required where programme evidence demonstrates that money should move between categories. The variation process should identify:
- existing line
- proposed line
- amount
- reason
- effect on deliverables
- approval required
Where the Government contract restricts variation, the contractual approval process applies.
A change to budget is not necessarily the same as a change to contract scope. Material changes involving:
- deliverables
- price
- duration
- geographic scope
- performance requirements
must follow the relevant contractual/legal variation mechanism.
The programme will maintain a Change Control Register showing:
- request
- reason
- financial effect
- schedule effect
- output effect
- approval
- status
Procurement decisions must be protected from personal financial interests. One Big Change will maintain a corresponding internal Conflicts Register.
A Gifts and Hospitality Register should record material gifts offered or received. No gift should influence:
- supplier selection
- Government decision
- school selection
- payment
- partner relationship
- LocaeAwards outcome
The programme prohibits:
- bribes
- kickbacks
- facilitation payments
- payments for public influence
- hidden commissions
- procurement collusion
- false invoices
- fabricated expenses
Suspected misconduct must be escalated.
No One Big Change employee, director, adviser or intermediary should receive commission calculated specifically on their ability to improperly influence or secure a Government procurement decision.
Commercial incentives for legitimate private-sector Traction Partner mobilisation may be structured separately and transparently where lawful and appropriate.
A protected reporting mechanism should allow concerns regarding:
- fraud
- bribery
- supplier conduct
- expense abuse
- conflict
- asset misuse
- procurement manipulation
to be raised confidentially.
Suspected fraud should trigger:
preserve evidence
↓
restrict further loss where possible
↓
notify appropriate senior authority
↓
investigate through an appropriately independent process
↓
obtain legal advice
↓
notify relevant authorities/contracting entity where required
↓
recover loss where possible
↓
document corrective action
The programme will maintain clear procurement and expenditure files. One Big Change's own record-retention period will be aligned with:
- the Government contract
- applicable law
- tax/accounting requirements
- audit requirements
Where the Government contract requires longer retention, that requirement will apply.
Every material transaction should be reconstructable from:
Need
↓
Approval
↓
Procurement
↓
Contract / PO
↓
Delivery
↓
Invoice
↓
Payment
↓
Accounting entry
↓
Programme outcome
Financial records should be held in a controlled system. Typical files include:
- budgets
- approvals
- supplier quotations
- contracts
- purchase orders
- invoices
- delivery notes
- bank evidence
- expense claims
- asset records
- reports
- reconciliations
- audit documents
Programme banking should be reconciled regularly. Unreconciled items should be investigated.
The person performing the reconciliation should not be the sole person who authorised every underlying transaction.
The programme should operate a monthly close including:
- bank reconciliation
- supplier balances
- commitments
- payroll
- expenses
- accruals where appropriate
- budget variance
- cash flow
- activation funds
- contingency use
Subject to the final contract, reporting may show:
- cumulative budget
- current-period expenditure
- cumulative expenditure
- commitments
- forecast
- variance
- milestone status
- school activation expenditure
- contingency use
- Traction Partner value separately
Reports must distinguish:
from
from
from
from
This avoids overstating either Government expenditure or partner mobilisation.
The same resource must not simultaneously be reported as:
- Government expenditure
- Traction Partner contribution
- school contribution
unless the report clearly identifies the respective components.
Partner in-kind value must be based on a documented valuation method. It should distinguish:
proposed
committed
delivered
verified
Only properly verified contribution should be presented as realised mobilisation.
The founding programme should include an independent financial review or internal assurance process proportionate to its size. Review may test:
- procurement
- supplier files
- payroll
- activation funds
- travel
- conflicts
- assets
- bank reconciliation
- budget control
- reporting
The final Government contract should define any external audit requirements. The programme should nevertheless maintain its records at a standard capable of supporting external audit.
Where required by the contract or applicable law, the relevant public authority and authorised assurance bodies may require access to appropriate programme financial records. The contract should define:
- scope
- notice
- access
- confidentiality
- retention
- cooperation
Audit findings should result in:
- responsible owner
- corrective action
- deadline
- verification of closure
Recurring findings should trigger broader control review.
Value for money is not simply: "Did we spend the entire budget?"
It asks whether resources were used to achieve the intended result appropriately. The programme will assess:
Economy
Were appropriate inputs obtained at reasonable cost?
Efficiency
Were inputs converted into outputs without unnecessary waste?
Effectiveness
Did the programme produce meaningful implementation change?
Equity
Did the model function across materially different school contexts?
Sustainability
Will the benefit continue after the expenditure?
Leverage
Did the programme mobilise additional useful resources?
Potential measures include:
- supplier price comparisons
- travel cost
- technology cost
- venue cost
- consultant rates
- equipment market comparison
The objective is not automatically to choose the cheapest input. The objective is to avoid unreasonable cost.
The founding phase should calculate:
- cost per founding school
- cost per completed baseline
- cost per implementation cycle
- cost per MicroSummit
- field cost per county
- support hours per school
- evidence cost per school
These figures are especially important because they become the basis for Year 1 costing.
Value for money must also consider:
- implementation priorities completed
- practice change
- leadership capability
- evidence quality
- resource utilisation
- school continuation
Cheap activity that produces no useful implementation change is poor value.
For each material school investment, the programme should ask:
What implementation barrier did this expenditure remove?
For example, it is not enough to state "KSh 800,000 spent on equipment." The programme should know:
- why the equipment was required
- whether it was used
- what implementation changed
- whether it can be maintained
The programme will calculate verified external mobilisation relative to relevant Government expenditure. However:
A high leverage ratio does not automatically mean high value.
Partner resources must also be relevant and usable.
At the December Decision Gate, Government should be able to ask:
The KSh 84.37 million founding programme should not be multiplied mechanically by 50.
The founding programme contains substantial one-off work including:
- methodology development
- legal setup
- governance
- platform development
- national architecture
- prototype processes
Year 1 also introduces new scale costs such as:
- Hub operations
- larger workforce
- 500 Core schools
- national technology
- national evidence
- 6,000-school network
Therefore Year 1 should be costed from actual resource requirements rather than simple multiplication.
The current Year 1 planning model is:
| Category | Indicative Amount |
|---|---|
| National Programme Office & Executive Delivery | KSh 170M |
| 50 LocaeHub Establishment & Operations | KSh 300M |
| 500 Core School Implementation Activation | KSh 400M |
| Champion Training & Train-the-Trainer | KSh 120M |
| 6,000-School National Learning Network | KSh 110M |
| National Field Travel & Logistics | KSh 105M |
| Evidence, Research & Independent Evaluation | KSh 120M |
| Technology, Data & Digital Infrastructure | KSh 100M |
| Expert & Specialist Support | KSh 85M |
| Traction Partner Mobilisation | KSh 45M |
| Legal, Safeguarding, Procurement, Audit & Compliance | KSh 45M |
| LocaeAwards & LocaeFest | KSh 45M |
| Communications & National Knowledge Products | KSh 30M |
| Programme Contingency | KSh 75M |
| TOTAL | KSh 1.75B |
The figures remain indicative until the founding phase produces actual cost evidence.
The founding programme must generate assumptions for:
- cost per Core school
- average Hub operating cost
- facilitator cost
- Champion development cost
- travel intensity
- Change Lens cost
- evidence cost
- technology cost
- resource mobilisation cost
These become the financial model for Year 1.
An indicative Year 1 payment model is:
| Tranche | Trigger | % | Indicative Amount |
|---|---|---|---|
| 1 | National programme inception | 20% | KSh 350M |
| 2 | 10 operational Hubs / 100 Core schools milestone | 20% | KSh 350M |
| 3 | 25 Hubs / 250 Core schools / mid-year evidence | 25% | KSh 437.5M |
| 4 | 50 Hubs / 500 Core schools / national infrastructure | 25% | KSh 437.5M |
| 5 | Year-end 6,000 network/evidence/completion requirements | 10% | KSh 175M |
These figures are planning assumptions rather than an approved payment schedule.
LocaeHubs must not become uncontrolled mini-budget centres. Before any Hub controls programme resources, Year 1 must establish:
- budget
- authority
- financial mechanism
- procurement rules
- reporting
- evidence
- audit access
- asset control
Where appropriate, procurement may remain centrally or regionally managed rather than transferring cash to individual Hub Lead Schools.
Each Hub should eventually report:
- operating cost
- implementation expenditure
- number of Core schools
- connected schools
- resources mobilised
- implementation outputs
- evidence outcomes
This enables comparison of delivery models without creating a school ranking.
Three different cost categories should be calculated separately:
Founding School Cost
Deep proof and methodology development.
Core Implementation School Cost
Structured Year 1 implementation.
Connected School Cost
Lighter network engagement.
Blending all three into one average will obscure the economics of the model.
The December Decision Gate should classify the model:
Green
Evidence suggests the programme can deliver meaningful value at credible national cost.
Amber
Potential value exists but costs/model need modification.
Red
Evidence does not support wider public investment at the proposed scale.
If Year 1 proceeds, financial controls should also operate through gates.
Gate 1
National mobilisation.
Gate 2
10-Hub replication.
Gate 3
25-Hub expansion.
Gate 4
50-Hub infrastructure.
Gate 5
Year-end completion.
Poor financial control at one stage should be capable of delaying the next expansion stage.
Before moving from 10 schools to 500 Core schools, the programme must determine:
- what should be purchased centrally
- what should be purchased at cluster level
- what should be Hub-coordinated
- what should remain school responsibility
- what should be sourced through Traction Partners
- what procurement capability is required
This is a founding-phase output.
The working principle should be:
Centralise where scale creates value
- technology platforms
- common licences
- national evaluation
- insurance
- major framework services
Localise where context matters
- certain field logistics
- locally available services
- context-specific support
Aggregate through Hubs where demand is shared
- common expertise
- training
- selected equipment
The final structure will depend on evidence and applicable procurement requirements.
The programme should avoid:
We bought it, therefore schools must use it.
Instead:
Change Lens
↓
Need
↓
Specification
↓
Procurement / Partner Response
↓
Use
↓
Evidence
Procurement is an implementation tool. It is not the implementation strategy.
The programme dashboard should show:
- total contract value
- cash received
- expenditure
- commitments
- forecast
- variance
- contingency
- school activation spend
- travel
- procurement status
- partner cash
- partner in-kind
- milestone payment status
Programme financial information should be transparent to the extent required by law, contract, Government reporting, audit and legitimate public accountability.
Transparency does not require publication of:
- personal payroll details
- commercially sensitive information
- confidential supplier information
where such disclosure is not legally required or appropriate.
One Big Change will ensure its own programme-record retention supports the contracting entity's audit and contract-management obligations.
Where applicable to One Big Change's participation in Government procurement, the required ownership information will be provided through the formal procurement process.
Material programme suppliers should also be subject to proportionate ownership/conflict checks.
Kenya Managing Director / CEO
Overall programme financial accountability
Designated Kenya Finance Function
Day-to-day financial control
Chief of Staff & Operations
Programme operations
Finance, Resources & Investment Lead
Financial planning/resource architecture
Relevant Procurement / Commercial Function
Commercial procurement interface
One Big Change Board / Governance Structure
Governance oversight
Kenyan Legal & Governance Counsel
Legal compliance
The Government/public entity retains responsibility for its own public procurement, public-finance and contract-management obligations.
Before accepting Government programme funds, One Big Change should have:
Before moving to a possible KSh 1.75 billion national programme, Government should receive evidence that:
- the KSh 84.37 million founding programme was financially controlled
- audits/reviews were satisfactory or findings addressed
- school activation expenditure was traceable
- procurement files were complete
- conflicts were managed
- assets were recorded
- financial reporting was reliable
- unit costs are understood
- the Hub financial architecture is ready
- national procurement capacity exists
- the Year 1 budget is based on actual evidence
The founding programme's financial architecture will be considered successful if Government can establish:
One Big Change Kenya will not measure financial success by the amount of money spent.
It will measure whether approved resources were converted into:
- credible implementation
- stronger school capability
- useful evidence
- sustainable change
- additional resource mobilisation
- a national model Government can judge on both outcomes and cost
Every shilling should be traceable.
Every material purchase should have a purpose.
Every payment should have authority.
Every national-scale cost should ultimately be justified by evidence from the founding programme.
