Skip to content

Grant Writing Guide: How to Start in 2026

Updated 9 official sources

Quick Answer: A good grant writing guide starts before the first paragraph. Pick one real opportunity, confirm eligibility, copy the review criteria into an outline, build the budget, then write the needs statement, project design, evaluation plan, and capacity section.

Full answer and how we checked it

A foundation proposal usually takes 15 to 20 hours. A federal proposal through Grants.gov usually takes 80 to 150 hours over 6 to 10 weeks, plus six weeks or more for first-time registrations, per NIH.

Data note: Funding amounts reflect the most recent federal fiscal year data available as of May 2026, drawn from agency program data, USASpending.gov, and Grants.gov. Amounts may shift with annual appropriations.

In this guide

If you're starting grant writing from zero, work in this order: choose the funder, check fit, outline from the scoring rubric, draft the budget, then write the proposal. The writing matters, but project design and submission readiness decide whether the proposal can compete.

The biggest misconception about grant writing is right there in the name. People assume it is primarily about writing. It is not. Grant writing is project design with a writing component.

A common beginner mistake is starting from the narrative before checking fit, score criteria, and submission mechanics. That is backwards. The decision work comes first.

The proposals that get funded aren't necessarily the ones with the best prose. They're the ones where the project makes sense: the need is real and documented, the approach is logical, the budget matches the activities, the timeline is realistic, and the organization can actually deliver what it's promising.

According to Grants.gov's Learning Center (opens in a new tab), federal applicants have to manage eligibility, registrations, budget forms, attachments, and submission validation before anyone ever scores the narrative. That's why beginner grant writing problems usually start upstream of the prose itself.

Where official sources stop: we compared the Grants.gov, NIH, NSF, and 2 CFR 200 guidance, and they tell applicants what systems, forms, review criteria, and cost rules apply, but they do not tell a beginner which task should happen first. Our source rule is to sort the work into 4 gates before drafting: eligibility, scoring criteria, budget realism, and portal authority. For example, one first-time nonprofit chasing a federal youth grant should stop writing if SAM.gov roles are not active, even if the project idea is strong, because the submission gate can block the application before reviewers see the prose.

Use current program records before drafting examples. The FTA Public Transportation Emergency Relief record, NCI cancer epidemiology cohorts forecast, Fogarty global NCD research training forecast, CDC laboratory leadership and infrastructure record, and Migrant Education State Grant Program record show why a beginner should check applicant type, deadline status, agency route, and source links before writing prose.

For the next practice screen, compare FIPSE, TRIO McNair, Lead Hazard Control for High Risk Areas, Healthy Homes Weatherization Cooperation Demonstration, and NHDAP. Each one changes the applicant, deadline, or evidence file before writing starts.

The next five practice records show why beginners should confirm source type first. San Francisco Association of Realtors Foundation is private foundation research, STD Prevention and Control Grants is a CDC health-department route, Disabilities Prevention is CDC disability-health capacity, Federal Transit Capital Investment Grants is a multi-year FTA CIG path, and State of Good Repair Grants is Section 5337 transit asset funding.

The next practice screen adds route triage. Unleashing Tribal Energy Development is a DOE tribal energy NOFO, Food for Education is a USDA international school-feeding route, Adult Education Basic Grants to States is state formula funding, St Francis Xavier Catholic School System Foundation is foundation research, and EPA 66.614 is a status-check record.

According to Grants.gov applicant guidance, finding an opportunity is only one step in a longer process that includes registration, form completion, and final submission checks. According to NIH grant writing guidance, reviewers score the application you submit against the stated criteria, so beginners should build the outline from the instructions before polishing sentences. NSF publishes funding rates by directorate, and in most of them the majority of proposals aren't funded, which is why fit matters before drafting.

If you're new to grant writing, that's good news. It means the skill you need to develop isn't literary talent. It's the ability to think through a project from problem to solution to measurable outcomes, then communicate that clearly to someone who has money to fund it.

