How do delay records skills gaps cost you in Burao?

A delay records skills gap in Burao shows up when nobody on site can tie a lost week to a named cause, a date and a piece of evidence. The work stops, the diary says "no progress", and months later the client, the quantity surveyor and the contractor argue about what actually happened. Unclear causes of lost time cost money because every party prices the unknown differently.

How does a delay records gap turn into a cost?

A delay record is only useful when it links three things: what happened, when it happened, and what it stopped. A crew that writes "rain, no work" has recorded weather. A useful entry names the cause, the date, the activity it stopped, and the resource left idle, for example: date, 06:00 to 14:00 rain, block laying stopped, masons stood down, decision taken to move them to internal works. The reader fills those fields from their own diaries, instruction register and delivery notes.

Without that link, the argument moves to memory. Memory favours whoever speaks last, and settlement usually lands somewhere between the two positions. The gap is practical competence, not literacy: knowing which events belong in the record, who signs them, and how to close the loop with a dated instruction. Ask the contractor to show the last four weeks of diary entries and the instruction register beside them. If the two cannot be read together, the record will not support a claim.

Which causes of lost time does a delay records skills gap leave unclear in Burao?

The causes that stay quiet are the ordinary ones: late deliveries, a change in the block or aggregate source, a subcontractor arriving after another trade has already moved through, or a decision waiting on the client. None of these look dramatic on the day. None get written down unless someone owns the record. Check the project's own diary and specification to see whether these causes were logged the last time they happened.

The mechanism is general practice, not a local rule. A delay record works when each entry carries a date, the activity affected, the resource standing idle, and the instruction or event that triggered it. Where a decision is pending, the entry should name the person or office holding it and the date the question was sent. Confirm the required record format against the project's specification and the engineer's instructions, because a format the engineer will not accept is wasted effort.

A reader can check record practice without accusing anyone. Walk a recent site and ask two questions: where is the diary kept, and who signs it. Ask the same questions on another project and compare the answers. The contract or project specification should state who keeps and signs the diary, so confirm it there.

How do you test a claim before you accept it?

Test the claim against documents, not against explanations. Start with the baseline programme and the latest update, and ask the contractor to mark each claimed delay event on both. A cause that does not appear on the updated programme was either not recorded at the time or not treated as a delay then.

Then check the evidence chain for one event only. Take the largest claimed delay and ask for the dated diary entry, the instruction or delivery note behind it, and the cost or idle-resource record that follows it. If one link is missing, the cause is unclear, and the extension of time or the loss and expense figure rests on nothing. Check what the contract allows for notice periods and records before you decide how to respond, and never treat a missing link as proof of bad faith.

Keep the test narrow. One event checked properly teaches the contractor what the record must contain, and that lesson transfers to the next claim faster than a general complaint about paperwork.

What to do next

Ask the contractor for the site diary for the last month and the instruction register covering the same dates. Read them side by side and mark any lost day that has no named cause, no instruction and no idle-resource note. Send that list to the engineer and agree the record format for the rest of the job in writing, so the next claim arrives with its evidence attached.