Who keeps concrete test records in Bosaso?

Test record control on a Bosaso build means one named person keeps the sample register, the result certificates and the file that links each pour to its evidence. When no one owns that register, cubes get taken and results get discussed, but nothing traceable reaches handover. Leave the register without an owner and the chain from sample to certificate breaks even where a supervisor was present on site.

What does weak test record control look like on a Bosaso site?

The chain from sample to signed result can break between the pour and the file cabinet, and this can happen when nobody owns each step. Several small failures can cause it. A site team may take cubes because a contract says so, but nobody writes the pour location, date, mix and sample number on the mould. The laboratory may issue results to a phone rather than a signed certificate, so the client holds a message instead of a document. Or the results arrive and sit in a folder that no one indexes, so a later engineer cannot match result to pour.

Run a self-check on your own project. Who signs the sample register? Where do certificates live? Can the clerk find the result for a named column in under five minutes? If any answer is a shrug, the gap is present. Confirm the contract's testing and handover clauses with the client's engineer before work starts, and ask the municipal engineer's office which records it expects to see for the type of building.

How does this gap turn into missing acceptance evidence?

Missing acceptance evidence appears when the work is done but the paper cannot prove it. Records fail in predictable ways. The cube register lists a sample number but no pour location, so no one can link the strength result to a slab or footing. Results arrive after the next stage has started, and the team moves on without filing them. The person who kept the notebook leaves the job, and the notebook leaves with them. A client then holds a concrete pour with no traceable route from sample to certificate.

This matters at handover and after it. Repairs, extensions, insurance questions and disputes all start with the same request: prove how this element was built and tested. Where evidence is missing, the practical outcome is retesting or accepting the element on inspection alone, and an engineer has to decide what that is worth. Check what the contract says about acceptance evidence, retention of records and who pays for repeat testing. If the contract is silent, raise the point and get it written into the next payment certificate or variation rather than leaving it to the end.

How do you close a test record control gap?

Name a record controller for the project and write that name into the site file, not just into a conversation. The controller owns four things: the sample register, the delivery of samples to the laboratory, the log of results received, and the handover file. Agree one register format per contract, in a form the laboratory and the client both accept, with a column for pour location, sample number, date, required test and result reference.

Then run short checks. Once a week, pick two entries in the register and ask the controller to produce the matching certificate. Log every sample at the moment it is taken, not at the end of the week. Keep certificates as signed originals or verified scans in one folder, with a copy held off site. Where the contract allows, pay the laboratory directly for the certificate set so the client holds the documents. General practice is to keep test records for the life of the building and beyond, but confirm the duration against the project's specification or the client's engineer.

What to do next

Open the current file and find the result for the last concrete pour. If it takes more than five minutes or the certificate is missing, name a record controller this week and start a single register for the remaining pours. Then ask the client's engineer to confirm the records required at handover in writing.