Stop Reporting What You Did. Start Proving What Changed.

You poured your heart into this year. You served the families, ran the workshops, kept the doors open. And when it came time to write the report, you proudly typed: "We trained 200 parents."

Here is the uncomfortable question that sits underneath that sentence: so what?

Did those parents actually become better able to raise their children? Did anything in their lives change? For about thirty years, nonprofit reporting focused almost entirely on what staff do: people served, hours delivered, sessions held. That is real work, and it matters. But it is the floor, not the ceiling. The leaders who grow past 100 supporters are the ones who can answer the "so what" question with confidence and honesty.

Let me walk you through how to make that shift without needing a research degree or a budget you do not have.

The one distinction that changes everything

Most of us mix up three words: outputs, outcomes, and impact. Getting them straight is half the battle.

• Outputs are the direct results of your activities, and they are almost always numerical. "200 parents trained." "40 hours of counseling delivered." These are easy to count, which is exactly why we lean on them.
• Outcomes are the change over time in the lives of the people you serve. "Parents are better able to raise their children." "A young person secured employment." "Someone gained confidence."
• Impact is stricter still. It is outcomes minus what would have happened anyway (the part researchers call deadweight or the counterfactual).

People routinely report outputs and call them impact. Reserve the word impact for the change you can genuinely tie to your work, and you will instantly sound more credible than most organizations in your field.

A simple way to picture the whole chain: inputs (your funding, staff, curriculum) lead to activities (the workshop), which produce outputs (200 attended), which lead to outcomes (better parenting), which contribute to impact (healthier families over time).

Name the change before you measure it

You cannot measure a change you have never described. Before collecting a single number, write down the change your program intends to create. A helpful prompt here is the BACKS model. Good outcomes describe a shift in:

• Behaviour (for example, reduced reoffending)
• Attitude (increased confidence)
• Condition (more people in permanent housing)
• Knowledge (improved parenting skills)
• Status (increased college enrollment)

Notice the difference between soft outcomes (a subjective change in knowledge, attitude, or behaviour) and hard outcomes (a tangible change in condition or status, like a qualification or a job). You will likely have both, and that is fine. Both are worth tracking.

Draw a simple logic model

A logic model is just a picture of how your program is supposed to work, linking inputs to activities to outputs to outcomes to impact. You can draw it as a flow chart, a table, or a few boxes on a napkin.

Why bother? Because it surfaces your assumptions, clarifies who is responsible for what, and gives you the template for choosing what to measure. Once the change is named, your indicators almost choose themselves. An indicator is a specific, observable, measurable marker that translates a fuzzy concept into something you can actually track.

Capture a baseline (this is the step everyone skips)

If you want to show change, you have to know the starting point. A baseline is the condition measured before your program begins. Without it, you are guessing. With it, you can say "confidence scores rose from here to there," which is far more honest and persuasive than a vague claim of improvement.

This does not require fancy software. A short survey at intake and again at exit, asking the same questions, will do real work.

Be honest about attribution

Here is where many leaders either overclaim or freeze entirely. Outcome measurement explores what your program provides and whether the intended changes occur. It does not prove your program caused them. Proving causation requires evaluation research with control groups, far more time, and far more effort.

So do not overclaim. It is more honest, and often more believable, to describe a plausible contribution rather than to insist you single-handedly caused the result. Funders and supporters trust the leader who says "we contributed to this change" over the one who claims credit for everything.

Make it a culture, not a chore

The goal is not a once-a-year scramble before a grant deadline. It is evaluation woven into daily work. The strongest organizations build a social-impact-focused culture: routine reflection, easy ways for participants to give feedback, and regular time set aside to make sense of what you are seeing.

This is everyone's job, not just an expert's. Leadership backs it and aligns it with strategy. Frontline staff capture data as they go. And the people you serve (yes, even your skeptics) get a voice throughout. Aim for evaluation that is useful, feasible, ethical, and accurate, and always proportional to your capacity.

What to do next

Pick one program. Just one. Name the change it is meant to create using the BACKS prompt, sketch a quick logic model, choose one or two indicators, and decide how you will capture a baseline. That single program becomes your template for everything else. If you want a structured way to see where this fits in your growth, the milestones at /milestones can help you connect impact measurement to your next supporter goal.

Your challenge this week

Take your most recent report and find one line that counts an output ("we served X people"). Underneath it, write the outcome you believe that activity created, and one indicator you could measure to know whether it is true. That single rewrite is the start of telling a story your supporters can actually feel.