5 Simple Ways to Make Foundation Staff Feel Better About Your Proposal

Show that you've done your homework. Indicate that you have reviewed any material published by the foundation (printed or on the web) and that you are aware of what they have funded and want to fund. And then make sure your proposal fits or don't go there!
Answer all the questions. If there is a legitimate reason you don't respond to a specific question or request for information, acknowledge the request and state why you can't respond to it.
Make it easy to read. Is the font legible without a magnifying glass? Is there enough white space? Do you have a "heading hierarchy" that consistently shows which are main sections and which are subsections? If you bind the proposal, make sure it will lay flat as someone is reading it.
Make it easy to find information. Be sure to have page numbers on each page. Use headings that correspond to the information requested. If the proposal is long, use a Table of Contents. Use tabs for Appendices or Attachments and say in the body of the document, as appropriate, "See Tab 1."
Avoid jargon. Do not presume that all readers share your use of language. Unless you know that your academic peers will be reviewing your proposal, write it for the educated layperson. Do not use abbreviations or acronyms without spelling them out the first time.

Maintained by webmaster@wpi.edu
Last modified: April 30, 2007 14:30:10