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: Back cover of technical documents From:"Banttari, Ananda" <ABanttari -at- SDSI -dot- COM> Date:Fri, 26 Jun 1998 17:55:20 -0500
Jon Herrera asks about being in charge of the back
covers of documentation books....
This is something that can be either easy or a real pain,
depending on your company. My suggestions:
1. Find out exactly who in Sales and Legal are responsible
for up-to-date information. Ask them to add you to their
contact list for change-of-information notices.
2. Whenever you print the cover, make sure you get
"sign-off" of a proof from the Sales and Legal people.
Go to them with a proof (not a copy of the proof, but the
real thing), and a sign-off list that you have created. The
sign-off list should include each Sales and Legal person
involved, you, your manager, and possibly others (like
Marketing, perhaps, for the "short description of the
company). Each signator should date their sign-off.
Let them all know that any one person can veto the
proof with sufficient cause.
My reasons:
1. You have a better chance of preventing problems.
2. There might be someone in Sales or Legal who
feels like some of their power or control is being
threatened. Giving them veto power reassures them.
3. If anything does go wrong, you pull out your sign-
off sheet. "All of these people reviewed it, and they
didn't see anything wrong, either."
Our corporate HQ just moved; my observations are
based on dealing with move-related issues, which include
most of the ones Jon was talking about. (If anyone
reading this is faced with a corp. HQ move, email me
off-list and I'll tell you my war stories ;-] and how to prevent
annoying -- and sometimes costly! -- issues.)