Here's an example of a checklist I included with a a printout of a manual for review. Most people had not really reviewed the document before the meeting (even though I gave them plenty of time). So the meeting is really useful to force people to look at the book and answer your questions. I highlighted all my questions and wrote names next to the person who needed to answer them. Then I went through it and read the question, and if the person couldn't answer it right away, I marked it as a "meet later to answer" and set up a one-on-one. Often, another engineer would disagree with the answer in the meeting--so that was another bonus of a group meeting for a doc review. This document helped a co-worker who was having trouble with getting review comments back in a timely manner. She wrote: "I sure appreciate your wisdom and advice. You're the Tech Pubs ‘mechanic.’ "

Draft 2 of the Reporting Guide includes the following updates:

• New template format in book style
• Topics arranged according to new outline (some information was missing, and outline updated to accommodate this).
• Grammar edits
• Some new topics
• More questions from me, underlined and in brackets (some are just comments to myself, so ignore those that don’t seem like a specific question.)

Stuff still missing:

• Links to sections on where to find what you’re looking for (in Introduction)
• Magic.pm info (got lost in shuffle somehow)
• Operations topics—there’s the info you all supplied me, but no overall guide for ops to get started on an installation (especially important to Phase 2). I’d like to get an overview of the process in the Friday meeting, or at least make plans on how to get this info right away.
• Phase 2 info

• Review your relevant section for my questions, which are underlined and in brackets. Hopefully some of this info will be sorted out in the meeting Friday.
• Skim through the entire book to see if anything obvious is missing (that I haven’t already listed above).