A fountain pen writing on a document, with a gold seal and ribbon at the bottom corner, bold and simple on a cream panel above the course title.

Starvard University · Grant Writing 101

Grant Writing 101

You will find grants that fit your organization and write proposals that reviewers want to fund. This advanced course walks the whole path, from reading an announcement closely to reporting after an award, grounded in the Grants.gov Learning Center. It teaches readiness and fit, and it makes no promises about outcomes: reviewers decide, and your job is to give them a clear, honest, complete proposal to judge.

Finn

Hello, my name is Finn, and I'm going to help you understand this course.

Here it is, explained like you are 10:

A grant is money a funder gives an organization to do a specific piece of work, and a grant proposal is the written request that explains what you will do, why it matters, and what it will cost. Grant writing means matching a real need in your community to a funder who cares about that need, then describing your plan so clearly that a busy reviewer can understand it and trust it.

The whole course in brief

What you will be able to do after this course

  1. Grant writing is writing proposals for funders. That distinct job, asking an organization with money to pay for specific work, is what this course teaches, not general writing craft.
  2. Explain how the grant world works, who gives grants, and why funders publish announcements instead of simply handing out money.
  3. Find funders across government, foundations, and companies, and judge fit before you spend weeks writing.
  4. Read a funding announcement closely and pull out eligibility, deadlines, required sections, and scoring language.
  5. Write a needs statement that proves a problem with evidence a reviewer can check.
  6. Turn a big goal into objectives and outcomes that can be observed and measured.
  7. Build a project plan and timeline where each activity has an owner and a date.
  8. Build a budget and a justification that explains every cost in plain words.
  9. Design an evaluation plan that shows how you will know whether the work helped.
  10. Gather letters of support and partners who add real capacity, not just names.
  11. Complete registration and submission correctly, including SAM.gov and the Unique Entity ID for federal applications.
  12. Handle reporting and compliance after an award, and learn from a rejection so the next proposal is stronger.

The twelve lessons

Lesson 1

How the grant world works

A grant is money given for a stated purpose, with conditions attached. Unlike a loan, it is not repaid if you spend it as agreed. Understanding that bargain is the start of grant writing: a funder trusts you with public or charitable money, and in return you promise specific work and honest accounting.

Funders give grants because they have a mission they cannot carry out alone. A federal agency may be directed by law to support health clinics, roads, research, or job training across the country. A foundation may exist to improve reading in one region. A company may fund programs near its stores or factories. The Grants.gov Learning Center describes itself as a gateway to the federal grants world, and that image helps: there is a whole system with its own vocabulary, calendar, and gates to pass through in order.

Three words will follow you through this course. An opportunity is a specific offer of funding with its own rules and deadline. An applicant is the organization asking for the money. A proposal, also called an application, is the full written package you submit. Reviewers read many proposals for the same opportunity and compare them against the funder's stated criteria. Nothing in this course can guarantee a result, because reviewers and budgets decide. What you can control is readiness, fit, and clarity, and those three things are teachable.

The grant world runs on trust and paperwork in equal measure. Learn the bargain, the vocabulary, and the funder's purpose before you write a word.

Lesson 2

Finding funders: government, foundation, corporate

Government grants are the most documented kind. Federal opportunities are listed on Grants.gov, where you can search by keyword, agency, and eligibility, and state and local governments run their own programs with their own portals and calendars. Government funding tends to be larger and more rule bound, with detailed reporting. Start your search broad, then filter hard by who is eligible to apply, because an opportunity your organization cannot legally receive is not an opportunity for you at all.

Foundations are independent organizations that give money from an endowment or from annual gifts. Some are large and national, with professional staff and published guidelines. Many are small and local, run by a family or a community board, and they often care deeply about one place or one kind of work. Foundation research means reading guidelines, looking at who received grants in past years, and noticing the size of typical awards.

Corporate giving comes from companies and their foundations, and it often connects to where the company works, who it employs, or what it sells. It can include cash, donated products, or employee volunteering alongside a grant. For every kind of funder, the test is the same: fit. Fit means your mission, your community, your size, and your timeline line up with what the funder says it wants. Chasing money that pulls your organization off mission is expensive even if you win it, because you must deliver work you never planned to do.

Fit comes before writing, always. A well matched small funder is worth more than a famous funder whose guidelines describe someone else.

Lesson 3

Reading a funding announcement closely