This grant writing guide covers the basics and the order of work. For the full proposal build, including every required section and how agencies score applications, our guide to writing a grant proposal goes deeper on structure and review criteria. If you want to filter down to real federal opportunities before you draft anything, start with the free eligibility checker.

If you are building your first reusable toolkit, keep how to write a grant needs statement, how to write a grant evaluation plan, and how to write a grant budget justification in the same working set. Those three pages cover the sections beginners usually underbuild.

May 2026 Grantsights Field Memo: The First Grant Draft Should Start With Fit

Most beginner grant-writing guides start with the proposal sections. That is useful, but it is not the first decision. Our May 2026 field review starts with fit because the wrong funder, wrong applicant, or wrong portal can make a polished proposal useless.

According to Grants.gov applicant training, applicants need registration, user roles, workspace setup, form preview, package completion, and submission workflow before the grant reaches review. According to the Grants.gov applicant overview, each person applying needs a profile and organization applicants need the right profile and role. The practical lesson is that grant writing starts before the narrative.

Beginner questionBetter first actionWhy this matters
"How do I write the proposal?"Pick one real opportunity and read eligibility firstA generic template can hide a fatal applicant mismatch.
"What should the project say?"Turn review criteria into the outlineReviewers score against the funder's words, not your preferred order.
"Can I submit this myself?"Check SAM.gov, Grants.gov roles, UEI, board authority, and attachmentsSubmission authority can block a good draft.
"How much should I request?"Build the budget before polishing the narrativeAn unrealistic budget weakens the project design.
"Should I hire a grant writer?"Decide whether the project is fundable firstA writer cannot fix a poor funder match.

Grantsights' apply/skip rule for beginners: apply when eligibility, project design, budget, deadline, and portal authority are all clear. Skip when the funder is only loosely related to the mission. Pause when the idea is promising but the organization lacks data, partners, or required registrations.

Looking for your next grant?

About once a week, we email a short list of open grant calls with real deadlines from different funders. It lists open calls only.

No spam. Unsubscribe anytime.

Beginner Path: What To Do First

If you are starting with...First moveWhat to avoid
A foundation prospect and a short applicationDraft the project design before the narrativeStarting with generic organizational history
A federal NOFORead eligibility and review criteria before writingDrafting prose before checking score criteria
A rough idea but no defined projectNarrow the target population and outcome firstChasing funders before the program is concrete
No data yetCollect local need data and baseline numbersFilling the needs statement with national statistics only

The Beginner Grant Writing Guide in 6 Steps

  1. Choose one real opportunity, not a generic template.
  2. Confirm the applicant type, geography, deadline, and portal.
  3. Pull the review criteria into a working outline.
  4. Build the budget and timeline before polishing narrative text.
  5. Draft the needs statement, project design, evaluation plan, and capacity section against the scoring criteria.
  6. Submit early enough to catch portal validation problems.

According to Grants.gov applicant guidance from its Learn Grants (opens in a new tab) materials, the application process includes registration, finding opportunities, completing the package, and submission. According to NIH grant writing guidance, applicants should start with an outline that reflects the funding opportunity and application instructions. That is why beginners should treat the NOFO or guidelines as the source document, not as a late-stage compliance check.

Who Should Learn Grant Writing First, and Who Should Get Help

  • Learn it yourself first if you are starting with foundation proposals, small local grants, or a program you already know well.
  • Get help early if the opportunity is federal, multi-partner, highly technical, or large enough that a weak submission will waste months of staff time.
  • Do not start with freelance hiring by default if your team has not yet decided whether the opportunity is even a good fit.

Your First-Week Grant Writing Checklist

  1. Pick one real funding opportunity instead of learning from a blank document.
  2. Confirm eligibility before you draft anything.
  3. Write the project in plain operating terms: who, what, where, when, and how many.
  4. Draft goals and objectives before the opening narrative.
  5. Build the budget and timeline before polishing the prose.
  6. Collect the attachments and portal requirements early.
  7. Ask whether this is a proposal you should write, not just one you could write.
  8. Save a clean outline for the next grant so you do not restart from zero.

