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.
I have been given the task of helping set document standards for documents
*other than* documentation that are produced by our company (right now only
user manuals are considered "documentation" here, and as such are the only
docs that have any standards whatsoever.)
What I am looking for is information about what sorts of standards other
companies have in place. We need to start at ground zero here: right now,
we have "official" docs that have no date, no author, no revision number,
etc. I need to be able to outline requirements for all kinds of docs, from
letters to customers to product specifications. (BTW, if you have any hints
about how to get others to buy off and actually *use* the standards, once
set, that'd be great ...)
We have a style guide that we tech writers use--do other companies routinely
require others in the company to follow the same guidelines? What about
revision history on things like product specifications--shouldn't there be a
history summary at the end of each new release of a document that says how
this version differs from the previous?