In brief
- Unresolved site instructions show up as rework at setting out, openings and embedded services, where a wrong assumption is buried under later trades.
- Clients and supervisors can close the gap by requiring numbered written queries, a dated register and one named person authorised to answer.
Contents
A supervisor who spots a clash between a drawing and the ground asks, gets a verbal answer, and builds. Weeks later the answer is disputed, the instruction is missing, and the work must be reopened.
Why do verbal design answers in Bosaso go missing?
A design query is a question about what the drawings require, and it only exists as a record once it is written and dated. On a site where the query is handled by phone call or across a stack of rebar, the answer lives in one person's memory. If that supervisor rotates to another job, or the client changes advisers, the next crew has no version to follow. The skills gap is the habit of knowing which questions must be written, who signs the answer, and where the paper is kept. A practical fix is a numbered query register: number, date raised, drawing reference, question, answer, answerer, date answered. Ask the project manager whether such a register exists, and ask to see the last ten entries. If the answers are one line and unsigned, the practice is not yet in place.
How do unresolved site instructions reach the work?
An unresolved site instruction leaves a decision open while the trades move on, and later work covers it. A query about the foundation setting-out line that is answered only by pointing at a peg gets buried under the slab. A query about conduit and pipe positions for a bathroom disappears behind the screed. When the answer changes later, the correction costs more than the question would have. Embedded services also carry a durability risk, because a pipe run placed without a confirmed fall, or a conduit run without a confirmed depth of cover, is hard to inspect afterwards. Ask the project engineer what ground and exposure conditions the specification assumes for the plot, and to confirm the design cover requirements for that plot against the project specification. General practice is to log every query before the trade that depends on it starts, and to hold the affected work until the answer is written.
What records show that design queries were handled on site?
Site-level competence in handling design queries leaves a paper trail and a matching physical result. Ask to see the query register before judging anything else. Look for numbered entries, a date raised, a drawing or specification reference, the answer, the name of the person who gave it, and the date it was answered. Then check whether the answer was actually built. Walk a recently completed job and compare the register entries against the as-built changes that followed from them. Ask the project engineer to show how the affected work was held until the written answer arrived. A register with entries but no follow-through on site shows paperwork without practice. A site with no register, or with answers that are one line and unsigned, shows the loop is not closed.
What to do next
Before the next pour or blockwork run, ask the project manager to open a query register with numbered, dated entries, one named person authorised to answer, and a rule that no affected trade starts until the answer is written. Ask the municipal engineer's office whether any records or permits for the plot need to be checked first. Then walk the live site and confirm the last three answers were actually built.
Local reporting: this article is written for building work in Bosaso and Puntland. Ground conditions, prices and rules differ between places; confirm the details for your own site.