If you want to learn from live federal records instead of a blank template, start with the federal grant database and search one page from your actual lane: Head Start for early-childhood service grants, Continuum of Care for homelessness funding, CAREER for junior faculty research proposals, or AREA R15 for undergraduate-focused institutions. If your lane is academic training rather than community service delivery, search K99/R00, T32, StARR, or R25 in the same database before drafting.

What Grant Writing Actually Involves

Grant writing is the process of preparing and submitting a formal proposal to a funder (foundation, corporation, or government agency) requesting money for a specific project or program. But "writing" is misleading because the work breaks down roughly like this:

  • 40% research and planning: Identifying the right funders, reading the funding announcement, researching the need your program addresses, and gathering data.
  • 30% project design: Designing the program, setting measurable goals and objectives, creating a logic model, developing the budget, and planning evaluation methods.
  • 20% writing: Drafting the narrative sections of the proposal.
  • 10% assembly and submission: Formatting, collecting required documents (letters of support, resumes, financial statements), and submitting through the funder's portal.

If you skip the first 70% and jump straight to writing, your proposal will read like it. Reviewers can tell when someone made up a program to fit a grant, versus when someone designed a real program and then found the right grant to fund it.


The 6 Core Components Every Grant Proposal Has

Whether you're writing a 3-page letter to a family foundation or a 60-page federal application, the same six components appear in some form. The names vary, but the content is consistent across virtually every funder.

1. Needs Statement (or Statement of Need)

This section answers one question: why does this project need to exist? You're making the case that there's a specific, documented problem affecting a specific population, and that current solutions aren't adequate.

What makes a strong needs statement:

  • Local data, not just national statistics. If you're serving a community, use data from that community.
  • Data from credible sources: Census Bureau, CDC, state health departments, local school district reports, peer-reviewed studies.
  • A clear connection between the problem and your proposed solution. Don't describe every issue in your community. Focus on the problem your project addresses.
  • The perspective of the people affected. Quotes, surveys, or focus group data from your target population add credibility.

What to avoid:

  • Circular reasoning ("the need is for our program" is not a need statement; the need is the problem your program solves).
  • Data older than 3 to 5 years without justification.
  • Hyperbole or emotional appeals without evidence.

2. Project Description (or Program Design)

This is the core of your proposal: what you're going to do, how you're going to do it, who you're going to serve, and when. A strong project description reads like a blueprint. Someone unfamiliar with your organization should be able to read it and understand exactly how the project will work.

Include:

  • Activities: What staff will do, in what sequence, on what timeline.
  • Target population: How many people, with what characteristics, in what geographic area.
  • Staffing plan: Who will do the work, what are their qualifications.
  • Timeline: A month-by-month or quarter-by-quarter plan for the grant period.

A common weakness in beginner proposals is vagueness. "We will provide educational programming to underserved youth" tells a reviewer nothing. "We will provide twice-weekly after-school tutoring in math and reading to 40 students in grades 3 through 5 at Lincoln Elementary, using trained volunteer tutors supervised by a licensed teacher" tells a reviewer exactly what to expect.

3. Goals and Objectives

Goals are the broad outcomes you want to achieve. Objectives are the specific, measurable steps that will get you there.

A useful framework is SMART: Specific, Measurable, Achievable, Relevant, and Time-bound. For example:

  • Goal: Improve reading proficiency among third-grade students at Lincoln Elementary.
  • Objective: By June 2027, 75% of participating students will score at or above grade level on the State Reading Assessment, compared to 45% at baseline.

Federal grants typically require 2 to 4 goals with 2 to 3 objectives under each. Foundation grants may only need 1 to 2 goals. The key is that objectives must be measurable. If you can't measure it, a reviewer will question whether you'll know if your program worked.

