Opening the book…
There are many different ways to approach the grant writing process, but I would like to frame this discussion by briefly describing the process that I typically go through when I undertake writing a grant proposal. Of course the process varies somewhat depending on the type of project, the funder (e.g., foundation or federal grant), the circumstances (e.g., timelines), and the personal characteristics of the client. However, there are certain steps and activities that I have found to be especially important.
15.1.1. Getting the Job
It goes without saying that you won’t be writing any grant proposals as a consultant if you don’t have a client who wants to hire you! My clients tell me that they feel much more comfortable engaging a known quantity for this important job; in other words, relationships matter. You will be much more likely to land grant writing jobs if you have a well-developed network of colleagues—also known as “potential clients”—who are knowledgeable about your skills and see you as a good collaborator (this network need not be large, but it should include individuals in organizations who are either responsible for managing programs that are supported by outside funding, or who have the ability to identify and contract with outside grant writers). One of my clients, a director of a national organization, noted to me recently that in his previous experience with grant writers, he had found himself doing (or re-doing) most of the work himself because the writer did not have strong writing skills, or was simply unable to understand the important concepts of the proposal. These kinds of grant writers are not likely to get repeat business.
I have been lucky in that I have generally been able to rely on having clients contact me with offers of work and have not had to go out and actively market myself as a grant writer. In order to achieve this enviable status, “all” I’ve had to do is spend over 10 years working in policy settings in Washington, DC, developing my skills and nurturing a professional network of key colleagues who respect my skills and who feel that they can call upon me to work with them on grant writing projects. Then, over the last 10 years as a consultant, I further developed and strengthened those networks. Especially now that I have a proven track record as a proposal writer, colleagues come to me when they need my services. But, it took years to develop a reputation as someone on whom they can rely to produce good work. That isn’t to say that you have to spend 20 years in the wings before you can be a successful grant writer, but you will be much more in demand if you have a demonstrated set of skills that people actually know about (e.g., because they have worked with you before, or because someone they trust has referred them to you).
15.1.2. Finalizing the Contract
My least favorite part of the process is setting up a work contract with a client, but as this is essential to getting paid, it is a necessary evil! And, of course, the contract protects both me and the client, so it is to the advantage of both to have a proper contract in place. Ideally, the contract is developed and signed before work begins. However, the pressing timeline of some work projects demands that work begin even before both parties have signed the contract. There is a real risk in doing this, in that work arrangements can potentially fall through at any point, but to date I have not experienced problems (this is likely in part because I work primarily for national organizations that have more than sufficient resources for supporting my services, and that also have internal checks and balances that require project approval before I am brought onboard). Once I have established an ongoing relationship with a client, and there is a history of prompt payment, I am also more willing to proceed with work before the final contract is signed.
Sometimes the client organization has a standard contract format that they use, in which case they draft the contract; otherwise I can draft the contract or let the client know what elements need to be included in the contract that they draft. The contract typically includes a statement of work that specifies the rate of pay (whether an hourly rate or a lump sum), the total payment of the contract; and the payment schedule; the deliverables (e.g., products to be produced and services to be rendered); the timeline; and how the contract can be terminated by either party. There may also be a statement regarding authorship (i.e., whether the contractor’s name will appear as an author on any products that directly result from work on the project) as well as ownership rights (as these projects are “works for hire,” the client typically retains ownership of the products).
Determining how much to charge for writing a grant proposal depends on a variety of factors, such as the client’s resources, the types of tasks involved in the project, and whether the project is long-term or short-term. For example, if I believe that a project is worthwhile and that the mission of the client is an important one, I will usually work with whatever limited resources the organization has, even if the rate of pay is lower than what I usually charge. I will also charge a reduced rate for ongoing projects that assure me continued income for a period of time (grant proposals are, however, typically short- term projects, so would rarely receive this “discount”). Otherwise, I stick to my standard hourly rate that I charge, which is based on my experience and market factors.
Payment terms may be by the hour, a daily rate, or lump sum (i.e., the total amount to be paid for the project is set in advance, no matter how many hours it eventually takes to complete the project, whether more or fewer than originally estimated). If the project is more open-ended or it is difficult to determine the number of hours that will be needed to complete it, then I prefer to be paid by the hour instead of a lump sum to assure that my time is fully compensated. For some projects, though, I prefer a lump sum payment simply because it relieves me of the burden of meticulously tracking and accounting for all of the time that I spend on the project (as I have gained more experience writing grant proposals, I have become better at estimating in advance the level of work required to complete the project, and thus am better able to set a fair lump sum amount).
Whichever method of payment is used, if the scope of work extends beyond the original agreement (e.g., I am asked to do additional background research, or to write additional sections of the grant proposal), I will discuss the need for additional payment with the client. I have never stopped a job in the middle because the budget has run out, but I will keep the client apprised of the rate at which resources are being used, and either get assurances regarding additional payment for additional work, or renegotiate the level of work expected to maximize the use of the remaining resources.
15.1.3. Mapping Out the Idea
Once I have been engaged to write a grant proposal, I meet with the client (usually in person) to learn more about the project they are proposing. In some cases, they have already spent a significant amount of time articulating the project and have a clear idea of what they want to do. More commonly, they have a general idea of the project that they want to do, but have not yet thought through the details. My preference is to become involved in the project early on so I can have input into the development of the idea. One reason for this is simply because I enjoy the process, but more importantly, it allows me to provide critical input by identifying strengths and weaknesses as well as gaps in thinking. I have found that proposals where I am brought into the process later do not fare as well as those where I am brought in at an earlier stage and can help the client more clearly articulate their goals, objectives, and project activities.
No matter where the client is in their development of the project, we engage in an ongoing process of thinking through the project in detail, including clarifying the goals. As we continue to work on the proposal, more and more details get filled in, with ideas sometimes being proposed and then rejected until we are satisfied that we have a well-articulated and viable plan that accomplishes the goals of the project. Sometimes mapping out the idea involves just me and the client, but in other cases, outside experts (e.g., university-based researchers with expertise in the project area) are also brought in to review the ideas critically and contribute their own. In any case, no good proposal is developed without getting the input of others—whether from me, other colleagues at the client’s workplace, or outside experts.
15.1.4. Understanding What the Funder Wants
Another important early step is to carefully review the guidance from the funder to determine what information they want to see in the proposal, and to be clear about such practical matters as how the document should be formatted and how long each section can be. If we are going to submit the proposal online, there may be additional procedures that have to be followed. Depending on who the funder is (e.g., a foundation or a federal funder), they may want something as simple as a 3-page prospectus, or as complex as a highly detailed (and lengthy) proposal that articulates the project’s theoretical rationale, its goals and objectives, all of the project activities, timelines, evaluation plan, measurement tools, and more. The more detailed and complex the call for proposals, the more important it is to carefully read it to make sure that we address all of the items in the grant proposal. Thus, an important early step is to create an outline of the proposal that reflects the guidance from the funder, including any reference to rating factors. This is not a time to be creative; we want to make it easy for the reviewers to see that we have addressed all of the items in the guidance. The penalty for not following directions can be severe, even preventing your proposal from entering the review process.
Although carefully reviewing the guidance is critical for understanding what the funder wants, it is also important to have a general understanding of the funder’s mission, its history, and any contextual political issues that might affect what types of projects are funded, and even what kind of language one should use to describe projects to increase the likelihood that they will be funded. Awareness of some of these issues is something that you may be able to pick up after working in a particular area for years, but it’s also important to get your client’s take on them (your client will likely be more knowledgeable about these factors since they are immersed in them on a day-to-day basis). The project officer responsible for the call for proposals is also potentially a source of information, as are your colleagues who may work in the same or similar areas.
15.1.5. Writing the Proposal
At some point during this process, the actual writing begins (usually once there is some clarity about the goals and activities of the project). Based on the guidance provided by the funder, my client and I decide who will be responsible for writing which sections. At a minimum, I am usually responsible for writing the project narrative (e.g., describing the project and all of its activities); I also typically develop and write the evaluation plan and develop the timeline, and sometimes also draft the budget. Responsibility for assembling supporting documentation (including securing letters from potential partners, obtaining project staff vitae, etc.) usually falls to the client, as does completing any required forms.
As I write the proposal, I often draw upon my general knowledge and background to fill in details, anticipating the activities and procedures that the client will need to accomplish to meet the goals of the project (I sometimes jokingly refer to this as “making stuff up,” but in fact it’s based on my broad knowledge of program development in a wide range of areas and on previous experience writing proposals). This might include, for example, articulating the steps for recruiting participants to a project, identifying information dissemination strategies, describing the steps involved in organizing a focus group, or clarifying the types of individuals to serve on a project steering committee and what should be their responsibilities. Writing is usually a collaborative process as the client and I exchange and review drafts, and as we work to resolve questions as they come up.
Ideally, this process begins far in advance of the deadline—as soon as the call for proposals is issued—in order to allow plenty of time for thoughtful discussions, multiple drafts, and critical review by knowledgeable colleagues before the draft is finalized and submitted. I won’t say that this never happens; I will only say that it has never happened to me. Even in cases where initial discussions begin several months in advance of the deadline, the bulk of the work always seems to be concentrated in the final few weeks— and then the final days and hours—before the deadline (sometimes even the final night before the deadline, as my client and I forego sleep to make final revisions together and assemble the application packet; this is not, however, a tactic that I recommend).
15.1: The Process of Writing a Grant Proposal is shared under a not declared license and was authored, remixed, and/or curated by LibreTexts.
The book could not be loaded just now.