I use this template to write the technical reports I produce for the Center for Evaluation and Assessment here at UNLV). I really can't think of anything to add to it.

However, I will make a number of general recommendations based on my experience writing technical reports. [My rationale for each recommendation is in brackets].

1. Make the report thorough, yet as non-technical as possible. [Often, tech reports are passed along to legislative bodies or PTA groups that don't understand essential concepts such as reliability and validity other than in the most general way. Keep your report non-technical. When you must use technical terms, define them, or append a glossary].
2. Include only the most essential information. [Most stakeholders skim the report or never read it at all. The more concise the report, the more likely it will be to reach the intended audience. As the template suggests, keep conclusions and recommendations to a list of 2-4 claims. Rank order your conclusions and recommendations in order of importance ].
3. Use data that lay readers can understand, and if you must include technical data such as statistical tests, make sure you translate the results into plain English.
4. Provide a clear interpretation of what the numbers mean. [Lay readers are not used to interpreting numbers and graphs. Example what the data means in a simple fashion].
5. Don't over-generalize. [Some writers make unfounded claims based on their results. Harry Walcott (1994) writes about three levels of reporting: Description, Analysis, and Interpretation. All reports should describe. All reports should provide simple, concise analysis of data that reduces larger chunks of data into meaningful results. Not all reports need to interpret. Be careful about the extent to which you interpret results subjectively. If you do interpret, provide several different potential interpretations and encourage the stakeholder to weigh each option].
   

- Gregg Schraw