Every field carries habits that have outlived the reason they started.
Someone did something a certain way once, under a specific deadline, for a specific reason. It worked well enough. Nobody revisited it. And a few years later, an entire team is following a process that made sense exactly once and has never been questioned since.
Grant proposal writing has its own collection of these habits. Most of them are not dramatic failures. They rarely cause an obvious, immediate problem. They just quietly cost an organization a little bit of quality, a little bit of time, or a little bit of credibility, proposal after proposal, without anyone stopping to notice the pattern.
Fall, when many organizations are already reviewing what worked and what didn't this year, is a reasonable time to look at a few of the most common ones and decide, deliberately, whether they are still earning their keep.
“We'll reuse last year's narrative and just update the numbers”
This is one of the most common shortcuts in proposal writing, and one of the easiest to get away with, right up until it backfires.
A recycled narrative often carries more of last year than anyone intended. It may still describe a partnership that has since ended, reference a staff member who left the organization, or describe a community context that has genuinely shifted. Funders who supported your organization last year are often the ones most likely to notice when nothing has actually changed except the date at the top of the document.
Updating the numbers is not the same as updating the proposal. If the program evolved, the narrative needs to reflect that evolution, not just report new totals against old language.
Writing the summary before the proposal is finished
A summary or executive summary drafted first, before the narrative, budget, and evaluation plan actually exist, tends to describe what the writer intended to say rather than what the finished proposal actually argues.
The stronger habit is to write the summary last, after every other section has been finalized. At that point, it can accurately reflect the proposal that funders will actually read, instead of an earlier, more aspirational version of it.
Treating the budget and the narrative as two separate jobs
In some organizations, the program team writes the narrative and finance builds the budget, and the two documents meet for the first time the week of the deadline.
This is how proposals end up promising eight workshops that the budget only funds for six, or listing a coordinator role the budget was never designed to support. A budget and a narrative developed separately, then stitched together at the end, rarely tell a fully consistent story.
The stronger version of this process brings program and finance staff into the same conversation early, so the plan being described and the plan being funded are the same plan.
A small habit with an outsized effect
Of all the habits worth retiring, submission timing is probably the easiest to fix and the most often ignored.
Submitting the day of the deadline, every time, occasionally reveals a problem: a portal that will not accept a file, an attachment that silently failed to upload, a formatting requirement buried on page four of the guidelines that nobody caught until the final review.
When submission happens the day before, instead of the day of, on a regular basis rather than as an occasional stroke of good planning, those problems get caught while there is still time to fix them. Building in that single day of margin, consistently, is a small habit with an outsized effect on how many “almost missed it” stories an organization accumulates over the years.
Measuring success only by whether the proposal was awarded
It is easy, and understandable, to sort every proposal into exactly two categories: awarded or not awarded. It is also a habit that quietly throws away useful information.
A well-written, well-targeted proposal that was not awarded because of a limited budget or an unusually competitive pool is a very different outcome than a proposal that was never genuinely competitive to begin with. An organization that tracks only the final yes-or-no misses the chance to learn which proposals were strong but unlucky, and which ones have a real, fixable problem.
Asking for feedback when a funder offers it, and keeping a simple record of the likely reason behind each decline, turns a string of outcomes into an actual source of improvement.
None of this requires a complete overhaul
None of these five habits is a crisis on its own. That is exactly why they tend to survive for years without being questioned. Each one, individually, is easy to justify as “how we've always done it” or “there wasn't time to do it differently this time.”
But together, they add up to real cost: proposals that feel slightly generic, summaries that slightly miss what the proposal actually says, budgets that slightly contradict the narrative, submissions with no room for error, and a process that never quite learns from its own results.
This fall is as reasonable a time as any to look at the habits your own team has been following out of routine, and decide, deliberately, which ones are still worth keeping.
The Grantsmanship Center helps organizations build the planning, proposal development, funder research, and grants management skills needed to pursue funding with clarity and confidence. For more information, visit our website: tgci.com
Get funding. Create change.
