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.
In writing proposals, is it a good idea to attach sample documents, or
sample document templates, to give the customer a feel for the documents
to be delivered?
For example, for an implementation effort, would a proposal that
contained a sample Operations Guide, as an attachment, impress the
customer more than a proposal without the sample Guide? Assuming it's a
produced well. This Operations Guide obviously would not contain all
operational instructions and information (since software customizations
have yet to be implemented, since even requirements have not been
defined, since details about the transitioned business processes have
not been realized, etc.--essentially, since the entire project has yet
to happen) but this sample would present the framework for the final
version.
--Christopher Shade in Denver, who's not sure that the last sentence in
the last paragraph, with that parenthetical interruption, makes any
sense.
