Mechanical Engineering SIWES Report: Workshop and Plant Guide

This guide concerns documentation, not permission or instructions to operate, service or isolate machinery. Actual work requires the applicable authorisation, competence, supervision and site procedures.

A mechanical engineering SIWES report should explain the workshop, plant or site work you actually went through: where you trained, the section you were attached to, the machines and systems you worked around, the jobs you saw and did, the measurements and readings involved, the hazards you met, and what you learnt. It must trace back to your dated logbook. Mechanical reports go wrong in a predictable way: the student writes a textbook chapter on "types of lathe" and "methods of welding" and forgets to say what happened on the Tuesday a gearbox came in for repair. Examiners and defence panels have usually seen those chapters many times. What they have not seen is your job, in your workshop, with your readings.

Your institution's SIWES guide and your supervisors set the chapter order, layout and evidence rules. Start from the general SIWES report guide and use this article for the mechanical-specific parts: what to record, how to describe machines and jobs without bluffing, how to handle measurements, and how to write about safety honestly.

Your job records should show what the team did and which part was yours. UniDraft helps organise the permitted workshop facts and instructions you confirm into an editable SIWES report. Start your mechanical SIWES document, then check readings and roles against the actual records. See the SIWES workflow; it does not certify machinery or approve procedures.

The short answer

• Keep a dated job record from week one: date, job or work order, machine or system, operation, measurement with its unit, and your role.
• Label every task observed, assisted or performed under supervision, and keep the label identical in the logbook, the report and your defence.
• Measurements and settings go in only if you took them or read them from a job card, drawing or instrument. Otherwise describe the process without numbers.
• Document the actual controls and responsible roles relevant to each activity. A short report summary is not a complete safe-work procedure.
• Your department's approved template beats any outline you read online, including this one.

What SIWES is, so your introduction is accurate

The Industrial Training Fund (ITF) describes SIWES as a skills training programme that prepares students of universities, polytechnics, colleges of technology, colleges of agriculture and colleges of education for the work situation they are likely to meet after graduation. Its stated objectives include giving students industrial skills and experience in their course of study and helping them apply theory in real work. The ITF also describes a logbook in which students record their training activities, vetted and signed by the institution's supervisor and the industry-based supervisor. You can see this on the ITF SIWES page.

Do not claim in your report that your programme is funded or approved in a particular way unless your SIWES office told you so. Funding, duration and the exact assessment rules differ by institution and course. If you want the basics first, read what SIWES is, and if you are unsure how marks are split, how SIWES is graded explains why you should ask your own department rather than trust a number from a forum.

Mechanical placements are not all the same

The word "mechanical" covers very different training. A student attached to a fabrication shop spends the term around cutting, welding and fitting. A student in a generator and vehicle workshop sees fault diagnosis and servicing. A student in a manufacturing plant sees production lines and quality checks. A student in a design office sees drawings and revisions. Each of them can write a strong report, but the skeleton of the activity chapters is different.

Pick the pattern closest to your placement and write in that language:

• Workshop (machining, welding, fitting, fabrication). Your evidence is job cards, drawings, tolerances, the sequence of operations and the tools used.
• Maintenance (plant, generators, vehicles, air-conditioning, hydraulics). Your evidence is fault reports, service intervals, symptoms, checks made and parts replaced.
• Production or assembly. Your evidence is output counts, stations, quality checks and the reasons for rejects.
• Design office or site installation. Your evidence is drawing revisions, bills of materials, site measurements and installation sequences.

Many students rotate across two or three of these. That is fine; give each section its own dated block and say how long you spent there.

Record the right things every week

The simplest way to make your report specific is to write one line per job, the day it happens. Weak records say "worked in the workshop". Strong records say what was done, on what, with which instrument, and what you did yourself.

A useful weekly record has these fields:

1. Date and job reference. The job card, work order or ticket number if there is one. If there is none, write a short description of the job.
2. Machine or system. Name what it is and, if visible, the model or plate details. "Centre lathe in bay 2" beats "machine".
3. Operation. What was done, in order. For machining, the sequence (facing, turning, drilling, parting off). For maintenance, the symptom, the checks and the fix.
4. Measurements and readings. Dimension, tolerance, pressure, temperature, clearance or torque, each with its unit and the instrument used (vernier calliper, micrometer, gauge, feeler gauge).
5. Your role. Observed, assisted or performed under supervision.
6. Safety step. The protective equipment worn, the guard in place, the isolation done and by whom.
7. Outcome. Part accepted or rejected, fault cleared, machine returned to service, job incomplete and why.

If you cannot fill a field, write "not recorded" in your notes rather than inventing it later. A short honest record can be written up well; an invented one cannot be defended. The logbook guide covers signatures and weekly sign-off, and the engineering logbook examples show sample entries across engineering disciplines.

A sample logbook entry table

This is an original fictional layout example, not a machining or maintenance procedure or real training record. Your own job names, numbers and readings replace everything in it.

Date	Job and machine	What was done	Measurement or reading	Role
Mon	Shaft repair, centre lathe	Observed the authorised technician review the shaft drawing and recorded the permitted job outcome	Final diameter read with a micrometer and written on the job card	Assisted
Tue	Generator no-start complaint	Observed the technician’s assessment and recorded the reported finding without claiming an independent diagnosis	Battery voltage read with a multimeter	Observed
Wed	Fabrication of a support frame	Compared the permitted fabrication record with the drawing reference under supervision	Lengths checked with a steel rule and tape	Performed under supervision
Thu	Hydraulic jack service	Recorded the authorised technician’s service summary; did not carry out the procedure	Oil level checked against the mark	Assisted
Fri	Weekly review	Reviewed the week with the supervisor and had the logbook signed	Not applicable	Performed

Notice what the table does not contain: no claim of a repair completed alone, no invented tolerance and no number that was not read from something. The same discipline carries into the report.

Describing machines and processes without bluffing

Machine descriptions are where textbook paragraphs creep in. A good test is whether a sentence could appear in any report by any student, or only in yours. "A lathe is a machine tool used to remove material from a rotating workpiece" belongs to every report. "The job card identified the shaft and required dimension; I recorded the technician’s reported measurement and my observation role" belongs to yours.

Use this pattern for each major machine or system:

1. What it was and where it sat. Name, location and the job it was used for.
2. How you saw it used. The steps, in order, in your own words.
3. What you did or did not do. Use the observed, assisted or performed labels.
4. What went right or wrong. A tool that chattered, a weld that had to be redone, a gasket that was the wrong size.
5. What you learnt. One sentence linked to course theory if there is a natural link, such as a fit and tolerance you had studied or a heat-transfer principle behind a radiator fault.

Keep textbook background short and put it in one clearly marked paragraph, not scattered across every page. If you use a definition from a book or a standard, cite it. If you used a manual at the workshop, say which manual and what it gave you. Do not paste manufacturer text into your report; the same school that checks your work for copying will look at it.

Measurements, tolerances and calculations

Mechanical placements produce numbers: dimensions, pressures, temperatures, speeds, torques, run hours. Numbers are persuasive, which is exactly why they must be genuine.

• State the instrument and the unit every time. "Measured 24.98 mm with a micrometer" is checkable. "Measured about 25" is not.
• Say whether the figure is yours or reported. If the supervisor told you a speed or a torque setting, write "the supervisor gave the setting as". If you read it off the nameplate, write that.
• Show a calculation only if you did it. A cutting-speed or gear-ratio calculation you actually worked through with real values from the job is excellent. A formula copied from a textbook with made-up values is padding.
• Do not round into precision you did not have. A steel rule does not give hundredths of a millimetre.
• Keep units consistent and use SI units unless the workshop's drawings use something else, in which case say so.

When a drawing is involved, refer to it by its number and describe what you took from it, rather than redrawing someone else's work. If you made your own sketch, label it as your sketch.

Maintenance and fault-finding records

If you spent time on maintenance, the strongest chapter you can write is a short set of fault case notes. Each case has the same layout:

1. The complaint as reported.
2. The checks made, in order, and what each showed.
3. The cause found, or "cause not confirmed" if it was not.
4. The action taken and who did it.
5. How the machine was proved to be working afterwards.

Three or four of these, written from real jobs, tell an examiner far more than a generic maintenance chapter on preventive, corrective and predictive maintenance. If you wish to include the types-of-maintenance theory, keep it to a paragraph and apply it: say which type the case you describe was.

Safety: write what you actually saw

A mechanical workshop is a hazardous place, and examiners know it. Safety writing fails when it is a pasted list of rules the student never saw followed. It succeeds when it is attached to real tasks.

For every activity, add the one or two safety steps that really applied. Examples of what students commonly witness, to be used only if true for you: safety boots and goggles at the grinder, clothing and hair controlled according to the actual machine-specific risk assessment, guards in place on belts and chucks, a machine isolated and its power source locked or tagged before a technician worked on it, lifting equipment checked before use, gas cylinders chained upright, and welding screens used.

Two public references are useful for understanding what good practice looks like, even though they are written for other countries and are not Nigerian law. The UK Health and Safety Executive publishes a machinery and work-equipment hub covering risk assessment, safe use of equipment and lifting operations. The US Occupational Safety and Health Administration explains lockout/tagout, the practice of disabling machinery and controlling hazardous energy before servicing, and notes that sources can be electrical, mechanical, hydraulic, pneumatic, chemical or thermal. Use them to understand the vocabulary and to compare with what your placement did. Do not present them as the rules your workplace followed.

Then add a short section on what your placement actually did: induction, protective equipment issued, a first-aid box, incident reporting, fire points. If your workshop did very little, say what you observed and what you would recommend. Honest weaknesses read better than an invented safety culture, and they feed naturally into the recommendations, which the closing chapter guide explains how to write.

Drawings, photographs and figures

Figures raise a report when they are your own and used properly.

• Sketches you drew of a layout, a part with its dimensions, or a sequence of operations.
• Photographs taken with permission, with people and confidential details out of frame.
• Tables of readings you took.
• Flow diagrams of a process you followed.

