The Complete SIWES Technical Report Writing Guide

What Is the SIWES Technical Report?

The SIWES technical report is a formal document you submit at the end of your industrial training. It summarises everything you did, learned, and achieved during your placement. Most schools require it for your IT grade, and some require it for graduation clearance.

A good report is 40 to 80 pages and covers your entire placement period in structured, professional language.

Standard Report Structure

1. Title Page

• Your full name and matric number
• Course and department
• Name and address of the company
• Supervisor's name
• Submission date

2. Declaration

A signed statement that the work is your own.

3. Certification

Signed by your industrial supervisor confirming you completed the placement.

4. Dedication (Optional)

A short dedication to family, mentors, etc.

5. Acknowledgements

Thank your supervisors, colleagues, and anyone who helped you.

6. Abstract

A 200 to 300 word summary of your entire report. Write this last.

7. Table of Contents

Auto-generate this in Microsoft Word after you've written everything else.

8. Chapter 1 — Introduction

• Background of the organisation
• Objectives of the SIWES programme
• Scope of your work
• Organisation of the report

9. Chapter 2 — Description of the Organisation

• History and overview of the company
• Organisational structure
• Products/services offered
• Your department and its role

10. Chapter 3 — Summary of Work Done

This is the most important chapter. Organise by project or by month. For each major task:

• What the task was
• How you approached it
• Tools and technologies used
• Outcome and what you learned

If you've been logging daily in your logbook, you have all the raw material for this chapter already.

11. Chapter 4 — Skills Acquired

List the technical and soft skills you developed. Be specific:

• Technical: programming languages, tools, frameworks, hardware
• Soft: communication, teamwork, time management, professional conduct

12. Chapter 5 — Conclusion and Recommendations

• Summary of your experience
• How it relates to your academic studies
• Recommendations for future students or the company
• Your personal career direction after this experience

13. References

Cite any books, websites, or documentation you referenced.

14. Appendices

• Code snippets
• Screenshots
• Diagrams
• Any supporting material too detailed for the main body

How to Write It Faster

Use Your Logbook

If you've been keeping a daily logbook, your Chapter 3 practically writes itself. Group your entries by project or theme, then expand each group into a narrative.

Use Lynktern's Report Generator

Lynktern can compile your logbook entries into a structured draft report. You still need to review and personalise it, but it saves hours of staring at a blank page.

Write in Sections

Don't try to write the whole report in one sitting. Set a target of one section per day for two weeks.

Common Mistakes

A 10-page report will not pass, so aim for at least 40 pages. Describe how you did things, not just what you did. Your report must be original since copying from the internet or other students is grounds for failure. Use consistent fonts, proper headings, and page numbers. Screenshots, flowcharts, and system diagrams make your report look professional and add pages legitimately.

Start early, use your logbook, and you'll have a report you're proud of.