A community project ends, the equipment is packed away, and someone asks a reasonable question: how many people did we help?

The answer matters. It can show whether supplies reached the intended destination, whether a team completed its planned work, and whether an event operated at the scale expected. But a number can also conceal the most useful questions. Was the assistance appropriate? Did people find it helpful? What remained unresolved? What changed after the team left?

A credible account of service needs room for both the count and the context. That does not mean every small project needs an expensive research study. It means choosing claims that match the evidence, and being willing to learn something more complicated than a success story.

Start with the decision the information will support

Before designing a reporting form, consider what the organization needs to decide. A team planning another distribution may need to understand whether its collection arrangements excluded people with limited mobility. A school-support project may need to establish whether donated equipment can be maintained. A funder may need a clear explanation of expenditure and delivery.

Those are different questions. Gathering the same long list of information for each can create work without producing useful answers. A practical starting point is one sentence: “We need this information so that we can decide whether to…” If the sentence cannot be completed, reconsider whether the information is needed.

This is an editorial recommendation for proportionate reporting, not a description of a system already adopted by WisdomPhilanthropy. Its value would depend on the actual project, the people involved and the resources available.

Separate what happened from what changed

The OECD's evaluation guidance distinguishes the immediate results of an intervention from broader, higher-level effects. It also encourages clarity about the different levels of results being assessed. This distinction helps prevent a record of activity from being presented as proof of lasting change. Source: OECD.

Consider a hypothetical school-kitchen project. An invoice might establish that an appliance was purchased. A delivery record could show that it reached the school. Confirmation from the school might establish that it was installed and used. These are useful pieces of evidence, but they answer different questions.

None alone proves that student attendance improved, that meals became more nutritious, or that learning outcomes changed. Those claims would require their own evidence. Even if such improvements occurred, other factors could have contributed. The project report should follow the evidence as far as it reaches, then stop.

Make a count understandable

Even a simple headcount needs a definition. Does “people reached” mean unique individuals, visits, households, or an estimate derived from items distributed? Were repeated visits counted separately? Does a total combine different projects whose participants might overlap?

A short explanatory note can make a modest number more useful than a large unexplained one. For example, a hypothetical report could state that it records service visits rather than distinct people. Another could report packages delivered without estimating how many household members benefited.

These are not reasons to abandon counting. They are reasons to count carefully. When records are incomplete, a range or an explicit unknown may be more responsible than a precise-looking total. Old figures should not acquire greater certainty simply because they are copied into a new website.

Let people describe usefulness in their own terms

A project can meet its internal delivery target and still miss something important. The IFRC's monitoring and evaluation guidance includes feedback and complaints as ways for people receiving services to express their views. Its approach recognizes that reports from the delivery team are only part of the picture. Source: IFRC.

For a small project, a proposed follow-up might ask three focused questions: what was useful, what was difficult, and what should change? The process should make room for criticism and for declining to participate. A request for feedback should not become a request for a grateful testimonial.

This distinction matters editorially as well as operationally. A compliment is a person's experience; it is not automatically representative of everyone involved. A concern raised by one person is worth understanding without presenting it as a universal judgment. Reporting should preserve those differences.

Choose a realistic follow-up

Some questions can be answered on the day. Others require time. A hypothetical equipment project might establish delivery immediately and check functionality later, after the school has had a chance to use the item. The timing should follow the question, rather than an arbitrary desire to publish a quick outcome story.

The follow-up also needs an owner. Who will ask, who will record the answer, and what will happen if a problem is reported? Promising extensive monitoring without the ability to respond can create expectations the organization cannot meet.

A small, completed follow-up is more useful than an ambitious plan that remains on paper. The published account should state which follow-up actually occurred, not only what had been intended.

Make room for an imperfect result

A useful project report can include an unmet need, a logistical difficulty or a change of plan. These details should be handled fairly, without exposing recipients or blaming volunteers to create a dramatic narrative.

Imagine a hypothetical distribution where the chosen collection time was inconvenient for some intended participants. The constructive question is what evidence reveals the problem and how the next plan should respond. A report that records only the total delivered would lose that opportunity to improve.

The same discipline applies when the result is encouraging. Explain why the team believes something worked, what evidence supports that interpretation, and what remains uncertain. Confidence grows when readers can see how a conclusion was reached.

Tell the fullest story the records can support

WisdomPhilanthropy's public work archive offers a starting point for recovering project history. As that history is developed into articles, old captions, figures and photographs need to be connected to their sources rather than treated as complete evaluations.

The aim should be a record that helps readers understand the work and helps future teams make better decisions. Count what can be counted reliably. Describe the experience that the evidence supports. Distinguish immediate assistance from lasting change, and leave unresolved questions visible.

A smaller claim that stands up to examination serves the community better than a larger claim the organization cannot explain.