33283 Chap.5 Writing a Formal Engineering Report
Writing a Formal Engineering Report
Reports are written for decisions
The Week 2 tutorial explains why engineers write reports: to explain findings, compare options and support decisions others can check.
It contrasts reports with essays and dissertations, and asks three questions before writing: who will read it, what they need to know, and how they will use it.
Structure and style
A complete report has a title page, summary or abstract, main content, references and appendices, and the main content follows either a lab report or a design report outline.
The chapter uses the two sample formal reports from the tutorial's grading exercise to show what a marker rewards, and closes with the rules for giving useful peer feedback.
How the chapter is organised
It begins with purpose and audience, compares the lab and design report outlines, rewrites an informal description into report prose, and then measures where the stronger sample report spends its words.
It ends with feedback: the five rules the tutorial gives for commenting on a classmate's draft and how to apply them to your own.
What this chapter covers
- 01
Why engineers write reports
- 02
Essay, dissertation and report compared
- 03
Audience and purpose questions
- 04
Parts of a complete report
- 05
Lab report and design report outlines
- 06
Lessons from the two sample formal reports
- 07
Giving and using peer feedback
Worked example · free
Sort sentences into the right report section
- 1(a) states the purpose, so it belongs in the introduction.
- 1(b) describes the procedure, so it belongs in materials and methods.
- 1(c) reports a measured value, so it belongs in the results.
- 1(d) explains why, so it belongs in the discussion.
Key terms
- Executive Summary
- A brief overview at the start of a report giving its purpose, approach, key findings and conclusion.
- Design Report
- A report that sets out requirements, concept designs, the final design and how it was tested.
- Lab Report
- A report on an experiment, organised as introduction, methods, results, discussion and conclusions.
- Appendix
- Supporting material placed after the main report, such as raw data, calculations or extra figures.
- Constructive Feedback
- Comments that help improve a piece of work by naming strengths and specific changes.
- Formal Style
- Report writing that keeps only relevant detail, states quantities precisely and avoids personal narrative.
Writing a Formal Engineering Report FAQ
What is the difference between an essay and a report?
An essay usually develops a broad argument in continuous prose with little formal structure beyond a beginning, middle and end. A report uses headings, evidence and concise sections so a reader, including a non-expert, can find information quickly and act on it.
What sections does a design report need?
The tutorial's design report outline runs through an introduction with the problem and objectives, design requirements, concept designs, the final design, testing and validation of the design, a discussion of strengths, limitations and improvements, and conclusions, followed by references.
What makes Sample Report B stronger than Sample Report A?
Report B has a quantified abstract, a cited introduction, a method with a circuit diagram, results with labelled tables and figures, a discussion that compares its values with the literature and numbered references. Report A narrates the lab session, guesses its error and cites one web page.
What goes in an abstract or executive summary?
The tutorial describes it as a brief overview of the purpose, the approach, the key findings and the conclusion. The stronger sample report shows the effect: its abstract states what was measured, the most likely explanation and the two key values with their uncertainties, so a reader gets the result immediately.
Assessment move
Download both sample formal reports and annotate them side by side, section by section, noting one thing each does well or badly. Then take a page of your own draft and run the essay versus report test: delete feelings, replace vague quantities with numbers and move interpretation out of the results.
Before any peer review session, reread the brief and marking criteria so your comments focus on requirements, and write every comment as a strength or a specific improvement. Allow a full day between finishing the draft and the final read, so you check it as a reader rather than as its author.
Working through Writing a Formal Engineering Report in 33283? Sia is AskSia’s AI Engineering tutor — ask any 33283 Writing a Formal Engineering Report question and get a clear, step-by-step explanation grounded in how 33283 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.