Who can run a critical path analysis in Hargeisa?

Critical path analysis experience gaps in Hargeisa put projects at risk because the programme that is meant to show what drives the finish date is often built by someone who has never linked activities, durations and predecessors into a working logic network. When that skill is missing, delay gets blamed on the wrong trade and the site keeps waiting. The check is simple. Ask who built the programme, and ask to see the logic.

What does a critical path analysis actually require?

A critical path method programme is a logic network, not a bar chart with dates typed in. Every activity needs a duration, predecessors and successors, and the longest chain through those links sets the finish date. General practice puts float on the activities that can slip without moving that date, and the critical path is the chain with none. Building that network takes someone who can sit with the trades, agree the sequence, and test the logic by walking the site. It also takes someone who can update it when the raft is poured late or the block delivery slips. Without those links, the dates are guesses and the path is whatever the sheet says.

How do experience gaps turn into misidentified delay drivers?

When nobody on the team builds the links, the programme becomes a list, and the delay discussion moves to whoever is loudest or latest. A common pattern is a programme copied from a previous job, with the same durations and the same logic, so the float sits on activities that are not on the real path in this project. The supervisor then argues about plaster when the actual driver is a late decision on the roof structure, or blames the blockwork gang when the steel fixing sequence is what holds the pour. Add the Gu and Deyr rains, and an unlinked programme cannot show which activities sit on the weather-exposed chain and which can shift. The result is recovery plans that speed up the wrong trade and leave the finish date untouched. The same gap appears when a claim is assessed: with no baselined logic, a delay event cannot be traced to the activities it actually moved.

How do you test for this gap before you award the work?

Ask for the programme file, not a PDF, and open the logic. In general practice, a usable critical path method submission shows predecessor and successor links for each activity, a clear critical path, and a reason for each duration. Then ask three questions. Who built this programme, and on which project did they last update one through to completion? What is the update interval, and who signs each revision? Which activities sit on the critical path today, and which have float? A contractor with real experience will answer these from the file in front of them. If the answers come as description rather than links, treat the programme as a schedule and price the risk accordingly. For public work, ask the awarding office what programme information it expects with the bid, and in what format.

What to do next

On any programme you hold, open it and check three activities for predecessor links. If the links are missing, ask the planner to rebuild the network with the trades present, then agree a weekly update day and keep every revision. Put the same request into the next tender: native file, logic links, update interval and named person.