Grant proposals submitted to the federal government are generally reviewed first by a peer review panel. This panel consists of people in related fields of interest who are instructed to offer an unbiased assessment of the grant proposals that have been submitted. The members of this panel will assign ratings according to the criteria that they are given. There are many different areas of interest.
When I first started, we were required to travel to Washington, DC. Today you will probably be able to perform your review services online. The rate of pay varies according to the different agencies. What you will appreciate besides the pay is the opportunity to learn just how the granting process works. It will also help to develop your skills as a grant proposal writer. This article will show you how easy it is to apply to become a federal grant reviewer. More...
Wednesday, December 17, 2008
Monday, December 8, 2008
Requested Information in Grant Proposals
In my experience with developing grant proposals, I have found that while headings may vary, Requests for Proposals (RFPs) tend to have common requirements for information. Whether you are preparing a grant proposal for an individual, Foundation or Government Agency, there are certain types of information that are generally required. The following is a list with brief description of common requirements for the contents of a grant proposal:
1. Needs Statements and Problem Statements: A Problem Statement is not the same as a Needs Statement. A Problem Statement clearly identifies the social, financial, economic, physical, community institutional problems that are in critical need of a solution. A problem is something that causes pain and suffering for others. On the other hand, a Needs Statement demonstrates the lack of resources and solutions that are required in order to solve a problem. For example: If Substance Abuse is the problem, then the social isolation caused by Substance Abuse may produce a need for developing skills in socialization.
2. Goals and Objectives: A goal is a general statement about the intent to reduce or eliminate a problem. It summarizes the answer about what the plan is to make the problem go away. Objectives are specific steps that can be measured to help meet the goals. For example the goal could be to prevent youth (ages 18-24) from going to jail for substance abuse related charges. An objective (to meet the stated goal) could be to develop alternative sentencing options for 50 youth arrested for substance use related charges.
3. Project Activities (Implementation/Methodology/Scope of Services): Project activities are generally given in Grant Proposal sections called Implementation, Methodology or Scope of Services. This section details a project design that lays out the plan to meet the goals and objectives. This will clearly describe what will be done and how the activities will be carried out. It will also determine the type of people and resources needed to make the project successful. This documentation should be a walk-through of what clients or participants will actually experience when they participate in your project.
4. Proving Capacity: After the plans to reduce or eliminate a problem have been effectively described, the proposal still needs to prove that the applicant has the ability to make it happen. This section should demonstrate that the applicant has a good idea of what it will take to run the project which includes adequate staffing and resources. The Capacity is the sufficiency of the staffing, resources etc. to make sure that the project produces favorable results.
5. Evaluation Plans: Everyone who receives funds for their projects will be required to prove to what extent their project was beneficial. They have to demonstrate how things have changed as a result of what was done. They will need to collect and report information that provide facts and figures about the effect on the goals, objectives and project implementation. An evaluation allows donors to have a measurable accounting of how impacting their contribution was.
6. Budget & Budget Narrative: A project budget is different from an organizational budget even though both must be considered in a proposal. Many organizations make the mistake of making the project budget the same as the organizational budget. A project proposal budget needs to be complete with details that show calculations about how each cost was determined. A budget narrative is required to describe how expenses are calculated, justified and relative to the stated goals, objectives and project implementation.
7. Abstract : An abstract is a summary of the project that generally includes the points about the Problem and Needs, and overall plan, target population, experience of the applicant and the cost. This is the information that may be used for press releases.
8. Executive Summary: An Executive summary is a more expanded detail that will include a summary of every section in the proposal. Both the abstract and the Executive Summary are developed after a proposal is completed and is generally the first documentation that a reviewer will read.
1. Needs Statements and Problem Statements: A Problem Statement is not the same as a Needs Statement. A Problem Statement clearly identifies the social, financial, economic, physical, community institutional problems that are in critical need of a solution. A problem is something that causes pain and suffering for others. On the other hand, a Needs Statement demonstrates the lack of resources and solutions that are required in order to solve a problem. For example: If Substance Abuse is the problem, then the social isolation caused by Substance Abuse may produce a need for developing skills in socialization.
2. Goals and Objectives: A goal is a general statement about the intent to reduce or eliminate a problem. It summarizes the answer about what the plan is to make the problem go away. Objectives are specific steps that can be measured to help meet the goals. For example the goal could be to prevent youth (ages 18-24) from going to jail for substance abuse related charges. An objective (to meet the stated goal) could be to develop alternative sentencing options for 50 youth arrested for substance use related charges.
3. Project Activities (Implementation/Methodology/Scope of Services): Project activities are generally given in Grant Proposal sections called Implementation, Methodology or Scope of Services. This section details a project design that lays out the plan to meet the goals and objectives. This will clearly describe what will be done and how the activities will be carried out. It will also determine the type of people and resources needed to make the project successful. This documentation should be a walk-through of what clients or participants will actually experience when they participate in your project.
4. Proving Capacity: After the plans to reduce or eliminate a problem have been effectively described, the proposal still needs to prove that the applicant has the ability to make it happen. This section should demonstrate that the applicant has a good idea of what it will take to run the project which includes adequate staffing and resources. The Capacity is the sufficiency of the staffing, resources etc. to make sure that the project produces favorable results.
5. Evaluation Plans: Everyone who receives funds for their projects will be required to prove to what extent their project was beneficial. They have to demonstrate how things have changed as a result of what was done. They will need to collect and report information that provide facts and figures about the effect on the goals, objectives and project implementation. An evaluation allows donors to have a measurable accounting of how impacting their contribution was.
6. Budget & Budget Narrative: A project budget is different from an organizational budget even though both must be considered in a proposal. Many organizations make the mistake of making the project budget the same as the organizational budget. A project proposal budget needs to be complete with details that show calculations about how each cost was determined. A budget narrative is required to describe how expenses are calculated, justified and relative to the stated goals, objectives and project implementation.
7. Abstract : An abstract is a summary of the project that generally includes the points about the Problem and Needs, and overall plan, target population, experience of the applicant and the cost. This is the information that may be used for press releases.
8. Executive Summary: An Executive summary is a more expanded detail that will include a summary of every section in the proposal. Both the abstract and the Executive Summary are developed after a proposal is completed and is generally the first documentation that a reviewer will read.
Saturday, December 6, 2008
Technology: Benefits and Challenges in Grant Proposals
In my grant proposals, the sections where I mentioned how our organization uses technology always gave me high scores. I would include our using Quickbooks Pro® to manage our financial activities and reporting. I would also describe how we used Microsoft® Access database to log our activities and other information.
However some of our technical abilities that we mentioned when submitting our first grant proposal actually did more harm than good. This is an area where I still disagree with fellow grant reviewers. Ours was a situation where the knowledge base was not the same as what was generally known.
There was a section where I was describing how long it would take for us to produce DVDs that featured drama addressing lifestyles and solutions regarding HIV/AIDS. I had stated that it would take us 4-6 weeks to complete each DVD. The grant reviewers’ comments stated that this was not a reasonable amount of time. In reality, it took us even less time than that because of the technology that we were using.
Unfortunately, our proposal did not help the grant reviewers to understand that we had tapped into a little known ability at the time (before 1998). Even the Microsoft support people did not know that their package could include an embedded video using their Pack and Go feature. I hounded the Microsoft support people by telephone and on-line to get them to tell me how to include video with my self running presentations on CD. They all told me the same thing. “You can not have a self running CD with embedded video using this package.” They were wrong. I stumbled upon how to do it by noticing that during the error process, the CD would be looking for the video from the file on the computer. So I simply copied all of the files onto a CD and reconstructed the presentation, drawing the files from the CD instead of from the hard drive.
We went on to apply this new revelation to developing multi-media presentations that could be used for training and development. We got so good at it that we could actually complete the whole process in even less time. The only obstacle that would take us longer was that my husband was so picky about the sound. He would often go to his keyboards and develop the music scores for our scenes rather than use the canned sounds that I chose from the software package. He would cringe at most of the canned sounds and music that came with the software.
When it came to detailing our project in the grant proposal, I simply could not see that they would accept our little known ability to generate self running video-enhanced multi-media presentations using Microsoft® PowerPoint. I did not see that it would benefit us to include that my husband is a gifted musician who scored our presentations with original music. Many people already found it hard to believe that he could play and record audio tracks with all of the instrumentation, including drums (that actually sounded like real drums) along with strings, horns, etc. People often doubted our claim that our music and multi-media productions were generated in the petite studio that resided in our living room. We had to give people demonstrations to get them to see that it was even possible.
With all of this doubt, I did not dare mention any of this in the grant proposal- which brings us to another lesson. Tell the truth about any technological enhancements, and let the reviewers sort it out. I only realized that this was the best way to do things after I became a grant reviewer. If you have a technological ability that is little known, you may include it with a brief explanation about how and why it works with your project. Your challenge is convincing the reviewers that you truly understand what you state that you are using. It is not always necessary that they understand it as long as they are convinced that you understand it. You must also be able to show how this complicated technology will be effective with producing the results that you claim.
However some of our technical abilities that we mentioned when submitting our first grant proposal actually did more harm than good. This is an area where I still disagree with fellow grant reviewers. Ours was a situation where the knowledge base was not the same as what was generally known.
There was a section where I was describing how long it would take for us to produce DVDs that featured drama addressing lifestyles and solutions regarding HIV/AIDS. I had stated that it would take us 4-6 weeks to complete each DVD. The grant reviewers’ comments stated that this was not a reasonable amount of time. In reality, it took us even less time than that because of the technology that we were using.
Unfortunately, our proposal did not help the grant reviewers to understand that we had tapped into a little known ability at the time (before 1998). Even the Microsoft support people did not know that their package could include an embedded video using their Pack and Go feature. I hounded the Microsoft support people by telephone and on-line to get them to tell me how to include video with my self running presentations on CD. They all told me the same thing. “You can not have a self running CD with embedded video using this package.” They were wrong. I stumbled upon how to do it by noticing that during the error process, the CD would be looking for the video from the file on the computer. So I simply copied all of the files onto a CD and reconstructed the presentation, drawing the files from the CD instead of from the hard drive.
We went on to apply this new revelation to developing multi-media presentations that could be used for training and development. We got so good at it that we could actually complete the whole process in even less time. The only obstacle that would take us longer was that my husband was so picky about the sound. He would often go to his keyboards and develop the music scores for our scenes rather than use the canned sounds that I chose from the software package. He would cringe at most of the canned sounds and music that came with the software.
When it came to detailing our project in the grant proposal, I simply could not see that they would accept our little known ability to generate self running video-enhanced multi-media presentations using Microsoft® PowerPoint. I did not see that it would benefit us to include that my husband is a gifted musician who scored our presentations with original music. Many people already found it hard to believe that he could play and record audio tracks with all of the instrumentation, including drums (that actually sounded like real drums) along with strings, horns, etc. People often doubted our claim that our music and multi-media productions were generated in the petite studio that resided in our living room. We had to give people demonstrations to get them to see that it was even possible.
With all of this doubt, I did not dare mention any of this in the grant proposal- which brings us to another lesson. Tell the truth about any technological enhancements, and let the reviewers sort it out. I only realized that this was the best way to do things after I became a grant reviewer. If you have a technological ability that is little known, you may include it with a brief explanation about how and why it works with your project. Your challenge is convincing the reviewers that you truly understand what you state that you are using. It is not always necessary that they understand it as long as they are convinced that you understand it. You must also be able to show how this complicated technology will be effective with producing the results that you claim.
Thursday, December 4, 2008
PROBLEMS: A LESSON ABOUT HANDLING THEM
Today I can say, “thank you Lord for sparing us.” One of the first lessons that I began to learn is that every problem is not for me to solve. I am not sure how or why it began, but I would hear about problems that I took on as my duty to seek solutions. What made it difficult for me to resist the problem solving mode was that I was generally successful with finding effective solutions. In preparing grant proposals for others, this skill was actually be a stumbling block. I helped people get funded that really should not have been.
A dear friend of mine, Midge Lansat helped me understand that this was over functioning. I also realized that it made me appear to be a control hound. I was only trying to help. But my helping often over burdened myself and my reluctantly obliging family.
This lesson that “every problem is not for me to solve” was coupled with “just because I could do something did not mean that I should do something.” I am sure to get more than a few “Amens” in agreement with that statement.
I used to wonder why Jesus did not simply stand at the top of the highest mountain, stretch out his hands and say, “every body in the world - be healed.” I knew that he could do this and all suffering from sickness would end at that instant. But as I learned more about the purpose of human development on earth, I realized that if Jesus took away all of the pain and suffering on earth, many of us would be robbed of the opportunity and responsibility that is developing us for our next level of existence.
Many outreach oriented people like me are doers. We want to do something about a problem that really bothers us. We are natural “wanna be” problem solvers. This mindset is further complicated by having the ability to actually do a number of tasks well.
You may ask, “what is wrong with wanting to help where you can make a difference?” What is wrong is that the constant pull of new problems can greatly interfere with fulfilling the true calling that God has ordained. When people operate in what they have been anointed to do, there is a certainty of success. With each success comes an awareness that the journey and efforts are on the correct path. There is also a sense of nearing a state of completion- not lacking anything.
On the journey to completeness, there is no space for emptiness or time for regrets. There are many doers that fill empty. I believe that this emptiness is the result of not connecting with what they were intended to accomplish. My understanding about the importance of operating in your calling began to sprout with my first serious effort to produce a government grant proposal.
When writing a government grant proposal, you will be forced to settle upon a single problem or else you will find it quite difficult to complete the documentation. You will be required to thoroughly account for every effort that you presented as necessary. This accountability is what helped me to become much more disciplined in my own stewardship of time as well as resources.
Fortunately, I ultimately realized that every problem is not mine to solve. I realized that I must account for the time and effort that I contribute towards trying to solve problems. In being accountable, it became harder for me to justify spending time with issues that could possibly return income, but little results. However the problems that I was prepared to address offered compensation as well as a track record for success.
A dear friend of mine, Midge Lansat helped me understand that this was over functioning. I also realized that it made me appear to be a control hound. I was only trying to help. But my helping often over burdened myself and my reluctantly obliging family.
This lesson that “every problem is not for me to solve” was coupled with “just because I could do something did not mean that I should do something.” I am sure to get more than a few “Amens” in agreement with that statement.
I used to wonder why Jesus did not simply stand at the top of the highest mountain, stretch out his hands and say, “every body in the world - be healed.” I knew that he could do this and all suffering from sickness would end at that instant. But as I learned more about the purpose of human development on earth, I realized that if Jesus took away all of the pain and suffering on earth, many of us would be robbed of the opportunity and responsibility that is developing us for our next level of existence.
Many outreach oriented people like me are doers. We want to do something about a problem that really bothers us. We are natural “wanna be” problem solvers. This mindset is further complicated by having the ability to actually do a number of tasks well.
You may ask, “what is wrong with wanting to help where you can make a difference?” What is wrong is that the constant pull of new problems can greatly interfere with fulfilling the true calling that God has ordained. When people operate in what they have been anointed to do, there is a certainty of success. With each success comes an awareness that the journey and efforts are on the correct path. There is also a sense of nearing a state of completion- not lacking anything.
On the journey to completeness, there is no space for emptiness or time for regrets. There are many doers that fill empty. I believe that this emptiness is the result of not connecting with what they were intended to accomplish. My understanding about the importance of operating in your calling began to sprout with my first serious effort to produce a government grant proposal.
When writing a government grant proposal, you will be forced to settle upon a single problem or else you will find it quite difficult to complete the documentation. You will be required to thoroughly account for every effort that you presented as necessary. This accountability is what helped me to become much more disciplined in my own stewardship of time as well as resources.
Fortunately, I ultimately realized that every problem is not mine to solve. I realized that I must account for the time and effort that I contribute towards trying to solve problems. In being accountable, it became harder for me to justify spending time with issues that could possibly return income, but little results. However the problems that I was prepared to address offered compensation as well as a track record for success.
Subscribe to:
Posts (Atom)