Discusses a proposal's executive summary: its purpose, how long it should be, what should be in it, when it should be started, who should write it, and how it should be reviewed. (SR)

Makes suggestions for editing technical proposals. Discusses the marketeers, the hierarchy of hype, how to save days, managing story boards, expediting a laborious process, teaching engineers to write, writing incrementally, the art group, and the editing task. Argues that the best proposals come from starting to write early. (SR)

Discusses how to develop a proposal in response to a Request for Proposals (RFP). Provides a list of things needed to write a proposal, a proposal outline, a general proposal checklist, and a proposal writing checklist. (DR)

With regard to proposal and report writing in particular, the Self-Monitoring Negative Checklist (SMNC) offers the potential of finished products that more completely realize the writer's objectives and serve the reader's or user's needs. Presented as a series of 31 warnings of what can go wrong in a proposal, the SMNC represents a mode of…

Describes a technical proposal writing assignment modeled after the conditions in industry. Provides a paradigm of government project proposals and then outlines the stages of the assignment that allow student to rework and revise, thereby discouraging students from writing formulaic and superficial proposals. (SRT)

Discusses difficulties technical writers and readers have concerning proposals that define problems and suggest innovation. Suggests that when writers recognize both their own and readers' assumptions about such problems, they can adopt techniques to gain reader concurrence. (KEH)

Intended for use by practitioners in the private and public sectors as well as by students, this book emphasizes writing techniques for internal and external proposals. The book stresses the competitive nature of proposals, the need to improve writing skills, the need for audience analysis, and the need to understand how presentation affects…

Assists writers in getting started, organizing material effectively, and producing high quality technical documents. Uses a nine-block information matrix to provide a system of checks to evaluate the paper. Indicates that each section of the matrix can be written separately and then combined into a coherent document. (Author/MVL)