You have written the need statement. You have described the problem. But if you cannot name exactly where that need came from, your evaluator will quietly mark it down. This post draws on Lesson 1.3 — Source of Need Identification from Module 1 Framing the Need Analysis in the EU KA2 Need Analysis course. Here we explore how needs analysis evidence sources determine whether your proposal convinces a reviewer or loses ground on relevance.
For more information please check Needs Analysis resources. The AI Agent Node community regularly shares practical guidance on what evaluators actually look for in this area.
Why Needs Analysis Evidence Sources Matter
Most applicants make the same mistake. They describe a need that sounds reasonable — youth workers need digital skills, educators need inclusive methods — and assume that because the problem is widely known, evaluators will accept it.
They won’t. An evaluator’s job is not to agree with you. Their job is to assess whether your proposal provides sufficient evidence for the need you are claiming. A generic sector claim with no named source scores poorly, regardless of how well-written the rest of your application is.
Furthermore, this is not a minor wording issue. It is a structural one. When your need is not traceable, evaluators cannot confirm that your proposed activities address a real, identified gap. That is when strong partnerships and innovative ideas still fail to secure funding.
The Real Cost of Weak Evidence
A weak evidence section does not stay contained. It spreads. Your objectives start to look unmotivated. Your activities appear disconnected from the actual problem. Your impact logic begins to fall apart. One underevidenced need can undermine every section that follows.
Consider a consortium with five experienced partners, a well-designed methodology, and a genuinely relevant topic. However, their needs section says youth workers “face challenges with digital tools in a rapidly changing environment.” That statement is not evidenced. It is an assumption. And assumptions, however reasonable, do not satisfy the relevance criterion.
The result is a proposal that scores low on relevance despite everything else being strong. That is a costly and entirely avoidable outcome.
Five Source Types Every KA2 Applicant Needs
There are five core source types for identifying a project need, and each serves a different purpose. Surveys provide direct, quantified evidence from your target group. They are strongest when you name the number of respondents, their profile, the countries covered, and the key finding you are using in the proposal.
Observation captures what people actually do in practice — not what they say they do. It is especially valuable when real behaviour differs from reported experience. Stakeholder feedback adds contextual depth by showing how a problem plays out in daily work, making the need feel grounded and specific.
Prior project learning draws on evaluations, pilot reviews, and lessons from earlier initiatives to show that the gap is not new or accidental. Finally, internal review uses organisational records and reports to reveal capacity gaps inside your own partner institutions. This source is often particularly credible because it comes directly from the organisations that are making the application.
Matching Needs Analysis Evidence Sources to Need Types
Not every source suits every need type, and choosing the right match strengthens your proposal logic considerably. Individual needs — where the gap sits in a person’s skills or behaviours — are best supported by surveys, observation, and direct stakeholder feedback, because these capture what the target group actually experiences.
Organisational needs, where the gap sits inside an institution’s processes or capacity, call for internal review and prior project learning. These sources show how the institution itself has recognised and documented the problem. Systemic needs, which cut across countries or sectors, typically require triangulation — using more than one independent source to confirm the same gap from different angles.
Triangulation is what separates adequate proposals from strong ones. Two or more sources pointing to the same need make your argument coherent, defensible, and genuinely transnational. That combination is exactly what evaluators are looking for when they score the relevance section.
The Source Matrix
A source matrix maps each identified need to the evidence that supports it. In practice, it works as a four-column table. The columns are the identified need, the source type used, what that source actually showed, and which partners or countries it is relevant to.
When you can complete all four columns clearly and specifically for every major need in your proposal, your needs analysis is ready to be written. Moreover, the matrix exposes gaps before submission — it shows you immediately where you are overrelying on one piece of evidence or where a need is still unsupported.
This simple exercise also helps the whole consortium align. Partners can see which needs they contributed evidence for, which sources came from which countries, and whether the full picture is genuinely transnational. That transparency strengthens both the proposal and the partnership.
Strengthen Your Needs Analysis Evidence Sources Before You Submit
There is a straightforward test you can apply to every need statement before you submit. Ask whether, if an evaluator challenged you on it, you could name the source, cite the specific finding, and explain why it matters for this particular project. If the answer is yes, you are in strong territory. If not, the need is not yet ready.
The good news is that this is a learnable and practicable skill. Once you understand the five source types, know how to match them to your need type, and can build a matrix that maps evidence to gaps, you stop guessing. You start building a proposal that holds together under scrutiny from the first page to the last.
Additionally, well-sourced needs do more than score well on relevance. They give your entire project logic a credible foundation. Activities make sense because the need is real. Outcomes are believable because the gap has been shown, not assumed. The whole proposal becomes more coherent as a result.
If you want to apply this directly to your own project context, our community works through exactly these methods in a structured training environment. Come in and see how it changes the way you write.
Conclusion
As conclusion, needs analysis evidence sources are not a detail you can add at the end of the writing process. They are the foundation that makes every other part of your proposal believable. When your evaluator can see exactly where your need came from, what it showed, and why it matters for this specific project, your application becomes a different kind of document — one that is traceable, convincing, and built to score. Join our Training Waiting List.
