Loading page…
Loading page…
Transparency
Openness is how Build & Learn Africa honours your trust. This page explains what your gift pays for, how a project is verified before it can receive a single donation, how each milestone release is approved, how evidence is reviewed, and where to go when something doesn’t look right.
Registration details are published here and in the Trust Centre as the organisation completes its registration disclosures. Until they are published, please treat any registration claim you see elsewhere as unverified.
Some platforms claim that “100% goes to projects” while covering their costs in ways donors never see. We won’t do that. Verifying applicants, inspecting milestones, processing payments and answering your emails genuinely costs money, and your gift funds both the project work and the protections around it:
Everything in the project's published budget: materials, labour, roofing, desks, books, teaching support. This is the work you chose to fund, itemised line by line on the project page.
Checking applicants and their documents, reviewing budgets, inspecting each milestone before funds are released, and collecting the evidence published on project pages.
The people and systems that keep the platform running and answerable: donor support, finance and accounting, safeguarding, security, and the technology you are using right now.
Fees charged by the payment provider on each card, mobile money or bank transaction. We negotiate these down where we can, but we cannot make them disappear.
We do not publish a percentage split. A ratio quoted before the accounts exist is a marketing number, not a fact. We will publish the split between these four categories once a full financial period has closed and its accounts have been prepared — and we will state plainly whether those accounts have been examined by an independent auditor. Until then there is no percentage to quote, and we would rather say so than invent one.
No project can receive a single donation until verification is complete. Every check is recorded individually against the application with its outcome, the person who did it and the date — so verification is an evidenced file, not an assurance.
The applying church, school or organisation is a registered entity in its own country, and its documents are checked against official records where those records are available.
Documented rights to build on the land — title, lease or a recorded community allocation — so a finished building cannot be lost to a later dispute.
How the applicant makes decisions and handles money: constitution or trust deed, committee structure, bank arrangements and who is authorised to approve spending.
Identity and references for the people who will lead the project, and a conflict-of-interest declaration covering related-party contracts and suppliers.
The budget is itemised, priced against local costs, and broken into milestones with the evidence each one must produce before publication.
What the community itself is putting in — land, labour, materials or funds. We build with communities, not for them, so this is a condition of approval, not a bonus.
Safeguarding expectations are agreed in writing before approval, covering child protection, consent for any published media and how concerns must be reported.
A visit to the site and the community, with photographs and location evidence recorded against the application file.
Funds are never handed over as a lump sum. Money leaves the platform one approved milestone at a time, and the person who asks for a release is never the person who approves it — a maker-checker separation applied to every request without exception.
The project team submits the evidence the milestone requires — photographs, receipts, delivery notes, inspection records — and requests the release for that milestone only.
A project officer checks the work and the evidence against the approved budget line before the request can move forward. A request that fails this check goes back with reasons.
Finance reviews the amount, the supporting documents and the funds actually available and restricted to that purpose. Requests are reviewed against procurement rules where suppliers are involved.
Approval is given by someone other than the person who requested it, and releases at or above a configured threshold require a second, separate approver. The same person cannot both request and approve a release.
The payment is recorded with its method and reference, matched back to the milestone, and reconciled against bank and provider records. Financial history is never deleted — corrections are made by posting adjustments.
Every administrative action in this chain (request, verification, review, approval, rejection) is recorded in an audit log the application only ever appends to, with the actor and timestamp. Entries are written once; nothing in the application edits or deletes them, and the database roles the public site connects with have no permission to update or delete audit rows.
Evidence arrives from the field as originals — photographs, receipts, invoices, delivery notes, inspection reports, narrative updates. Originals are stored privately and are never published as they arrive.
Financial and governance documents are published in the Trust Centre, where anyone can read them without an account. A document appears there only once it has been completed and approved for publication.
No independent auditor has been appointed yet. When one is, we will name them here and in the Trust Centre, and publish each completed audit report in full. Until an audit has actually been carried out, we will not describe any figure on this site as audited.
If no financial reports are listed in the Trust Centre yet, it is because none has been completed and published. We would rather show an empty shelf than a reassuring estimate.
Open the Trust CentreQuestions about the accounts can go to giving@buildlearnafrica.org, and governance questions to giving@buildlearnafrica.org. See who is accountable.
If you believe funds have been misused, a project misrepresented, or anyone connected to the platform has acted improperly, we want to hear about it — including anonymously. Every report is logged with its own reference number so it can be tracked to a conclusion, and we do not tolerate retaliation against anyone who raises a concern in good faith.
You can also write to giving@buildlearnafrica.org marked “Complaint”, or use the contact form. Keep the reference number you are given — it is how you and we track the same case.
The donation policy sets out how designations are honoured and what happens when a project raises more than it needs or cannot proceed. The refund policy sets out when a gift can be returned and how long that takes. Refund requests are accepted within 30 days of the donation, and requests about unauthorised payments are accepted at any time.
These policies took effect on September 3, 2026.