4. Evaluation Plan

The evaluation plan describes how you'll measure whether your project achieved its objectives. This is where many beginners stumble, either by leaving it out entirely or by writing something vague like "we will evaluate the program's effectiveness."

A solid evaluation plan covers:

  • What data you'll collect: Test scores, attendance records, survey responses, pre/post assessments.
  • When you'll collect it: At enrollment (baseline), mid-program, end of program, and follow-up if applicable.
  • How you'll analyze it: Comparing pre/post data, tracking against benchmarks, using statistical methods if appropriate.
  • Who will do the evaluation: Internal staff, an external evaluator, or both. Some federal programs require an independent external evaluator, so check the NOFO before you budget for evaluation.

If you need examples and section structure, use how to write a grant evaluation plan as the next step after this overview.

5. Budget and Budget Justification

The budget translates your project description into dollars. Every activity you described should have a corresponding cost, and every cost should connect to an activity. If your budget includes a $65,000 salary for a project coordinator but your project description never mentions a project coordinator, that's a problem.

Federal grant budgets follow specific categories defined by 2 CFR 200 (opens in a new tab):

  • Personnel (salaries and wages)
  • Fringe benefits
  • Travel
  • Equipment (items over $10,000)
  • Supplies (items under $10,000)
  • Contractual (subawards and consultant fees)
  • Other direct costs
  • Indirect costs (using your negotiated rate or the 15% de minimis rate)

According to 2 CFR 200, the federal equipment threshold is $10,000 and the de minimis indirect cost rate is 15% when an applicant does not have a negotiated indirect cost rate. Those two numbers change how beginners should classify supplies, equipment, and overhead before they draft a budget justification.

The budget justification is where you explain why each cost is necessary and how you calculated the amount. "Project Coordinator, $65,000" is not a justification. "Project Coordinator (1.0 FTE at $65,000/year), responsible for managing all program activities, supervising 8 volunteer tutors, and collecting evaluation data, consistent with median salary for similar positions in the Chicago metro area per Bureau of Labor Statistics data" is a justification. For detailed guidance, see our grant budget justification guide.

6. Organizational Capacity

This section convinces the funder that your organization can actually deliver what you're proposing. It covers:

  • Your organization's mission and history
  • Relevant experience with similar programs or populations
  • Key staff qualifications
  • Financial stability (annual budget, audit status, other funding sources)
  • Partnerships and collaborations

For new organizations, this section is the hardest to write because you don't have a long track record. Focus on the qualifications of your staff and board, any pilot programs you've run, partnerships with established organizations, and your financial management practices.


How to Read a NOFO (Notice of Funding Opportunity)

Before you write a word of your proposal, you need to read the funding announcement thoroughly. For federal grants, this is called a NOFO (Notice of Funding Opportunity). Foundations call it an RFP (Request for Proposals), guidelines, or application instructions.

Here's what to look for, in order of importance:

Eligibility Requirements

Read these first. If your organization type, geographic area, or project focus doesn't match, stop here. Don't waste time on a proposal you're ineligible for.

Review Criteria and Point Values

Federal NOFOs tell you exactly how your proposal will be scored. If "Need for the Project" is worth 25 points and "Quality of Management Plan" is worth 15 points, you should spend proportionally more effort on your needs statement. This is the single most actionable information in any NOFO. Many beginners ignore it.

Award Amount and Duration

Know the minimum and maximum award amount and the grant period length. A proposal requesting $50,000 when the minimum award is $250,000 will be seen as too small in scope. A proposal requesting $1 million in FY2025 when the maximum is $500,000 won't be reviewed.

Required Documents and Format

Federal grants require specific forms (SF-424, SF-424A, etc.), specific page limits, font sizes, and margin widths. Missing a required attachment or exceeding page limits can result in your application being returned without review.

Match or Cost-Sharing Requirements

