Nyumbani/Hifadhi/How to Write a Small Grant Application That Clearly Shows the Need
Makala Grant Basics

How to Write a Small Grant Application That Clearly Shows the Need

A step-by-step guide to connecting community need, planned activities, and a realistic small-project budget without overstating what you can prove.

Birgit Sommer/ 28 Juni 2026 /9 dakika kusoma /Local Grantmaking
How to Write a Small Grant Application That Clearly Shows the Need

Grant writing is mostly translation. You translate what people in the neighborhood already know into a form a funder can responsibly read, compare, and approve. The danger is that translation can turn into theatre: bigger claims, cleaner stories, and outcomes no small project can honestly promise.

A good small application does not sound expensive. It sounds clear. It shows a real need, a proportionate response, and a budget that behaves like the activity plan in numbers.

Step 1: Write the need before you write the project

Begin with the situation, not your idea. Many applications fail softly because they describe the activity with warmth but never show why it is needed.

Use three or four plain sentences:

  • What is happening or missing?
  • Who is affected or asking for something different?
  • How do you know?
  • Why is a small local response useful now?

For example, do not start with “We want to run creative workshops.” Start with “Families in our housing estate have asked for low-cost activities after school because the nearest regular offer is difficult to reach and many parents cannot pay commercial fees. Our group has spoken with parents at the courtyard meetings and tested one afternoon activity. Children came back the next week asking when it would happen again.”

That is not a statistic. It is community evidence. For a small grant, that can be enough if it is specific and honest.

Step 2: Use evidence you actually have

Small groups often think evidence means a formal survey or published research. Sometimes those help. But early neighborhood projects can also use grounded evidence from direct contact.

Useful evidence includes:

  • Notes from open meetings or resident conversations.
  • A waiting list or repeated requests.
  • Attendance at a pilot event.
  • Observations from volunteers who regularly meet the group.
  • Feedback forms, if they are simple and accessible.
  • Letters of support from a school, community center, tenant group, cultural association, or local service.
  • Photos of a space or material problem, if consent and privacy are handled properly.
  • Public information about missing services, distance, cost, or barriers.

Do not inflate evidence. “Several parents told us…” is acceptable if that is what happened. “The whole district urgently needs…” is probably too broad unless you can support it. Funders can work with modest evidence. They struggle with claims that sound copied from a policy document but are not connected to the project.

If your evidence involves personal stories, ask permission before using details and remove identifying information unless the person clearly wants to be named. For deeper work on ethical story use in public campaigns, Civic Futures Lab and Community Voices Media go further than this funding guide.

Step 3: Define the group you are serving without flattening people

Grant forms often ask for a target group. Answer clearly, but do not reduce people to a problem label.

Better than “disadvantaged residents” is “older residents in the estate who have told us they rarely attend city-center activities because of distance, cost, and not knowing anyone there.” Better than “migrant women” is “women in our language exchange group who want a low-pressure way to practice German while also sharing childcare and local information.”

Name the access issue, not only the identity category. Funders need to understand who the project is for, but your neighbors should still recognize themselves with dignity if they read the application.

Step 4: Turn the need into activities

Now describe what you will do. Activities should be concrete enough that a stranger can imagine the work.

Include:

  • What will happen.
  • How often.
  • Where.
  • Who will prepare and deliver it.
  • How people will hear about it.
  • What support is needed for access, language, travel, childcare, food, or materials.

Keep the scale believable. If you have never run a monthly event, do not promise a year of weekly sessions unless a partner is carrying serious capacity. A small funder is usually more comfortable with a well-planned first round than a grand plan held together by hope.

Link each activity back to the need. If the need is isolation among older residents, the activity should create repeated, reachable contact. If the need is lack of low-cost youth activity, the budget should not mostly buy publicity. If the need is language access, translation or interpretation should appear in the plan and budget.

Step 5: State outcomes as changes you can reasonably notice

Outcomes are the difference the project aims to make. They are not the same as activities. “Run four workshops” is an activity. “Participants know where to find local support and have met neighbors they can contact again” is an outcome.

For a small grant, choose two or three realistic outcomes. Avoid promising social transformation. A courtyard project will not “end loneliness.” It may create a regular meeting point where residents exchange practical help and some people return more than once. That is worth funding.

