RE:Communication Handbook vs Style Guide (with corrections)

Subject: RE:Communication Handbook vs Style Guide (with corrections)
From: David Handy <david -dot- handy -at- automsoft -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Tue, 27 May 2003 10:56:34 +0100

It sounds like your and your colleagues may have got some lines crossed when
discussing this. I could be wrong; anyway, that stuff happens sometimes...
At any rate, you'd probably agree that there's typically no advantage to
having two style guides in a workplace. If there's any overlap or
disagreement between them, then the risk of people writing inconsistent
documents in your company is increased, not decreased -- which surely
defeats the purpose of having a style guide in the first place.

It may be that the clerk (or whomever) has a lot emotionally invested in the
current comms guide, but so be it. (Who knows, they may have slaved over it
for years.) If the clerk's style guide is a good one, then let him/her deal
with their issues, if any, and say "thanks for the cool style guide"...

If the Society of Petroleum Engineers' style guide you found has good
chapters on, say, industry-specific jargon not covered in your current
guide, then you could recommend it to the clerk as a source for updating the
comms guide. But from where I'm standing, I don't think I'd expend much
energy competing with a colleague on this one.

As to whether there's a diff between a "style guide and a communcations
handbook" per se, I couldn't say without seeing inside the docs in question.
I wouldn't focus on the titles.




Robohelp X3, from eHelp, lets you quickly and easily create
professional Help systems for all your Windows and Web-based
applications, including Net.

Order RoboHelp X3 in May and receive a $100 mail-in rebate, PLUS
free RoboScreenCapture and WebHelp Merge Module.

Order RoboHelp today:

You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit for more resources and info.

Previous by Author: Re: Automating docs compilation in the software build process
Next by Author: RE: XP look-and-feel
Previous by Thread: RE: re system administrators and documentation
Next by Thread: Re: You're SUPPOSED to have good communication skills if you're a tech writer]

What this post helpful? Share it with friends and colleagues:

Sponsored Ads