RE: Best Practices in Indicating Versions

Subject: RE: Best Practices in Indicating Versions
From: "Lippincott, Rick" <Rick -dot- Lippincott -at- flir -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Thu, 24 Jul 2003 09:12:40 -0400

>So, anyone have research on best practices on indicating changed
>documents? In the old old days, documentation departments used to issue
>docs with multidigit version numbers, change bars, and change pages.

And some still do. My last job, the customers would get a complete new
doc set revision on CD, three times a year. This did away with the old
practice of inserting change pages, but the CD still makes use of change
bars for new or changed material. The docs also include in each section
a summary of what has changed in that section.

I haven't been at this job long enough to issue a changed document, so
we don't yet know what we do here. Given our customer expectations,
however, it will likely be change bars.

--Rick Lippincott
FLIR Systems
Billerica, MA


sourcing tool for FrameMaker that lets you easily publish your content
online. No macro language required!

Mercer University's online MS Program in Technical Communication Management:
Preparing leaders of tomorrow's technical communication organizations today.
See or write George Hayhoe at hayhoe_g -at- mercer -dot- edu -dot-

You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit for more resources and info.

Previous by Author: RE: Partnumbers
Next by Author: RE: Best Practices in Indicating Versions
Previous by Thread: Re: Best Practices in Indicating Versions
Next by Thread: Re: Best Practices in Indicating Versions

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

Sponsored Ads