Why Impact Documentation?
Impact documentation is how we tell the story of what actually happened, in a way that is usable for future funding, accountability, and learning. In Regenerant Catalunya, we:
- Focus first on documenting activities and outputs in a simple Google Doc activities report
- Use this as the basis for later Karma GAP reporting and evaluation
- Follow a lightweight version of the Impact Value Chain used in Regen Coordination’s GG23 round
For this round, we are not asking projects to become impact measurement experts. We only need clear, honest descriptions of:
- What you did (activities)
- What you produced (outputs / deliverables)
- What numbers show the scale of what happened (metrics)
The Impact Value Chain (Simplified)
The Impact Value Chain describes how resources turn into actions and then into change:
- Inputs → Resources you invest (time, money, people, spaces, materials)
- Activities → What you actually do with those resources
- Outputs → Tangible results or products directly created by your activities
- Outcomes → Changes that happen for people, communities or ecosystems
- Impact → The part of those outcomes that can reasonably be linked to your work
In this round we start with the middle of the chain:
- We ask you to list your key activities
- For each activity, capture outputs (deliverables) and metrics
- Outcomes and long‑term impact can be described briefly where relevant, but are not mandatory
This keeps the process manageable for small teams while still generating structured data we can use for evaluation and future rounds.
Key Concepts for Your Activities Report
Activities – What you did
Activities answer the question “What did we do?”. They are the chunks of work that matter most in your project.
Examples:
- Hosting a community workshop or assembly
- Running a weekly space, market, or mutual support activity
- Coordinating a planting, clean‑up or restoration action
- Designing and publishing an educational resource
- Organizing a campaign or event series
For this round, focus on high‑level activities, not every micro‑task. One activity can include several sub‑tasks.
Outputs / Deliverables – What was produced
Outputs are the tangible things that come out of an activity. In this program we split outputs into:
- Deliverables: concrete artefacts or products
- Metrics: numbers that show scale or reach
Deliverables (things)
Examples:
- Workshop slides, agendas or handouts
- Event recordings or podcasts
- Reports, guides, manuals, zines
- Prototypes, tools, or platforms
- Photo folders or documentation packs
For each deliverable we want to know:
- Name – what is it?
- Proof / link – where can we see it? (Drive folder, website, social post, etc.)
- Short description – what is it for / why it matters?
Metrics (numbers)
Metrics are numbers that help us see scale, participation or results.
Examples:
- Number of participants in a workshop or event
- Number of sessions held
- Hectares restored, trees planted, meals served
- Views / downloads of materials
- Number of collaborations, partners, or volunteers involved
For each metric we want to know:
- Name of metric – what are you counting?
- Description – how did you count it / what does it represent?
- Value – the actual number (or a reasonable estimate)
- Proof / link – if there is a source (attendance sheet, report, stats, etc.)
Which Activities Should You Report?
You do not need to report everything. Focus on the activities that:
- Best represent your work in this period
- Are most relevant to the goals of your project and network
- Have clear outputs and at least some metrics
Good candidates:
- A major initiative or project you led
- A key collaboration or partnership
- An important event or campaign
- An ongoing program that is central to your work
You can group repeated small events (for example, weekly sessions) into one activity with a metric like “Number of sessions in 2025: 12”.
How This Connects to Karma GAP and Evaluation
Your Google Doc activities report is the single source of truth for this round:
- It is the main preparation for future Karma GAP entries (Project Activity posts)
- Evaluators will use it, together with context from your network, to understand:
- What you did
- What you produced
- What scale you reached
Later, in the hands‑on Web3 & Karma GAP workshop, we will:
- Show you how to translate each activity block from the Google Doc into one or more Karma GAP activities
- Support wallet, account, and submission steps in a guided way
You do not need to worry now about how Karma GAP works technically. For the first wave of workshops, your job is simply to capture your work clearly in the Google Doc.
Quick Checklist for a Good Activities Entry
For each activity in your Google Doc:
- Activity name is clear and specific
- Description explains briefly what you did and with whom
- Dates show when it happened (or the period)
- Deliverables are listed with links where possible
- Metrics capture at least 1–2 meaningful numbers
- Evidence links point to folders, reports, images or posts
If you can do this for a handful of your most important activities, you will already have everything needed for later Karma GAP reporting and for this round’s evaluation.
Where to Go Next
- Use this page together with the Activities Report Google Doc template (one per project)
- During the documentation workshops, facilitators will:
- Help you decide which activities to report
- Co‑write or refine some examples with you
- Answer questions about deliverables, metrics and evidence
For more advanced background on impact and the full Impact Value Chain, see the original Regen Coordination Impact Reporting guidance (EN), which inspired this simplified version for Regenerant Catalunya.