Reports

1. Reports An General Introduction

2. Reports are Important Because: • They identify a problem and reason for writing. • They give a more in-depth look at an issue – explore an organization’s needs and goals. • They are grounded in evidence to support their conclusions.

3. Reports • Are often written big picture to little picture with support for each claim. • Assume that readers are skeptical and in hurry. Reports are designed in ways that help this busy audience. • Have their BLUF in both the executive summary and introduction.

4. Parts of a typical Report • Cover sheet • Table of contents • Executive summary (written last and highlights the main ideas) • Body text including visuals, research conducted, interpretation of research, and conclusions about what research means to the problem. • References • Appendices

5. Feasibility Reports • Done after possible solution(s) have been identified. • Is designed to determine whether or not a particular course of action is desireable. • Determines what can be done based upon limits of context (ODU in our case). • Asks should this be done? Is it reasonable? - Weigh the pros and cons.

6. Feasibility Structure • Cover • TOC • Ex. Summary. • Introduction • Organization problem • This report’s scope and approach • Recommendation • Discussion of Each Component that Comprises Feasibility • Background on criteria • Application of each criterion to the proposed solution • Rationale for decision about feasibility • Conclusion and Recommendations • [References] • [Supporting Documents]