Corporate partnership

Fund capability that is still working after we leave.

Ubuntu Gale works with companies that want their skills, enterprise development and social investment spend to produce something durable — and that want to be told the truth about what it can and cannot claim.

Why corporates fund Ubuntu Gale

Four reasons, and the limits attached to each.

Operating capability, not activity counts

Programmes are built around a real operating problem and continue past the workshop into implementation, coaching and adoption review. What a funder buys is capability that is still in use months later, and reporting that says whether it is.

Evidence you can hand to a verifier

Participation, attendance, completion and outcome evidence are recorded as the programme runs, not reconstructed at reporting time. That is what a B-BBEE verification agency or an internal auditor asks for, and it is the part most social spend cannot produce.

A funding relationship with stated limits

We publish what we do not do. Ubuntu Gale is not accredited by SAQA, the QCTO or a SETA, holds no s18A or public benefit organisation approval, and guarantees no employment or funding outcome. Everything on this site is written to that standard.

One accountable relationship

A named partnerships contact, a written contribution agreement setting out exactly what is and is not provided in return, and a reporting schedule agreed at the start rather than negotiated at the deadline.

Contribution routes

Nine ways a company can contribute.

Most funders combine two or three. The route matters because it decides what evidence we collect, how we report, and which recognition instrument your advisers will be looking at.

Unrestricted cash grant

The most useful contribution there is. Funds delivery where it is most needed, including the unglamorous parts — facilitation, evaluation, participant access and follow-through.

Deductible business expenditure route

Restricted programme grant

Funds a named programme, cohort or geography. Reporting is scoped to that restriction, and we will tell you plainly if the restriction makes delivery impractical.

Deductible business expenditure route

Enterprise and supplier development spend

Structured around identified beneficiary enterprises so that the support delivered to those businesses is what gets recorded, which is what a verification agency tests.

B-BBEE Code 400 — conditional

Skills development spend

Funds participant places and delivery. Ubuntu Gale programmes are not SETA-registered learnerships, so which Learning Programme Matrix category applies is a question for your verification agency.

B-BBEE Code 300 — conditional

Bursary or participant sponsorship

Covers the cost of individual participants — place, device access, data and travel — so that ability to pay is not what decides who takes part.

Socio-economic development route

In-kind technology

Devices, connectivity, software licences or cloud credit. We will say no where the equipment cannot be maintained locally after the programme ends.

Valued at fair market value

Employee volunteering

Structured, scoped volunteering against a defined need — not a team-building day. Volunteers work to the same safeguarding and data rules as staff.

Time-based contribution

Mentor supply

Experienced people who commit to a defined mentoring period with real participants. Mentors are screened, briefed and matched, not simply listed.

Time-based contribution

Employer host or placement partner

Hosting a cohort, offering work exposure, or opening a route into employment for graduates. No employment outcome is guaranteed to anyone, by us or by you.

Capacity contribution

What a funder receives back

Evidence, reporting and a named person.

  • An evidence packParticipation and attendance records, completion evidence, adoption and outcome data, and the delivery narrative behind it — the underlying material, not a summary slide.
  • A B-BBEE contribution letterA letter recording what was contributed, when, and what was delivered with it. Whether your verification agency recognises it, and under which element, is their determination.
  • Impact reporting on an agreed scheduleReported against the evidence ladder we publish — participated, completed, demonstrated, implemented, adopted, evidenced. Pilot targets are reported as targets, never as achieved results.
  • Recognition at the tier you chooseIncluding the choice of no public recognition at all. Every specific use of your name or mark requires separate written approval from you.
  • A named partnerships contactOne person who owns the relationship, answers questions and escalates problems, rather than a shared inbox.
  • An honest answer about taxWe tell you which instruments a contribution can and cannot support before you commit, and we do not overstate our own standing to make a contribution look better than it is.

Recognition tiers

Recognition scales with contribution. Influence does not.

Bands are indicative and cumulative. Any tier can be taken anonymously, and no tier carries a say in curriculum, beneficiary selection or what an evaluation is allowed to find.

Recognition tiers, indicative contribution bands, recognition and reporting
TierIndicative bandRecognitionReporting
SupportingUnder R250,000Named in the annual report and on the funders page, with your approval.One delivery report at completion.
ContributingR250,000 – R1 millionThe above, plus recognition on the funded programme's page and in cohort materials.Six-monthly reporting plus a completion report.
ProgrammeR1 million – R5 millionThe above, plus named association with a specific programme or cohort, and a joint communications plan you approve in writing.Quarterly reporting, a beneficiary demographic breakdown and an annual review meeting.
StrategicMore than R5 millionThe above, plus an agreed multi-year recognition schedule. Recognition never extends to influence over curriculum, beneficiary selection or evaluation findings.Quarterly reporting, an agreed evaluation approach and a standing review with the partnerships lead.

Due diligence

We check you. You should check us.

Ubuntu Gale assesses every corporate application against its published funding acceptance criteria: the source of funds, alignment with our purpose, the absence of undue influence over programme content or beneficiary selection, and the absence of any conflict that would compromise independence. We decline contributions that would compromise those things, and we say why.

  • Legal identity confirmed against the registration certificate.
  • Beneficial ownership disclosed to the level our acceptance criteria require.
  • Sanctions and adverse-media screening of the entity and its beneficial owners.
  • Tax compliance status confirmed and current.
  • Source of funds understood and consistent with the declared business.
  • Declared conflicts of interest assessed against the board register.
  • No condition that would give a funder influence over programme content, beneficiary selection or evaluation findings.
  • Reporting expectations checked against what we can genuinely evidence — we would rather decline than promise a report we cannot produce.

Next step

Two places to go from here.

Read the tax and B-BBEE position first if your finance or transformation team needs to see it — it sets out, instrument by instrument, what a contribution to Ubuntu Gale can and cannot currently support. Last reviewed 2026-07-29.