An engineering design report documents the full design process — from problem identification through concept generation, evaluation, detailed design, and testing. This guide covers every section with worked examples of requirements matrices, decision tables, and engineering specifications.
An engineering design report documents the systematic design process applied to an engineering problem. It is distinct from a technical report (which reports findings from an investigation) in that its primary content is the design process itself — from requirements through concept selection to detailed design and validation.
Design reports are common in:
| Section | Content |
|---|---|
| Executive Summary | Problem, approach, key design decisions, outcome |
| Introduction | Background, problem statement, project scope |
| Design Requirements | User needs → engineering specifications |
| Literature/Background Review | Existing solutions, relevant standards, theory |
| Concept Generation | Multiple design concepts with sketches/descriptions |
| Concept Evaluation | Decision matrix — systematic selection |
| Detailed Design | Drawings, calculations, material specs, tolerances |
| Prototype/Simulation | What was built or simulated; process and decisions |
| Testing and Validation | Test plan, results vs requirements |
| Discussion | Performance assessment, limitations, future improvements |
| Conclusions | Summary of achievement against objectives |
| References | Standards, papers, material datasheets |
| Appendices | Full calculations, CAD drawings, BOM, test records |
Requirements translate a user's need into measurable engineering targets. This is the most important step — poorly defined requirements produce designs that solve the wrong problem.
Use the QFD (Quality Function Deployment) approach: convert customer needs (what) into engineering specifications (how), then set a target value and tolerance for each:
| Customer Need | Engineering Specification | Target Value | Tolerance | Priority |
|---|---|---|---|---|
| Lightweight | Total mass | ≤ 2.5 kg | ±0.1 kg | High |
| Strong enough to carry load | Max load capacity | ≥ 50 N | ±5 N | Critical |
| Low cost | Material + manufacture cost | ≤ £80 | ±£10 | High |
| Easy to assemble | Assembly time (trained user) | ≤ 10 min | ±2 min | Medium |
Distinguish "shall" from "should." Engineering requirements use precise language: "The structure shall support a load of ≥50 N" (mandatory). "The structure should be manufacturable from standard stock material" (desirable). This distinction is enforced in standards like IEEE 830 and ISO 25010 and signals professional practice.
Generate a minimum of three distinct design concepts before evaluating any. This breadth is required in academic design reports and ensures you have genuinely explored the solution space rather than defaulting to the first idea.
Concepts should be genuinely different — three variants of the same idea is not concept generation.
Our engineering specialists write design reports with requirements matrices, concept evaluations, detailed design sections, and IEEE-formatted references.
A weighted decision matrix evaluates competing concepts against the design requirements systematically. Without it, concept selection is arbitrary — and markers will penalise unsupported selections.
Structure: list evaluation criteria as rows, concepts as columns. Assign a weight to each criterion (total = 100%). Score each concept on each criterion (1–5 or 1–10). Multiply score × weight, sum for each concept. The highest total score is the recommended concept.
| Criterion | Weight | Concept A | Score A | Concept B | Score B | Concept C | Score C |
|---|---|---|---|---|---|---|---|
| Mass | 25% | 4 | 1.00 | 3 | 0.75 | 5 | 1.25 |
| Load capacity | 30% | 5 | 1.50 | 4 | 1.20 | 3 | 0.90 |
| Cost | 25% | 3 | 0.75 | 5 | 1.25 | 3 | 0.75 |
| Ease of assembly | 20% | 4 | 0.80 | 3 | 0.60 | 4 | 0.80 |
| Total | 100% | 4.05 | 3.80 | 3.70 |
Concept A scores highest (4.05/5.00) and is selected for detailed design. Critically discuss the result — if the matrix outcome conflicts with your engineering judgement, explain why and whether you override it.
The detailed design section turns the selected concept into a manufacturable or implementable product. It must include:
Every design requirement specified in Step 1 must be tested. Present a test plan with: the requirement being tested, the test method, the pass/fail criterion, and the result.
| Requirement | Test method | Pass criterion | Result | Pass/Fail |
|---|---|---|---|---|
| Mass ≤ 2.5 kg | Weigh assembled unit on calibrated scale | Reading ≤ 2.5 kg | 2.31 kg | Pass |
| Load ≥ 50 N | Apply incremental static loads; record deformation at failure | No permanent deformation at 50 N | First permanent deformation at 67 N | Pass |
| Assembly ≤ 10 min | Timed assembly by 3 untrained participants, mean recorded | Mean ≤ 10 min | Mean 8.4 min | Pass |
Not always — many academic design reports are for paper designs validated through simulation (FEA, CFD, circuit simulation) rather than physical prototypes. If the design is simulation-validated, the testing section presents simulation results against requirements. Be clear about what was simulated vs physically tested, and acknowledge the limitation that real-world performance may differ.
A minimum of three distinctly different concepts is standard academic practice and the professional minimum for most design processes. For complex or safety-critical designs, five or more is typical. More concepts at the generation stage means a broader solution space explored — and a more defensible final selection.
CAD screenshots are acceptable for illustrative purposes in the concept generation section. For the detailed design section, proper engineering drawings with dimensions, tolerances, and projection type are required. Most CAD software (SolidWorks, Fusion 360, FreeCAD) can generate drawing layouts directly — use this functionality rather than inserting 3D rendering screenshots.