Transcription of A guide to technical report writing
{{id}} {{{paragraph}}}
A guide to technicalreport writingA guide to technical report writing Contents02 Contents1. What makes a good technical report ? 32. Objectives 4 Who are you producing the report for? 43. Format 5 Appendices 5 Sections and subsections 5 References 64.
– What level of formality is appropriate? (e.g. a short emailed report to a colleague will be less formal than a report for a managing director of another company) Reports are often written for multiple readers, for example, technical and financial managers. Writing two separate reports would be time-consuming and ...
Domain:
Source:
Link to this page:
Please notify us if you found a problem with this document:
{{id}} {{{paragraph}}}