Your SIWES abstract should tell a reader where you trained, what you actually did and what you learned, without making them read the whole report first. Write it after the report, using your completed chapters and logbook. Confirm whether your department requires an abstract, an executive summary or neither.
The hard part is choosing what to leave out. You do not need the history of SIWES, every department you visited or a sentence announcing each chapter. You need a short, accurate picture of your own placement.
An accurate abstract starts with a report built from your actual placement. UniDraft helps organise your confirmed activities and guidelines into an editable SIWES report. Start your SIWES document with UniDraft, then check the summary against the finished chapters and logbook. It cannot verify that you performed a task or supply an experience you did not have.
Gather five facts before writing
Open your report and make these notes. Do not fill a blank by guessing.
| Note | What to take from your own records |
|---|---|
| Context | Organisation or approved description, unit and placement period |
| Purpose | What the training was meant to help you understand |
| Activities | Two or three tasks that best represent your experience |
| Learning | A specific skill or connection between practice and your course |
| Conclusion | What the experience showed, including an important limitation if relevant |
If an employer does not allow its name or operational details to be disclosed, use the description your coordinator and employer permit. Do not include client names, passwords, patient records or confidential production figures.
An annotated SIWES abstract example
This is a fictional teaching example, not a student's placement record. Its purpose is to show how the sentences work. Replace the facts with your own; do not claim its activities as yours.
This report describes an industrial attachment in the IT support unit of an organisation. The placement focused on understanding how routine support requests were recorded and resolved. Under supervision, the student assisted with workstation setup, documented troubleshooting steps and observed network fault diagnosis. The experience developed a clearer understanding of the relationship between equipment checks, accurate fault records and the escalation of unresolved issues. Access to live infrastructure was restricted, so independent administration of the organisation's network was outside the student's role. The report concludes that supervised practical work helped connect classroom networking concepts with the responsibilities and limits of workplace IT support.
The opening establishes the setting. The next two sentences explain the purpose and representative work. The fourth identifies learning. The fifth prevents an exaggerated impression of the student's responsibility. The last gives the report's overall conclusion.
Notice what the example does not say: no invented performance percentage, no claim to have redesigned the network and no claim that the supervisor approved every sentence. A specific, honest account is more useful than an impressive claim you cannot explain at your SIWES defence.
Turn your notes into one connected summary
Draft the context first, then select the activities that support the report's main learning. Group related tasks rather than listing every day. Finish with what the experience means, not a general statement that industrial training is good for all students.
Keep your role precise. “Observed sample preparation” and “prepared samples under supervision” describe different responsibilities. Use the one supported by your records. If you did not collect numerical results, do not add numbers to make the abstract sound scientific.
For a report about completed work, past tense will often fit the activities. Definitions and continuing facts may use present tense. Follow any specific departmental instruction about tense, headings, paragraphs and keywords.
Fix these common problems
| Weak draft | Better revision task |
|---|---|
| Several sentences defining SIWES | Use the space to describe your own placement |
| “I gained many skills” | Name a skill and the work through which you developed it |
| “I managed all operations” | State your actual level of supervision and responsibility |
| A result missing from the report | Remove it or verify and document it properly in the report first |
| A miniature table of contents | Summarise the experience and conclusion instead |
Read the abstract beside your report conclusion. They should agree, but the abstract covers the whole report while the conclusion develops its closing lessons and recommendations.
Before you submit
- Can you locate support for every activity in your report or logbook?
- Does the abstract reflect the finished report rather than an early plan?
- Are your role and any important restrictions clear?
- Have you removed confidential details and unsupported figures?
- Does it meet the exact word limit and layout your department supplied?
The complete SIWES report guide shows where the abstract belongs among the preliminary pages. If those pages are still unfinished, use the separate acknowledgement guide rather than putting thanks into the abstract.
Where UniDraft fits
UniDraft helps organise the placement facts and activities you confirm into an editable Word report, using the guidelines you supply. Review the abstract against your records before submission; the tool cannot confirm that you performed a task. Explore UniDraft.
Further reading
The UNC Writing Center's abstract guide explains the distinction between a summary of completed work and an introduction. Its general writing guidance does not replace your SIWES handbook.