Some grants require your organization to contribute a percentage of the project cost from non-federal sources. This is called cost sharing or matching. If the grant requires a 20% match on a $200,000 award, you need to document $40,000 in non-federal funds. If you can't, don't apply.


How to Match Your Project to a Funder's Priorities

The most common reason grant proposals fail isn't bad writing. It's misalignment. You proposed a good project to the wrong funder, or you proposed a project that doesn't match what the funder said they wanted to fund. See our detailed breakdown of common grant rejection reasons for more on this.

Matching your project to a funder works in two directions:

Start With Your Program, Then Find Funders

If you already have a program running or a specific project planned, search for funders whose priorities align with what you're already doing. Don't redesign your program to fit every funder you find.

Where to search:

  • Grants.gov (opens in a new tab): All federal grant opportunities. Filter by eligibility, agency, and category.
  • Candid (Foundation Directory Online): The largest database of foundation grants. Available free at Funding Information Network libraries (opens in a new tab) in most states.
  • State grant portals: Your state's agency websites or a central grant portal.
  • Funder websites: If you know a specific foundation funds work like yours, go directly to their website for application guidelines.

Start With a Funder, Then Design Your Project

Sometimes you'll find a funding opportunity that's a strong match for your mission, but you don't have an existing program that fits perfectly. In this case, you can design a project to respond to the NOFO. This is common in federal grant writing, where agencies fund very specific program models.

The danger here is mission drift: designing programs just to get money, even when they don't align with your core mission. Every project you propose should advance your organization's mission, not just your budget.

The work also continues after submission. If you win, you will need an operating plan for how to write a grant progress report, grant no-cost extension guide, and grant closeout checklist guide, not just a draft narrative.


How Long Does It Take to Write a Grant?

A first foundation proposal usually takes 15 to 20 hours of work over 2 to 4 weeks, and a first federal proposal 80 to 150 hours over 6 to 10 weeks. These are typical estimates, not figures any agency publishes, and they assume you already have program data, a draft budget and your organization's documents. Hours aren't usually what sinks beginners. Calendar time is.

StepLead timeSource
SAM.gov registration for a new organization3 weeks or moreNIH organization registrations (opens in a new tab)
All federal registrations (SAM.gov, Grants.gov, and eRA Commons for NIH)6 weeks or moreNIH organization registrations (opens in a new tab)
Letters of support from partnersAsk 3 to 4 weeks before the deadlineTypical estimate
Submission buffer for federal portalsAt least 48 hours before the deadlineTypical practice

So for a first federal grant with no active SAM.gov registration, start about 10 weeks before the deadline: registrations and drafting run at the same time, and the registrations are the part you can't speed up. For a foundation grant with a short application, 3 to 4 weeks is usually enough.

Realistic Time Estimates

Rough estimates of how long different types of grant proposals take:

Proposal TypeTime EstimateTypical Team
Foundation letter of inquiry (1 to 3 pages)3 to 5 hours1 person
Full foundation proposal (5 to 15 pages)15 to 20 hours over 2 to 4 weeks1 to 2 people
State government grant (10 to 25 pages)30 to 50 hours over 3 to 5 weeks2 to 3 people
Federal discretionary grant (30 to 60+ pages)80 to 150 hours over 6 to 10 weeks3 to 5 people
NIH R01 or NSF proposal100 to 200 hours over 2 to 4 monthsPI + grants office

These estimates include research, program design, writing, budget development, internal reviews, and assembly. They do not include the time to build relationships with funders, which is an ongoing process that happens before you ever start writing.

If you're a beginner writing your first proposal, add 30% to 50% more time. You'll be learning the process while doing the work.

FAQ

Should beginners start with foundation grants or federal grants?

Most beginners should start with foundation grants because the applications are shorter, the compliance burden is lighter, and the feedback loop is faster. Federal grants make sense once your organization already has a clear program model, baseline data, and the capacity to manage forms, budgets, and attachments.

