Trace every choice to a requirement
Requirements, design decisions and test evidence — engineered structure for engineers.
- 1Title Page
- 2Introduction
- 3Requirements
- 4Design Description
- 5Verification & Testing
- 6Discussion
- 7Conclusion
- + 1 more section
What it is & when you’ll write one
A report documenting an engineering design against requirements, with verification and testing. Common in mechanical, electrical and mechatronics coursework.
The scaffold you start with
Every section arrives as a labelled heading with guidance bullets and a suggested word count — generated the moment you create the document.
- 1
Title Page
Heading, guidance bullets and a suggested word count.
- 2
Introduction
Heading, guidance bullets and a suggested word count.
- 3
Requirements
Heading, guidance bullets and a suggested word count.
- 4
Design Description
Heading, guidance bullets and a suggested word count.
- 5
Verification & Testing
Heading, guidance bullets and a suggested word count.
- 6
Discussion
Heading, guidance bullets and a suggested word count.
- 7
Conclusion
Heading, guidance bullets and a suggested word count.
- 8
References
Heading, guidance bullets and a suggested word count.
How your answers shape the draft
Add as much or as little as you like — the only required field is the title. Everything else fine-tunes your scaffold, and most fields auto-fill straight from your brief.
- You addtext auto-fills from brief
Module / Course
your module or course code
Notesierlabels the document and seeds AI memory so every suggestion matches your subject
- You addtext auto-fills from brief
Deadline
when it is due
Notesiersets the pacing Assignment Copilot uses to keep you on track
- You addtextarea auto-fills from brief
Hypothesis / aim
your hypothesis or aim
Notesierframes your Introduction and Discussion
- You addtext
Procedure / design focus
your apparatus, variables or design
Notesiershapes your Methods section
- You addtext
Role in larger thesis / project
how this piece fits the whole
Notesieradds cross-chapter signposting so nothing repeats
- You addtext
Artefacts / repository links
repo, dataset or prototype references
Notesierfeeds your appendices and traceability
- You addtextarea auto-fills from brief
Testing / traceability notes
your testing and traceability notes
Notesiermaps evidence back to requirements
- You addtextarea auto-fills from brief
Instructor notes
grading notes, required angles or constraints
Notesierbecomes high-priority guidance for the AI and section coach
- You addselect
Citation style
your required referencing style
Notesierformats in-text citations and the reference list in any of 15 styles, aiming for 1 citations per 1,000 words
What you get
- Numbered requirements you can trace to design choices
- A clear design rationale for each decision
- Verification, testing and failure-mode thinking
A student scenario
A mechatronics design coursework
A student documents a design. The procedure focus captures design decisions, traceability notes link requirements to design, and artefact links populate the appendices.
Related assignment types
Technical Specification
SHALL/MUST requirements with IDs and acceptance criteria.
Project Report
Objectives to lessons learned, mapped honestly to your aims.
Final Year Project Report
Aims to evaluation, with traceability and test evidence.
All stem & lab reports
Hypothesis, methods, results and error analysis — scaffolded.
Start your report free
Set up your design / engineering report in minutes — drop your brief and start writing with structure, coaching and citations built in.