Show Your Impact Without Sharing People's Data

Applications for NGO, CSR, public-health and development roles often ask for proof of impact. A strong example may involve a real community, a sensitive service or an unpublished dataset. The candidate's challenge is to show sound judgment without moving participant records, internal dashboards or identifiable stories into a CV, portfolio or interview slide.

This guide offers an evidence ladder: show the decision, describe the result at a safe level, then state the disclosure boundary. It is a practical way to prepare an application, not permission to reuse an employer's confidential material. Follow your current or former organisation's policies and any agreement governing the work.

Start with the decision you made

Before choosing a statistic or a story, identify the professional judgment the employer needs to see. Did you revise outreach after low attendance? Change the way field teams recorded referrals? Test whether a training schedule suited participants? State the problem, the options you considered, the action you owned and the trade-off. This can demonstrate capability even where the underlying records cannot leave the programme.

For example: “I compared three outreach schedules using weekly attendance patterns, consulted field facilitators, and recommended a later session for workers who could not attend in the morning.” That sentence explains the decision. It does not require names, phone numbers, exact village locations or a screenshot of the register.

Choose the least revealing evidence that still proves the point

Work down this ladder only as far as the role requires: (1) process and decision, (2) approved aggregate result, (3) a public or explicitly cleared artefact. A hiring panel rarely needs raw participant data to understand how you reasoned. If a number is approved for external use, explain its denominator and period. If it is not approved, describe the direction of change and the method rather than inventing precision.

The OCHA Data Responsibility Guidelines address safe handling and sharing of humanitarian data. The ICRC Handbook on Data Protection in Humanitarian Action emphasises the dignity and protection of people whose information is processed. These sources concern humanitarian operations; the application rule here is our own conservative practice: share only the minimum evidence you are authorised to disclose.

Run a disclosure check, even on “anonymous” examples

Removing a person's name is not always enough. A rare condition, a very small group, an exact date and a named location may identify someone when combined. Inspect tables, chart labels, image metadata, filenames, photographs and quotations as well as the body text. Ask: could a colleague, neighbour or local partner work out who this is? If the answer is uncertain, widen the geography or period, suppress the small cell, use a composite illustration clearly labelled as such, or leave the example out.

The ICRC handbook discusses re-identification risk in aggregate and supposedly anonymised information. Do not call a document anonymous merely because names have been replaced with codes. A code may still connect back to a person through another file.

A worked application example

Illustrative scenario: A programme officer helped improve follow-up after maternal-health sessions in one district. The internal dashboard contains small village counts and participant contact details. The candidate wants to apply for a monitoring and learning role.

A weak portfolio page copies the dashboard and blurs names. The remaining village labels and low counts could still expose participants; it also exports an internal work product without approval. A stronger account says: “I found that the follow-up measure mixed attempted calls with completed conversations. I proposed separate definitions, tested them with the field team, and added a weekly review of unresolved cases. The revised measure helped managers distinguish a workload issue from a contact-quality issue.” If a public annual report contains an approved district-level result, the candidate can link to that report and explain their own contribution accurately. Otherwise, they stop at the decision and method.

In an interview, a useful line is: “I can explain the method and my role. I cannot share participant-level records or unpublished programme figures.” A credible employer should be able to assess the reasoning without expecting a confidentiality breach.

Make a one-page evidence sheet

For each application example, write five short lines: problem; decision owned; alternative considered; result you can substantiate; disclosure boundary. Mark the source of every number as public, cleared for external use, or internal only. Keep internal-only material out of the version you send. Review the sheet again before an interview, because an informal screen share can reveal as much as a file attachment.

Takeaway: The best impact example shows how you made a decision, what changed and how you know, while respecting the people and organisations behind the work. Demonstrating that boundary is itself evidence of professional judgment.

Transparency: EvitasJobs shares opportunities and career guidance. It is not the recruiter or employer and does not handle applications, selection or hiring decisions.