A funding announcement is the funder's complete instruction sheet, and reading it closely is the highest value hour in grant writing. It may be called a notice of funding opportunity, a request for proposals, or a solicitation, depending on the funder. Read it once for the story, then again with a pen, marking every requirement.

Turn the announcement into a working checklist. Note the deadline and work backward to set your own earlier deadline for a full draft. List every required form, attachment, page limit, and formatting rule. Write down eligibility in your own words and confirm your organization meets it, asking the contact person listed in the announcement if anything is unclear.

Pay special attention to the review criteria, because they show you what reviewers will look for. If the announcement says reviewers will judge the strength of the need, the quality of the project design, and the reasonableness of the budget, then those three things deserve your best writing and your clearest evidence. Where the announcement repeats a phrase, treat it as a signal. Write your section headings to mirror the announcement's structure, so a reviewer scanning quickly can find each required point without hunting. Reviewers reward proposals that are easy to score.

The announcement is the exam paper and the marking guide in one document. Build a checklist from it and let its structure shape your proposal.

Lesson 4

The needs statement

The needs statement answers one question: what problem will this money address, and how do you know? Reviewers look for a specific, documented need in a defined community, not a general claim that times are hard. Start with the people or place at the center of your work. Describe who they are, where they are, and what difficulty they face, in concrete terms a reader can picture. Then show the gap between what exists now and what should exist, because a grant pays to close a gap.

Evidence is what separates a strong needs statement from a sad story. Use the best data you can find and name its source in the text: public statistics, a local survey your organization ran, waiting lists, school or clinic records, or reports from trusted agencies. Pair the human detail with numbers that show how widespread the problem is, and keep every figure honest and current. Reviewers notice inflated claims, and one doubtful number can weaken everything around it.

End the section by connecting the need directly to your proposed work. If the need is that families wait months for a service, your project should visibly shorten that wait. If the need is that a skill is missing in a workforce, your project should teach that skill to the people who lack it. A good needs statement respects its community and makes the rest of the proposal feel necessary rather than optional.

A needs statement proves a gap with evidence, then points straight at your project. Specific, sourced, and respectful beats dramatic every time.

Lesson 5

Goals, objectives, and outcomes

Reviewers look for a clear chain from need to result, and three words carry that chain. A goal is the broad change you work toward, stated in one sentence. Objectives are the smaller, concrete steps that move you toward the goal, each one narrow enough to check. Outcomes are the changes that actually happen for people or places because of your work, such as new skills, better health habits, a safer building, or a shorter wait. Keeping the three separate keeps your proposal honest and easy to follow.

A useful objective names who will change, what will change, by how much or in what way, and by when. Vague objectives, such as improving lives in the community, give a reviewer nothing to score and give you nothing to manage. Stronger objectives can be counted or observed: participants complete a course, families receive visits, acres are restored, or calls are answered faster. You need targets that are ambitious enough to matter and modest enough that a careful reader believes your team can reach them with the time and money requested.

Outcomes need a way to be noticed. For each outcome, decide now what evidence will show it: attendance records, test scores, surveys before and after, inspection results, or case notes kept in a consistent form. This decision belongs in the proposal, not after the award, because it shapes staffing and budget. Also separate what your project directly controls from larger changes it merely contributes to. A tutoring grant can credibly claim improved reading scores for its students.

Goals point the direction, objectives make it checkable, and outcomes name the real change. Write all three so a reviewer can follow the chain without guessing.

Lesson 6

The project plan and timeline

The project plan turns your objectives into a sequence of work. For each objective, list the main activities, who is responsible for each one, what resources it needs, and what finished looks like. Reviewers look for a plan that a real team could actually run: recruitment before sessions begin, purchases before they are needed, training before staff deliver a service. A plan that ignores dependencies reads as hopeful rather than credible, and experienced reviewers spot the difference quickly.

A timeline gives the plan dates and rhythm. Lay activities across the grant period in months or quarters, showing start and finish points, major milestones, and the moments when you will check progress. Allow time for the slow, unglamorous parts: hiring always takes longer than expected, partnerships need meetings before they produce referrals, and reports need drafting before their deadlines. A timeline with a little honest slack looks more professional than a heroic schedule that assumes nothing will ever go wrong.

Name the people behind the plan. A short paragraph for each key person, covering their role and the experience that qualifies them, reassures a reviewer that the work is staffed, not wished for. Finally, describe how you will manage the project day to day: who meets, how often, who keeps records, and who decides when something must change. Good management is invisible in a finished project and very visible in a proposal, because it shows up as order, names, and dates.

