Guide · Proposal craft

Grant writing tips for first-time applicants

Strategies and common mistakes to avoid when writing your first federal grant proposal.

The short answer

Federal grant writing is reviewer-conscious composition: read the NOFO as a scoring rubric, align every section to published criteria weights, and replace vague claims with sourced numbers, specificity is the highest-leverage edit.

90 min
typical substantive review time per application
20–30%
applications fail administrative review first
NOFO
is the blueprint, write to its criteria, not your outline

Where programs concentrate

ED77HHS65USDA51HUD35DOT26EPA26
Top agencies by assistance-program count in this catalog (24 agencies). Tailor voice and compliance to the issuing agency.

Before You Write a Word

Read the NOFO Multiple Times

The Notice of Funding Opportunity (NOFO) is your blueprint. Read it at least twice before writing. Highlight key requirements, evaluation criteria weights, and page limits. If reviewers are told to score on specific criteria, your proposal must directly address those criteria.

Check Your Eligibility First

Confirm your organization meets every eligibility requirement in the NOFO before investing time in writing. Also verify your SAM.gov registration is current, many applicants discover their registration has expired days before the deadline.

Contact the Program Officer

Most FOANOs include a program officer contact. A short, professional email with a genuine question shows interest and may yield valuable insight about what reviewers are looking for. Avoid generic questions, ask something specific about the program.

Writing a Strong Narrative

Lead with the Problem, Not Your Organization

Reviewers want to know that you understand the problem deeply, not just that your organization exists. Start your needs statement with data, stories, or community input that demonstrates the severity and scope of the issue you're addressing.

Align Your Project with the Funder's Priorities

Explicitly connect your project goals to the program's stated objectives. Use language from the NOFO where appropriate. If the program emphasizes "evidence-based interventions," name the evidence base for your approach.

Be Specific About Activities and Timelines

Vague proposals lose points. Instead of "we will provide training," write "we will conduct eight 3-hour training sessions for 20 participants each month from January through August, using the XYZ curriculum." Reviewers want to see that you've thought through implementation.

Quantify Everything Possible

Use numbers: populations served, hours of service, number of sites, percentage improvement targets. Programs with measurable outcomes score higher than those with aspirational language.

Budget Best Practices

Justify Every Line Item

The budget justification narrative should explain the calculation method and rationale for every cost. Use only the rates, categories, and cost rules stated in the current funding opportunity notice and your organization's governing records.

Know the Allowable Cost Rules

Federal cost principles are governed by 2 CFR Part 200 (Uniform Guidance). Key rules: costs must be allocable, allowable, and reasonable. Entertainment, lobbying, and certain fundraising costs are generally unallowable.

Calculate Indirect Costs Correctly

Use the rate and method permitted by the current funding opportunity notice and the applicable eCFR rule. PlainGrants does not store an applicant's negotiated indirect-cost rate or a program-specific alternative.

Common Mistakes to Avoid

  • Ignoring page limits - Many systems truncate submissions at the limit. Over-length proposals may be returned or disqualified.
  • Generic proposals - Copy-pasting from previous applications without tailoring to this NOFO is obvious to reviewers.
  • Weak evaluation plan - "We will track number of people served" is insufficient. Include pre/post measurements, comparison groups, or validated tools.
  • Overestimating capacity - Proposing to serve 10,000 people when your current capacity is 500 raises red flags.
  • Submitting at the last minute - Build in time to resolve validation or technical issues before the official deadline.
  • Missing required attachments - Create a checklist from the NOFO and verify all attachments are included before submitting.

After Submission

If funded: celebrate, then get organized. If not funded, you can often request reviewer comments from the program officer. Many successful grantees were initially turned down, use feedback to improve your next submission.

Find Programs Worth Applying For

Use the Eligibility Finder to discover programs matching your organization type and sector.

Worked example: rewriting a weak opening

Compare a generic opening with one that names a local need, a cited source, a measurable outcome, and a budget that follows the current opportunity notice. Specificity helps a reviewer evaluate feasibility, but every number must come from a source the applicant can provide and must not be inferred from PlainGrants.

Common scoring criteria and weights

CriterionTypical weightWhat reviewers want
Significance / need20-25%Documented gap with citations
Approach / methodology25-30%Feasible plan, evidence base
Innovation10-15%What's new vs. status quo
Investigator / team10-15%Qualifications, track record
Environment / resources10-15%Org capacity, facilities
Evaluation plan10-15%Measurable outcomes
Budget reasonablenessPass/failCost per outcome unit

Federal grant writing is reviewer-conscious composition, every paragraph should make a specific reviewer's job easier by giving them a clear number, a sourced claim, or a feasible plan element.

Final-week revision checklist

Before submission, run six checks. First, executive summary stress test: can a reviewer who reads only the first page understand the project? Second, claim-source pairing: every quantitative claim has a citation, and every citation points to a credible source. Third, budget-narrative consistency: every line item appears in the narrative, and every activity in the narrative appears in the budget. Fourth, deliverable mapping: every promised deliverable has a person responsible, a timeline, and a cost estimate. Fifth, reviewer rubric self-score: compare the application with the published criteria. Sixth, technical compliance: confirm page limits, font, margins, file format, and attachments against the current NOFO.

Reviewer-conscious writing

Three habits that separate competitive first drafts from rejections at administrative review.

General guidance compiled from public federal documentation, not individualized advice for your organization.

Every figure on PlainGrants is rendered directly from SAM.gov Assistance Listings data, no number is typed in by an editor. PlainGrants catalogs Assistance Listings; program-specific financial terms must be confirmed in the official funding notice. See our editorial standards & corrections policy, the methodology behind these numbers, the data changelog, or report a data issue on this page.