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.
Phyllis Palmer asked:
"How does one keep control over the revisions on this "ever
We use a version control system where the document is held
electronically, and only printed out when someone needs a copy. Our
document management system actually lets any user with the right
permissions access any version, read-only. There's also a note on the
inside front cover that includes the creation date, the last revised
date, and a field for date printed. Only one person handles revisions.
The danger, as Phyllis implies, is that you might get a steady trickle
of requests to revise this document, keeping one busy on a daily basis.
Nobody wants to keep tinkering with a document. Any documents that could
be considered "evergreen" generally don't need such frequent revision.
If that were the case, we'd probably set up a revision schedule, such as
monthly, quarterly. Anyone accessing the most recent copy would also
know it had been changed as of X date, and was valid up to that point.
In our situation, it's unlikely that anything truly important would have
been missed. If someone absolutely has to have the most current version,
then I get a phone call, and I let them know as soon as all the
revisions (minor) have been made.
Senior Technical Writer, InSystems Technologies Inc.
65 Allstate Parkway, Suite 100 Tel: (905) 513-1400 ext. 280
Markham, Ontario, Canada L3R 9X1 Fax: (905) 513-1419 mailto:bagnew -at- insystems -dot- com Visit us at: http://www.insystems.com