A credible plan has activities, owners, and dates that respect how work really happens. Reviewers fund plans they can picture being carried out.

Lesson 7

Building the budget and justification

A grant budget is your plan translated into money, and reviewers read it as a test of honesty and competence. Build it from the project plan, not before it: every activity should appear as costs, and every cost should trace back to an activity. Common categories include personnel, fringe benefits, travel, supplies, equipment, contracts with partners or specialists, and other direct costs. Follow the funder's categories and format exactly, even if your own bookkeeping uses different names.

The budget justification, sometimes called the budget narrative, explains each line in plain words. For personnel, name the role, the share of time charged to the grant, and how the amount was calculated. For travel, say who travels, where, why, and how the cost was estimated. For supplies and contracts, describe what will be bought and why the project needs it. A reviewer should never have to guess what a number means or how you arrived at it.

Check the budget the way a reviewer will. Add it up again. Confirm the total matches the amount requested everywhere it appears in the proposal. Confirm nothing in the budget contradicts the narrative: if the plan serves people in three sites, the travel and staffing should show three sites. Leave out costs the funder does not allow, and never pad a line expecting negotiation. If your organization contributes its own money, staff time, space, or volunteer help, list that contribution where the funder asks for it, valued carefully and honestly. A clean budget quietly argues that you will handle the award well.

Every budget line should trace to an activity and carry a plain explanation. Accuracy, consistency, and no padding are what reviewers look for.

Lesson 8

Evaluation plans

An evaluation plan explains how you will know whether the project worked. Reviewers look for evaluation that is planned from the start, proportionate to the size of the grant, and tied directly to your objectives and outcomes. Begin by restating each outcome and naming the evidence you will collect for it. That evidence might be counts of people served, completion records, surveys, interviews, test results, or observations recorded in a consistent way. Say who collects it, how often, and where it will be stored and reviewed.

Distinguish between tracking activity and judging change. Counting sessions held and people attending tells you the work happened. Comparing a measure before and after, such as a skill check, a waiting time, or a satisfaction survey, tells you whether the work helped. A good plan includes both kinds of information and sets a regular moment to look at them, for example a monthly review by the project lead. Funders respect a plan that expects to learn.

Some large grants require an outside evaluator, and the announcement will say so if it does. For most smaller projects, a staff member with clear responsibility and simple tools is enough, as long as the methods are honest. Report results you actually found, including mixed results, and keep the raw records so your reports can be checked. It is the part that turns one funded project into knowledge your organization and your funder can use for the next decision.

Evaluation names the evidence for each outcome before the work begins. Track activity, measure change, and plan a regular moment to act on what you learn.

Lesson 9

Letters of support and partners

A partner is an organization that will actually do part of the work, share resources, or open a door your project needs, such as referring participants or providing space. A letter of support is a written statement from a partner or community voice confirming that role. Reviewers look for letters that are specific: what the writer's organization will do, when, and with what resources. A letter that could be attached to any proposal, praising your good work in general terms, adds paper without adding confidence.

Ask for letters early and make them easy to write well. Give each writer a short summary of the project, the exact commitment you are asking them to confirm, and your deadline, which should be well before the submission deadline. If a partnership is central to the project, a fuller agreement may be needed, describing responsibilities, money if any flows between you, and how decisions get made. The announcement may name the exact document required, so check it.

Choose partners for capacity, not decoration. A small partner who will genuinely host sessions every week strengthens a proposal more than a famous name with no defined role. In the narrative, introduce each partner where their work appears in the plan, so the letters confirm a story the reviewer has already read. The partners you treat well on a rejected proposal are often the partners who stand with you on the funded one that follows.

Strong letters confirm specific commitments from real partners. Ask early, describe the role exactly, and let the letters back up a story already in your plan.

Lesson 10

Registration and submission systems

Many proposals are lost before review because registration or submission went wrong, so treat the systems as part of the craft. For federal grants, Grants.gov is the place to find and apply for opportunities, and its Learning Center explains every phase of the process, from applying and reporting to the award closeout.

