How to Assess Impact

A practical guide for telling the truth about your chapter's impact

We get it - “impact assessment” sounds like the kind of phrase that belongs in a consulting deck, not a Tuesday night board meeting. But strip away the jargon and it's really just one honest question: did anything actually change because of what we did? This guide is here to help you answer that - without a stats degree.

Introduction

Many chapters are great at counting - “200 people attended,” “5 events conducted.” Those numbers matter, but they don't tell the whole story. This guide helps you move from activity thinking to impact thinking, in a way that's simple, practical, and aligned with how oikos reports impact globally.

🧭 Here's What You'll Walk Away With

• A clear answer to: who benefited, what changed, and how do we know?

• A way to separate reach (who showed up) from beneficiaries (who actually got something out of it)

• A simple framework for spotting change across four different types - learning, behaviour, ecosystem, systems

• A fillable, copy-this-tonight structure for writing your own one-sentence impact statement

What Is Impact Assessment, Really?

It's the practice of checking - after (or during) a project - what genuinely changed, for whom, and how you know it's true. It's not a report you write to satisfy oikos International; it's a tool that helps your own chapter learn faster and make better decisions next semester.

Use it after any initiative - a workshop, a campaign, a partnership - and ideally, build it into your project design before launch (see Impact Project Design → Step 7).

Why Does This Matter for oikos Specifically?

Because oikos's entire value proposition to students, universities, and partners is that we develop leaders who create real sustainability impact - not leaders who are good at filling calendars. If your chapter can't say what changed because of your work, you can't:

• tell a credible fundraising story (see Fundraising Strategies - sponsors fund impact, not activities)

• prove to your university that you deserve continued support

• hand over a project to the next board with any idea of whether it's worth continuing

• genuinely know if you're living up to oikos's mission, or just staying busy

This isn't bureaucracy. It's the difference between doing things and doing things that matter.

How: From Activity to Impact - The Funnel

Step 1 - Start With the Intent

Before measuring anything, ask: what was the main intent of this initiative?

Common intents:

• Raise awareness

• Build sustainability leadership

• Encourage behaviour change

• Strengthen partnerships

• Support local communities

• Create systems change

Why this matters: success should be measured against the original purpose - not against a generic checklist. If the intent was awareness, measure learning and mindset shifts. If the intent was behaviour change, measure actions actually adopted, not just who showed up.

INTENT → INDICATOR → MEASUREMENT

Example: Awareness → Knowledge Gained → Survey Results

Helpful question to ask: What does success look like before we even start?

Step 2 - Identify Who Was Reached and Who Actually Benefited

These are not the same thing, and conflating them is the single most common mistake chapters make.

Key message: Attendance alone ≠ meaningful benefit.

Helpful question to ponder upon: Who participated, and who actually benefited?

Step 3 - Understand What Changed (The Most Important Step)

Ask: what changed because of this initiative? Think across four types of change:

• Learning change - what did people understand better? (increased ESG awareness, improved sustainability literacy)

• Behaviour change - did people act differently? (reduced single-use plastic, joined sustainability initiatives)

• Ecosystem change - did collaboration improve? (stronger NGO partnerships, business involvement)

• Systems change - did structures improve? (curriculum integration, new campus sustainability policies)

❌ Weak: “200 people attended.”

✅ Strong: “200 people attended, and 68% reported improved sustainability understanding.”

That one extra clause is the entire difference between an activity report and an impact statement.

Step 4 - Support It With Evidence (Numbers and Stories)

Quantitative evidence (what can be counted): participants reached, organisations involved, funds raised, waste reduced, volunteer hours, repeat participation.

Qualitative evidence (what can be experienced): testimonials, participant reflections, observations, quotes, stories of change.

“This project completely changed how I think about sustainable consumption.”

Golden Rule: Measure both numbers and narratives. Numbers alone feel cold and are hard to remember; stories alone are hard to compare or track. Together, they're the complete picture.

If you want one TED Talk that will permanently change how you think about “proving impact,” watch Dan Pallotta's "The way we think about charity is dead wrong". It's not specifically about measurement, but it'll make you rethink what you're optimising for in the first place - genuinely one of the most shared talks in the nonprofit world for a reason.

Step 5 - Think Across Levels of Impact

A single initiative can create change at multiple levels simultaneously. This is the oikos Cross-Level Impact Lens:

Helpful food for thought: At what levels did change occur?

Step 6 - Learn, Reflect, and Share

After every initiative, gather your team and ask:

• What worked well?

• What did not work?

• What surprised us?

• What would we improve?

• Could another chapter replicate this?

Sharing these learnings is what transforms a single project into an oikos best practice - and lets chapters across the world learn from each other instead of repeating the same mistakes in 40 different countries.

PROJECT → REFLECT → DOCUMENT → SHARE → BEST PRACTICE → OTHER CHAPTERS

Looking to document and hand off your reflections cleanly? Pair this with the Design for Continuity step in Impact Project Design and the chapter history / project documentation templates being built separately as part of the Toolbox.

🧩 Worked Example - Copy This Structure

Field	Example
Initiative	Sustainability Conference
Intent	Raise sustainability awareness
Reached	220 students, faculty, and sustainability professionals
Beneficiaries	Students interested in sustainability careers
What changed	72% reported stronger understanding of sustainability topics
Collaborators	NGOs, businesses, university faculty
Cross-Level Impact	Individual + Educational + Business & Industry

One-sentence impact statement:

“The conference strengthened sustainability awareness and fostered stronger collaboration between students, academia, and industry.”

Try it now: grab your chapter's last project and fill in these same seven lines. If you can't fill in “what changed,” that's not a failure - it's your sign for what to measure next time.

Summary

Impact is not what you did - it's what changed because of what you did, for whom, and how you know. Start with intent, separate reach from beneficiaries, look for change across four types, back it up with both numbers and stories, check which levels it touched, and always close the loop by reflecting and sharing.

🎯 Main Takeaway

Impact is not “what we did” - it's what changed because of what we did, for whom, and why it mattered.

💡 Tips & Tricks - Try This Tomorrow

• Rewrite your last event's headline stat. Take “X people attended” and add one clause about what actually changed for them. Notice the difference.

• Add one open-text question to your next feedback form: “What's one thing you'll do differently because of this?” - instant qualitative evidence.

• Run a 10-minute reflection round at your very next board meeting on your most recent project, using the five questions in Step 6. Document it somewhere you'll actually find it again.

• Pick one project from this semester and try to fill in the worked-example template above - intent, reach, beneficiaries, what changed, collaborators, cross-level impact, one-sentence statement.

• Before your next event, decide in advance what “success” looks like - write it down, so you're not retrofitting a definition afterward.