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.
Susan, this is a golden opportunity. If your company doesn't have a
written definition for a QA protocol, then *you* can write it, based on
your own good sense and organization. Get your written definition to the
manager, get it signed, and you'll be the envy of all of us.
> -----Original Message-----
> From: Susan Hogarth
> Sent: Monday, February 12, 2007 12:25 PM
> To: TECHWR-L
> Subject: Re: QA plan help?
> On 2/12/07, Dan Goldstein <DGoldstein -at- riverainmedical -dot- com> wrote:
> > ... So to return to Susan's question: The difference
> > between a QA plan and a protocol is defined within her
> > company's own quality system. The rest of us can guess
> > till the cows come home, but only someone within
> > Susan's company could know the correct answer for sure.
> Right. The thing is... we don't have any distinction. We have QAs but
> no protocols. I am trying to make a case that the protocol comes
> FIRST, THEN the QA plan.
This message contains confidential information intended only for the use of the addressee(s). If you are not the addressee, or the person responsible for delivering it to the addressee, you are hereby notified that reading, disseminating, distributing, copying, electronic storing or the taking of any action in reliance on the contents of this message is strictly prohibited. If you have received this message by mistake, please notify us, by replying to the sender, and delete the original message immediately thereafter. Thank you.
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include single source authoring, team authoring,
Web-based technology, and PDF output. http://www.DocToHelp.com/TechwrlList
Now shipping: Help & Manual 4 with RoboHelp(r) import! New editor,
full Unicode support. Create help files, web-based help and PDF in up
to 106 languages with Help & Manual: http://www.helpandmanual.com
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-