You did the consultations, sent the surveys, and gathered partner feedback from across multiple countries. So why does your findings section still read like a shopping list? This post is based on Lesson 2.2 from Module 2 — Consultation and Interpretation — in the EU KA2 Need Analysis course. It explores the key findings needs analysis process that separates a strong Erasmus+ proposal from a weak one. The difference is rarely how much evidence you collect. It is what you do with it afterwards.
For more information please check Needs Analysis resources. The AI Agent Node community explores exactly what evaluators look for in this area.
What Evaluators Actually See
Most project coordinators collect more evidence than they can use. They organise consultations, design questionnaires, interview target groups and gather partner comments. Yet when the findings section is finally written, it often becomes a catalogue of what people said. That is not a findings section. That is a data report.
Evaluators are trained to notice this. They are not looking for a list of comments. They are looking for a coherent, prioritised and evidence-backed explanation of what the consultation actually reveals. Raw data describes. Key findings explain what the evidence means and why it matters for the specific project being proposed.
The Cost of Skipping Interpretation
The gap between collecting evidence and producing key findings is where many promising proposals fall apart. It happens because interpretation feels harder than reporting. However, it is a learnable skill — and skipping it has a measurable cost.
When findings are presented as a list of stakeholder comments, the logical connection between evidence and project objectives disappears. Evaluators must then construct their own interpretation. That is additional work they should not have to do — and many will simply mark the section as insufficient.
Consequently, a project that ran excellent consultations can still score poorly on needs analysis. Not because the evidence was weak. Because it was never interpreted.
How the Key Findings Needs Analysis Process Works
In the 2026 Erasmus+ assessment logic, experts are explicitly instructed to evaluate only what is provided in the application. They cannot assume missing information or infer unstated reasoning. A findings section that reports data without interpreting it cannot receive credit for consultation work the evaluator cannot verify. That single rule explains a great deal about why thorough consultations still produce weak proposals.
There is a systematic method that changes this. It requires no specialist software and no advanced research training. It requires three structured steps applied to the evidence you already have — and the discipline to move through them in order.
The first step is coding. You read each piece of consultation evidence — each interview excerpt, survey response or partner comment — and assign it a short descriptive label. For example, a youth worker describing difficulty helping young people verify online information might be coded as “media verification gap”. This step transforms unstructured material into something you can examine systematically.
The second step is clustering. You look across the labelled excerpts and identify which codes share an underlying concern. Those belong in the same group. The goal is no more than three major clusters. Three focused findings connect more cleanly to objectives, work packages and expected results than a longer list ever will.
From Codes to Clusters
Naming a cluster is the bridge between raw evidence and a written finding. A good name captures the shared concern without becoming too vague. “Communication” tells the reader nothing. “Lack of structured feedback channels between youth workers and young participants” tells them everything they need to assess the need.
Not all clusters deserve equal prominence. Two criteria help you decide. First, urgency — does the issue actively block progress or create a significant gap? Second, recurrence — does the issue appear across multiple sources or stakeholder types? Findings that are both urgent and recurrent should lead the paragraph.
Findings that are interesting but low on both criteria should be set aside. Including weak findings dilutes the persuasive force of the needs analysis. Three well-supported claims are always more convincing than ten patchy observations.
Writing Key Findings Needs Analysis Paragraphs
A strong findings paragraph does three things. It names the finding clearly. It anchors the finding in evidence. It shows why the finding matters for the project being proposed. Each part is necessary — remove any one of them and the paragraph loses its persuasive force.
For example, a well-constructed finding might read: “Consultation with educators across partner organisations revealed a consistent gap in structured time for collaborative professional development. This finding recurred across both survey data and focus group discussions. It directly underpins the project’s proposed peer-learning modules.” That works because it names the issue, anchors it in evidence and connects it to the project logic.
The most common mistake is treating the findings paragraph as a place to report data. If you write that a majority of respondents said something, you are describing, not interpreting. To turn that into a finding, you must explain what the response reveals about the underlying need. That shift from description to interpretation is the core skill this lesson develops.
Inside our community, this is exactly what we work on together. Join us and start turning your consultation data into key findings that evaluators can follow — and fund.
Conclusion
As conclusion, the key findings needs analysis process is not simply a writing task. It is an analytical one. Coding, clustering and writing are the steps that transform consultation activity into a convincing argument for your project. A focused findings section — specific, traceable and proportionate — is one of the strongest signals that a project was genuinely designed around evidence. Join our Training Waiting List below.
