technical writing

Read the working drafts of the Analytical Reports posted by your group members in the File Exchange area of your Group Page, then use this forum to post your reader response to each draft.

Be sure to address the writer by first name, then write a response of at least 250 words to each writer. Give them your response as a reader of the report: where does the writer communicate clearly? Where do you get confused or lost? Where would you like to see more details or supporting information? Is there any information presented that needs more clarification or definition?

Notice that these questions are not about editing and grammar, but instead give the writer insight into how the report is being understood. This is the kind of information that benefits a writer when in the working/revising stage of writing.

I have attached 3 files.

  • 2 documents of each writer

  • The instruction of the exercise

  • Below there is the guideline of the analytical report



Checklist: Analytical Reports Checklist Analytical Reports

Use the following Checklist when writing a formal analytic report.

Content
  • Does the report address a clearly identified problem or purpose? (See “Clearly Identified Problem or Purpose” in this chapter.)

  • Are the report’s length and detail appropriate for the subject? (See “Adequate but Not Excessive Data” in this chapter.)

  • Is there enough information for readers to make an informed decision? (See “Accurate and Balanced Data” in this chapter.)

  • Are all data fully interpreted? (See “Fully Interpreted Data” in this chapter.)

  • Is the information accurate, unbiased, and complete? (See “Subordination of Personal Bias” in this chapter.)

  • Are visuals used whenever possible to aid communication? (See “Appropriate Visuals” in this chapter.)

  • Are the conclusions logically derived from accurate interpretation? (See “Valid Conclusions and Recommdations” in this chapter.)

  • Do the recommendations constitute an appropriate and reasonable response to the question or problem? (See “Valid Conclusions and Recommdations” in this chapter.)

  • Are all limitations of the analysis clearly acknowledged? (See “Valid Conclusions and Recommdations” in this chapter.)

  • Are all needed front and end matter supplements included? (See “Front Matter and End Matter Supplements” in this chapter.)

  • Is each source and contribution properly cited? (See “End Matter” in this chapter.)

Arrangement
  • Is there a distinct introduction, body, and conclusion? (See “Structuring a Formal Report” in this chapter.)

  • Does the introduction provide sufficient orientation to the issue or problem? (See “Introduction” in this chapter.)

  • Does the body section present a clear picture of the evidence and reasoning? (See “Body” in this chapter.)

  • Does the conclusion answer the question that originally sparked the analysis? (See “Conclusion” in this chapter.)

  • Are there clear transitions between related ideas? (See ​Appendix​ ​B​, “Transitions.”)

Style and Page Design
  • Is the level of technicality appropriate for the primary audience? (See ​Chapter 2, “Assess the Audience’s Technical Background.​”)

  • Are headings informative and adequate? (See Chapter 13, “Using Headings for Access and Orientation.”)

  • Is the writing clear, concise, and fluent? (See ​Chapter 11, “Editing for Clarity,” “Editing for Conciseness,” and “Editing for Fluency.”)​

  • Is the language precise, and informative? (See Chapter 11, “Finding the Exact Words.”)

  • Is the report grammatical? (See Appendix B, “Grammar.”)

  • Is the page design inviting and accessible? (See Chapter 13, “Page Design in Print and Digital Workplace Documents.”)

  • Will the report be delivered in digital format, in print, or both? (See Chapter 13, “Page Design in Print and Digital Workplace Documents.”)