In brief
- Interface coordination gaps appear at the junctions between trade packages, not inside any single package.
- The main check is a signed schedule naming who completes, inspects and hands over each junction.
- A supervisor's experience on one site type does not transfer to a plot with different ground, access, drainage or building use.
Contents
Interface coordination experience gaps in Hargeisa show up at the junctions between trade packages, not inside them. A team can pour concrete well and still leave a slab penetration nobody planned. Someone has to own that junction before work starts, and that is where limited experience costs the project.
The risk is quiet. Each package looks complete on its own. The failure sits between two of them, and it appears late, when the first trade has left site. This article sets out how the gap forms, how it damages the work, and how a project manager or supervisor can detect and close it in Hargeisa.
How does an interface coordination experience gap form in Hargeisa?
The gap forms when a supervisor has run packages on one kind of building but not on the specific junctions of this one. Experience of laying block does not cover a wet area membrane tying into a drainage outlet. That junction sits between two packages, and it needs someone who has closed it before.
Experience also carries across site conditions that may not match. A supervisor who worked on one plot may not have handled a plot with a different slope, a different access route or different drainage. A person who ran fit-out in one building may not have run a project where the ground behaves differently in the wet season. Confirm the plot's slope, drainage and wet-season groundwater against the site investigation and the project specification, and ask the municipal engineer's office whether it holds borehole logs or level information for the plot.
The mismatch stays hidden at bid time. A firm lists projects and roles. The list shows years, not junctions. When the interface falls between packages, nobody notices until two trades meet and one of them has already moved on. Ask any contractor for their project list with the interfaces they closed, not just the buildings they finished.
What does an interface gap do to the work on site?
The work slows, then gets redone. The first trade reaches its boundary and stops. The second trade arrives and finds a condition it did not price: a penetration with no sleeve, a level that does not suit its material, an opening too narrow for its duct or pipe. Work stops while someone decides who pays.
Cost and programme move together. The idle crew waits, the second trade returns later, and the junction is cut open after finishes are in place. Rework at a junction usually means breaking something already complete. A membrane, screed or rendered face may be cut to reach it, then reinstated.
Responsibility becomes the argument. Each package can point to its own scope. The contract may not name who completes the junction. The delay then depends on how fast the client, engineer or main contractor decides, and on what the contract allows them to direct. Check what your contract says about interface works and who bears the cost of waiting.
How do you check for interface experience before it bites?
Ask for a junction schedule before work starts. List every place two packages meet: slab openings, waterproofing terminations, embedded pipes and conduits, door thresholds, tank bases, drainage connections, and the transition between substructure and superstructure. For each, name who completes it, who inspects it, and who accepts the handover.
Walk a recent site by the same team and look at those junction points, not the finishes. Ask the supervisor to describe what went wrong there and how it got fixed. A person with real interface experience can name the conflict and the sequence that resolved it.
Confirm the checks with the people who hold the records. Ask the municipal engineer's office what drainage or level information it holds for the plot. Ask the laboratory for test records on fill and compaction at the boundaries between packages. Request inspection sign-offs at each junction, not only at package completion. Where the contract is silent on interfaces, raise it with the client before mobilising.
What to do next
Take the current programme and mark every point where two trade packages meet. For each, write one line naming who completes it, who inspects it and when it is handed over. Send the list to the main contractor and the client, and ask them to confirm it or correct it in writing before the next package mobilises.
That single register, agreed before work starts, closes more gaps than any later meeting.
Frequently asked questions
Who should own an interface between two trade packages?
The contract should name one party. Where it does not, ask the client or engineer to confirm in writing who completes, inspects and accepts each junction before the first trade starts.
How do you test interface experience?
Walk a recent site with the same supervisor and ask about the junctions between packages, not the finishes. Ask what conflicted there, what sequence fixed it, and who signed off.
Local reporting: this article is written for building work in Hargeisa and Somaliland. Ground conditions, prices and rules differ between places; confirm the details for your own site.