Academic Writing: Scientific Reports
This handout describes an organizational structure commonly used to report experimental research in many scientific disciplines, the IMRAD format: Introduction, Methods, Results, And Discussion. (This format is usually not used in reports describing other kinds of research, such as field or case studies, in which headings are more likely to differ according to discipline.) Although the main headings are standard for many scientific fields, details may vary; check with your instructor, or, if submitting an article to a journal, refer to the instructions to authors.
University of Wisconsin (2003). Articles>Scientific Communication>Reports
Analyzing and Reporting Usability Data
The Just-In-Time (JIT) method of data analysis has the virtue of immediacy, rapid turn-around, and team involvement; however there are several disadvantages. First, this type of analysis is problem-focused, rather than goal-focused. Long lists of problems are generated, but there is no clear relation to specific usability goals. Second, developers may not be able to fix things immediately so the context of the problem may be lost when it is time to fix the problem. Third, the JIT analysis requires that the entire development team observe the testing sessions since problems may occur that are the responsibility of different developers.
Wilson, Chauncey E. Usability Interface (1997). Articles>Usability>Testing>Reports
Offers suggestions for creating excellent annual reports.
Worth, Carol. Intercom (2000). Articles>Writing>Reports
Annual Reports: A Literature Review (1989-2001)

Since the collapse of Enron Corporation in November 2001, annual reports and corporate financial disclosures have been the focus of government, corporate, and public attention. This article examines the literature written about annual reports between 1989 and 2001 to identify trends in research and determine areas of future study. Articles were categorized as related to SEC regulations and guidelines, summary annual reports, online annual reports, rhetorical analysis of annual reports, readability and accessibility of annual reports, methods of conveying negative information in annual reports, effective annual report writing, use and importance of annual reports, or use of annual reports in business writing classes. Post-Enron, it is likely that the number of articles in this area will dramatically increase over the next five to ten years.
Lord, Heather L. Journal of Technical Writing and Communication (2002). Articles>Business Communication>Financial>Reports
Applying the Elaboration Likelihood Model to Technical Recommendation Reports

