The cliche goes, “Chance favors the prepared mind,” and we could repurpose it to, “Short deadlines favor the prepared nonprofit.” I have the dubious pleasure of reading the Federal Register every week and have noticed that deadlines are shrinking like hemlines. This means the organizations that apply with a complete and technically correct proposal are, even more than usual, the ones who don’t dawdle in deciding to apply and don’t procrastinate once they’ve made the decision.
If you’re thinking about applying for a grant with a thirty-day deadline, don’t take a week to mull it over. Take an hour. Need to wait on a board meeting? See if you can schedule an emergency meeting that night. Can’t do it? Text the chairperson immediately and set up a conference call. If you wait long enough, you won’t be able to get your application together, and, in an environment like this one, you don’t want to miss a deadline for a good program. It could be the life or death of your organization. Small delays tend to turn into big ones; don’t delay any part of the process any longer than you have to.
We sometimes find ourselves in a situation where a couple of clients hire us before a funder issues an RFP. Once the RFP is issued with a very short deadline, we get deluged with calls; as a result, we often have to say “no” to jobs because we lack the capacity and the time to do them. For us, this sucks, since we want to help our clients get funded. But we’re also unusual because we always hit our deadlines; part of the reason we can always hit deadlines is because we decline work if we can’t finish it.
This sometimes makes potential clients, who think hiring a consultant is like shopping at the Apple Store, irritated: “Whaddaya mean, you can’t write the proposal?” “We don’t have the capacity.” “That’s ridiculous! I’m ready to pay.” But consulting isn’t like stamping out another MacBook Air: it’s an allocation of time, and, like most people, we only have twenty-four hours in our days. While we can often accept very short deadlines, sometimes our other obligations mean we can’t. No matter how much it hurts to say “no,” we say it if we have to. This is one reason it is a good idea to hire in advance of a RFP being issued.
There are also situations with misleading or hidden double deadlines. For example, the HRSA Section 330 programs Isaac wrote about last week list application deadlines of October 12. But that deadline is only for the initial Grants.gov submission, which requires an SF-424, a budget, and a couple other minor things. Stuff you could do in a day. The real application—the HRSA Electronic Handbook (EHBs) submission—isn’t due until November 22. So what looks like thirty days is actually closer to two months, but only to people in the know (like those of you who read our e-mail grant newsletter; I’ve seen lots of sites present the October 12 deadline HRSA offered instead of the real deadline). If you’re not paying attention, you’re going to miss what’s really happening on the ground.
But you should still make your choice to apply for any grant program quickly, not slowly. Slow food might be a virtue, but slow grant application decision-making and proposal writing aren’t.
When Seliger + Associates began, the Internet was just breaking into the mainstream and relatively few nonprofits used computers in the workplace and few business and home computers had reliable Internet connection. Grant deadlines were routinely in the neighborhood of 60 days. They had to be: disseminating information about deadlines was slow, shipping hard copies of RFPs was slow, research was slow and required trips to libraries. Plus, there’s an element of fundamental fairness in giving nonprofit and public agencies enough time to think about what they’re doing, gather partners, solicit community input, decide to hire grant writers, and so forth, and funders appear to have lost interest in that issue. Now, nonprofits have to do this much faster. The ones that succeed are the ones who realize that circumstances on the ground have changed and then adapt to the new environment.