How do test record control gaps affect Hargeisa projects?

Limited test record control experience on a project shows up as acceptance evidence that cannot be found, matched or signed off when the client needs it. The tests may have been done and the concrete may be sound, but without a working record system the proof is scattered across phones, loose sheets and memory.

Record control is the discipline that ties each test result to the element it proves, the date it was taken, the sample identity and the person who witnessed it. On a build where a client or facilities team may take over long after the finishing trades have left, that chain is what handover rests on.

What does a test record control gap look like on site?

A gap in test record control means the team can produce a number but not the story behind it.

Concrete cube results arrive as a message or a photograph. Nobody writes down which pour they belong to, which truck delivered it or whether the samples came from the same batch. A cube result without a pour reference proves nothing at handover. The same applies to compaction tests, soil samples, waterproofing flood tests and pipe pressure tests. Each one needs a location, a date, an identifier and a witness.

Experienced record controllers set this up before the first pour. They agree sample identities with the laboratory, keep a register that lists every test against its element, and file results the day they arrive. Ask to see a contractor's register for the current job and how a result is traced back to a plot. If the answer is a phone gallery, the project is carrying execution risk that will surface at handover.

How does the gap turn into execution risk?

The gap becomes risk when a decision has to be made and the evidence is missing.

A client asks for the compaction record before accepting a hardstand. The test was done but the chainage was never written down, so the area is re-tested or accepted on trust.

Re-testing takes time and can push the programme. Missing records also weaken the client's position if a defect appears later: without a traceable result, the conversation turns on memory rather than evidence. Check how far the laboratory and the supplier are from the site yourself, because travel time changes how quickly samples can be re-taken. Ask the laboratory what sample identification it needs on delivery and how long it keeps its own records. Ask the relevant local authority which records it keeps for a project of this type, and ask what a client would normally receive at handover.

How do you detect and close the gap?

Detect the gap by testing the paper trail, not the concrete.

Pick three recent test results on a live or completed job and ask to see the full path: request, sample identity, delivery note, result, and the register entry that links it to an element. If any step is missing or the register is written up after the fact, the record control is not working.

Close the gap before mobilisation. Put the record system in the contract: who takes samples, who witnesses, how samples are identified, where results are filed, and how quickly. Require a register that is updated as results arrive, not at the end. Name one person on the contractor's side and one on the client's side who signs each entry. Walk a recent site and ask the finishing foreman how he would find the cube result for a column he is about to load. If he cannot answer in a minute, the system is not real.

What to do next

Before the next pour, ask the contractor to show the test record register for the current job and trace one result from sample to element. If the trace fails, agree a written register format, name the sign-off people on both sides, and add the requirement to the contract or instruction before more work is covered up.