When should a beginner hire a grant writer?

Hire help when the opportunity is large, technical, or time-sensitive enough that learning on the job would cost more than the consultant fee. For smaller foundation proposals, it usually makes more sense to learn the process yourself and pay for review support only if needed.

What should a beginner do before drafting the first paragraph?

Confirm fit, read the full funding instructions, map the review criteria, and outline the project in operating terms. If you cannot explain who the project serves, what changes, how much it costs, and how success will be measured, you are not ready to start writing.


Free Resources for Learning Grant Writing

You don't need to spend money on courses to learn grant writing. The best resources are free:

Government Resources

University and Extension Resources

Library Resources

Your local library likely has free access to Foundation Directory Online (now Candid Search), which is the most complete database of foundation and corporate grants in the country. Many libraries also host free grant writing workshops. Call your nearest public library and ask about their Funding Information Network access.

Nonprofit Support Organizations

State and regional nonprofit associations frequently offer free or low-cost grant writing workshops. The National Council of Nonprofits (opens in a new tab) maintains a directory of state-level associations.


Whether to Hire a Grant Writer

This question comes up constantly, and the answer depends on your situation:

Write It Yourself If:

  • You're pursuing foundation grants under $50,000
  • Your organization has strong program knowledge internally
  • You're willing to invest 15 to 20 hours per foundation proposal
  • Your budget can't absorb $3,000 to $15,000 in consulting fees

Hire a Grant Writer If:

  • You're pursuing federal grants over $100,000
  • The grant has complex requirements (federal forms, SBIR/STTR technical sections)
  • Your staff doesn't have time to dedicate 80+ hours to one proposal
  • You've been rejected multiple times and need an outside perspective

Important Warning About Grant Writer Fees

The Grant Professionals Association and the Association of Fundraising Professionals both explicitly prohibit paying grant writers on a percentage-of-funds-raised basis. If someone offers to write your grant for "10% of whatever you get funded," that's a red flag. Ethical grant writers charge hourly rates ($50 to $150/hour), project fees ($2,000 to $15,000 per proposal), or are employed on salary. Percentage-based fees create a conflict of interest, and many funders prohibit them.


Grant Writing Certifications: Do You Need One?

Grantsights checked GPCI's eligibility and exam-fee pages on October 9, 2026 for the details below. The most recognized certification in the field is the Grant Professional Certified (GPC) credential, administered by the Grant Professionals Certification Institute (opens in a new tab).

