#67: A Checklist for Beginning a Grant Writing Assignment for a New Organization

Tara emailed me asking whether I have a form that I use when I go to see a new client. I don't. But, I jotted down a few things for her and then thought I'd share them with you, too.

When a new (to me) organization engages me to do a piece of work, here's how I get started.

Before my initial interview in person or on the phone:

• Review the organization's 990 and website
• Ask them to send me a packet of their PR materials, any boiler plate they have, and perhaps an earlier grant application they've submitted.
• Do a Google search on them including news and blogs
• Sometimes I'll review the research and best practices prior to the first meeting, sometimes later

Based on that, I usually go into the interview with a pretty good idea of the public face of the agency. Then, if the interview is for a specific grant, we discuss:

• Project orientation - how we'll work together, who's on the team, who's the agency's lead, what tools we'll use, time table, etc.
• What makes them want to apply for this grant? What are they currently doing makes them feel they have a good chance at receiving the funding?
• Review the grant requirements - assume they haven't read the details
• Walk through each section of the application and appendices discussing content, identifying what information is outstanding, determining who will get it, by when.

If they are asking for help to identify new funding opportunities we discuss

• Current operations
• Strategic direction
• Previous and current funders
• Applications submitted but not funded
• How we'll work together

Does this sound like what you do? Do you have additions?

Grant Writing: Getting Blamed?

September brings good news and bad news in the grant writer's world. The Feds finally make all their decisions public in anticipation of their new fiscal year, October 1.

As usual, the results for applications I've written are mixed. We're all disappointed when we get a rejection, especially when we thought it was an especially good match. So, this post on Kivi Leroux Miller's blog caught my eye. Here's an excerpt and a link --

Nonprofit Communications » Blog Archive » Why I Don’t Write Grant Applications or Direct Appeals: "1) Nonprofits blame you, the grant writer, if they don’t get the funding, even if their project is really weak or they are applying to the wrong funding source. Even a beautifully written grant application can’t turn a lousy project into a winner, nor can it convince a project officer to fund you if the project is outside her area of interest."

I don't think I've ever been blamed for a grant application not getting funded. Maybe I've been lucky, but it's always seemed such a team effort that blame hasn't entered the equation.

What's your experience? Am I just lucky?

Photo by debaird

# 16: Does Anyone Around Here Read?

Long ago, I gave up expecting grant prep team members to read the RFP. Yes, some conscientious individuals will. But most won't. They're busy running programs, as they should be. Grant applications get sandwiched in. Why be disappointed or frustrated with them? Compensate.

I start the grant writing process with a 1 or 2 page (max) summary which includes the funders goals and requirements followed by bulleted questions for the team to consider, or the program content already under discussion. I aim to make the document one someone can scan in less than five minutes.

It's worth the effort. It helps fix the funder's agenda in my mind. It guarantees we have easily referenced requirements in front of everyone as we plan. And it serves as the basis of the background material we provide to people who agree to provide letters of support. (More about those letters another time.)

Does Anyone Around Here Read? Not the RFPs! But why worry?

#11: Grant Writing and Client Feedback

When do you ask your client to read your draft grant application? And what kind of feedback do you want, when?

Working with short deadlines forces me to share drafts sooner than I'd like. My client often sees a draft that looks nothing like the finished product. But I need feedback on the content.  Are the facts right? Am I emphasizing the right points in the evidence?

Seth Godin's blog entry about giving good feedback is useful in thinking through how to ask your client for feedback on that early draft. 

Seth's Blog

In the interest of promoting your career, making your day at work more fun, improving the work life of your colleagues, and generally making my life a whole lot better, I'd like to give you some feedback on giving feedback. As usual, the ideas are simple--it's doing them that's tricky.

Resource #2: Basecamp

My friend Tom told me about this collaboration software and after two days I don't know how I managed putting together a grant without it. Tom works for a start-up company that has a handful of employees seldom in the same place at the same time. Things change rapidly and everyone needs to be in the loop on decisions. As he described how they use basecamp I realized its value to me.

Putting together a grant requires input from a team of people, all busy with their real jobs. And when the grant is for a coalition...well, you know how complex the communication becomes. Keeping track of who's providing what and making sure they know when you need it. Keeping everyone apprised of the program changes (oh, no, that component got dropped 3 days ago. The budget wouldn't stretch that far.)

Well, Basecamp has messages, to-do's, milestones, writeboards for brainstorming and drafting. It's web based so you can access it from anywhere. There's a free version that handles one project at a time. That's what I thought I'd use but I quickly realized the benefit of having several seperate projects going. And my clients have found it simple to use and really seem to appreciate it. (Do any of you want to comment from the client side?)

Take some time to look at it. Read the case studies. Sign up for the free level to try it out. You'll like it, too. It's worth five, maybe even ten, resource entries.