TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Visuals within a proposal From:Tim Altom <taltom -at- IQUEST -dot- NET> Date:Thu, 26 Oct 1995 11:53:00 EST
:I am in the process of collecting data for a project proposal for one
:of my graduate classes. The visuals I want to use vary in size, but I have
:at least four I want to submit with the proposal. Would it be easier for the
:readers to include the visuals with its appropriate text? The other option I
:am considering is to include them all together in an appendix section.
:Any suggestions would be helpful.
We approach the proposal with the same guidelines we use for other
documents. If a graphic bears directly on a point in the text, a point that
can't be readily appreciated or understood without the graphic, then we put
the graphic on the facing page (usually following page) or in-line. This
would be for things like samples of graphics we would use, or even photos of
our key people.
On the other hand, supporting visuals go into an appendix, where the reader
can get them if he wants them. This is for project plans and Gantt charts,
In short, we depend on our understandings of what the reader will need to
know, as opposed to those things that would be merely handy to know.
Simply Written, Inc.
Technical Documentation and Training