Number every figure and table, caption it, refer to it in the text and say what it shows. Do not include company drawings that are confidential or that you were not allowed to copy, and do not present downloaded images as your own. If you are unsure what your host allows, ask your industry-based supervisor and note the permission.

A working chapter outline

Use this only where your approved template leaves the activity chapters open. Your department's layout comes first.

Preliminary pages. Title page, certification, dedication if allowed, acknowledgement, abstract or summary, table of contents, and lists of tables and figures as your guide requires.

Chapter 1: Introduction. Brief background of SIWES (accurate, sourced, short), aims and objectives of your training, and the scope of the report.

Chapter 2: The host organisation. Name, location, brief history if you can verify it, organisation structure, products or services, and the section(s) you were attached to. Write it from what you saw and from permitted company information, not copied from a website.

Chapter 3: Training activities. Organised by section or by period, using the job record. Each activity has the machine or system, the steps, measurements, your role and the safety step. Fault case notes belong here.

Chapter 4: Experience gained, challenges and lessons. Skills you built, tied to specific weeks, and the genuine challenges you met (limited tool access, power outages, lack of supervision) with how you dealt with them.

Chapter 5: Conclusion and recommendations. A short summary, your judgement of the training, and recommendations addressed to a named party: the company, the school or future students.

References and appendices. Standards, manuals or books you cited, and appendices such as a sample job card layout or a sketch, if permitted.

Common mistakes supervisors flag

• Textbook chapters in place of your own work. Pages on engine types or welding processes that never mention a job you did.
• Perfect numbers. Verify every reading against its source. Repeated or rounded values alone do not establish copying.
• Role inflation. "I overhauled the engine" when the record shows you handed tools to the technician.
• Report and logbook that disagree. A week in the report that the logbook does not support.
• No safety content, or safety copied from a poster. Real hazards, real steps.
• Copied host descriptions. A company history lifted from its website or from a previous student's report.
• Unsigned or backfilled logbook. Resolve gaps through the approved correction process; never invent past dates or signatures.
• Figures without captions or explanation. A photograph dropped in with no reference in the text.
• Wrong formatting. Font, spacing, margins and heading levels that differ from the institution's rules. The free formatting checker reads a .docx and flags mismatches, and the format directory lists university rules where they are on record.

Defence questions to prepare for

Panels usually ask about what you did and why. Prepare short, honest answers to questions such as:

1. Walk me through one job from the moment it arrived to the moment it left.
2. How did you measure that dimension, and what was the tolerance?
3. What was the cause of the fault you described, and how did you confirm it?
4. What safety precautions applied to that machine, and what happened if they were ignored?
5. What would you do differently if the same job came tomorrow?
6. Which part of the report did you only observe, and what did you learn from watching it?
7. How does something you saw connect to a course you took, such as thermodynamics, strength of materials or manufacturing processes?
8. What would you recommend the workshop change?

The guide to defending your SIWES report covers how to structure answers and what to bring. If your department also looks at the report for formatting and completeness before the defence, submitting a report that passes departmental review explains what that stage checks.

A realistic writing timeline

If you are writing the report after returning to campus, work in this order:

1. Week one: review the existing record. Lay your logbook out by week. Mark gaps honestly. Ask your industry supervisor, if you can, to confirm a job or two you are unsure about.
2. Week two: draft the activity chapter. Write from the record, job by job, with the labels. Add fault case notes.
3. Week three: the rest. Host organisation, experience gained, safety section, conclusion and recommendations.
4. Week four: figures, formatting and checking. Number and caption figures, apply the institution's formatting, read it aloud once and compare with the logbook, then submit to your supervisor.

If your supervisor sends corrections, managing IT report supervisor corrections shows how to track them so nothing is missed.

Electrical and civil students can see the same approach applied to their own disciplines in the electrical and electronic engineering guide and the civil engineering guide.

Pre-submission checklist

• Every activity matches a dated logbook entry and carries an observed, assisted or performed label.
• Every number has an instrument and a unit, or is marked as reported to you.
• Each figure and photograph is numbered, captioned, permitted and discussed in the text.
• Safety steps appear inside the activities, plus a short section on what the placement did.
• Chapter order, headings and length match your approved guide.
• Font, spacing and margins follow your institution's rules.
• No signature or approval appears that you have not actually received.

Where UniDraft fits in

UniDraft builds the written IT/SIWES report as an editable Word (.docx) document from the placement facts you confirm, your supervisor's instructions, your department's format and your university's format, applied in that order of priority. It does not invent jobs, measurements, results or approvals, and it does not fill your logbook or Form 8 or produce slides. If your supervisor sends corrections, you provide them, confirm the changes, and a new version is created while earlier versions are kept. You still supply the real workshop details, because those are what you will be asked about at your defence.

Start your document →

Sources

• ITF: SIWES management: scheme description, objectives and logbook supervision.
• HSE: work equipment and machinery: machinery safety, work-equipment regulations and lifting guidance (United Kingdom; used for vocabulary and comparison only).
• OSHA: control of hazardous energy (lockout/tagout): purpose of isolating energy sources before servicing (United States; used for vocabulary and comparison only).