March 25, 2009

The Effective Project Proposal, Part II

Well, after months since the first part, I now have the third and final part of our Project Proposal series. Now I am going to share to you the points on how to make your project proposal standout from others. Take time to read the following, especially if you are planning to make one.

Continue Reading this Entry..
1. Write Clearly. Proposal reviewers usually have to read dozens of proposals in a shortperiod. They appreciate direct statements; they are exasperated bt cleverness and needlessrepitition. If you take five pages to say what can be said adquately in one, reviewers willremember your proposal for other than positive reasons.

2. Be Logical and Balanced. The proposal should flow and conclusions reached, not jumpedat. It means that the proposal shows internal consistency. In the 'rationale' the basis/needfor the project is explained and project components identified. The components and strategywill lead to the attainment of objectives through the project management set up and budgetoutlay. external factors have been taken into consideration. The length of sections may wellreflect your assessment of their importance.

3. Be specific. Specify numbers, sequences, outcomes as appropriate. Include time/flow charts,allowing for start-up and phase-out of your project.

4. Be thorough. Especially in detailing programme administration, managemet and monitoring.donors like to know that their money is going to conscientious and capable agencies.

5. Make propsal attractive to read. put in a lot of spaces, and make clear headings. Use theroman numerical System or ABC for identifying major sequence of your proposal. you might includepictures as well.

6. Don't philosophize. A proposal for the Food Secutiry and Nutrition Improvement Programme is noplace for a speech on hunger in the Third world. Know the difference between a proposal for fundingand a polemic.

7. Don't assume that reviewers know the problem or programme. Given the mix of possible readers,it makes ense to avoid unsupported assumptions, and to specify and document the existence of needsto be met and the capacity of your programme to meet them. the best way to handle jargon andspecialized acronyms, which arise among old hands with various programme details, is to eliminatethem- at least in proposals.

8. Don't include surprises. Examples are personnel who show up in an organizational chart or budget,but are not mentioned in the proposal narrative. Or charges in budget, with no prior referencesas to purpose or necessity. A good proposal answers questions, does not raise them.

9. End the proposal with an impact. Summarize the arguments for the project in one last paragraph.Formulate a catchy closing sentence, one that would convince the funding agency to consideryour proposal.

Source: Bakwit, Bubong, Binhi, Bayanihan: Project Development Monitopring and Evaluation inDisaster Situations by Citizen's Disaster Response Center