Elaboration Likelihood Model (ELM) can help proposal writers identify effective document design techniques and parts of arguments that are critical to persuasion. In addition, ELM has implications for other types of technical communication, including recommendation or feasibility reports. While one would anticipate that decision-makers would be willing and able to evaluate critically all arguments presented in a recommendation report, ELM explains why this is rarely so. Therefore, technical communicators can profit by understanding and using the two routes to persuasion or attitude shift, the central and peripheral routes, explained by ELM.
Engle, Carol. STC Proceedings (1993). Articles>Business Communication>Reports>Rhetoric
Better Reports: How to Communicate the Results of Usability Testing 
You've spent several days setting up a usability test, recruiting the participants and running it. Then you've pored over the data. What next? If you are doing usability testing as part of user-centred design within a business setting, then there are many ways that you can communicate the results. This paper looks at reports and then considers presentation and observation as alternatives to reports.
Jarrett, Caroline. STC Proceedings (2004). Articles>Usability>Testing>Reports
Business Reports that Demand Attention 
Walinskas offers tips for improving business reports.
Walinskas, Karl. Intercom (2001). Articles>Writing>Reports
Cherryleaf Survey: Use of Single-Sourcing Solutions
During March and April 2003, Cherryleaf carried out an online survey into the current trends in technical communication. One of the questions we asked was: Do the people directly involved with user assistance development at your organization use a single sourcing authoring solution? Our findings are summarised in the article
Cherryleaf (2003). Articles>Content Management>Single Sourcing>Reports
Communicating the Results of Field Studies to Support Usable Design 
When you have completed the study, analyzed the data, and organized the interpretations and conclusions along with supporting data, you have to communicate the results to the people who need to know about them. How you communicate the results depends upon who the intended audience is, content needs of the audience, and the scope of the content. Increasing the odds of this information being used in the design process requires an understanding of the company's culture and the barriers limiting its use in the development process. Various strategies such as computer-slide presentations, reference notebooks, bound reports, and memos have been shown to be very effective in various circumstances.
Carlevato, Denise, Judith A. Ramey and Erin Leanne Schulz. STC Proceedings (1996). Articles>Usability>TC>Reports
Computer-Assisted Grading of Essays and Reports 
Someday computers may grade our students' essays and reports, but until then they can assist human graders in this onerous task. I wrote a program composed of three major sections: the first is a simple test editor for writing original comments; the second section consists of pre-written commentaries on common writing errors, principally in mechanics and organization; section three keeps track of bookkeeping. Questionnaire results show that students prefer this type of grading over traditional hand-written methods because it doesn't involve marks on their papers, and it produces more extensively detailed comments.
Jobst, Jack W. Computers and Composition (1984). Articles>Education>Reports>EPSS
Government auditors collect data and assess, via written reports, the operations of a government; however, little is known about what can affect and govern their representations of those operations. This analysis examines research studies about author bias and government audit manuals in order to understand how government auditors' neutrality is threatened. While bias may be an overt function of preferential or prejudicial thoughts, most sources of bias that influence auditors derive from less explicit sources including prior expectations, media coverage, nondiagnostic information, and other significantly less direct channels. To determine how government guidelines address this issue for their auditors, the principle audit manuals for Canada and the United States were reviewed for their references to bias, impartiality, and objectivity. Neither manual provides a significant amount of guidance to assist auditors in addressing the problems of bias in data collection, interpretation, and representation. If bias is to be reduced in audit reports, more must be done.
Palmer, Laura A. JBC (2008). Articles>Business Communication>Government>Reports
Developing Business Plans for High-tech Companies 
Illustrates how technical communicators can add value to business plan projects.
Petersen, Judy H. Intercom (2000). Articles>Business Communication>Reports
Businesses, non-profit organizations, government departments, and other groups produce a lot of proposals and reports. This article summarizes some features of reports and proposals that are not the same as books, news items, manuals, magazine articles, memos and many other documents.
Hollis Weber, Jean. Technical Editors Eyrie (2001). Articles>Editing>Proposals>Reports
English 3301: Principles of Professional and Report Writing 
The main objective of this class is to help you gain the skills needed to think through writing tasks, analyze the audience(s) involved, secure various types of resources, generate documents, and present those documents in an effective manner.
Garza, Susan Loudermilk. Texas A and M University (2007). Academic>Courses>Writing>Reports
Feminizing the Professional: The Government Reports of Flora Annie Steel

