Impact & evidence

Measure what changed—not only what happened.

This page shows how targets are defined, how evidence is assessed and how results are verified before any public impact claim is made. Every figure below is labelled with what it is.

Impact framework

Six lenses for understanding meaningful progress.

No single metric can explain whether technology created lasting value. Each programme selects relevant indicators across these connected areas.

01Capability

Can people confidently use, manage and adapt what was introduced?

  • Demonstrated practice competency
  • Named local ownership
  • Confidence and self-efficacy change
  • Independent task completion
02Adoption

Are agreed practices still in use after implementation support ends?

  • Active use at follow-up
  • Frequency and consistency of use
  • Process adherence
  • Documented adaptation
03Operational value

Has the work become safer, clearer, faster or more reliable?

  • Time or effort change
  • Error and duplication reduction
  • Service reliability
  • Decision-information quality
04Reach and inclusion

Who can access the benefit—and who may still be excluded?

  • Participant and organisation reach
  • Geographic distribution
  • Accessibility barriers
  • Connectivity and device constraints
05Sustainability

Can the solution continue without unhealthy dependence?

  • Ongoing affordability
  • Data and account ownership
  • Documentation completeness
  • Support and succession readiness
06System contribution

What reusable knowledge, product or partnership value was created?

  • Reusable resources produced
  • Practice insights published
  • Partnership contributions
  • Replication with adaptation

Proposed programme targets

A baseline for future accountability.

Targets may change after discovery. Any revision will preserve the reason, date and approver.

ProgrammeCodeTargetIndicatorMeasurement definitionPeriodStatus
Small Business Digital FoundationsUG-SBDF30businesses across a proposed two-cohort pilotProposed recruitment target for two workshop waves of up to 15 businesses. No businesses have yet been recruited or supported.Proposed 12-month cycleProposed target
Community Technology CatalystUG-CTC6organisations in the proposed first cycleProposed selection target for one catalyst cohort of up to six organisations. No organisations have yet been selected or supported.Proposed 15-month cycleProposed target
Digital Skills in PracticeUG-DSIP120learners in the proposed cumulative pilot targetProposed cumulative target across five replicated workshop cohorts in two learning cycles. No learners have yet been recruited or trained.Proposed 18-month cycleProposed target

Evidence source: programme design documentation. Approval owner: the programme owner role defined in Ubuntu Gale’s content governance. Last updated: 28 July 2026.

Public evidence ladder

Attendance is not adoption, and adoption is not an outcome.

Ubuntu Gale reports each level separately. These levels are never collapsed into a single “people impacted” counter.

  1. 01Participated

    The person attended programme activity.

  2. 02Completed

    Required attendance, artefacts and safety rules were met.

  3. 03Demonstrated competence

    The participant personally performed or explained the practice.

  4. 04Implemented

    The practice or intervention was introduced into the intended environment.

  5. 05Adopted

    The practice was still being used at the defined follow-up point.

  6. 06Outcome evidenced

    A defined measure changed, with limitations and contribution clearly stated.

Verification workflow

A result moves through evidence, review and approval.

01

Record

A result is recorded against an approved indicator and reporting period.

02

Evidence

The source, method, owner and limitations are attached.

03

Review

A responsible reviewer checks quality, relevance and calculation.

04

Verify

Only an authorised verifier can approve the result for use.

05

Protect

Sensitive or personally identifying evidence remains private.

06

Publish

The result appears publicly with period, status and source context.

Evidence standards

Every published result needs context.

A number without its definition, period, source and limitations can create more confidence than the evidence deserves.

A defined indicator and unit of measure An approved baseline or reference point where relevant A named reporting period and geographic scope A documented source and collection method Disaggregation only where safe and meaningful Quality review and verification status Known limitations and material caveats Protection of personal and sensitive information

Reporting commitments

We will report learning, not only success.

Programme reporting

Activities, milestones, expenditure, risks, outcomes, evidence and next-period priorities.

Funder reporting

Grant use, budget versus actual, deviations, results, evidence and upcoming decisions.

Public impact reporting

Verified outcomes, reporting periods, methods, limitations and programme learning.

Data-quality reporting

Evidence coverage, verification state, missing data and corrective action.