Documentation review

Subject: Documentation review
From: "Lucero, Peggy" <plucero -at- atsva -dot- com>
To: <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Tue, 27 Dec 2005 12:09:42 -0500

Hoping someone can shed light on how to seemingly work a miracle!!
I have 10 technical documents, varying in length from 60 to 600 pages.
They need to be reviewed, starting 2/1/06 and ending in mid April.
They need to go to:
1. Peer review
2. Client review

It seems a consensus that 5 days are ok to allow as the time period for
each document to be reviewed in, though for the one really long one
(almost 600 pages), I've recommended a group review meeting, that I'm
suggesting will take 4-5 hrs, but, I actually have no idea how long it
is likely to take.
I've been advised by boss that it is expected that no two documents
overlap. In other words, I'm only to give documents one at a time to a
reviewer because if they get more than one at a time it is believed
they'll get 'overloaded' and never get anything reviewed and returned to
I've worked and worked on writing the documentation review schedule.
Given the number of documents to be reviewed and the short time frame to
get them through the reviewing process, I can't concoct a schedule that
does not contain any overlap.
Any suggestions/recommendations are most appreciated.

Peggy Lucero
McLean, VA


Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today!

Doc-To-Help 2005 now has RoboHelp Converter and HTML Source: Author
content and configure Help in MS Word or any HTML editor. No
proprietary editor! *August release.

You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit for more resources and info.


Previous by Author: Best Practice for reviewing documents
Next by Author: Help Authoring Tools
Previous by Thread: RE: Text to xml: Encoding issues
Next by Thread: Re: Documentation review

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

Sponsored Ads

Sponsored Ads