To write a capstone project report in STEM, show a clear problem, measurable requirements, a justified design, honest test results and a critical evaluation. Examiners mark the reasoning behind your work as much as the final product.
This page sets out the phases of a capstone, the report structure, an example evaluation excerpt and a final checklist. It ends with how STEM Donkey can help with the write-up.
What a STEM Capstone Report Must Show
A strong capstone report answers five questions: what problem you tackled and why it matters, what the solution had to achieve, how you designed and built it, how well it performed against each requirement, and what you would change.
Tie every test result back to a numbered requirement. That single habit makes the evaluation section almost write itself.
What a Capstone Project Is
A capstone is the final-year project that draws together what your degree has taught. In STEM it usually means building, testing or analyzing something real, then writing it up as a technical report and often presenting it.
| Capstone type | Typical output | Main evidence |
|---|---|---|
| Engineering design | Prototype, CAD model or simulation | Test data against specifications |
| Software | Working application with tests | Functional tests, performance and user evaluation |
| Experimental science | Lab investigation | Measured data with uncertainty analysis |
| Data or computational | Model, analysis pipeline or tool | Validation against known results or held-out data |
| Industry-linked | Solution for a sponsor's problem | Requirements agreed with the sponsor and test results |
The Phases of a Capstone Project
- Define the problem. Write a one-paragraph problem statement and agree the scope with your supervisor.
- Research the background. Review existing solutions, standards and relevant theory.
- Set requirements. Turn needs into numbered, measurable requirements, such as "R3: battery life of at least 8 hours at 20 °C".
- Generate and select concepts. Compare options with a weighted decision matrix.
- Build and test. Plan tests for each requirement before you build, then record results carefully.
- Evaluate and reflect. Judge results against requirements and explain gaps.
- Write and present. Draft the report as you go, not in the final fortnight.
Capstones are long hauls. Steady weekly progress, logged in a project diary, carries you further than a late sprint, and the diary feeds your reflection section later.
Capstone Report Structure
| Section | What it contains | Typical share |
|---|---|---|
| Abstract | Problem, approach, key results and conclusion | About 250 words |
| Introduction | Background, problem statement, aims and objectives | About 10 percent |
| Literature and background | Existing solutions, theory, standards | 15 to 20 percent |
| Requirements and design | Requirements table, concepts, selection, detailed design | 20 to 25 percent |
| Implementation | How it was built, tools, key decisions | About 15 percent |
| Testing and results | Test plan, results, figures and tables | 15 to 20 percent |
| Evaluation and conclusion | Performance against requirements, limits, future work | About 10 percent |
| Appendices | Drawings, code listings, full data, risk assessment | As needed |
Check your department's handbook for required sections, word limits and formatting. Some programs also require a separate reflective log or project management section.
Writing Measurable Requirements
Vague requirements make evaluation impossible. Each one should be testable, with a value, a unit and the conditions of the test.
| Weak | Measurable |
|---|---|
| The device should be light | R1: mass no more than 1.5 kg including battery |
| The app should be fast | R2: search results returned in under 500 ms for 10,000 records |
| The filter should remove noise | R3: attenuation of at least 40 dB at 50 Hz |
Critical Evaluation: An Example Excerpt
Evaluation is where many reports lose marks by simply restating results. Compare each result with its target, explain the difference and say what it means.
Example evaluation paragraph. Requirement R2 specified a search response under 500 ms for 10,000 records. The median response measured over 50 trials was 320 ms, with a 95th percentile of 610 ms. The median meets the target, but one search in twenty exceeded it. Profiling showed the slow cases involved queries with leading wildcards, which bypass the index. A trigram index would likely remove these outliers, and testing it is listed as future work.
Notice the structure: target, measured result with spread, judgment, cause and next step. Negative or partial results are acceptable when explained this way.
The Presentation and Viva
Many capstones end with a demonstration or viva. Prepare to explain decisions, not just describe the product.
- Know why you rejected the alternative concepts.
- Be ready to explain any equation, algorithm or test in your report.
- Admit limitations plainly and say how you would address them.
- Bring a backup video in case a live demonstration fails.
Capstone Report Checklist
- The problem statement and aims are clear in the introduction.
- Every requirement is numbered, measurable and tested.
- Design choices are justified with evidence or a decision matrix.
- Results include units, uncertainty or spread, and labeled figures.
- The evaluation compares every result with its requirement.
- Limitations and future work are specific, not generic.
- All sources, code libraries and datasets are cited.
- The report meets the word limit and formatting rules.
How STEM Donkey Helps with Capstone Projects
Send your project brief, handbook, data, test results and any supervisor feedback. A writer matched to your field prepares a custom report draft or specific sections, such as the literature review, design justification or evaluation, built from your own project work.
Use it as a reference for structure and argument while you write your final version. Your results are used as provided and never invented. Free revisions within the scope of your original request are included.
Want Help Turning Your Project into a Strong Report?
Send your project brief, results and supervisor feedback. You get a custom report draft that links requirements, design, testing and evaluation clearly.
Order Your Capstone ReportFree revisions · Full refund if late · Written from scratch for your order
Frequently Asked Questions
Yes, if your program allows it. A computational or data project still needs clear aims, a validated method and evaluation against objectives.
Report it honestly. Explain what failed, why, what you learned and what you would change. A well-analyzed failure can still score well.
Include material a reader may want to check but does not need to follow the argument: full drawings, code listings, raw data and risk assessments.
It varies widely by program and project type, so follow the word limit in your handbook. Appendices usually sit outside the limit, but check, since some departments count them.
Follow your department's guidance. Many STEM reports use a neutral style, but the reflection section often uses the first person.
From the first weeks. Draft the background and requirements early, then add sections as each phase finishes.