Grant Writing Tips for Applicants: How to Write a Strong Grant Application

Most grants management content is written for funders. This guide is written for applicants — specifically for people writing grant applications who want to understand what assessors are looking for, and how to present their work in a way that makes its value clear.

This isn't a guide to gaming the system. It's a guide to communicating your real work clearly, so that funders can make an informed decision about whether to support it.

Read the guidelines carefully

The most common reason grant applications fail is that they don't follow the guidelines. Before writing a single word, read the guidelines thoroughly:

  • Eligibility criteria. Are you genuinely eligible? Don't assume — check every criterion explicitly. If you're uncertain about any criterion, contact the funder before investing time in an application.
  • Funding priorities. What does this funder specifically care about? Applications that are excellent but don't align with the funder's stated priorities rarely succeed.
  • Format requirements. Word limits, required attachments, budget format, deadline. Not following format requirements signals to assessors that you don't pay attention to detail.
  • What's excluded. Many funders have explicit exclusions. If your project involves excluded activities, don't apply.

Understand what the funder is trying to achieve

The best applications don't just describe what the applicant wants to do — they explain how the applicant's work connects to what the funder is trying to achieve. This requires understanding the funder's goals, priorities, and theory of change.

Ask: Why does this funder exist? What problem are they trying to solve? How does my work contribute to that?

If you can't answer these questions from the funder's guidelines and website, consider contacting the funder to understand their priorities better before applying.

Make the problem clear

Most grant applications describe what the applicant wants to do, but don't make the underlying problem clear first. A strong application starts by establishing:

  • What problem or need exists?
  • Who is affected by it, and how significantly?
  • Why does this problem exist — what are the contributing factors?
  • What happens if nothing changes?

Evidence — data, research, community testimony, your organisation's experience — makes the problem description credible. Don't just assert that there's a problem; show it.

Describe your solution clearly

After establishing the problem, describe your approach:

  • What will you do, specifically?
  • How does this address the problem you've described?
  • Who will deliver it, and what are their qualifications?
  • How many people will it reach?
  • Where and when will it happen?

Clarity is essential. Assessors read many applications. Applications that require effort to understand what the applicant is actually proposing are harder to assess and often score lower than simpler applications that are equally strong.

Avoid jargon. Sector-specific language that makes sense to insiders may be opaque to an assessor from outside your field. Plain language is almost always better.

Show your track record

Funders are assessing whether you can deliver what you're proposing, not just whether the proposal is a good idea. Evidence of track record is important:

  • What has your organisation done previously that's similar to this proposal?
  • What were the outcomes?
  • If your organisation is new, what relevant experience do the key people bring?

Don't over-claim. A modest, honest description of what you've achieved is more credible than exaggerated claims. Assessors who suspect inflated track record claims may discount the whole application.

Be specific about outcomes

Vague outcome statements — "improve community wellbeing," "build capacity," "increase awareness" — are almost meaningless to assessors. Strong applications specify:

  • What specifically will change for whom?
  • How will you know if it's changed?
  • How will you measure it?

Good outcomes are: specific (what, for whom), measurable (how you'll know), achievable (realistic given what you're proposing), and time-bound (by when).

Bad: This project will improve mental health outcomes for young people.

Better: By December 2026, 80% of programme participants will report improved confidence and reduced anxiety symptoms on standardised self-assessment tools.

Budget credibly

Budget credibility is a significant factor in grant assessment. A budget that doesn't add up, uses round numbers throughout, or includes unexplained items signals poor planning.

Be specific. Rather than "$5,000 — facilitation," show "$5,000 — 5 workshop facilitation days × $1,000/day." Real calculations are more credible than round numbers.

Justify staff time. If staff costs are included, show the calculation: role, hours, rate. Unexplained salary costs are a common red flag.

Show other funding. If the funder is funding part of a larger project, show where the rest of the money is coming from, and what the status of that funding is (confirmed vs pending). Applications that don't account for the full project budget raise questions.

Don't underbudget. Applications that are clearly underfunded to look more attractive are likely to fail delivery. Funders have seen this pattern before.

Address the hard questions

Strong applications anticipate the concerns an assessor might have and address them directly:

  • Is there a risk this won't work? What's your contingency plan?
  • Is there someone else already doing this? How is your approach different?
  • Why should the funder trust that you can deliver this?
  • What happens to the programme after the grant period ends?

Applications that don't acknowledge risks or challenges can seem naive. Applications that acknowledge difficulty honestly and explain how it will be managed are more credible.

Follow up appropriately

After submitting:

  • Confirm receipt. If the system doesn't automatically acknowledge receipt, follow up to confirm the application was received.
  • Don't pester. Contacting the funder repeatedly about the status of your application is annoying and can be counterproductive. Check the funder's stated timeline and only follow up if it's significantly overdue.
  • If unsuccessful, ask for feedback. Not all funders provide individual feedback, but many do. Feedback — even brief — can help you improve future applications or understand whether re-applying is worthwhile.

What assessors see all day

Assessors read many applications. From their perspective, the most common problems are:

  1. Applications that don't follow the guidelines
  2. Applications that describe activities without making outcomes clear
  3. Applications with vague, jargon-heavy descriptions of what will actually happen
  4. Applications where the budget doesn't match the description
  5. Applications where the stated problem doesn't connect to the proposed solution
  6. Applications that claim implausibly large impact for the amount of money requested

The best application isn't the most technically sophisticated — it's the one that makes the assessor's job easiest by clearly answering: what are you trying to achieve, who will benefit, what specifically will you do, how will you know if it worked, and can we trust you to do it?


This guide is provided for applicants. Tahua builds grants management software for the funders you apply to — software that helps them run clearer, fairer, more efficient grant programmes. If you're a funder interested in improving your programme design and applicant experience.

**.

book a conversation →