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.
Proofreading Everything Under the Sun-- A TWs responsibility?-- P lease Help!
Subject:Proofreading Everything Under the Sun-- A TWs responsibility?-- P lease Help! From:Gina Hertel <Ghertel -at- ALPHA88 -dot- COM> Date:Fri, 22 May 1998 09:49:49 -0400
Our company does consulting work for migrations, upgrades, installs, and the
like. Some people think that every server configuration, site survey,
conceptual, logical, and functional design, disaster recovery procedure,
etc. etc. etc. that is written by a consultant should be "proofread" by a
technical writer before delivery to the client (even if the TW isn't listed
as a resource on the project). What do you think? Do other companies do
this? Then they want the TW to archive the documentation too.
I see the following problems:
1.) We have 100 consultants and 2 writers. Can you say "bottleneck"?
2.) If the TW isn't listed as a resource, the client isn't paying for
his/her services, which devalues them.
3.) TWs are also responsible for Proposals, Courseware, the Corporate
Intranet, Any Internal Communication (from the EE handbook to Creating Forms
for Sales), User Guides, Presentations, Production, and any and all dirty
work. Where are the priorities? How much more can we throw into the mix?
4.) Who wants to do nothing all day but be a wordsmith, cleaning up after
consultants and filing their papers electronically?