NASA TM-105419

Technical Review Committee Guidelines

General Guidelines

1. Determine if the report is worthy of publication.
2. Ensure that the major contribution of the report is emphasized.
3. Ensure technical accuracy and clarity.
4. Work with the author to produce a quality product within a reasonable time.
5. Take the time to be thorough. Whenever possible, criticism should be accompanied by a suggested revision. Avoid generalities. If a statement, table, or figure is technically correct and not subject to misinterpretation, the committee should feel free to suggest but should not insist upon revisions.
6. Major and/or general comments on method of presentation, validity of argument, etc., should be prepared for the chairperson at least 3 days before the meeting.
7. If a report is to be reviewed by Publishing Services editors, prolonged discussions of grammatical errors and administrative policy and security should be avoided; these comments can be given to the author outside the meeting.
8. If any member of the committee is unable to reach an agreement with the author, the member should submit a memorandum to the author's division chief stating the objections.

Guidelines for Chairpersons

1. Talk with the author to become familiar with the purpose and scope of the report and the results of any pretechnical review committee or outline meetings.
2. Set the meeting day. (A maximum of 2 weeks for members to review the report is a reasonable goal.)
3. Determine prior to the meeting day that members are prepared by soliciting each for major and/or general comments and discuss possible major problem areas with the author before the meeting day.
4. Keep committee discussions focused on the major contributions of the report and concentrate committee time on problem areas.
5. Do not allow trivial or nontechnical discussions on questions of grammar, punctuation, etc.
6. Keep a record of changes that were agreed upon during the meeting for use in checking the revised draft.
7. Check revised draft resulting from committee discussions and sign the Publication Review and Approval Record (NASA C-22 form) if the technical content of the report is correct. If issues arise that cannot be resolved, note this on the Form C-22 without signing it, and submit it and the report with written details to the author's division chief.

Guidelines for Checkers

1. Check the accuracy of equations, calculations, and plots. If necessary, examine raw data and/or computer instructions and formulas used to obtain results.
2. Check tables and figures against text for accuracy of statements.
3. Ensure that figure keys are consistent throughout a set of figures.
4. Check all symbols used and comment on confusing redundant usage or incomplete listings. Verify the accuracy of all conversions from one unit system to another.
5. Determine that references are listed completely and are appropriate. (See the author for the references before contacting the Glenn Library.)

Guidelines for Advisors

1. To ensure clarity for the nonspecialist in the field of science covered by the report, freely question confusing passages.
2. Check the report for elemental completeness—an abstract, summary, introduction, etc.
3. Compare the summary of results or conclusions with the text to ensure that all results or concluding statements are explicitly stated in the text.
4. Compare the summary against the summary of results or the conclusions to ensure that all major points included in the summary are in the summary of results or the conclusions. (Make sure that these sections are complete in themselves and do not require the text for clarification).

Chapter 7—Review of Reports

• Chapter Descriptions
• Editorial help with your technical report
• FAQ—Publishing Your Technical Report at the NASA Glenn Research Center
• Reports Publication— GRC-P 3.7.4 (Center Procedure for Glenn's Business Management System)
• Hone your writing skills with our serial online articles— Word of the Week and Word Wizards

Scientific and Technical Information Program

From computers in the grc.nasa.gov domain, go to http://ltid.grc.nasa.gov to find out more about the Logistics and Technical Information Division. (Note that this is not meant to be an active link.)

Skip Navigational Links

[Privacy Policy and Important Notices]

Responsible NASA Official: Sue.E.Butts@nasa.gov, Glenn Technical Publications Manager
Web Curator: Caroline.A.Rist@nasa.gov (Wyle)

Last updated: 1/20/2009

This server now includes some full documents in portable document format (PDF). These files, can be viewed with Adobe® Acrobat® Reader®, which is incorporated in some Web browsers.

If Acrobat® Reader® is not included in your browser, you can download the current version of this software free and use it as a standalone program to view pdf files.