Formal Reports 1

10,600 views
9,887 views

Published on

Published in: Business, Technology
1 Comment
1 Like
Statistics
Notes
  • thank you so much for this presentation.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
10,600
On SlideShare
0
From Embeds
0
Number of Embeds
530
Actions
Shares
0
Downloads
232
Comments
1
Likes
1
Embeds 0
No embeds

No notes for slide

Formal Reports 1

  1. 1. Writing Formal Reports in Business<br />Xakema Henderson<br />
  2. 2. What is a formal business report?<br />A formal report is a written account of a major project –something you did, discovered, or organized.<br />The audience may be managers, co-workers, or someone from outside your organization. <br />Formality, accuracy, and ethical standards should be maintained because reports can be used in court cases and other situations.<br />
  3. 3. Prepwork<br />
  4. 4. Get it together<br />Writers of formal business reports do have to cite sources, so they must devise a system to keep track of reading, interviews, emails, conversations, visuals—anything that contributed to the final product should be credited.<br />
  5. 5. Format<br />Often a business will prescibe a format for publications such as formal reports. <br />Usually, there are 3 main parts:<br />Front Matter<br />Body<br />Back Matter<br />Use headings to help readers navigate.<br />
  6. 6. Front Matter<br />Must include:<br />Cover<br />Title page<br />Abstract<br />Table of contents<br />If necessary…<br /><ul><li>List of figures
  7. 7. List of tables
  8. 8. Foreword
  9. 9. Preface
  10. 10. List of abbreviations & symbols</li></li></ul><li>Abstract<br /><ul><li>Addressed to others researching the same topic; key words help researchers find it in databases
  11. 11. Highlights major points so that readers can decide if they want to read the entire report
  12. 12. About 250 words in length
  13. 13. The following four can be used as a road map for composition:</li></ul>Purpose<br />Scope/Methods<br />Results<br />Recommendations<br />
  14. 14. Body Sections<br />Executive summary (not always included)<br />Introduction<br />Procedures (Methods)<br />Results or Discussion<br />Conclusions <br />Recommendations<br />Works Cited<br />
  15. 15. Executive Summary<br />An executive summary is like abstract, but longer, up to 2 pages. It provides information in abbreviated form for busy decision-makers. <br />It highlights a project’s benefits or sells the project.<br />It should cover costs and benefits or anything decision makers must know.<br />It can exclude the details of methods, results, problems encountered but solved, etc.<br />
  16. 16. Introduction<br />Tells the reader about the project or study<br />Includes the purpose<br />Includes the scope (how broad was the project?)<br />May repeat some of what was previously stated in the abstract or executive summary<br />
  17. 17. Procedures<br />Lets readers know how data was obtained or what procedures led to a conclusion<br /><ul><li>The study may have required only a review of existing literature, which should be outlined. If it required surveys, interviews, or product testing, this section should explain how research was set up so others can evaluate the quality of the data.</li></li></ul><li> Results or Discussion<br />Narrates what was found <br />Connects the data to the purpose and findings<br />Includes visuals where efficient or effective to show large amounts of data (Data not related to the conclusions goes in an appendix.)<br />Includes limitations, need for further research, problems<br />
  18. 18. Conclusions<br />Conclusions are the implications drawn from the main ideas. <br /><ul><li>What is the significance of the project or study?
  19. 19. What are the recommendations, if any?</li></ul>What course of action needs to be taken?<br />What benefits come from this project?<br />
  20. 20. Bibliography or References<br />List of ALL sources that were consulted and/or cited (If the writer looked at them and got ideas or background from them, they were consulted.)<br />Documentation style depends on the field<br />
  21. 21. ME, ME , ME!!!<br />When the report is a written account of a project performed by the author first person (I) can be used<br />Must be objective and procedural<br />No anecdotes<br />No subjective implications<br />i.e. “I think”<br />
  22. 22. References<br />Alred, Gerald J., Brusaw, Charles T., Oliu, Walter E. Handbook of Technical Writing. Boston: Bedford, 1996.<br />Markel, Mike. Technical Communication. Boston: Bedford, 2001.<br />

×