In brief

  1. A training log earns acceptance when it names the task, the standard the work was checked against, the person who supervised it and the correction made on the day.
  2. The engineer's office and the client's representative should agree the log format before work starts, so nobody argues about it at handover.
  3. A log that only records attendance proves nothing; the entry must point to finished work that can still be inspected.
Contents
  1. What should each entry in the log contain?
  2. Who should sign it, and how does that tie to the work?
  3. How do you keep the log alive through the job?
  4. What to do next

A training log an engineer will accept records four things for each task: what the trainee did, the standard the work was checked against, who watched and corrected it, and the date and signature. It links to work still visible on site. A notebook of attendance names alone will not survive a handover review.

What should each entry in the log contain?

Each entry needs the task, the element or grid reference where it was done, the standard or drawing detail used, the supervisor's name and role, and the correction made. Add the trainee's name and the date. One entry per task, not one per day, so the log builds a record of capability rather than presence.

Write the entry at the bench or on the slab, while the work is in front of you. A supervisor who fills the book in the office at the weekend writes what they remember, and an engineer reading it months later sees generic lines that fit any site.

The standard is the part people skip. "Blockwork to line and level" says nothing. "Wall on grid line B between C1 and C2, plumb checked with spirit level on face and end, courses level to the line, mortar joint thickness checked against the specification" tells the engineer what was measured and how. Confirm the tolerances against the project specification or the engineer before you write them down, and quote the clause or drawing number you used.

Where a correction was made, say what was wrong and what changed. "First course out of level by one joint, lifted and relaid to the line" is a stronger record than a clean page, because it shows the supervisor was checking and the trainee was learning. The education page sets out learning paths that help a supervisor frame these entries.

Keep a copy of the drawing or sketch referred to, in a plastic sleeve in the same file. An entry that cites drawing 04 rev B is only useful if drawing 04 rev B can be produced.

Who should sign it, and how does that tie to the work?

A supervisor who watched the work signs it, and the engineer or clerk of works countersigns at each inspection. The signature must belong to a named person with a stated role, not a company stamp. If the signer cannot describe the work when asked, the entry fails its purpose.

The chain of sign-off already exists for inspections. Use it. When the engineer inspects reinforcement before a pour, that is the moment to countersign the fixing entries in the log. The two records then match: the inspection sheet and the training log both point to the same bars, the same date and the same person. The sign-off article explains who signs an apprentice's work; the log follows the same chain.

At handover, the engineer will sample the log and walk to the elements it names. If a wall has been plastered, the blockwork entry behind it is harder to verify, so photograph the work before covering it and file the photo number in the entry. That single habit makes the log defensible.

How do you keep the log alive through the job?

Set it up before the first task, agree its format in writing, review it weekly and keep it with the inspection file. A log started in month three has a gap that no amount of neat handwriting closes.

Agree the format at the pre-start meeting. Ask the engineer's office what it wants to see and write that into the site file. Then review weekly: the site supervisor checks that every entry has a task, a standard, a name and a date, and that photographs exist for anything about to be covered up. The apprenticeship progress check gives a routine for that review.

Store the log with the inspection records, not in a supervisor's bag. One file, numbered pages, kept dry. If the site runs a risk review for documentation gaps, the log belongs in it; the construction risk analyzer lists documentation as a category to check.

Expect the engineer to ask two questions: show me the work, and tell me who checked it. A log built this way answers both without a search.

What to do next

Before the next pour or blockwork lift, take one page of the current log and rewrite one entry with the grid reference, the standard used, the supervisor's name and role, the correction made and the date. Show it to the engineer or clerk of works and ask whether that format is acceptable for the rest of the job.

Frequently asked questions

Does a training log need to be in Somali or English?

Ask the engineer's office and the client's representative which language they will read at handover. A bilingual entry, with the task and standard in the language the drawings use, avoids the argument later. Keep names and dates exactly as they appear on site records.

Can a company stamp replace a signature?

No. A stamp shows a firm was involved, not that a person watched the work. The entry needs a named person with a role who can describe what they saw if the engineer asks.

Sources

  1. Somali Construction Review education pagesomaliconstructionreview.com
  2. Somali Construction Review construction risk analyzersomaliconstructionreview.com

Local reporting: this article is written for building work in Puntland. Ground conditions, prices and rules differ between places; confirm the details for your own site.

Report an error