ETEC 579

Things to keep in mind when preparing a Tech Plan or Grant Proposal…

  • The document should have a positive and professional tone. [B]
  • Use correct spelling and grammar. Always write in 3rd person in any professional writing. [B]
  • Properly cite references. APA 5 style is appropriate. [B]
  • Exact dollar values are essential in a proposal, but less critical in tech plan. [B]
  • We sure could use some extra money to finance this operation. Let’s get us one o’ them thar grants. Ya’ont to? Now you may be the subject of them redneck jokes but lets just keep that ‘tween you and me and ol' Capella here. You gotta sound professional in your writing and avoid using slang and regional verbiage. Don’t let your "hick" shine through if ya know whut ah mean? [B]
  • Don’t use a tech plan or grant proposal as a vehicle to simply voice complaints about a current lack of technology. Be honest about needs, but don’t "whine" about them. [GP]
  • Less is more. Don’t add un-necessary "fluff." Proposal evaluators want to know what’s important. If you bore them with irrelevant information, it is almost guaranteed to get your proposal tossed in the trash. [GP]
  • You are trying to get the funding agency to make an investment in you and your organization. You must convey that you will act responsibly and professionally in administering any monies awarded. [GP]
  • First impressions are critical. Many funding decisions are made within the first paragraph of the proposal. If you want your proposal to be read and seriously considered, you must capture the interest of the evaluator in the Executive Summary. Most evaluators will stop reading at this point if they don’t see evidence of a well thought-out, worthwhile endeavor. [GP]
  • Never, ever, make negative statements regarding previously received grants. This will send up red flags as an indication that you may later speak negatively about the new funding agency. [GP]
  • Don’t open a can of worms! Don’t bring up issues that are indicative of more serious internal problems. [GP]
  • Proposals are generally written to provide at least a partial solution to an identifiable need. The need you address must be able to be backed by quantifiable evidence. There must be qualified proof of need. Ways to build your case are with surveys, test scores, formal evaluations, and other data gathered via valid research methodologies.
  • Supporting documentation may be included in an appendix to the document. (Data may be hypothetical in this class project, but if you submit a proposal for real, you better have ALL of your data together and available for inspection if requested by the funding agency.) [GP]
  • The length of the pre-proposal will be approximately 5-7 pages to sufficiently address the required elements. A more comprehensive proposal may be slightly longer, but remember, don’t overwrite. It is highly unlikely that these elements could be adequately addressed in fewer than 5 pages (double-spaced, 10pt font). [GP]
    •

    [TP] = Tech Plan
    [GP] = Grant Proposal
    [B] = Both TP & GP