Who checks test record control on a Berbera build?

A test record only controls quality if the supervisor reads it before the work is covered. On many Berbera builds, test record control supervision gaps let failures stay invisible: the test happens, the result is spoken, the sheet is never filed, and the next trade covers the work. Missing acceptance evidence then surfaces at handover, when nobody can prove the pour, the fill or the joint complied with the specification.

What do test record control gaps look like in Berbera?

They look like ordinary site practice, not sabotage. A cube is taken but no cast date, location or mix reference is written on it. A plate test is run for a hardstanding and the number is relayed by phone. A compaction result is known to the operator but never reaches the file.

The critical mechanism is that a test record without four things is not acceptance evidence: what was tested, where, when, and against what limit. Supervisors who sign activity logs instead of results accept a process, not an outcome. Hold a missing number next to the work it covers. Ask the site team to show the acceptance record for the last slab poured, the last trench backfilled, or the last structural weld. In Berbera, where salt-laden air and coastal groundwater can attack buried concrete and steel, the records that matter most are the ones hidden below ground and behind finishes. Once a slab is poured or a trench is backfilled, no inspection can recover the evidence.

Where does weak supervision miss the warning signs?

A single missing sheet is an administrative slip; a pattern of gaps across one trade is a control failure. Weak supervision reviews records as a filing task at the end of the month, when the sequence of missing dates, repeated mix references and unsigned results is invisible.

The pattern is readable early. Sort the records by date and by element, and look for tests that always sit far behind the work. Check whether the same person records and approves the results. Check whether any test is noted only in a diary or messaging thread. Check whether any record carries a result with no stated limit to compare it against. A test record control gap shows up as silence around a specific activity, not as a bad result. Where the site cannot show the pattern, ask the municipal engineer's office what records it expects for building work in its area, and align the site file with that list. That single conversation gives the supervisor a checklist to audit against.

How do you close a test record control gap?

Make the record the gate, not the afterthought. No placement, backfill, covering or handover step proceeds until the acceptance record for the preceding step is signed, dated and filed with the location marked.

Set the rule before the work starts, in the inspection and test plan. Name who takes each sample, who witnesses it, where the result goes, and what happens when a result fails or a record is missing. Keep a single controlled register per element, and require the supervisor to write the location on the record at the time of the test, while it is still visible. Confirm sampling rates, test methods and acceptance limits with the project's specification or the design engineer, because these vary by element and contract. Check what the contract requires before deciding whether a disputed item is acceptable, and never treat an unsigned record as evidence. At handover, hand the client a complete, indexed record set: it is the only proof of what was built.

What to do next

Ask the site team for the test register for the last completed element. Walk that element and try to match each record to a specific location, date and acceptance limit. Find one record that fails the match, then fix the filing rule for the trade before the next pour or backfill starts.