Module 2: Building a Competitive Application

Federal grant applications are scored, not read. Every section of your application is a rubric response — a direct answer to the evaluation criteria you identified in Module 1.

This module walks through every major component of a competitive federal grant application, explains what reviewers look for, and shows you how to write each section so it earns maximum points.

How Reviewers Work

Before we talk about writing, it helps to understand who's reading your application and how they approach it.

Federal grant reviewers are typically subject-matter experts — professionals in the field your grant addresses. They volunteer or are contracted to review a batch of applications (often 8–15 at a time) over a few weeks.

Here's what that means for you:

Reviewers are reading many applications. Yours needs to be clear, well-organized, and easy to follow. If a reviewer has to hunt for information, your score suffers.

Reviewers score against the criteria. They have a scoring sheet with the same criteria listed in Section V of the NOFO. They read your application with that sheet in hand, assigning points criterion by criterion.

Reviewers write justifications. For each score, they write a brief explanation of why they gave those points. Make their job easy by clearly addressing each criterion.

The takeaway: Write for the scoring sheet, not for a general reader. Label your sections to match the criteria. Put information where reviewers expect to find it.

The Project Narrative

The project narrative is the core of your application — the written document where you make your case. Most NOFOs set a page limit (typically 15–25 pages) and specify what sections to include.

While every NOFO is different, most project narratives include these components:

Need Statement (Sometimes Called "Statement of Need" or "Problem Statement")

The need statement establishes why your project matters — what problem exists in your community that this grant would help solve.

What reviewers look for:

Specific data about the problem (population statistics, health data, economic indicators, environmental assessments)

Evidence that the problem exists *in your community specifically* — not just nationally

Connection between the problem and the funding program's goals

Urgency or timeliness (why now?)

How to write a strong need statement:

1. Lead with your community's data. "The XYZ Tribe has a population of 4,200 members, of whom 38% live below the federal poverty line" is stronger than "Many tribal communities experience poverty."

2. Use local evidence. Tribal-specific data, community assessments, and local reports carry more weight than national statistics alone.

3. Connect to the funder's mission. Show that your need aligns with what this specific agency and program are designed to address.

4. Quantify the gap. "Our community has 0 licensed substance abuse counselors for a population of 4,200" is more compelling than "We lack adequate mental health resources."

Common mistakes:

Writing about the problem nationally without connecting it to your specific community

