NGOs can publish useful programme results by reporting clearly defined measures, explaining what the evidence supports and keeping unnecessary participant information out of public reports. Start with the reporting purpose and audience.
A participant database and a public impact page serve different needs. A spreadsheet suitable for authorised internal work should not automatically become a public download.
Define what each result actually measures
Registrations, attendance, completion, demonstrated learning and later employment are different measures. State which one you are reporting and the period it covers.
Explain the source and limitations. A follow-up survey may not reach every participant. A count of certificates may not establish independent competence. Avoid turning programme aims into reported achievements.
| Measure | What it may show | What needs separate evidence |
|---|---|---|
| Registrations | Recorded interest or applications | Attendance and participation |
| Attendance | Presence under the chosen method | Completion or learning |
| Completion | Meeting the programme’s stated completion criteria | Longer-term outcomes |
| Follow-up findings | Responses collected in a defined review | Results for people not reached |
Decide what belongs in the public report
Aggregate information can communicate scale and reach without listing every individual. Choose categories that answer the reporting question and avoid unnecessary detail.
Small groups can still reveal identities when combined with location, age, course or other facts. Review the risk of identifying someone from a combination of details, even when names are removed.
Do not assume replacing names with codes makes a dataset anonymous. The organisation should assess what can be linked back to people and who can access the underlying records.
Use participant stories with specific permission and context
A story, photograph or quotation should have an appropriate publishing basis and the necessary permissions for the intended channel. Keep the approved wording and any limits with the source record.
Explain the person’s programme status accurately. A current learner should not be described as a graduate, and a learning project should not be presented as paid client work without evidence.
Where a story includes sensitive personal circumstances, assess whether the detail is necessary and whether publishing it is appropriate. The person’s dignity matters alongside the communication objective.
Use the right organisational review
Nigeria Data Protection Commission guidance describes the importance of fair, lawful and accountable handling of personal data. Public reporting should be reviewed alongside the organisation’s privacy responsibilities. Reference: https://ndpc.gov.ng/faqs/.
The appropriate lawful basis, permissions and retention arrangements depend on the activity and information involved. Ask the responsible privacy or legal adviser to assess the organisation’s circumstances rather than treating a website template as legal approval.
A hypothetical reporting example
Imagine a programme with attendance records, a practical assessment and a later voluntary survey. Its public report could describe each measure separately, explain the assessment and state how many survey responses were available.
It should not describe all registered participants as employed graduates because some survey respondents reported work. Any approved individual story would be presented as that person’s experience.
This is an illustrative reporting method. It is not a statement of results from ARISE, Mita School or another programme.
Connect the report to a useful programme page
A public report should help readers understand the programme’s purpose, activities, evidence and next steps. Use clear dates and links to the relevant background.
My ARISE Youth Skills Week website case study documents public information, participation and media destinations. It illustrates the website’s communication role; participant outcomes belong to the organising institutions and their evidence.
My programme website support and content development can help organise approved material for publication.
Review images, tables and downloads
Check photographs for visible badges, screens, documents or other details that could expose private information. Review captions and credits as carefully as the main text.
Check exported documents and spreadsheets for hidden sheets, comments, metadata and identifiable records. Removing a visible name column is not a complete review.
- Confirm definitions, periods and source records.
- Separate aims from observed results.
- Review aggregation and re-identification risk.
- Verify story and image permissions.
- Check downloads and embedded media.
- Record the approved version and correction owner.
Keep a correction process
Assign someone to receive concerns and correct inaccuracies. If a figure changes, explain the correction appropriately and update the relevant public versions.
Retain enough evidence to support the report under the organisation’s access and retention process. Public transparency should come from clear methods and supported claims, not unnecessary disclosure of participant records.
Frequently asked questions
Can we publish the full participant list?
Assess the purpose, lawful basis, expectations and risks with the responsible owner. A full list is not automatically necessary to demonstrate programme delivery.
Can consent to attend cover a public testimonial?
Do not assume that it does. Review the actual permission and intended publication use.
What if outcome data is incomplete?
Report the evidence available and its limitations. Clear uncertainty is more credible than an unsupported success claim.
Discuss your next step
For help applying this to your organisation, share a short description of your situation and the decision you need to make.





