In brief
- A design query disappears when it is asked on site, answered verbally and never written down, so the work proceeds on an assumption nobody can check.
- The gap shows up as repeated rework in the same location, trades waiting on each other, and finishes laid before services are confirmed.
- Keep a numbered query register, get a signature on each answer before the affected work starts, and ask the relevant records holder for any existing drawings or ground records.
Contents
A design query in Berbera gets missed when it is raised on site, answered by word of mouth and never written down. The drawing stays wrong, the answer stays in one person's memory, and the next trade builds on top of it. Weak supervision lets that happen because nobody holds the register of open questions.
What is a design query on a Berbera site?
A design query is any point where the drawing, the specification and the ground do not agree, and someone has to decide before work can continue. On a Berbera build that can be a foundation depth against what the excavation actually shows, a service route that crosses a structural element, or a wall set-out that clashes with a boundary the survey did not capture. A project may run with a small design team and drawings issued in stages, so the site team meets these questions daily; confirm the review and issue arrangements for your own project with the designer. The query becomes a risk only when it is settled by a conversation. A verbal answer leaves no record of who decided, what was decided, or which drawing revision it applies to. Ask the relevant authority or records holder on the project, for example the municipal engineer's office, for any existing drawings or ground records for the plot, and treat every difference between those records and the issued drawings as a query to close on paper.
How do unresolved site instructions reach the work?
The instruction travels by memory, so each trade receives a slightly different version of it. The excavator hears one founding level, the steel fixer hears another, and the concrete arrives before anyone checks the two against the drawing. By the time the error is visible, the element is cast and the cost of correction has moved to the client. Weak supervision misses this because it reacts to finished work instead of checking open questions before the trade starts. A supervisor who walks the site but never reads the query register will see diligent workers and no obvious problem. The warning signs are indirect: the same detail corrected twice in one month, a trade standing idle while a decision is chased, and finishes started before embedded services are confirmed. None of these prove a defect, but each one justifies opening the register and asking which query is still open.
How do you check supervision quality on design queries?
Walk a recent site and count the queries that were closed with a signature rather than a conversation. That count, not the number of site visits, tells you how the supervision actually works. Ask for the query register and check three things: each entry has a number, a date and the drawing revision it affects; each answer names the person who gave it; and each closed item is signed before the work it governs started. Where the register is thin, test the chain directly. Pick a completed element, ask the foreman why it was built that way, then ask the engineer the same question. If the two answers differ, the instruction never left the site office. Confirm technical limits such as cover, founding depth and services clearance against the project specification or the engineer, since those values belong to the design, not to site practice.
What to do next
Start a numbered query register this week, on paper or in a shared file. Log every question raised on site with the date and drawing revision, record who answered it and which drawing revision the answer applies to, then raise any item still open at the next site meeting so the project can decide how to proceed. Keep closed entries on file, so the client can see how decisions were made.
Frequently asked questions
Who should keep the design query register in Berbera?
One named person should own it, and the project should decide that title. The project manager reviews it at each meeting, and the client or their representative should be able to read it on request. What matters is that a single owner keeps it current, not which title they hold.
Can a verbal answer from the engineer be enough?
It can settle a small matter on the spot, but it leaves nothing to check later. Write the answer into the register the same day, note who gave it and which drawing revision it affects, then ask that person to sign it. If they will not sign, keep the query open and log it for the next site meeting.
Local reporting: this article is written for building work in Berbera and Somaliland. Ground conditions, prices and rules differ between places; confirm the details for your own site.