Skip to content

Instantly share code, notes, and snippets.

@MaXFalstein

MaXFalstein/Technical-Report-Writing.html

Last active September 4, 2016 11:30
Show Gist options
  • Save MaXFalstein/3b5763f1e2e21dea5a9f785006725249 to your computer and use it in GitHub Desktop.
Save MaXFalstein/3b5763f1e2e21dea5a9f785006725249 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
Technical-Report-Writing.html
<head>
<title>MaX Saxe Design Inc. Guide to Technical Report Writing</title>
<!-- Latest compiled and minified CSS -->
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css" integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7" crossorigin="anonymous">
<!-- Optional theme -->
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap-theme.min.css" integrity="sha384-fLW2N01lMqjakBkx3l/M9EahuwpSfeNvV63J5ezn3uZzapT0u7EYsXMjQV+0En5r" crossorigin="anonymous">
<!-- Latest compiled and minified JavaScript -->
<script async="" src="https://www.google-analytics.com/analytics.js"></script><script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/js/bootstrap.min.js" integrity="sha384-0mSbJDEHialfmuBBQP6A4Qrprq5OVfW37PRR3j5ELqxss1yVqOtnepnHVP9aJ7xS" crossorigin="anonymous"></script>
<!-- jQuery -->
<script src="https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js"></script>
</head>
<body class="container">
<header id="page">
<h1>Guide to Technical Report Writing</h1>
</header>
<article>
<section id="table-of-contents">
<header>
<h3>Table of contents<strong><a href="#1"></a></strong></h3>
</header>
<article>
<p><strong><a href="#1">1 Introduction</a></strong></p>
<p><strong><a href="#2">2 Structure</a></strong></p>
<p><strong><a href="#3">3 Presentation</a></strong></p>
<p><strong><a href="#4">4 Planning the report</a></strong></p>
<p><strong><a href="#5">5 Writing the first draft</a></strong></p>
<p><strong><a href="#6">6 Revising the first draft</a></strong></p>
<p><strong><a href="#7">7 Diagrams, graphs, tables and mathematics</a></strong></p>
<p><strong><a href="#8">8 The report layout</a></strong></p>
<p><strong><a href="#9">9 Headings</a></strong></p>
<p><strong><a href="#10">10 References to diagrams, graphs, tables and equations</a></strong></p>
<p><strong><a href="#11">11 Originality and plagiarism</a></strong></p>
<p><strong><a href="#12">12 Finalising the report and proofreading</a></strong></p>
<p><strong><a href="#13">13 The Summary</a></strong></p>
<p><strong><a href="#14">14 Proofreading</a></strong></p>
<p><strong><a href="#15">15 Word processing / desktop publishing</a></strong></p>
<p><strong><a href="#16">16 Recommended reading</a></strong></p>
</article>
</section>
<section id="introduction">
<header>
<h3>1 Introduction</h3>
</header>
<article>
<p>A technical report is a formal report designed to convey technical information in a clear and easily accessible format. It is divided into sections which allow different readers to access different levels of information. This guide explains the commonly accepted format for a technical report; explains the purposes of the individual sections; and gives hints on how to go about drafting and refining a report in order to produce an accurate, professional document.<br> <a id="2" name="2"></a></p>
</article>
</section>
<section id="structure">
<header>
<h3>2 Structure</h3>
</header>
<article>
<p>A technical report should contain the following sections:</p>
<section id="structure-table">
<table>
<tbody>
<tr>
<td><strong>Section</strong></td>
<td><strong>Details</strong></td>
</tr>
<tr>
<td>Title page</td>
<td>Must include the title of the report. Reports for assessment, where the word length has been specified, will often also require the summary word count and the main text word count</td>
</tr>
<tr>
<td>Summary</td>
<td>A summary of the whole report including important features, results and conclusions</td>
</tr>
<tr>
<td>Contents</td>
<td>Numbers and lists all section and subsection headings with page numbers</td>
</tr>
<tr>
<td>Introduction</td>
<td>States the objectives of the report and comments on the way the topic of the report is to be treated. Leads straight into the report itself. Must not be a copy of the introduction in a lab handout.</td>
</tr>
<tr>
<td>The sections which make up the body of the report</td>
<td>Divided into numbered and headed sections. These sections separate the different main ideas in a logical order</td>
</tr>
<tr>
<td>Conclusions</td>
<td>A short, logical summing up of the theme(s) developed in the main text</td>
</tr>
<tr>
<td>References</td>
<td>Details of published sources of material referred to or quoted in the text (including any lecture notes and URL addresses of any websites used.</td>
</tr>
<tr>
<td>Bibliography</td>
<td>Other published sources of material, including websites, not referred to in the text but useful for background or further reading.</td>
</tr>
<tr>
<td>Acknowledgements</td>
<td>List of people who helped you research or prepare the report, including your proofreaders</td>
</tr>
<tr>
<td>Appendices (if appropriate)</td>
<td>Any further material which is essential for full understanding of your report (e.g. large scale diagrams, computer code, raw data, specifications) but not required by a casual reader</td>
</tr>
</tbody>
</table>
</section>
</article>
</section>
<section id="presentation">
<header>
<h3>3 Presentation</h3>
</header>
<article>
<p>For technical reports required as part of an assessment, the following presentation guidelines are recommended;</p>
<section id="presentation-table">
<table>
<tbody>
<tr>
<td>Script</td>
<td>The report must be printed single sided on white A4 paper. Hand written or dot-matrix printed reports are not acceptable.</td>
</tr>
<tr>
<td>Margins</td>
<td>All four margins must be at least 2.54 cm</td>
</tr>
<tr>
<td>Page numbers</td>
<td>Do not number the title, summary or contents pages. Number all other pages consecutively starting at 1</td>
</tr>
<tr>
<td>Binding</td>
<td>A single staple in the top left corner or 3 staples spaced down the left hand margin. For longer reports (e.g. year 3 project report) binders may be used.</td>
</tr>
</tbody>
</table>
</section>
</article>
</section>
<section id="report-planning">
<header>
<h3>4 Planning the report</h3>
</header>
<article>
<p>There are some excellent textbooks contain advice about the writing process and how to begin (see <a href="#16">Section 16</a>). Here is a checklist of the main stages;</p>
<section>
<ul>
<li>Collect your information. Sources include laboratory handouts and lecture notes, the University Library, the reference books and journals in the Department office. Keep an accurate record of all the published references which you intend to use in your report, by noting down the following information;<br> <br> <strong>Journal article:</strong><br> author(s)<br> title of article<br> name of journal (italic or underlined)<br> year of publication<br> volume number (bold)<br> issue number, if provided (in brackets)<br> page numbers<br> <br> <strong>Book:</strong><br> author(s)<br> title of book (italic or underlined)<br> edition, if appropriate<br> publisher<br> year of publication<br> <br> N.B. the listing of recommended textbooks in section 2 contains all this information in the correct format.</li>
<li>Creative phase of planning. Write down topics and ideas from your researched material in random order. Next arrange them into logical groups. Keep note of topics that do not fit into groups in case they come in useful later. Put the groups into a logical sequence which covers the topic of your report.</li>
<li>Structuring the report. Using your logical sequence of grouped ideas, write out a rough outline of the report with headings and subheadings.</li>
</ul>
</section>
</article>
</section>
<section id="draft-writing">
<header>
<h3>5 Writing the first draft</h3>
</header>
<article>
<p>Who is going to read the report? For coursework assignments, the readers might be fellow students and/or faculty markers. In professional contexts, the readers might be managers, clients, project team members. The answer will affect the content and technical level, and is a major consideration in the level of detail required in the introduction.</p>
<p>Begin writing with the main text, not the introduction. Follow your outline in terms of headings and subheadings. Let the ideas flow; do not worry at this stage about style, spelling or word processing. If you get stuck, go back to your outline plan and make more detailed preparatory notes to get the writing flowing again.</p>
<p>Make rough sketches of diagrams or graphs. Keep a numbered list of references as they are included in your writing and put any quoted material inside quotation marks (see <a href="#11">Section 11</a>).</p>
<p>Write the Conclusion next, followed by the Introduction. Do not write the Summary at this stage.</p>
</article>
</section>
<section id="first-draft-revisions">
<header>
<h3>6 Revising the first draft</h3>
</header>
<article>
<p>This is the stage at which your report will start to take shape as a professional, technical document. In revising what you have drafted you must bear in mind the following, important principle;</p>
<section id="first-draft-revisions-list">
<ul>
<li>the essence of a successful technical report lies in how accurately and concisely it conveys the intended information to the intended readership.</li>
</ul>
</section>
<p>During year 1, term 1 you will be learning how to write formal English for technical communication. This includes examples of the most common pitfalls in the use of English and how to avoid them. Use what you learn and the recommended books to guide you. Most importantly, when you read through what you have written, you must ask yourself these questions;</p>
<section id="first-draft-revisions-table-2">
<ul>
<li>Does that sentence/paragraph/section say what I want and mean it to say?<br> If not, write it in a different way.</li>
<li>Are there any words/sentences/paragraphs which could be removed without affecting the information which I am trying to convey?<br> If so, remove them.</li>
</ul>
</section>
</article>
</section>
<section id="diagrams-graphs-tables-maths">
<header>
<h3>7 Diagrams, graphs, tables and mathematics</h3>
</header>
<article>
<p>It is often the case that technical information is most concisely and clearly conveyed by means other than words. Imagine how you would describe an electrical circuit layout using words rather than a circuit diagram. Here are some simple guidelines;</p>
<section id="diagrams-graphs-tables-maths-table">
<table>
<tbody>
<tr>
<td>Diagrams</td>
<td>Keep them simple. Draw them specifically for the report. Put small diagrams after the text reference and as close as possible to it. Think about where to place large diagrams.</td>
</tr>
<tr>
<td>Graphs</td>
<td>For detailed guidance on graph plotting, see the <a href="/engineering/internal/labreportguide/">'guide to laboratory report writing'</a></td>
</tr>
<tr>
<td>Tables</td>
<td>Is a table the best way to present your information? Consider graphs, bar charts or pie charts.<br> Dependent tables (small) can be placed within the text, even as part of a sentence.<br> Independent tables (larger) are separated from the text with table numbers and captions. Position them as close as possible to the text reference. Complicated tables should go in an appendix.</td>
</tr>
<tr>
<td>Mathematics</td>
<td>Only use mathematics where it is the most efficient way to convey the information. Longer mathematical arguments, if they are really necessary, should go into an appendix. You will be provided with lecture handouts on the correct layout for mathematics.</td>
</tr>
</tbody>
</table>
</section>
</article>
</section>
<section id="layout">
<header>
<h3>8 The report layout</h3>
</header>
<article>
<p>The appearance of a report is no less important than its content. An attractive, clearly organised report stands a better chance of being read. Use a standard, 12pt, font, such as Times New Roman, for the main text. Use different font sizes, bold, italic and underline where appropriate but not to excess. Too many changes of type style can look very fussy.</p>
</article>
</section>
<section id="heading">
<header>
<h3>9 Headings</h3>
</header>
<article>
<p>Use heading and sub-headings to break up the text and to guide the reader. They should be based on the logical sequence which you identified at the planning stage but with enough sub-headings to break up the material into manageable chunks. The use of numbering and type size and style can clarify the structure as follows;</p>
<section id="heading-table">
<table>
<tbody>
<tr>
<td>
<h2>3 Methods of harnessing wave energy</h2>
<h3>3.1 Shore-based systems</h3>
<h3>3.2 Deep-water systems</h3>
<strong>3.2.1 <em>"Duck"</em> devices</strong><br><strong>3.2.2 Rafts</strong></td>
</tr>
</tbody>
</table>
</section>
</article>
</section>
<section id="references">
<header>
<h3>10 References to diagrams, graphs, tables and equations</h3>
</header>
<article>
<section id="references-list">
<ul>
<li>In the main text you must always refer to any diagram, graph or table which you use.</li>
<li>Label diagrams and graphs as follows;<br> <br> Figure 1.2 Graph of energy output as a function of wave height.<br> <br> In this example, the second diagram in section 1 would be referred to by "...see figure 1.2..."</li>
<li>Label tables in a similar fashion;<br> <br> Table 3.1 Performance specifications of a range of commercially available GaAsFET devices<br> <br> In this example, the first table in section 3 might be referred to by "...with reference to the performance specifications provided in Table 3.1..."</li>
<li>Number equations as follows;<br> <br> F(dB) = 10*log<sub>10</sub>(F) (3.6)<br> <br> In this example, the sixth equation in section 3 might be referred to by "...noise figure in decibels as given by eqn (3.6)..."</li>
</ul>
</section>
</article>
</section>
<section id="originality-plagiarism">
<header>
<h3>11 Originality and plagiarism</h3>
</header>
<article>
<p>Whenever you make use of other people's facts or ideas, you must indicate this in the text with a number which refers to an item in the list of references. Any phrases, sentences or paragraphs which are copied unaltered must be enclosed in quotation marks and referenced by a number. Material which is not reproduced unaltered should not be in quotation marks but must still be referenced. It is not sufficient to list the sources of information at the end of the report; you must indicate the sources of information individually within the report using the reference numbering system.</p>
<p>Information that is not referenced is assumed to be either common knowledge or your own work or ideas; if it is not, then it is assumed to be plagiarised i.e. you have knowingly copied someone else's words, facts or ideas without reference, passing them off as your own. This is a <strong>serious offence</strong>. If the person copied from is a fellow student, then this offence is known as collusion and is equally serious. Examination boards can, and do, impose penalties for these offences ranging from loss of marks to disqualification from the award of a degree</p>
<p>This warning applies equally to information obtained from the Internet. It is very easy for markers to identify words and images that have been copied directly from web sites. If you do this without acknowledging the source of your information and putting the words in quotation marks then your report will be sent to the Investigating Officer and you may be called before a disciplinary panel.</p>
</article>
</section>
<section id="finalising">
<header>
<h3>12 Finalising the report and proofreading</h3>
</header>
<article>
<p>Your report should now be nearly complete with an introduction, main text in sections, conclusions, properly formatted references and bibliography and any appendices. Now you must add the page numbers, contents and title pages and write the summary.</p>
</article>
</section>
<section id="summary">
<header>
<h3>13 The Summary</h3>
</header>
<article>
<p>The summary, with the title, should indicate the scope of the report and give the main results and conclusions. It must be intelligible without the rest of the report. Many people may read, and refer to, a report summary but only a few may read the full report, as often happens in a professional organisation.</p>
<section id="summary-list">
<ul>
<li>Purpose - a short version of the report and a guide to the report.</li>
<li>Length - short, typically not more than 100-300 words</li>
<li>Content - provide information, not just a description of the report.</li>
</ul>
</section>
</article>
</section>
<section id="">
<header>
<h3>14 Proofreading</h3>
</header>
<article>
<p>This refers to the checking of every aspect of a piece of written work from the content to the layout and is an absolutely necessary part of the writing process. You should acquire the habit of never sending or submitting any piece of written work, from email to course work, without at least one and preferably several processes of proofreading. In addition, it is not possible for you, as the author of a long piece of writing, to proofread accurately yourself; you are too familiar with what you have written and will not spot all the mistakes.</p>
<p>When you have finished your report, and before you staple it, you must check it very carefully yourself. You should then give it to someone else, e.g. one of your fellow students, to read carefully and check for any errors in content, style, structure and layout. You should record the name of this person in your acknowledgements.</p>
</article>
</section>
<section id="word-processing">
<header>
<h3>15 Word processing / desktop publishing</h3>
</header>
<article>
<section id="word-processing-table">
<table>
<tbody>
<tr>
<td><strong>Advantages</strong></td>
<td><strong>Disadvantages</strong></td>
</tr>
<tr>
<td>Word processing and desktop publishing packages offer great scope for endless revision of a document. This includes words, word order, style and layout.</td>
<td>Word processing and desktop publishing packages never make up for poor or inaccurate content</td>
</tr>
<tr>
<td>They allow for the incremental production of a long document in portions which are stored and combined later</td>
<td>They can waste a lot of time by slowing down writing and distracting the writer with the mechanics of text and graphics manipulation.</td>
</tr>
<tr>
<td>They can be used to make a document look stylish and professional.</td>
<td>Excessive use of 'cut and paste' leads to tedious repetition and sloppy writing.</td>
</tr>
<tr>
<td>They make the process of proofreading and revision extremely straightforward</td>
<td><strong>If the first draft is word processed, it can look so stylish that the writer is fooled into thinking that it does not need proofreading and revision!</strong></td>
</tr>
</tbody>
</table>
</section>
<section id="tips">
<p>Two useful tips:</p>
<ul>
<li>Do not bother with style and formatting of a document until the penultimate or final draft.</li>
<li>Do not try to get graphics finalised until the text content is complete.</li>
</ul>
</section>
</article>
</section>
<section id="recommended-reading">
<header>
<h3>16 Recommended reading</h3>
</header>
<article>
<section id="recommended-reading-list">
<ul>
<li>Davies J.W. <em>Communication Skills - A Guide for Engineering and Applied Science Students</em> (2nd ed., Prentice Hall, 2001)</li>
<li>van Emden J. <em>Effective communication for Science and Technology</em> (Palgrave 2001)</li>
<li>van Emden J. <em>A Handbook of Writing for Engineers</em> 2nd ed. (Macmillan 1998)</li>
<li>van Emden J. and Easteal J. <em>Technical Writing and Speaking, an Introduction</em> (McGraw-Hill 1996)</li>
<li>Pfeiffer W.S. <em>Pocket Guide to Technical Writing</em> (Prentice Hall 1998)</li>
<li>Eisenberg A. <em>Effective Technical Communication</em> (McGraw-Hill 1992)</li>
</ul>
</section>
</article>
</section>
</article>
<footer>
<p>MaX Falstein &copy; 2016</p>
</footer>
</body>
</html>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment