Capstone project

Write up your final-year project like it deserves

You spent months building the thing and have two weeks to write about it. Examiners mark the report, not the demo. They want to see why you made the decisions you made, how you tested the result, and what you'd do differently.

Try it freeSee the steps

Free plan includes 100 AI Autocomplete / Ghost Text · 5,000 AI Writing Words · 100 AI Rewrites.

Report plan

ChapterOwnerStatus
Introduction and objectivesPriyaDone
Background and related workSamNeeds citations
Design and implementationLenaDrafting
Testing and evaluationSamResults in, text to write
Conclusion and reflectionAllNot started

Illustrative plan for a three-person team. Names are invented.

The problem

Where project reports lose marks

Supervisors see strong projects undersold by weak reports every year.

A diary instead of a report

"First we tried X, then we tried Y." Examiners want the final design and the reasons for it, not the chronology.

Decisions without reasons

The report says what was built and never says why this approach was chosen over the alternatives.

No real evaluation

"The system works well." Against which requirements, measured how, compared with what?

Four writers, four reports

Team chapters that differ in tone, terminology and tense, with the same background explained twice.

Step by step

How to do it in LitraMind

Agree the outline and the vocabulary as a team before anyone writes a chapter.

  1. Build the outline from the marking scheme

    Create a document with your department's required chapters. Under each heading, paste the marking criteria it has to satisfy and who is writing it.

    About Write New Paper

  2. Write objectives and requirements first

    State what the project set out to achieve as a numbered list of objectives or requirements. The evaluation chapter will come back to this list, item by item.

  3. Ground the background in sources

    Find related work and existing solutions with Research & Cite, and upload key papers or documentation to ask what approach they took and where they fall short.

    About Research & Cite

  4. Write up design and implementation

    Describe the final design, then explain each significant decision and the alternatives you rejected. Draft from your own notes and commit history; Ghost Text helps with phrasing.

    About AI Autocomplete

  5. Evaluate against the objectives

    For each objective, say how you tested it and what the result was, including what didn't work. Add a short reflection on what you would change.

  6. Make it read as one report

    Combine the chapters and run AI Edit to catch inconsistent terms, abbreviations and capitalization. Use Make Academic on informal passages and Trim on repeated background.

    About AI Edit
Start step 1 free
The guide

What examiners look for

Read your department's handbook and marking scheme first. This structure fits most engineering, computing and applied projects.

Chapter by chapter

Each chapter answers a question the examiner will ask in the viva or presentation anyway.

Typical chapters of a capstone project report
ChapterExaminer's question
IntroductionWhat problem did you take on, and what were your objectives?
BackgroundWhat exists already, and why isn't it enough?
Requirements or specificationWhat exactly did the solution have to do?
DesignWhat did you decide to build, and why that way?
ImplementationHow did you build it, and what was hard?
Testing and evaluationDoes it meet the objectives? How do you know?
Conclusion and future workWhat did you achieve, and what would come next?
ReflectionWhat did you learn, and what would you do differently?

Justify, don't just describe

For each major decision, name the options you considered, the criteria you used and why the chosen option won. A short comparison table often does this well.

Examiners give more credit for a modest design that is well reasoned than for an ambitious one that is only described.

Evaluate honestly

Go back to your objectives and report against each: met, partly met or not met, with evidence such as test results, measurements or user feedback. Describe the test method so the result is believable.

Things that failed are worth marks if you can explain why. An evaluation that reports no problems is not credible.

Team reports and individual contribution

Agree terminology, tense and formatting before writing, and give one person the job of the final edit. Many courses require a statement of who did what, or an individual reflection alongside the group report; be accurate, since supervisors usually know.

Check your course's rules on AI tools as a team, and declare any use the way the course asks.

What goes in appendices

Full code listings, raw test data, questionnaires, meeting logs and user manuals belong in appendices or a repository, with the main text referring to them. Keep the body for explanation and evidence.

Written by the LitraMind team. Last reviewed .

In their words

What researchers and students say

“It helped our team turn a project with several separate deliverables into one report with a consistent narrative.”

Joshua R•••Final-Year Student, EngineeringN••• Institute of T•••, United Kingdom

“The biggest improvement was connecting the problem statement, implementation and evaluation instead of presenting them as unrelated sections.”

Megan C•••Graduate Student, Information SystemsW••• University, United States

“It was useful near the end of the project when we had plenty of technical material but needed to make the report readable.”

Abhishek R•••Final-Year Student, Computer ScienceN••• Institute of A••• C•••, India

“I used it to reduce repetition between the methodology and implementation chapters. The final report became significantly tighter.”

Felix W•••Master's Student, EngineeringR••• T••• University, Germany

“The evaluation section improved because it encouraged us to relate the project outcomes directly to the original objectives.”

Camille R•••Graduate Student, Data ScienceP••• Institute of T•••, France

“It made final editing much easier because terminology and section structure stayed consistent across a report written by several people.”

Jia W•••Final-Year Student, ComputingP••• Institute of T•••, Singapore
The tools

What this workflow uses

All of them live in the same editor, so you don't move text between apps.

Research & Cite

Highlight a claim, search scholarly sources for it, and insert the citation in your chosen style.

About Research & Cite

AI Autocomplete

Ghost Text suggests the next sentence as you type. Press Tab to keep it, keep typing to ignore it.

About AI Autocomplete

AI Edit

Grammar, tone, clarity and consistency suggestions that you accept or reject one at a time.

About AI Edit

AI Rewrite

Seven rewrite modes for selected text: Paraphrase, Make Academic, Improve Fluency, Simplify, Trim, Change Tone and Synonyms.

About AI Rewrite
Straight answer

What it doesn't do

The report describes work the tool has never seen.

  • It doesn't know what you built. Technical descriptions, results and diagrams have to come from your project.
  • It doesn't draw diagrams or format code listings. Make those in your usual tools and add them after export.
  • It doesn't know your department's template or AI policy. Check both.
Questions

Questions people ask

Short answers before you start. Plan limits are on the pricing page.

See plans and limits
Can I use AI to write my capstone report?
Check your course policy and declare what you use. Sensible uses are finding and citing related work, improving the clarity of your own draft and making a team report consistent. The technical content and evaluation must describe what you actually did.
How long should a capstone report be?
Your handbook will give a word or page limit. Individual final-year reports are often 8,000 to 15,000 words; group reports can be longer. Appendices usually don't count.
How do we make a group report read consistently?
Agree an outline, key terms and tense up front, combine the chapters into one document, and run AI Edit across it for terminology, abbreviations and capitalization. Then have one person read it start to finish.
What if the project didn't fully work?
Say so clearly and analyze why. Reports are marked on reasoning, method and evaluation as much as on the outcome, and an honest account of a partial result usually scores well.
Can I export the report to Word?
Yes. Export as DOCX or PDF and apply your department's template.
Keep going

Related use cases

All use cases

Thesis and dissertation writing

Break a thesis into chapters with one job each, draft from sources you've read, and keep terms and citations consistent throughout.

Read the guide

Methodology section

Describe what you did precisely enough to repeat, say why you did it that way, and keep terms and tense consistent.

Read the guide

Case study analysis

Read the case once properly, name the real problem, apply a framework to the evidence, and commit to a recommendation.

Read the guide

Start with the outline and the objectives

Create your report in LitraMind, add the required chapters, and write the numbered objectives first.

Create a free accountView pricing