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.
> We definitely have a QA department. Hoo boy.
> But they verify that the product meets the specified requirements.
Like regulatory compliance codes? ;-)
> I've been arguing that the list of required statements should be part of the Marketing Requirements Document, which would trickle down through the engineering response document (the Statement of Work), and eventually be on the checklist for QA.
> And if the Product Line Manager (who writes the MRD) doesn't know which statements are needed, then s/he should get that info from the bod in charge of regulatory and compliance stuff.
Ayup.
> One problem is that "compliance" is a big umbrella. We have people whose full-time jobs are to process compliance paperwork for export permits. Others deal with industry-specific evaluations (against NIST standards for example), but those do not require customer-document statements and disclaimers. The hardware guys know which labs they've sent samples for electrical and RF compliance testing, and which other labs for environmental testing (shock, vibration, temperature, etc.). Common-Criteria evaluators wander through here for a week every other year, for yet another kind of compliance. I haven't seen ISO auditors, but I'm sure it won't be long.
> But off-hand, I'm not aware of a God of Regulatory Compliance that knows all.
Sounds like an opportunity to open a requisition for hire.
> Did you know that some folks think you must have a Lithium Battery warning on your product and in your docs if the product contains a Lithium-ion battery? But other folks think that's necessary ONLY if the Lithium battery is replaceable or at least accessible.
Hire and consult an expert. Hopefully they're the same person. ;-)
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. http://www.doctohelp.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
