Project Report Writing – SS3 Computer Hardware & GSM Repair Lesson Note (Third Term)

A project report is the permanent written record of a technical project. It is organised into chapters, uses diagrams and photos as evidence, explains test data, and is written in clear, honest language. A reader in another city should be able to 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 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?

Imagine you have built a beautiful house, but you did not tell anyone where it is or how you built the foundation. Eventually, people will forget it exists.

In the technical world, documentation is the permanent record of your hard work. A report is a professional document that proves you followed a logical process, and it is more than a set of pages for your teacher. If a technician in another city reads your report, they should be able to understand exactly how you fixed that phone or built that network.

What goes inside a project report?

A professional report is organised into “chapters”. This makes it easy for a reader to find specific information without reading the whole book.

• Chapter 1: Introduction. Why did you choose this project? What problem were you trying to solve? (e.g. “Many laptops in our school are slow because of RAM issues.”)
• Chapter 2: Literature Review (Research). What did you read? Did you look at a service manual or watch a master technician’s video?
• Chapter 3: Methodology. This is the “How-To” section. List every tool you used, from your multimeter to your soldering station.
• Chapter 4: Implementation and Results. What happened when you did the work? Did the phone turn on? Did the network connect?
• Chapter 5: Conclusion and Recommendations. What did you learn? What should the next student do differently?

How do diagrams improve a report?

In a technical report, long paragraphs can be boring and confusing. Diagrams make your work “visible”. A picture is worth 1,000 words.

Types of diagrams to include

1. Block diagrams: Use these to show the “big picture” (e.g. Battery → Power IC → CPU).
2. Circuit schematics: If you did a motherboard repair, include a screenshot of the schematic. Circle the component you replaced so the reader can see exactly where it is.
3. Flowcharts: Use these to show your troubleshooting steps. Example: “Check Battery Voltage” → “If low, charge” → “If okay, check Power Button.”
4. Before and after photos: These are your best evidence. A photo of a corroded board next to a photo of a clean, working board is very powerful.

How do you analyse data in a report?

A professional does not just say “It is working.” They provide data. Analysis means looking at your test results and explaining what they mean.

• Voltage readings: Do not just say the power was okay. Write: “The expected voltage was 3.8V, but the initial reading was 1.2V. After replacing the charging IC, the reading returned to 3.8V.”
• Current consumption: Create a small table showing the “amps” drawn by the device at different stages (power off, booting, full load).
• Comparison: Compare your results with “known good” values. This shows you have done your homework.

What tone should a report have?

Even though it is a technical report, it should be easy to read.

• Be clear: Instead of saying “The electronic communication device exhibited non-functional behaviour,” just say “The phone would not power on.”
• 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 you have integrity.
• Use active voice: Say “I measured the voltage” instead of “The voltage was measured by me.” It sounds more direct and professional.

How do you finish and check a report?

Before you bind your report and submit it, do a “final polish”:

1. Check the labels: Every diagram and photo should have a figure number (e.g. Figure 1: Multimeter reading showing a short circuit).
2. Table of contents: Make sure the page numbers match your chapters.
3. References: If you used a specific website or a textbook for help, list the name and the author at the end. This is called “giving credit”.

Why does your report matter after school?

Your project report is the “voice” of your hands. When you are done with school and looking for a job or starting your own shop, you can show this report to a client to say, “See? I am a professional. I plan, I execute, and I document.” Treat your writing with as much care as you treat your soldering iron.

Evaluation

1. 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)?
2. Why is a flowchart better than a long list of sentences when explaining how to find a fault?
3. What is the difference between “Results” (Chapter 4) and “Recommendations” (Chapter 5)?
4. 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.