A study of forty current business/technical/professional writing textbooks suggests that little disciplinary agreement exists about what proposals are and how they differ from some kinds of reports; how the various types of proposals should be classified; and what structural features characterize the genre. Though many texts blur the distinction between proposals and internal recommendation reports, the two are never the same. The textbooks present a bewildering array of classification systems, often failing to distinguish between situation and function. A function-based system could divide all proposals into two categories-analytic (research proposals, R&D proposals, and consulting proposals) and service/product, with bids representing a special case. The lack of disciplinary agreement also makes it difficult for textbook users to internalize a generic structure that will serve for all proposal-writing tasks. Such a structure would include the following: situation, objectives, methods, qualifications, costs, and benefits. The major advantages of such a generic structure are its slots, which make it like a schema; its event sequence, which makes it like a script; and its ability to help writers and teachers understand the relationship among the macropropositions that exist explicitly or implicitly in all proposals.

A qualitative study using reading protocols suggests that when readers of informative documents understand conveyed information satisfactorily, they make direct confirmations and positive comprehension evaluations. When readers are uncertain about the accuracy of their understanding, they guess, make assumptions, or render the text's language into their own words. When readers' understanding is impaired, they ask for more clearly established links or relationships in the text, or they pinpoint some ambiguity or lack of resolution. When readers' understanding is unsatisfactory but not impaired, they request additional information. In addition, readers make evaluative suggestions that introduce, focus, emphasize, or reiterate their other comprehension-related responses. The response patterns isolated in this qualitative study indicate the need for specific quantitative research and suggest some directions for developing reader-based heuristics for informative writing.

Since technical writing is changing from a course for the scientific elite to one with a much broader base, the need to diagnose in technical writing classes is growing too. The right diagnostic tools can allow the instructor to set class goals more effectively, structure the course more efficiently, and discover and deal better with student expectations. The diagnostic we have designed, asking students to compose a memo which discusses their projected needs as aspiring technical writers, yields useful information about the stylistic strengths and weaknesses of the students. But more important, the diagnostic provides guidelines for choosing among the flexible units of study at the instructor's disposal, and also reveals student attitudes, preconceptions, and prejudices — data which aid the instructor in laying the proper groundwork in the early phases of the course.