Welcome to my blog! I am excited to share and discuss my grant writing/researching/administering experience with you. I hope this advice, which comes from years of wanderings, informs and encourages you.
For my inaugural post, I wanted to tackle some of the reasons why proposals aren’t even read. In this day and age, funding agencies are receiving more and more proposals, even as their funding shrinks. I have literally heard reviewers say that they look for any reason to weed out proposals without spending a lot of time on them. If a proposal is out of compliance – well, that makes it easy to “chuck” – after all, should a reviewer or program officer entrust funds to someone who can’t even follow basic directions?
Don’t let your worthy project go totally unread! Avoid these (non-comprehensive) reasons why your proposal may get thrown out without even being read, and then leave any questions or comments below!
- Your proposal was late.
I know you meant well, when you were revising right up to the deadline. But often, this strategy can backfire, especially if your proposal has to go though a lengthy internal process to be submitted (for instance, if you are working at a university). Also, some agencies (such as the National Institutes of Health), will spit back your proposal if their system detects errors in compliance. By the time you push it back, it might be too late.
A tip from me to you – some agencies, such as the NIH, might still review your proposal, if it is a tad bit late. But they are within their rights to reject your application if it comes in even a minute after the deadline. NSF, NEH, and other agencies will not even consider your proposal if it is late.
- Your proposal was too long.
I know it’s tempting to get every bit of your research on paper for reviewers to experience, but that will not be worth it if they decide to throw out your proposal because you exceeded the page/character limits. Some agencies also put a cap on how many of your publications you can include. Better that you skimp on some of the details than never have your proposal read.
- Your narrative did not meet the stated requirements.
Writing your narrative seems intuitive enough – you describe your project and what you want to accomplish. But read – re-read – and re-read again – the exact questions the application is asking. Unfortunately, I have seen many seasoned academics skim over the funding agency’s questions and write their agenda without consulting them ever again. Here’s a tip: Be explicit when you are answering the specific questions required by the funder. Put these sections in bold. Use the same language as the question. Use bullet points. If the reviewer cannot easily find the answers to the RFP’s first question, they will probably toss your proposal without a second glance.
The same goes for your budget narrative. I cannot over-emphasize this. Do not put something in your budget without connecting it to the overall proposal.
- Your budget was off.
Your proposal might never see a reviewer if your budget does not add up, is on the wrong form, or has unallowable costs on it. The program officer might be kind enough to give you a call and ask for a revision. But they are under no obligation to do so. Check and double-check your numbers, and make sure someone else checks them for you.
If you are working at a university with an Office of Research or a Grants Manager, work with them on the budget beginning months before the due date. If you pass along the basic information on what you want to ask for, they can usually take it from there. Who has time to calculate fringes, indirect costs, and tuition increases when you have so much to write, anyway?
- Your proposal’s format was non-compliant.
The details matter here. Font type, font size, pagination, and margins can become your worst enemy. Before submitting, check to make sure you are meeting the agency’s formatting requirements. Keep in mind that these may be found in the agency’s broad guidelines, and not necessarily the RFP.