You've been handed a funding notice full of terms you've never seen, a portal that wants three registrations and a deadline that seems to be in a different language. Everyone around you assumes you know what you're doing. You suspect they're wrong.
That feeling is familiar to many people starting something new, and it doesn't mean you're unsuited to the work. This article covers why the first months of grant writing feel this way, what you already bring, how to learn the rest quickly and one task to do this week.
Why the first months feel so unsteady
The feeling is often called imposter syndrome: a sense that you're about to be found out, even when the evidence says you're doing fine. It's a description of a feeling, not a diagnosis. This article doesn't try to treat it. If it's weighing on you beyond the job, talk to someone you trust or a professional.
For a new grant writer, the feeling has practical causes that you can do something about:
- The vocabulary is dense. NOFO, SAM.gov, UEI, indirect costs, cost share, logic model, subaward. Nobody is born knowing these.
- The rules are partly invisible. A federal notice can point to regulations such as 2 CFR 200, a registration process and a portal, none of which appear on the first page.
- The stakes feel high. A missed requirement can sink an application, and you may be the only person in the building who has read the notice end to end.
Seen this way, the problem is missing information, not missing ability. Information can be gathered.
Start with what you already know
Grant writing asks for three kinds of knowledge. You probably have more of the first than you think.
- Your program. You know who comes through the door, what happens when they do and where the work is hard. Reviewers can't get that from a database.
- Your community. You know what people say they need, what's changed in the last few years and which partners are already at the table.
- Your organization. You know the history, the staff, the budget and the promises you've already made to other funders.
What you're learning is the fourth kind: how funders ask for those facts. That's a skill, and skills improve with repetition.
Here is a hypothetical example. Say a new hire at a small youth-sports nonprofit is asked to draft a need statement. She doesn't know the term, so she lists what she can already say: how many kids joined last season, how many were on a waiting list, what families told staff about transportation and cost. Her list is the raw material of a need statement. What's left is arrangement, and the need statement shows how to arrange it.
Learn the language in a week, not a year
You don't need a course to get started. You need a few hours with the right documents.
Read the notice like a textbook
A funding notice is the best teacher you have, because it's written for the exact application in front of you. Under 2 CFR 200.204, federal agencies must include summary information at the top of a notice on Grants.gov, including key dates and an executive summary of no more than 500 words, and the regulation tells agencies to write in plain language. Read that summary first, then the eligibility and review criteria. How to read a funding notice walks through the order.
Keep a running glossary. Each time you hit a term you don't know, write it down with a one-line definition in your own words. The Grants.gov Learn Grants section has a terms section and a grants 101 section that cover many of them.
Read funded applications
Some funders and agencies publish examples of applications that won. The National Institute of Allergy and Infectious Diseases, for instance, posts sample applications and their summary statements, with a caution that the samples may not reflect the latest format or rules. Those are research grants, so the subject matter may be far from yours, but you can still see how a funded application is organized, how it answers the review criteria and what reviewers said about it.
For your own field, ask colleagues at other organizations or your program officer whether they can share a past application. Asking costs nothing, and one real example teaches more than a generic template.
Find out who gets funded
USAspending.gov lets you search federal awards, so you can see which organizations in your state or field have received money from a program before. Many foundations list recent grants on their own websites. Either is a way to learn what funders actually pay for.
Ask for a second pair of eyes
Find one colleague, mentor or peer at another organization who will read your drafts. Grant writing alone covers where to find people for that.
Reframe the mistakes you'll make
You will get something wrong in your first year. A budget line won't match the narrative, or you'll misread an eligibility rule. That's how everyone learns the work, and it's why a checklist and an early internal deadline matter so much. They catch problems before a funder does.
When something goes wrong, write down what happened and what you'd do differently. Over a few months that note becomes your own handbook, and it's the quickest way to turn doubt into evidence of progress.
Your next step
This week, find one funded application or a published sample in your field and read it with a pen. Mark where it states the need, where it describes the work and where it explains the budget. Then pick the next notice you might apply to and write down the three terms in it you can't yet define.
If the blank page is the hard part, SoliContraX lets you start from the notice itself. Upload it, approve a concept and work from a draft built from your organization's own materials, then finish it in your own words. See how to get started.