Re: ISO Document Control

Subject: Re: ISO Document Control
From: "Peter Neilson" <neilson -at- windstream -dot- net>
To: techwr-l -at- lists -dot- techwr-l -dot- com
Date: Fri, 28 Oct 2011 11:31:53 -0400

Here's a report from my wife who maintained this stuff at Gillette's QC department: To avoid all computer problems, QC kept printed copies of all the FDA-required manuals, including all the signed revision sheets, under lock and key. If there was ever any question, THAT was the authoritative version.

That method avoids problems with partial updates, multiple but contradictory versions, missing signatures, untestable authentication, and so forth.

For maintenance of the printed manuals in the various laboratories, the QC manager (my wife) took the replacement pages into each lab, had the lab manager sign for the new copy, replaced the pages, took the old pages and shredded them. That was >copies< that got shredded. The originals of the old pages were archived.

A paper-intensive system such as this just cries out for computerization, doesn't it?

Possibly. But everything Gene says is on target. Modestly endowed (or home-grown) documentation management software will get you in trouble later. In the FDA environment the manuals are legal documents, and their loss leaves the QC manager open for legal action. "Would you want," says my wife, "your home's deed stored only on some computer somewhere?"

There are two styles of audits. (1) A genuine auditor actually inspects the details of your operation, and calls out the aspects that need correction. Argument with the auditor is futile. (2) A lazy auditor looks to see that the facility actually exists and that there are computers, and maybe books that look like manuals on the shelf. He gets taken out to lunch. Argument with the auditor is totally unnecessary.

You can hope for style 2, but creative paranoia will leave you prepared for style 1.

On Fri, 28 Oct 2011 10:38:13 -0400, Gene Kim-Eng <techwr -at- genek -dot- com> wrote:

You don't need to automate ANY of the functions of a document control system. Restricted access and past revision recovery can be accomplished with a locking file cabinet full of printouts. But if you're going to go to the trouble and expense of implementing a tool, you want one that provides all the features even if you don't use them all initially, because if you ever have to pass other audits, such as one for a federal CFR, the last thing you want to have to do is go out shopping for another document control tool because the one you already implemented doesn't provide the ability to turn on additional controls.

Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days.

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com
or visit

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Please move off-topic discussions to the Chat list, at:


ISO Document Control: From: Sally Derrick
Re: ISO Document Control: From: Scott Turner
Re: ISO Document Control: From: Keith Hood
Re: ISO Document Control: From: Sally Derrick
Re: ISO Document Control: From: Gene Kim-Eng

Previous by Author: (Screed) - Re: STC certification: what's in it for tech writers?
Next by Author: Re: ISO Document Control
Previous by Thread: Re: ISO Document Control
Next by Thread: Re: ISO Document Control

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

Sponsored Ads