Despite being raised in a culture that denied her access to formal education and employment, Flora Annie Steel became an Inspector of Female Schools in the Punjab, India, in 1884. Her inspection reports for the occupying British government of India are the focus of this study, which examines texts within the context of British imperialism and late-nineteenth century report conventions. The study concludes 1) that cultural expectations for women in imperialism influenced Steel's response to the genre and 2) that the report genre may have been fluid within imperialism, crossing boundaries between professional and government writing pertaining today. The study suggests that, historically, we need to study these genres of writing from the perspective of economic and political expansion as genres of imperialism.
Sutcliffe, Rebecca J. Technical Communication Quarterly (1998). Articles>Writing>Government>Reports
During the mid-1580s Sir Walter Raleigh, operating under letters patent of Queen Elizabeth, supported two major voyages to establish an initial colony in Virginia. These two voyages produced three major commercial reports that evaluated the economic potential of the region for English colonists and merchants. The reports, written by Arthur Barlowe, Ralph Lane, and Thomas Hariot, represent the beginnings of American commercial communication in English. Using Kenneth Burke's idea of the four major tropes, this article develops the notion of the 'dominant figure'--a figure of speech that serves to focus a report's rhetorical power--to analyze the persuasive effects of these reports.
Moran, Michael G. Technical Communication Quarterly (2005). Articles>History>Reports>Tropes
Formal Usability Reports vs. Quick Findings
Formal reports are the most common way of documenting usability studies, but informal reports are faster to produce and are often a better choice.
Nielsen, Jakob. Alertbox (2005). Articles>Usability>Reports
Going On-Line: Bringing Technical Reports To The Desktop 
Information management is moving quickly toward archiving and retrieving documents electronically, so Oak Ridge National Laboratory (ORNL) is taking steps to help its research staff create electronic documents. Declining budgets frequently dictate that authors handle the technicalities of getting published as well as the scientific and technical information that they publish. To help the Laboratory benefit from being the leader in this area, ORNL’s Information Management Section formed a multidisciplinary team to develop, pilot, and implement a Webbased process to register and clear technical documents and to add the full text of these documents to the Laboratory’s Comprehensive Publications and Presentations Registry (CPPR). Making this happen required implementing policy changes to address the new performance measure, acquiring software needed for file conversion, developing Web guidance, and providing training and consulting for ORNL staff.
Dole, Jeanne, David Hamrin and Rebecca Lawson. OSTI. Articles>Content Management>Reports
This guide supplements work instruction PR2-W3 - Document Formatting. It gives a detailed outline of the recommended document formatting standards for reports. You should use the standard Word template, which has been configured to conform with these guidelines.
Tuffley, David. Griffith University (2000). Resources>Style Guides>Statistics>Reports
Guide to Effective Report Writing
The Guide to Effective Report Writing outlines a practical method for IT professionals to develop and maintain reports which address the needs of the reader and which are expressed in language easily understood by the reader.
Tuffley, David. Griffith University (2000). Resources>Style Guides>Reports
Hiding Humanity: Verbal and Visual Ethics in Accident Reports 
Located at the critical intersection of technology and humanity, technical communicators must always try to avoid human injury and promote sensitivity to the needs of human beings. The reporting of human injuries and fatalities in accident reports, however, often strips victims of their humanity and hides the tragic human consequences of technological failures from individuals trying to devise appropriate public policy, establish effective safety regulations, and modify or abolish dangerous industrial processes—government officials, company executives, labor representatives, community activists, and ordinary citizens. Technical communicators have the rhetorical ability, the requisite editorial and graphic skills, and the moral responsibility to bring humanity to the verbal and visual display of information.
Dragga, Sam and Daniel W. Voss. STC Proceedings (2003). Articles>Writing>Ethics>Reports
How to Write a Report Without Getting Lynched
You put forth your best effort to explain to the stupid sods exactly how and where they screwed up, then they have the temerity to not appreciate your fine efforts. Here's how to write a report that will cause change, instead of uproar.
Tognazzini, Bruce. Nielsen Norman Group (2001). Articles>Usability>Reports>Technical Writing
In October of 1997, the U.S. National Institute of Standards and Technology (NIST) initiated an effort to increase the visibility of software usability. Cooperating in the IUSR project are prominent suppliers of software and representatives from large consumer organizations.
Industry Usability Reporting and the Common Industry Format (ANSI-NCITS 354-2001)
The Common Industry Format (CIF) is a standard method for reporting usability test findings. The format is primarily for reporting results of formal usability tests in which quantitative measurements were collected and is particularly appropriate for summative/comparative testing. The CIF targets two audiences: usability professionals and stakeholders in an organization. Stakeholders can use the usability data to help make informed decisions concerning the release of software products or the procurement of such products. While the CIF is formally aimed for software products, it can be used for hardware usability as well.
Parush, Avi and Emile Morse. Usability Professionals Association (2003). Articles>Usability>Standards>Reports
Integrating Business Core Knowledge Through Upper Division Report Composition

The most ambitious project of many undergraduate business communication courses is the formal report. This assignment typically requires the use of many writing skills nurtured throughout the course. Skills such as proper style, tone, organization, flow, and mechanics are enhanced through the writing of memos and various types of letters (persuasive, bad news, etc.). While these skills are all evident in a report, it is a much different kind of document. This synthesis of writing skills can be complemented by the integration of fundamental business subject knowledge. Both skill sets can be concurrently developed through business simulation report assignments, particularly in upper division business communication courses. Such courses are often required in business programs where students have already completed courses in business law, management, basic business statistics, and computer applications. Choosing an appropriate topic and scope for such a report writing assignment can be challenging. As offered in Business Communication Quarterly, many good assignments lend themselves to adoption, each with varying degrees of flexibility, coverage of current topics, and data analysis requirements. The following formal report assignment provides the opportunity to present a wide enough scope to integrate several business disciplines.
Roach, Joy, Daniel Tracy and Kay Durden. Business Communication Quarterly (2007). Articles>Education>Business Communication>Reports
There are 17 readers currently online: 0 registered users and 17 guests. Register.

![]()
![]()


![]()
![]()
![]()