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.
Adding one thought to the excellent responses, writing the justifications
(by any name) might be an opportunity for capturing some statements of
values, which might not currently be seen as a requirement, but could
ultimately please the client.
On Tue, Jan 20, 2015 at 12:05 PM, Peter Neilson <neilson -at- windstream -dot- net>
> It depends, somewhat, on the purpose of the manual. If it is to sit on a
> shelf then the organization and perhaps even the content do not matter, as
> long as it fills the requirements. ("This book fills a much-needed gap in
> the literature.")
> If people are going to use it as a catechism, quoting the rule without
> understanding, the justification can be buried.
> If the readers will need to understand the justification before they have
> much hope of buying into the rule, the two should be together.
> As an example of this last kind of document, I remind myself of the NFPA's
> National Electrical Code or of "Dangerous Properties of Industrial
> Materials" by Irving Sax, both of which provide at least some degree of
> justification for their safety rules.
> The last time I wrote a P&P Manual it was a "useless" but required book,
> but in the course of developing it I discovered that the client had no
> procedure for retrieving door keys from terminated employees. The powers
> that beed quickly wrote one.
> On Tue, 20 Jan 2015 14:21:10 -0500, Cardimon, Craig <ccardimon -at- m-s-g -dot- com>
> Hello, Whirlers,
>> I am putting together a Policies & Procedures Manual, which is proceeding
>> I have been asked to include some justifications, which I will be given,
>> for said procedures.
>> My questions involve *how* to include them:
>> 1. Should I put the justification for the procedure directly after the
>> procedure? This is what I'm planning to do right now.
>> 2. Should I put all justifications in a separate section?
>> 3. Should I put all justifications in a separate document?
>> 4. If the justifications go into the same document, should the name of
>> the document be changed to Policies, Procedures, & Justifications? I'm
>> thinking no.
> Doc-To-Help: The Quickest Way to Author and Publish Online Help, Policy &
> Procedure Guides, eBooks, and more using Microsoft Word |
> You are currently subscribed to TECHWR-L as elisawyer -at- gmail -dot- com -dot-
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources and
> Looking for articles on Technical Communications? Head over to our online
> magazine at http://techwhirl.com
> Looking for the archived Techwr-l email discussions? Search our public
> email archives @ http://techwr-l.com/archives
Elisa Rood Sawyer
Technical and Creative Writer
"Apparently there is nothing that cannot happen today." Mark Twain
Doc-To-Help: The Quickest Way to Author and Publish Online Help, Policy & Procedure Guides, eBooks, and more using Microsoft Word | http://bit.ly/doctohelp2015