🎯Level 3 Challenge: Build a Community Initiative

Needs Assessment

Before any initiative, you must understand what the community actually needs — not what you assume it needs.

You work at a volunteer association and your coordinator has asked you to launch an initiative for young people in the neighbourhood. There is no ready data, no confirmed budget yet, and the proposal deadline is in three weeks. A needs assessment is not an opinion poll or an internal brainstorm. It is a systematic process of gathering information from multiple sources: affected community members, partners working in the area, and any existing data. The gap between need and demand matters: young people may ask for recreational activities, but the real need might be employability skills, psychosocial support, or a safe space for constructive dialogue. The steps in this context include: first, identifying who the target young people are and what different groups exist within them — female and male, people with disabilities, in school and out, married or not. Second, choosing information-gathering tools suited to the context and time available: individual interviews with representatives, focus groups, or direct field observation. Third, analysing what was gathered and ranking needs by expected impact and feasibility given available resources. Fourth, checking findings with the community itself before building on them, so that people are not surprised by an initiative they had no hand in shaping. The core principle: plan with people, not for them. Every decision at this stage shapes everything that follows — and bias in the assessment produces bias in design, which produces failure in delivery.

Writing the Proposal

A proposal is not a written dream — it is a contract with yourself about what you will do, how, with what, and how you will know if it worked.

After identifying the main need, you must turn it into a project proposal that can be evaluated, resourced, and held accountable. A good proposal answers six questions clearly: why this project (the documented problem), for whom (the direct beneficiaries and their characteristics), what exactly will be done (activities and timeline), with what (resources required), how we will know if it worked (measurable indicators), and who is responsible for each part (accountability structure). The most common mistake in volunteer proposals is writing beautiful goals without indicators. A goal like "empower youth" or "build self-confidence" without a defined measure means any outcome will look like success. A good indicator answers: how many? By when? Against what baseline? And it connects directly to the need you started with. The second mistake is unlimited promises: "we will solve unemployment in the neighbourhood" or "we will guarantee every participant succeeds." A commitment that exceeds available resources damages community trust more than honesty does. A sincere commitment to what you can actually deliver — even if less than what people want — is the foundation of long-term trust with the community you serve.

Building the Team

The proposal is approved. You now need three more volunteers for the event, with only two weeks to prepare.

Choosing the team and assigning roles is the phase that determines whether a good proposal will be delivered with quality or will stumble. The most common mistake here is selecting based on personal closeness — "I know them and trust them" — rather than the competence and availability needed for a specific role. Personal trust is valuable, but it cannot substitute for the skill a given role demands. Before choosing people, define the roles: what tasks are necessary to deliver this event? Who handles registration and reception? Who facilitates sessions? Who monitors safety and attendance? Who coordinates with the venue? Each role has clear responsibilities and defined accountability — and what is not named will not get done. After selection, clarity is a requirement, not a luxury: every volunteer must know exactly what they are responsible for, what requires coordination, and to whom they report if they face a situation outside their role. Ambiguity at the start produces duplication, gaps, and tensions that are hard to resolve during delivery.

• Define the necessary roles before choosing people, and tie each role to a skill it requires
• Select based on competence and actual availability, not personal closeness alone
• Clarify each volunteer's responsibility in detail: what to do, what not to do, and who to tell when needed
• Set a shared communication channel, meeting times, and a mechanism to cover unexpected absences
• Confirm understanding: ask each person to restate their role in their own words

Running the Event and an Unexpected Safeguarding Case

The event is running according to plan. Then something happens that was in no plan.

Thirty participants have arrived. The first session ended well and reactions seemed positive. During the break, a sixteen-year-old called Layla approaches you and says quietly: "There is an adult messaging me on the app asking for my personal photos. I told him no but he keeps insisting and won't stop." She looks confused and anxious, adding: "I haven't told anyone because I didn't know if this is a big deal or not." This situation has three dimensions at once: protecting Layla right now by making her feel safe and not returning her to the experience with questions; ensuring that what she said is recorded in her exact words without addition or omission; and referring the matter immediately to the appropriate channel — all without stopping the event or making the other participants feel that something exceptional is happening. Managing these three dimensions together while running an ongoing event is exactly what this challenge tests at this phase.

Evaluation and Accountability

The event is over. The initiative is not — what happens now determines whether it deserves to be repeated and built upon.

Evaluation is not a mandatory step to close a paper file — it is the tool that returns the association to the community with a genuine and honest question: did we do what we said we would, and did we produce the impact we promised to those we promised it to? Good evaluation begins before the event by documenting a baseline: what was the participant's level before the intervention? It ends afterwards by measuring change: what actually changed, for whom, to what degree, and why? Between those two points it monitors delivery for gaps: what did not go as planned and can it be corrected in real time? Volunteer accountability to the community means honestly answering three questions: did we actually reach who we intended to reach, or did we reach whoever was easiest to reach? Did we deliver what we promised, or did we step back from part of it without communicating? And did our initiative harm anyone in ways we did not anticipate? The third is the hardest, because answering it with "no" requires genuine investigative effort, not merely the absence of formal complaints. And before closing the file, the community represented in the initial assessment must participate in reading the findings — because they are the only party who can tell you whether what you call "success" matches what they experienced.