Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Post History

50%
+0 −0
Q&A What's the common practice for warranty chapters in technical manuals?

This is a decision you need to make in consultation with your company's legal advisors. The ability to defend against claims is affected by both what the warranty says and how prominent it is. A ...

posted 9y ago by Monica Cellio‭  ·  last activity 5y ago by System‭

Answer
#3: Attribution notice added by user avatar System‭ · 2019-12-08T04:11:07Z (almost 5 years ago)
Source: https://writers.stackexchange.com/a/16845
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision by (deleted user) · 2019-12-08T04:11:07Z (almost 5 years ago)
This is a decision you need to make in consultation with your company's legal advisors. The ability to defend against claims is affected by both _what_ the warranty says and _how prominent_ it is. A separate document or appendix that people are less likely to read might cause problems in this area. (Never mind that users are trained to skip past all that stuff at the front of manuals in consumer products...)

In my position I don't have to deal with warranties but I do have to deal with licensing terms, a similar case. We have restrictions on what you can do with our product based on what license you bought; that text is owned by product management and we technical writers don't alter even one word without discussion. The placement of that documentation in the doc set (ours is part of the bundle too) was worked out with product management. I would personally prefer that this be in a separate document (that product management can then maintain), but it's not my decision to make.

I suggest that you consult with your product manager if you have one or your team lead otherwise, to make sure you know all the requirements before you act.

#1: Imported from external source by user avatar System‭ · 2015-04-16T15:05:59Z (over 9 years ago)
Original score: 3