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.
On Mon, Sep 29, 2008 at 8:40 AM, Technical Writer <tekwrytr -at- hotmail -dot- com> wrote:
>
> Other than implied warranty of fitness, and similar "generic good will" considerations, is anyone aware of specific legislation that mandates accuracy in documentation under penalty of law? For example, a mandate that would require a software product manual or other similar document to be "absolutely perfect"--meaning, if there was an error (not threatening to the life, limb, or well-being of the user), is there some law that would require a company to essentially recall and replace the entire manual?
>
> Despite having worked in the field as an independent contractor for a number of years, and taken various business classes at the local university on legal and regulatory issues, I have never heard of such. If anyone has, I would really appreciate it.
>
> The issue is not the software or product itself, but rather the documentation for that product. The way it was stated to me(by a technical writer for a software company), was that every manual, and presumably every piece of documentation generated, was a "legally binding contract," and as such, had zero tolerance for errors of any type.
>
A company I worked for put in their contracts that the software was
warranted to work "as documented". This did not lead to them requiring
that the documentation be perfect. Rather, it led to omitting things
from the documentation if there was any possibility that the software
might now work that way (e.g., last-minute features), while still
producing plausibly complete docs. I think they also took the view
that a discrepancy between the docs and the software would simply be
considered a software defect, to be remedied under the maintenance
section of the contract. The software in question was potentially
business-critical but not life-critical.
That clause of the contracts was never tested while I was there.
ComponentOne Doc-To-Help gives you everything you need to author and
publish quality Help, Web, and print content. Perfect for technical
authors, developers, and policy writers. Download a FREE trial. http://www.componentone.com/DocToHelp/
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
