How do you check a supervisor's record in Borama?

Courses, certificates and job titles say a supervisor attended training. They do not show whether that person can hold a line on a Borama site. Supervisor development competency risk, wherever it occurs, is the gap between what a CV claims and what the person actually controls day to day: setting out, checking formwork, calling for tests, rejecting bad concrete. When that gap is not checked, the client carries the cost through rework, delays and disputes.

What does a lack of supervisor development competency look like on site?

A supervisor whose competence is unverified leaves weak first line leadership behind, so problems surface late. Setting out errors sit under the first course of blockwork until the walls are up. Formwork is stripped before the concrete has gained strength. A pour goes ahead without cube samples because nobody called the laboratory.

The pattern is about authority and habit. A supervisor who has never run a pour may not know the sequence of checks, or may not feel able to stop a gang that is ready to place concrete. Signs to look for include inspection requests with no previous visit, no daily diary, no record of which mix was used, and answers that refer back to the contractor's head office rather than the site file.

Ask what the supervisor personally checked and signed. Ask which pour they stopped. Ask what happened to a failed cube result on their last job. Vague answers to those three questions are the clearest warning.

How do you verify supervision experience before award?

Competence is verified with records, not references. Request the last two projects the named supervisor ran, and ask for documents that carry their name and a date: daily site diaries, inspection requests and their outcomes, concrete cube test certificates, setting out records, and non conformance reports they raised.

Where a contractor cannot produce records, ask why. Some small firms keep poor files because the client never asked. That is a training need, and it can be addressed with a written method statement for each activity, weekly toolbox talks and a reporting format the client agrees before work starts.

Walk a recent site the contractor completed. Look at how blockwork joints line up, whether there are tie holes left open, and how the roof meets the wall. That walk tells you more than a certificate. Then ask the local municipal engineer's office which records it requires during works and at handover, and shape your site instructions around that list. Confirm the details against the project specification and the engineer's requirements, not against this article.

How do you close the gap once work has started?

Build the check into the contract and the weekly routine. Agree which inspections the supervisor must request before covering work, and require a signed record for each. Ask for concrete cube results as they come, and make sure the supervisor sees them before the next pour. Add a short weekly written report from the supervisor, with photographs and the tests completed, so gaps in attention become visible early.

Where the gap is real and the contractor is willing, pair the site supervisor with an experienced engineer for the first two months, and set a small list of tasks they must handle alone before that support is withdrawn. Check what your contract allows on supervision, payment and replacement of key staff before you withhold anything or insist on a change. Review the arrangement with the project engineer and record what was agreed.

What to do next

Ask the contractor for the named site supervisor's last two projects, with the site diaries and inspection requests from those jobs, and review them before you sign the award. Then call the municipal engineer's office and ask which records a site supervisor must keep and hand over.