Who does root cause analysis on Gabiley building defects?

Root cause analysis experience gaps in Gabiley show up when a defect is repaired and then returns in the same place. A team without that experience treats the visible crack, damp patch or loose tile as the problem. The cause, whether it sits in the substrate, the detail or the sequence of work, stays in the building and produces the same failure again after the next Gu or Deyr rain.

Why does a repair that skips diagnosis fail again?

A repair fails again because the team never established what produced the defect in the first place. Diagnosis starts with a written description of the failure, its location and its timing, then tests the likely causes one by one until the evidence points to one. Without that method, crews often work from the nearest visible fault. A damp patch on an internal wall may come from a bridged damp-proof course, a failed wet area membrane, a leaking pipe joint or rain driving through a window detail. Each cause needs a different repair. Ask the team to describe how they separate those causes on a real job, what they measure or open up, and what evidence they record before they touch anything. If the answer is a list of repair methods rather than a sequence of checks, the analysis experience is thin.

How do you detect the experience gap before work starts?

You detect it by asking for the record of one past recurring defect and how it was traced. A team with real root cause analysis experience can walk through a case: what failed, what they ruled out, what test or opening confirmed the cause, what they changed and how they checked the repair held. Request those records in writing. On a Gabiley project, also ask the municipal engineer's office whether it holds borehole logs, drainage records or earlier defect complaints for the plot or the street, since ground and drainage conditions shape many recurring failures. Walk a recent building the team completed and ask the caretaker or facilities staff what has come back. One recurring defect with a documented cause and a repair that held carries more weight than a long list of finished jobs.

How do you close the gap on a live project?

You close it by writing the investigation sequence into the contract and supervising it as its own activity. Agree that any defect appearing twice triggers a written investigation before repair, with causes listed, evidence recorded and the chosen cause stated. Name who signs that record and keep it with the handover file. Budget time for openings and tests as general practice, and confirm the exact scope and any acceptance criteria against the project specification or the engineer. Ask two suppliers or testing services what they charge to inspect a sample or run a simple test, and get that in writing. For facilities teams, keep a defect log with dates, locations and repairs so a pattern is visible. A

What to do next

Pick one recurring defect on your current or last Gabiley project and ask the team to write a one-page investigation: symptom, location, causes ruled out, evidence and the repair chosen. If they cannot produce it, add the investigation sequence and record-keeping to the next contract, and ask the municipal engineer's office what records it holds for the site before work restarts.