Before the application: test the need.
Ask the intended target group about current experience, obstacles and the support they would use. Partner assumptions and participant evidence should inform each other. A survey does not guarantee a successful grant application.
Keep a short record of who was invited, the languages used and how participants were selected. Explain the sample in the proposal rather than treating every response as a population estimate.
During implementation: measure the appropriate outcome.
- Use a short poll for an immediate activity decision.
- Ask about content, teaching and organisation separately in an event survey.
- Use a scored test when the question concerns knowledge or a specific skill.
- Follow up later when the question concerns using what was learned.
Attendance, satisfaction, learning and impact are different claims. Pre/post evaluation helps plan a comparison, but a score change alone is not proof of a causal project effect.
Across countries: preserve shared meaning.
Create language versions within the same study, review translations with local partners and pilot each version. Record language, country and recruitment source separately when needed.
A shared dataset saves you from manually combining language files. It does not eliminate differences between the people each partner reached.
At reporting: make the result usable.
Place selected findings from different project measurements in one live report. State the participant base and timing for each component. Explain what changed and what the study cannot establish.
Add researcher audio commentary where useful. Permitted readers can share a chart image or an audio-supported animated video, helping findings reach people beyond the partnership.