When an application is declined, most organizations assume the writing was not good enough. In my experience that is rarely what happened. The writing was fine. Something else went wrong, usually before a reviewer ever formed an opinion about the prose.
Here are the mistakes that actually cost money, in roughly the order they cost it.
1. Not writing to the scoring rubric
This is the biggest fixable mistake in the field and it is almost embarrassingly simple to correct.
Competitive applications are scored. There is a rubric, it is usually published in the funding notice, and it assigns points to specific criteria. Fifteen points for need. Twenty-five for program design. Fifteen for organizational capacity. Ten for evaluation. Ten for budget justification.
Most applicants read that section once and then write the narrative they wanted to write. Which means they spend nine hundred beautiful words on the mission story worth fifteen points and four paragraphs on the program design worth twenty-five.
The fix costs nothing. Build a checklist from the funder's own criteria, in the funder's own words. Write to it. Then grade your own draft against it before you submit, criterion by criterion, and be honest about the score. If you cannot find where a criterion is addressed, the reviewer will not find it either.
Reviewers do not decide whether they like you. They assign points against a list. Write to the list.
2. A need statement with no local data
National statistics establish that a problem exists. They do not establish that it exists in your service area, or that you are the organization to address it.
An application that cites a national poverty rate and then asks for money to serve three zip codes has left the most persuasive material on the table. What moves a reviewer is your county's numbers, your neighborhood's numbers, your waitlist, your intake data, the specific gap between demand and capacity that you can document.
If that data does not exist, that is your real problem, and it is worth more attention than the application in front of you. It will affect every proposal you submit for the next five years.
3. Outputs presented as outcomes
"We will serve 200 youth" is an output. It describes activity.
"Of the 200 youth served, 80 percent will improve attendance by at least one grade level equivalent, measured against district records at intake and at twelve months" is an outcome. It describes change, and it names how you will know.
Sophisticated funders score for this explicitly, and a lot of otherwise strong applications lose points here without the applicant ever understanding why. The tell is a goals section full of numbers that are all counts of people and none of them are counts of change.
4. A budget that contradicts the narrative
Budgets are where good applications quietly break, and the break is arithmetic rather than prose.
The narrative promises a full-time coordinator; the budget funds half of one. The evaluation plan describes an external evaluator; there is no evaluation line. Personnel percentages across a three-year period do not add to what the narrative claims. An indirect rate is applied to a cost category the funder excludes. Costs appear that the funder does not pay for at all, which for federal awards includes several categories most people have never had reason to learn.
Reviewers find all of these, and every one costs points that had nothing to do with your program.
Do not assume the funder's own workbook will protect you either. I have worked inside a state budget template whose formulas miscalculated composite totals across program areas. The file the funder distributed was wrong. Somebody had to foot the columns by hand and reconcile them against the narrative, and no amount of careful writing would have surfaced that.
5. Answering the question you wish they had asked
Long applications hide sub-questions inside prompts. A single item will ask about your staffing plan, then quietly add "and describe how you will ensure continuity if key personnel depart."
Applicants answer the first half, because the first half is the part they had a good answer for. The reviewer scoring that item sees half a response.
Break every prompt into its component questions before drafting. Answer each one visibly, in the order asked, using the funder's own vocabulary. This is not elegant writing, and it is not supposed to be. It is a scored document.
6. The mechanical failures
Unglamorous, entirely preventable, and they end applications outright.
- A missing required attachment. Board list, 990, audit, letters of support, indirect rate agreement.
- Letters of support dated for a prior cycle, or addressed to a different funder.
- Exceeding a page or character limit, which some portals silently truncate rather than warn about.
- A registration that had lapsed and takes weeks to renew.
- Submitting near the cutoff. Portals slow down under load on deadline day, and a hard cutoff is hard. Aim to submit a full day early, every time.
None of this requires skill. It requires a checklist and someone who owns it.
Ahead of all of these sits the eligibility screen, which removes applicants before scoring begins and which I covered in the post on AI and grant writing. It is worth reading if you have never had an application returned without a score.
7. The mistake that happens after you win
This one is not in anybody's list of grant writing mistakes, and it costs organizations more than most of the ones above.
Reimbursement-based awards require you to prove you spent the money. Organizations assume their receipts do that. Frequently the receipts do not.
I have worked a reimbursement invoice where twelve of the thirteen supporting documents were order confirmations rather than proof of payment. An order confirmation shows that something was ordered. It does not show that money left your account. The funder rejected the invoice on exactly that ground, and the work of going back through months of transactions to produce bank records and paid receipts cost far more than doing it correctly at the time would have.
Worse is the version where reporting never happens at all. I took on an organization where a departed employee had never reported hundreds of thousands of dollars of federally funded work that was genuinely performed. The service was delivered. The record did not exist. Reconstructing it and filing a formal appeal took months.
Winning is the beginning of the obligation. Build the documentation habit on day one of the award, not in the week the report is due.
8. Applying to too many wrong things
The meta-mistake, and the most expensive one in aggregate.
Organizations under funding pressure submit more applications, which lowers the quality of each one and drains the staff who deliver the programs. Six carefully targeted applications beat twenty scattered ones, every time, and cost less to produce.
Before drafting anything, ask three questions. Do we clearly meet every eligibility requirement. Does this funder have a history of funding organizations our size doing our kind of work. Can we actually administer this award if we win it. A no to any of those is a reason not to write, and declining to write is a legitimate and underused outcome.
What to do with a rejection
Ask why. Government funders will usually release score sheets or reviewer comments, sometimes automatically and often just for the asking. Private foundations vary, but a short, gracious note asking what would make a future application more competitive gets a real answer more often than people expect.
Then read the comments against the rubric and fix the specific criterion that scored low. That loop, run consistently, improves an organization's funding results faster than any writing advice on this page.
Most organizations never close it. They file the rejection and start the next application from scratch, and lose for the same reason again.
Common questions
Why do most grant applications get rejected?
In rough order: the applicant was screened out before scoring for an eligibility or completeness reason, the application scored in the middle of the pack against a rubric the writer never read closely, the budget contradicted the narrative or included costs the funder does not pay for, or the program was simply not the funder's priority that cycle. Only the last of those is outside your control, and it is not the most common.
What are the 5 R's of grant writing?
This phrase circulates widely and there is no authoritative version of it. Different trainers teach different sets, which is a reasonable signal that it is a memory aid rather than a standard. If a framework helps you, use one. But no acronym substitutes for the four things that actually decide outcomes: you are eligible, you wrote to the published scoring criteria, your budget ties to your narrative, and your claims are backed by real numbers from your own programs.
How can we write better grants without hiring anyone?
Three habits, in order of impact. Build a scoring checklist from the funder's own criteria and grade your draft against it before submission, honestly. Keep a narrative library of previously approved language, budgets, and attachments so each application starts at sixty percent rather than zero. And request reviewer comments on every rejection, then actually read them. Organizations that do those three things improve faster than organizations that simply write more applications.
Should we ask a funder why we were rejected?
Yes, and most organizations never do. Government funders will usually provide score sheets or reviewer comments on request, sometimes automatically. Private foundations vary, but a short, gracious email asking what would make a future application more competitive gets a substantive answer more often than people expect. That feedback is the cheapest program evaluation you will ever receive.
Can we reapply to a funder that rejected us?
Usually yes, and for many competitive programs the second or third application is the one that lands. Rejection frequently reflects oversubscription rather than a judgment about your organization. What matters is that the next application visibly responds to the feedback rather than resubmitting the same document with a new date. If you were declined without comment, ask before you rewrite.