GPC Requirements

  • Eligibility (opens in a new tab) is points-based: at least 120 of 170 possible points across Education, Professional Experience, Continuing Education, and Community Involvement, with minimum thresholds in Education and Professional Experience
  • Activities are documented over a three- to seven-year window before you apply, depending on the pathway you choose (details are in GPCI's Candidate Guide)
  • GPCI says the GPC "is not considered appropriate for entry-level grant professionals"
  • Passing an exam with a multiple-choice part and a writing exercise
  • $639 first-time exam fee (opens in a new tab); retakes are $639 for the full exam or $320 for one part

The GPC is worth pursuing once you're an experienced grant professional, especially as a freelance consultant where the credential adds credibility. But it's not required to get hired, and no funder checks whether your grant writer is certified. What matters is a track record of funded proposals.

Other training programs exist (Grant Writing USA, GrantSpace, various university certificates), but none carry the same weight as the GPC. Free workshops from your state nonprofit association or local community foundation are often just as valuable for building practical skills.


10 Common Beginner Mistakes (and How to Avoid Them)

1. Applying for Every Grant You Find

Be selective. A well-matched proposal has a real chance of funding. A poorly matched proposal has close to none. Use the grant-finding strategies described above to identify only the best fits.

2. Starting With a Dollar Figure

Don't pick a target amount and work backward. Sketch the program design first, then build the budget and timeline early, before you polish the narrative, so every cost ties to an activity. If you start with "we want $100,000" and work backward, the program will feel forced.

3. Ignoring the Review Criteria

Federal NOFOs include point values for each section. If "Significance" is worth 30 points and "Approach" is worth 25 points, your needs statement and project design deserve the most attention. Write to the rubric.

4. Using Jargon and Acronyms

Don't assume reviewers know your field's terminology. Spell out acronyms on first use. Explain technical concepts. Federal review panels often include members from outside your discipline.

5. Writing Vague Objectives

"We will improve community health" is not an objective. "By September 2027, 200 participants will complete our 12-week nutrition education program, with 70% reporting improved dietary habits on a validated post-program survey" is an objective.

6. Forgetting Letters of Support

Many grants require or strongly encourage letters from partner organizations, community leaders, or the population you serve. Start requesting these at least 3 to 4 weeks before the deadline. Provide a draft or talking points to make it easy for the letter writer.

7. Submitting at the Last Minute

Federal grant portals (Grants.gov, eRA Commons) can take up to 48 hours to validate your submission. If the system finds a formatting error at 11 PM on the due date, you have no time to fix it. Submit at least 48 hours early.

8. Copying and Pasting From Old Proposals

Recycling proposal language without updating data, dates, and funder-specific language is immediately obvious to reviewers. Every proposal should be customized to the specific funder and opportunity.

9. Neglecting the Abstract

The abstract or executive summary is often the first (and sometimes only) thing a reviewer reads carefully. Write it last, after you've completed the full proposal, and make sure it summarizes the strongest elements of each section.

10. Not Having Someone Else Read It

After spending 40 hours on a proposal, you'll miss errors and logical gaps. Have someone unfamiliar with the project read the full proposal and tell you what's unclear. Their confusion points are the reviewer's confusion points.


Your First Grant Proposal: A Step-by-Step Checklist

If you're ready to write your first grant proposal, here's the order Grantsights recommends:

  1. Identify a well-matched funder. Use the resources above to find a foundation or government program that funds work like yours.
  2. Read the entire NOFO or application guidelines. Take notes on eligibility, review criteria, required documents, and deadlines.
  3. Design your project. Create a logic model, define your target population, outline activities, and set measurable objectives.
  4. Develop the budget. Cost out every activity. Make sure the budget matches the project description exactly.
  5. Write the needs statement. Gather local data, cite credible sources, connect the problem to your solution.
  6. Write the project description. Describe what you'll do, when, where, and with whom.
  7. Write the evaluation plan. Describe what data you'll collect and how you'll measure success.
  8. Write the organizational capacity section. Highlight your team's qualifications and your organization's relevant experience.
  9. Write the abstract. Summarize the full proposal in one page or less.
  10. Assemble required documents. Letters of support, resumes, financial statements, IRS determination letter, board list.
  11. Have at least one person review the full proposal. Ideally someone who didn't help write it.
  12. Submit 48 hours before the deadline. Leave time for technical issues.

For a deeper walkthrough of the federal process, see our guide on how to write a federal grant proposal. For details on the submission process itself, see how to apply for federal grants on Grants.gov. If you're moving from learning the craft to identifying actual federal fits, the fastest next step is the free eligibility checker, which screens organization type, geography, and funding area before you spend time on a full NOFO.


What Experienced Grant Reviewers Doesn't Tell You

Your first grant proposal should not be a federal application. Federal grants have the steepest learning curve, the longest timelines, and the lowest success rates for first-time applicants. Start with a local community foundation or corporate giving program where the application is 3-5 pages and the turnaround is 6-8 weeks.

Reviewers score what you wrote, not what you meant. The most common beginner mistake is assuming the reviewer will infer your qualifications or understand your program model from context. If it's not explicitly stated on the page, it doesn't exist for scoring purposes.

A rejection letter is more useful than a funded proposal for learning. Many funders provide reviewer comments with their rejection notices. Request feedback every time you're declined, and use it to improve your next submission.


Sources

Beginner grant-writing workflow

Start with fit, budget, and deadline before writing

Beginner grant-writing searches usually need a practical workflow, not a long theory lesson. Use these tools to choose a grant, outline the proposal, test the budget, and build a deadline plan before drafting.

Beginner checks

Fit before writing

Confirm applicant type, project scope, location, deadline, match, and required registrations first.

Six core sections

Draft need, goals, activities, evaluation, budget, and organization capacity as one connected plan.

Budget before prose

Check whether the numbers support the work before polishing the narrative.

Tool path

1. Find the grant

Use the free grants database and eligibility checker before committing staff time.

2. Draft the outline

Use the outline builder to organize the project around funder review criteria.

3. Validate budget and deadline

Use the calculator and planner before assigning writers, reviewers, and approvers.

Route hubs

Move from this guide into the strongest grant route

Broad grant searches often split by sponsor, applicant type, location, or notice number. These hub pages help you choose the route before opening exact program records.

Best follow-up

Choose the grant before writing the proposal

Free eligibility check: answer 9 questions and see ranked matches with deadlines and fit reasons.

Free. No payment on this step.

Next stepFind grants that fit youCheck eligibility

Next steps

Where to go next

These next pages help you move from research into a specific grant choice.

Frequently Asked Questions

How long does it take to write a grant proposal?

Time varies dramatically by funder type, and these are typical estimates rather than agency figures. A foundation letter of inquiry takes 3 to 5 hours. A full foundation proposal takes 15 to 20 hours spread over 2 to 4 weeks. A federal grant proposal through Grants.gov takes 80 to 150 hours spread over 6 to 10 weeks, involving multiple staff members, budget specialists, and sometimes external consultants. These estimates assume you already have program data, organizational documents, and a clear project design. If you're starting from scratch on any of those, add significant time.

Do I need a certification to write grants?

No certification is required to write grants. Many successful grant writers have no formal certification at all. The Grant Professionals Certification (GPC), offered by the Grant Professionals Certification Institute, is the most recognized credential in the field. Eligibility is points-based: candidates need 120 of 170 possible points across education, professional experience, continuing education, and community involvement, with minimums in education and experience, before they can sit for an exam with multiple-choice and writing parts. GPCI says the credential isn't meant for entry-level grant professionals. While the GPC can strengthen your credibility, especially if you're freelancing, employers and funders care more about your track record of funded proposals than any certificate.

Can I make a career out of grant writing?

Yes. Grant writing is a full-time profession at nonprofits, universities, hospitals, school districts, and government agencies. Pay depends on experience, location, and employer type, and directors of grants or development earn more than entry-level staff; check a current salary survey for your region before negotiating. Freelance grant writers charge $50 to $150 per hour or work on a project fee basis. The field is growing as more organizations compete for limited funding. Entry-level positions often have titles like 'grants coordinator' or 'development associate.'

Should I hire a grant writer or learn to do it myself?

For small nonprofits with budgets under $500,000, learning to write foundation grants yourself is the most cost-effective approach. Foundation proposals are shorter (5 to 15 pages), use plain language, and follow predictable formats. For federal grants, which are longer, more technical, and have strict formatting rules, hiring an experienced grant writer or consultant makes sense once you're pursuing awards over $100,000. A middle option: hire a grant consultant to review and strengthen a proposal you've drafted yourself. This costs less than full-service writing while still improving your chances.

What's the success rate for grant proposals?

Success rates vary widely. For federal grants, NIH R01 success rates fell to about 13% in FY2025, and NSF publishes funding rates by directorate. Foundation rates depend heavily on the funder and on whether you were invited to apply. The key factor isn't writing quality alone, it's whether you applied to the right funders for the right amount with the right project. A perfectly written proposal sent to the wrong funder will still be rejected.

Last updated October 18, 2026. Corrected October 9, 2026: what changed. Published by Grantsights from public sources. See our editorial policy, how we build and check guides, corrections and how we make money.