Good small outcomes sound like this:

  • Participants know about a local service or opportunity.
  • Residents meet others they did not previously know.
  • Volunteers test a model and learn what is needed for a regular version.
  • A shared space becomes easier to use for a specific group.
  • A group produces a simple resource in accessible language.

Also say how you will know. You might count attendance, collect short feedback, hold a closing conversation, record repeat participation, or document what changed in the next plan. Keep evaluation smaller than the project.

Step 6: Build the budget from the activities

The budget is not a separate document with numbers attached at the end. It is the activity plan in money form.

Make a line for each real cost:

  • Room hire or contribution to space costs.
  • Materials.
  • Food or refreshments, if they support participation.
  • Travel or transport.
  • Translation, interpretation, or accessibility support.
  • Childcare during sessions.
  • Volunteer expenses.
  • Honoraria for people doing defined work.
  • Printing and communication.
  • Insurance, permits, or host administration, where relevant.
  • Coordination time, if someone must organize reliably.

Then check whether every cost has a reason. If you request materials, the activity plan should show what they are for. If you request food, explain whether it is part of participation, hospitality, or the activity itself. If you request coordination time, say what coordination includes: booking rooms, contacting participants, buying supplies, preparing sessions, documenting spending, and following up.

Do not hide labor. Many community projects pretend that organizing happens by itself. It does not. If the funder allows coordination or honoraria, include them honestly. If the funder does not, decide whether the grant is still fair to the people doing the work.

Step 7: Make the budget detailed enough, not decorative

How detailed should a first project budget be? Detailed enough that the funder can see the logic and you can manage the money without guessing later.

Use clear units where possible:

  • Number of sessions times room cost.
  • Number of participants times material estimate.
  • Number of hours times honorarium rate.
  • Number of print items times estimated print cost.

You do not need false precision. If a cost is an estimate, say it is an estimate and base it on a realistic quote, past purchase, or local price check. Do not invent exactness to look professional.

Add a short note for unusual costs. Accessibility support, interpretation, childcare, and volunteer reimbursement are not extras if they make participation possible. Name that. A funder who understands community work should not treat access as decoration.

Step 8: Explain who is responsible

Funders do not only fund ideas. They fund the ability to carry them out. For an informal group, this does not mean pretending to have an office. It means naming roles.

Write who will:

  • Coordinate the project.
  • Handle money and receipts.
  • Deliver activities.
  • Communicate with participants.
  • Keep basic records.
  • Liaise with a host organization, if there is one.

If you have a fiscal host, explain what the host does and what the project group does. For example: “The host organization will receive the grant, pay invoices, and support accounting. The resident group will plan and deliver the sessions, collect feedback, and submit receipts.” That division reassures funders because it reduces confusion.

Step 9: Name risks without making the project sound doomed

Every project has risks. A small application can name them briefly and show the practical response.

Common risks include low attendance, volunteer illness, room problems, cost increases, language barriers, conflict in the group, or weather for outdoor activity. Pair each risk with a sensible action: reminder calls, a backup volunteer, a second room option, simpler materials, interpretation, a short group agreement, or an indoor alternative.

Do not write a crisis manual unless the project calls for one. If your work involves child safeguarding, domestic violence, serious mental-health crisis, or other specialist safety questions, get appropriate guidance. Safe Childhood & Family Support Network covers safeguarding depth; this article stays with grant design and operations.

Step 10: Cut claims the project cannot carry

Before submitting, read the application once with a red pen for overclaiming.

Cut or soften phrases like:

  • “This will solve…”
  • “All residents need…”
  • “No other support exists…”
  • “The community wants…”
  • “We guarantee…”

Replace them with honest language:

  • “This will test…”
  • “Residents who spoke with us described…”
  • “Nearby options are difficult for this group because…”
  • “The project aims to…”
  • “We will learn whether…”

This is not weakness. It is credibility. A funder can say yes to a project that knows its size.

Finally, check the three links: need to activities, activities to budget, budget back to need. If a budget line does not support an activity, remove it or explain it. If an activity does not respond to the need, revise it. If the need is moving but unsupported, ground it in what you know.

The best small grant applications are usually not the most polished. They are the ones where the reader can see the neighborhood, the work, the money, and the limits without having to guess.

More from the archive