In brief

  1. A certificate proves someone attended a course, not that they can set out a building, read a reinforcement drawing or reject a bad concrete pour.
  2. Engineer availability and engineer competence are separate claims: ask who signs the inspection record, on which dates, and for which pour.
  3. Close the gap with supervised site tasks and a signed log before you hand over unsupervised control of work.
Contents
  1. What does an engineer availability training gap look like on a build?
  2. Why does nominal technical oversight put the work at risk?
  3. How do you close the gap before work starts?
  4. What to do next

A certificate from a course does not prove an engineer can supervise a site. Engineer availability training gaps appear when a name is offered to satisfy a contract, but nobody checks whether that person has set out a building, read a bar bending schedule or rejected a poor concrete pour. Attendance records presence in a room, not judgement on a site.

What does an engineer availability training gap look like on a build?

The gap shows up as a person who is available but not tested. A contractor lists an engineer for a project, and the CV shows a diploma and a short course. What it does not show is which structures that engineer actually supervised, how many pours they inspected, and who they reported to. An engineer may be offered to satisfy a contract even though nobody has checked whether that person has run site work.

Training courses teach principles. Site work needs judgement under pressure: deciding whether formwork can be struck, whether a mix is workable enough to place, whether a trench is safe to enter. Those decisions are learned by doing them while someone experienced watches and corrects. When training stops at the classroom, the engineer arrives on site able to name a test but not to interpret a failing result, or able to describe a level but not to check one.

Ask for the gap to be shown to you, not described. Request the last three inspection records the engineer signed, with dates and locations, and ask which pour or which setting-out point each one covers. If the records come back unsigned or undated, treat the availability claim as unverified. Ask the relevant local office what records it holds; the instruction stops there.

Why does nominal technical oversight put the work at risk?

Nominal oversight means a qualified name sits on the paperwork while the decisions happen elsewhere. The site continues because the crew has routines, but nobody with authority checks them.

Several failures follow. Reinforcement is placed at the wrong cover because nobody measures it before the pour. Concrete is placed without a cube or cylinder being taken, so strength is assumed rather than tested. Setting-out errors carry up through the walls before anyone checks diagonals. When these errors are found later, the correction costs more than the original inspection would have.

The mechanism is simple: work that is never checked gets done the quickest way available. A supervisor who does not understand the details cannot challenge a crew, and a crew soon learns which checks will not be asked for. If curing and protection are not recorded, they are easy to skip; check the site conditions against the specification rather than assuming they are being met.

To detect nominal oversight, walk a recent site with the engineer and ask them to explain one decision they made and why. Ask what they rejected and what happened next. An engineer who has never rejected anything has probably never been asked to decide anything.

How do you close the gap before work starts?

Replace the certificate with a task the engineer must perform under observation, and record the result. This converts a paper claim into evidence.

Use a short, practical assessment:

  • Give the engineer a drawing and ask them to set out one corner and explain the checks they would run.
  • Ask them to read a concrete test result and state what they would do next.
  • Ask them to inspect a piece of formwork or reinforcement and list what they would reject.
  • Have them write and sign the inspection record for that task.

Pair a less experienced engineer with someone who has run similar work, and set a defined period of supervised practice before they take independent control. Keep a simple site log of decisions, tests and rejections, signed by the person who made them. Confirm the assessment format and any required records against the project specification or with the project engineer; general practice varies between projects.

What to do next

Before the next pour, ask the contractor for the engineer's three most recent signed inspection records with dates and locations, then set one observed site task: set out a corner or check a reinforcement cage and write the record. If the records are missing or the task is refused, agree with the contractor in writing how supervision will be strengthened before work continues, within whatever the contract allows.

Frequently asked questions

Can a training certificate replace a site assessment?

No. A certificate shows attendance at a course. It does not show that the engineer can set out a building, read a drawing or interpret a failed test. Ask for signed inspection records and watch the person do one task.

Who should keep the site inspection records?

The engineer who made the decision should sign and date the record. Ask the project engineer and the relevant local office what format and retention they require for a building of this type.

What if the contractor cannot produce any records?

Treat the engineer's experience as unverified. Agree in writing on supervised practice, observed tasks and signed records before independent work continues, and check what the contract allows you to require.

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