For an organization applying federally, registration comes first and takes time. Grants.gov states that an organization must register as an entity with SAM.gov first, because Grants.gov uses SAM.gov to establish organizational authority for its users. During SAM.gov registration the organization designates a main contact, called the Electronic Business Point of Contact, or EBiz POC, and receives a Unique Entity ID, or UEI, which automatically appears in applications. Registration is free, SAM.gov registration must be renewed every year, and Grants.gov advises allowing up to 10 business days for SAM registration to become active, warning that it can take weeks or longer if information cannot be verified. The Grants.gov help pages describe the UEI as a 12 character alphanumeric identifier. Start registration the moment you consider a federal opportunity, not after the proposal is written.

Submission day should be boring. Finish the full draft days ahead, check every attachment opens, confirm file names and formats match the announcement, and submit early enough that a slow upload or a missing field is an inconvenience, not a disaster. Keep the confirmation the system gives you, and keep the exact final version you submitted.

Registration is a gate that opens slowly, so start it first. Know SAM.gov, the EBiz POC, and the UEI, and submit early enough for surprises to stay small.

Lesson 11

After the award: reporting and compliance

Winning a grant starts a new job: doing the work exactly as funded and proving it. Your award document states the amount, the period, the approved budget, and the conditions you accepted. Read it fully, file it where your team can find it, and set up tracking from day one. Keep spending inside the approved categories, and ask the funder before you make a significant change to the work or the budget, because many changes need written approval in advance.

Reporting is how you keep the funder's trust. Most awards require progress reports that compare what you planned with what happened, financial reports that show spending against the budget, and a final report at the end. Put every report date on a shared calendar with an earlier internal deadline, and keep records as you go: receipts, timesheets, attendance, contracts, and the evaluation evidence your plan promised. Recording them weekly is dull, quick, and exactly what compliance means in practice.

Compliance also includes the wider rules attached to public and charitable money, such as keeping grant funds accounted for separately, following procurement care when you buy goods or services, and protecting the private information of the people you serve. The Grants.gov Learning Center frames the life of a grant as running through award closeout, the final step where last reports are accepted and records are retained as the award requires. Close well. An organization known for clean reporting and honest communication is an organization program officers remember kindly when the next opportunity opens.

An award is a promise with a calendar attached. Spend inside the rules, record as you go, report on time, and close the award cleanly.

Lesson 12

Learning from rejection

Most proposals are rejected, including good ones from strong organizations, because many worthy requests compete for limited money. A rejection is information, not a verdict on your worth. When the decision arrives, first check the practical lessons. Did you miss a requirement, misjudge fit, or submit to a funder whose recent awards look nothing like your project? Keep the submitted version and your checklist together so you can review what reviewers actually saw.

Many funders will share reviewer comments or allow a short conversation with a program officer. Ask politely, after the decision, whether feedback is available, and take notes without arguing. Reviewers often point to the same few things: a need that was asserted rather than shown, outcomes that could not be measured, a budget line that was never explained, or a plan that seemed too large for the team. Sort the comments into what you can change in the writing, what you must change in the project itself, and what was simply competition.

Then decide what the material becomes. A strong proposal can often be revised for another funder whose fit is better, with the announcement specific parts rewritten rather than copied across. Keep a simple file for each attempt: the funder, the deadline, the amount requested, the decision, and the main lesson. Over a year or two that file becomes your organization's real education in grant writing. The writers who improve are not the ones who never hear no. They are the ones who turn every no into specific knowledge and keep submitting careful, honest work.

Rejection is data about fit, evidence, and clarity. Ask for feedback, sort it honestly, revise for the right funder, and keep a record of every lesson.

Sources

The guides behind this course

This course is grounded in the Grants.gov Learning Center and the official Grants.gov applicant registration guidance, which explain the federal grants lifecycle, how organizations register, and how applications are submitted. Foundation and corporate research is taught as general craft in original prose.

Graduation

You finished Grant Writing 101

You worked through the whole life of a grant: how the grant world works, finding funders, reading an announcement closely, the needs statement, goals and outcomes, the project plan, the budget, evaluation, partners, registration and submission, reporting and compliance, and learning from rejection. You now have a complete, honest method for writing proposals that reviewers can follow and judge fairly.

Keep going: Next course: Nonprofits 101 · all free Starvard courses

Back to Starvard University

Keep learning

This course is part of Starvard University, striving for greatness.

Explore Starvard · All free courses

A note on accuracy: Much of what you read at Starvard was created with help from AI agents, working alongside people. We check what we can, but we cannot guarantee that everything here is true, current, or complete. If something really matters, your health, your money, a grade, a job, please verify it with a trusted source before you rely on it.