Project Report Writing – SS3 Computer Hardware & GSM Repair Lesson Note (Third Term)
Lesson note at a glance
- Class
- SS3
- Subject
- Computer Hardware & GSM Repair
- Term
- Third Term
- Reading time
- 6 min
A project report is the permanent written record of a technical project, such as a phone repair or a network installation.
- Organised: it is divided into chapters so a reader can find information quickly.
- Evidence-based: it uses diagrams, photos and test data to prove the work was done.
- Clear and honest: it is written in plain language and reports mistakes as well as successes.
- Useful to others: a reader in another city should understand exactly how you fixed a phone or built a network.
Behavioural objectives
By the end of the lesson, students should be able to:
- state why documentation is important in technical work;
- list the five chapters of a project report and say what each one contains;
- name four types of diagram or visual evidence and say when to use each;
- present test results, such as voltage readings, with a short explanation;
- write a report in a clear, honest and direct tone;
- check labels, table of contents and references before submitting a report.
Why do we write a project report?
We write a project report to keep a permanent record, called documentation, of the work we did and how we did it.
- Documentation: the permanent written record of your technical work.
- Everyday example: a house is soon forgotten if nobody records where it is or how the foundation was laid.
- Proof of process: the report shows you followed a logical, step-by-step method.
- Help for others: a technician in another city can repeat your fix by reading it.
- Value to you: it is more than a set of pages for your teacher, because it also shows your skill to future clients.
What are the five chapters of a project report?
A project report has five chapters: Introduction, Literature Review, Methodology, Implementation and Results, and Conclusion and Recommendations.
Chapters let a reader find specific information without reading the whole report.
| Chapter | Title | What it contains |
|---|---|---|
| 1 | Introduction | Why you chose the project and the problem you wanted to solve. |
| 2 | Literature Review (Research) | What you read or watched before starting. |
| 3 | Methodology | The tools and the method, the “How-To” section. |
| 4 | Implementation and Results | What happened when you did the work. |
| 5 | Conclusion and Recommendations | What you learnt and what the next student should do differently. |
Chapter 1: Introduction
- Reason: say why you chose this project.
- Problem: state what you were trying to solve, e.g. “Many laptops in our school are slow because of RAM issues.”
Chapter 2: Literature Review (Research)
- Sources: say what you read, such as a service manual.
- Videos: mention any video you watched from a master technician.
Chapter 3: Methodology
- Tools: list every tool used, from your multimeter to your soldering station.
- Method: describe the steps you followed, in order.
Chapter 4: Implementation and Results
- Actions: say what happened when you did the work.
- Outcome: say whether the phone turned on or the network connected.
- Data: include your test readings and photos here.
Chapter 5: Conclusion and Recommendations
- Lessons: say what you learnt.
- Advice: say what the next student should do differently.
What is the difference between Results and Recommendations?
Results (Chapter 4) are the facts of what happened, while Recommendations (Chapter 5) are your advice for the future.
- Results: the readings, observations and outcome of the work you did.
- Recommendations: suggestions based on your experience, for the next student or technician.
| Point | Results (Chapter 4) | Recommendations (Chapter 5) |
|---|---|---|
| Looks at | What happened | What should be done next time |
| Based on | Test data and photos | Lessons learnt |
| Example | The reading returned to 3.8V after the repair. | Check the charging IC first on similar faults. |
What types of diagram should a report include?
There are four types of diagram or visual evidence to include: block diagrams, circuit schematics, flowcharts, and before and after photos.
Diagrams make your work visible, because a picture can replace many lines of text.
Block diagram
- Use: to show the big picture of how parts connect.
- Example: Battery → Power IC → CPU.
Circuit schematic
- Use: when you did a motherboard repair.
- Tip: include a screenshot of the schematic and circle the component you replaced.
Flowchart
- Use: to show your troubleshooting steps.
- Example: “Check Battery Voltage” → “If low, charge” → “If okay, check Power Button.”
Before and after photos
- Use: as your best evidence of the repair.
- Example: a corroded board next to a clean, working board.
How do you present and analyse data in a report?
Data analysis means looking at your test results and explaining what they mean.
A professional does not just say “It is working.” They give measured data.
- Voltage readings: do not just say the power was okay. Give the expected value, the reading found and the reading after repair.
- Current consumption: make a small table of the current the device draws at different stages (power off, booting, full load).
- Comparison: compare your results with “known good” values to show you have done your homework.
Example of a voltage statement
- “The expected voltage was 3.8V, but the initial reading was 1.2V. After replacing the charging IC, the reading returned to 3.8V.”
Example of a current table
| Stage | Current drawn (record your own reading) |
|---|---|
| Power off | Write your reading and unit here |
| Booting | Write your reading and unit here |
| Full load | Write your reading and unit here |
What tone should a report have?
A report should be clear, honest and direct, even though it is technical.
- Be clear: write “The phone would not power on” instead of “The electronic communication device exhibited non-functional behaviour.”
- Be honest: if something went wrong, such as a screw stripping or a screen ribbon tearing, write it down and explain how you fixed the mistake. This shows integrity.
- Use active voice: write “I measured the voltage” instead of “The voltage was measured by me.” It sounds more direct and professional.
| Weak wording | Better wording |
|---|---|
| The electronic communication device exhibited non-functional behaviour. | The phone would not power on. |
| The voltage was measured by me. | I measured the voltage. |
How do you finish and check a report?
You finish a report with a “final polish”, which means checking it carefully before you bind and submit it.
- Check the labels: every diagram and photo needs a figure number, e.g. Figure 1: Multimeter reading showing a short circuit.
- Check the table of contents: make sure the page numbers match your chapters.
- List the references: write the name and author of any website or textbook you used, at the end of the report. This is called “giving credit”.
Why does your report matter after school?
Your report is proof of your skill that you can show to employers and customers.
- Voice of your hands: the report speaks for your practical work.
- Jobs: you can show it when applying for work.
- Your own shop: you can show it to a client to say, “See? I am a professional. I plan, I execute, and I document.”
- Care: treat your writing with as much care as you treat your soldering iron.
Evaluation
- Look at a photo of a repair you did recently. If you had to put it in a report, what would be the caption (figure number and description)?
- Why is a flowchart better than a long list of sentences when explaining how to find a fault?
- What is the difference between “Results” (Chapter 4) and “Recommendations” (Chapter 5)?
- Write one sentence describing a repair using technical words, then rewrite it in simple words for a customer to understand.
Assignment
Choose a repair or project you have done. Write an outline of its report with the five chapter titles and one sentence under each to say what it would contain. Then write a figure caption for one photo or diagram you would include.
This term's Computer Hardware & GSM Repair topics
SS3 Third Term · 8 topics