Using outdated data (older than 3–5 years unless it's Census data)

Overstating the problem to the point of seeming hopeless (reviewers want to fund projects that can succeed)

Project Design (Sometimes Called "Approach" or "Project Description")

This section explains what you will do — the specific activities, timeline, and methods you'll use to address the need.

This is usually the highest-weighted criterion. Give it the most space and detail.

What reviewers look for:

Clear, specific activities (not vague statements of intent)

A logical connection between activities and outcomes (if you do X, it leads to Y)

A realistic timeline with milestones

Evidence that your approach is proven or well-reasoned

How to structure it:

1. State your goals — 2–3 broad outcomes you want to achieve

2. List your objectives — Specific, measurable targets under each goal (use SMART format: Specific, Measurable, Achievable, Relevant, Time-bound)

3. Describe activities — The specific things you'll do to meet each objective

4. Provide a timeline — A month-by-month or quarter-by-quarter plan showing when each activity happens

Example structure:

> Goal 1: Increase access to language learning for tribal youth ages 5–18

> Objective 1.1: Develop and pilot a 40-week language curriculum by Month 6

> - Activity: Convene an elder advisory panel of 5 fluent speakers (Months 1–2)

> - Activity: Draft curriculum with weekly lesson plans (Months 2–5)

> - Activity: Pilot with 3 classrooms, collect teacher and student feedback (Months 6–9)

> Objective 1.2: Train 8 tribal educators to deliver the curriculum by Month 9

> - Activity: Recruit educators from tribal school system (Month 4)

> - Activity: Conduct 40-hour training institute (Month 7)

> - Activity: Provide monthly coaching sessions during pilot year (Months 8–12)

Organizational Capacity

This section demonstrates that your organization can actually do what you're proposing. Reviewers want confidence that the money will be well-managed and the project will be executed competently.

What reviewers evaluate:

Prior experience — Has your organization managed federal grants before? Successfully?

Key personnel — Who will lead the project? What are their qualifications?

Financial systems — Do you have accounting systems capable of managing federal funds? An audited financial history?

Partnerships — Do you have relationships with other organizations that strengthen the project?

Sovereignty track record — For tribal applicants, reviewers value evidence of effective self-governance and program management

How to write a strong capacity statement:

1. Name your experience. "Our Tribe has successfully managed 12 federal grants totaling $4.3 million over the past 5 years, including 3 from this agency" is concrete and credible.

2. Introduce key staff. Include brief bios (3–5 sentences) for the project director, key personnel, and financial officer. Highlight relevant experience.

3. Describe your systems. Mention your accounting software, audit history, internal controls, and any compliance certifications.

4. Reference partnerships. Letters of support from partner organizations belong in the appendix, but describe the partnerships here.

Evaluation Plan

This section explains how you will measure whether your project is working. Reviewers want to see that you've thought about accountability and continuous improvement.

What to include:

What you'll measure — Outputs (activities completed) and outcomes (changes that result)

How you'll measure it — Data collection methods (surveys, attendance records, pre/post tests, community assessments)

When you'll measure it — A schedule for data collection and analysis

Who will do the evaluation — Internal staff, external evaluator, or both

How you'll use the findings — Will you adjust the project based on what you learn?

Tip: Many agencies prefer or require an external evaluator for larger grants ($500,000+). Even if not required, mentioning an external evaluation component shows rigor.

The Logic Model

A logic model is a one-page visual that shows the connection between what you put into your project and what comes out. Nearly every federal NOFO requires one.

Think of it as a chain:

Inputs → Activities → Outputs → Short-term Outcomes → Long-term Outcomes

Common mistakes with logic models:

Making them too complicated (keep it to one page)

Confusing outputs with outcomes (outputs are what you produce; outcomes are the changes that result)

Not aligning the logic model with the narrative (they should tell the same story)

Budget Construction

The budget is where many applications lose points — not because the numbers are wrong, but because they aren't explained clearly.

SF-424A Budget Categories

Federal budgets use standard categories from the SF-424A form:

Budget Justification Narrative

The budget justification explains why each expense is necessary and how you calculated it. This is where most budget problems occur — not in the numbers, but in the explanations.

Good budget justification:

> Project Coordinator (1 FTE, 100% time on project)

> Annual salary: $55,000. The Project Coordinator will manage daily operations, coordinate with partner organizations, supervise program staff, and prepare quarterly reports. This position is essential to project implementation and was benchmarked against comparable tribal program coordinator salaries in our region.

Weak budget justification:

> Project Coordinator: $55,000

Tip: For every line item, answer three questions: What is it? Why do you need it? How did you calculate the cost?

Indirect Cost Rates

Indirect costs are overhead expenses (rent, utilities, administrative staff) that support your project but aren't directly tied to a single activity.

How it works:

If your Tribe has a Negotiated Indirect Cost Rate Agreement (NICRA) with your federal cognizant agency, use that rate

If you don't have a NICRA, you can use the 10% de minimis rate (10% of your modified total direct costs)

Some agencies cap indirect costs — check the NOFO

Why your rate matters: A higher indirect cost rate means more of the grant covers your operational overhead. If your rate is 25% and you receive a $500,000 grant, $100,000 goes to indirect costs — money that keeps your office running and your administrative systems functioning. Negotiating an appropriate rate is worth the effort.

Common Reasons Applications Are Rejected

Before you submit, check your application against these common failure points:

1. Didn't follow instructions — Exceeded page limits, used wrong font size, missed required forms

2. Didn't address all criteria — Skipped a criterion or addressed it superficially

3. Vague project design — "We will improve outcomes" instead of specific, measurable activities

4. Weak or missing evaluation plan — No clear way to measure whether the project works

5. Budget doesn't match narrative — The narrative describes activities not reflected in the budget, or vice versa

6. No local data — Used only national statistics instead of community-specific evidence

7. Late submission — Grants.gov closed and the application wasn't uploaded in time

8. Missing required documents — Forgot a letter of support, tribal resolution, or required form

Exercise: Score a Sample Capacity Statement

Take this sample capacity statement and score it using the criteria from Module 1:

> *"Our organization has been serving the community for many years. We have experienced staff who are committed to this work. We have managed grants before and have an accountant on staff. We are well-positioned to implement this project."*

Questions to consider:

1. What specific information is missing?

2. If you were a reviewer, how many points (out of 15) would you give this?

3. Rewrite 2–3 sentences to make them specific and evidence-based

This exercise builds the skill of reading your own application from a reviewer's perspective — the most valuable editing skill in grant writing.

Key Takeaways

Write for the scoring sheet: label sections to match criteria, allocate space proportionally to point values

Every claim needs evidence — use local data, specific numbers, and named experience

The logic model and narrative must tell the same story

Budget justifications explain the "why" and "how calculated," not just the dollar amount

Review your application against common rejection reasons before submitting

How GrantsPath Helps

GrantsPath's rubric-based generation system creates supporting documents — logic models, capacity statements, and budget justifications — scored against the same criteria reviewers use. The NOFO Criteria Extraction from Module 1 feeds directly into this process, ensuring your documents are aligned with the specific evaluation criteria.

The tools generate strong first drafts. Your job is to review them with the knowledge from this module: Does the capacity statement include specific numbers? Does the logic model connect inputs to outcomes? Does the budget justification explain every line item?

Related guides: Supporting Documents · SF-424 Forms · Budget Builder

Building a Competitive Application