How to Write a Grant Application That Reviewers Actually Fund

A grant application is not a form you fill out — it is a persuasive document scored against a rubric by a reviewer reading dozens of submissions in a row. The winners aren't always the best projects; they're the best-argued ones. Here is what each section is really asking for, and how to write it so a tired reviewer at application number 27 still says yes.

Before You Write a Word: Read the Rubric

Almost every government funding opportunity publishes its scoring criteria — how many points go to need, approach, capacity, budget, and outcomes. This is the single most ignored document in grant writing. If "community impact" is worth 40 points and "organizational capacity" is worth 10, you write accordingly. Applicants who skip the rubric spread effort evenly and lose to those who aimed at the points.

Print the scoring criteria and keep them next to you. Every paragraph you write should map to points on that sheet.

The Need Statement: Make the Reviewer Care

This is where you establish the problem your project solves. The mistake is describing your need ("we need funding to grow") instead of the problem in the world ("40% of small manufacturers in our county lack the equipment to bid on federal contracts"). Reviewers fund problems, not wish lists.

Ground it in specifics: local data, named populations, concrete gaps. A need statement built on "many people" and "a lot of businesses" reads as guesswork. One built on real numbers reads as a team that understands its territory.

The Project Narrative: Show the Machine Working

This is the heart of the application — what you will actually do. Weak narratives describe intentions ("we will support entrepreneurs"). Strong ones describe mechanisms ("we will run four 8-week cohorts of 15 businesses each, delivering 32 hours of instruction and one-on-one mentoring, measured by a pre/post capability assessment").

A fundable narrative answers, in order:

• What exactly will you do? (activities, not adjectives)
• Who will you serve, and how many?
• When — a timeline with milestones the reviewer can picture
• Who is doing it — the people and their relevant track record
• How you'll know it worked — measurement built in from the start

Reviewers are trained to look for a clear line from activities → outputs → outcomes. If they can't trace it, they can't score it.

The Budget: Where Applications Quietly Die

The budget is not an afterthought — it is a credibility test. Every number should tie back to an activity in your narrative. If your narrative promises mentoring but your budget has no line for mentors, the reviewer notices. If you request $200,000 but the work described plausibly costs $80,000, you look like you're padding.

Budget rules that separate funded from rejected:

• Justify every line. "Personnel: $60,000" is weak. "Program coordinator, 0.5 FTE × $120,000 salary = $60,000" is fundable.
• Match the narrative exactly. No costs for activities you didn't describe; no activities you didn't fund.
• Respect the cost principles. Federal grants disallow certain expenses (entertainment, lobbying, some equipment). Know the rules before you list a cost.
• Handle matching funds honestly. If the program requires a 1:1 match, show exactly where your share comes from. Vague matches get flagged.

Outcomes and Evaluation: Prove You'll Measure Yourself

Agencies increasingly fund based on measurable impact, and they want to see your measurement plan before they give you money. Distinguish outputs (what you produce — "trained 60 businesses") from outcomes (what changes — "40% of trained businesses won a new contract within a year"). Outputs show activity; outcomes show impact, and impact is what gets renewed.

Name your metrics, your baseline, your target, and how you'll collect the data. A reviewer who sees a real evaluation plan trusts you with public money.

The Five Mistakes That Sink Strong Projects

1. Ignoring the rubric — writing a good application aimed at the wrong points.
2. Describing intentions, not mechanisms — "support" and "empower" instead of specific activities.
3. A budget disconnected from the narrative — the fastest way to look unserious.
4. No measurement plan — you can't be funded for impact you can't prove.
5. Submitting at the deadline — portals crash, and a late federal application is simply not reviewed.

Free Help Is Available — Use It

You don't have to do this alone. Your local Small Business Development Center (SBDC) and SCORE mentors review applications for free. A second set of eyes that knows the process catches the gaps you've gone blind to.

When you're ready, find a program that fits your project and read our companion guide on the most common application mistakes.