1988
DOI: 10.3133/ofr88320
|View full text |Cite
|
Sign up to set email alerts
|

Report Planning and Review Guide

Abstract: Readability-Is it written for the intended audience, and with correct grammar, syntax, and a minimum of scientific jargon? Are illustrations and tables legible and readily understandable? Title-Is it explicit and does it reflect the objectives of the report? Generally the title should not exceed 12 words and, if appropriate, should give the project location and study period.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

1992
1992
1992
1992

Publication Types

Select...
1

Relationship

0
1

Authors

Journals

citations
Cited by 1 publication
(1 citation statement)
references
References 1 publication
0
1
0
Order By: Relevance
“…The QA objectives assist the project chief to reach conclusions relevant to the data-quality objectives. Moore andothers (1988,1990) suggest that a topical outline for each planned report be prepared during the first month of a project, and an annotated report outline be prepared during the first 3 to 4 months, assuming a 3-year project. Moore and others also present a guideline for preparing a report work plan.…”
Section: Data-quality Objectivesmentioning
confidence: 99%
“…The QA objectives assist the project chief to reach conclusions relevant to the data-quality objectives. Moore andothers (1988,1990) suggest that a topical outline for each planned report be prepared during the first month of a project, and an annotated report outline be prepared during the first 3 to 4 months, assuming a 3-year project. Moore and others also present a guideline for preparing a report work plan.…”
Section: Data-quality Objectivesmentioning
confidence: 99%