1. Home
  2. Insights
  3. Building Defect Diagnosis: Finding the Cause Before Repair
ENGINEERING INSIGHT

Cracks and damp do not reveal the cause on their own: a method to reduce repeated repairs

A practical approach to diagnosing cracks and damp: define the question, test competing causes, document uncertainty and verify repairs.

English translation published . Original Arabic article published 24 September 2026.

Cracking, damp or settlement is an observable symptom, not a diagnosis. Damp, for example, may result from a leaking service, failed waterproofing, condensation or water travelling from another location. A crack may be nonstructural and caused by shrinkage, or it may be an indication requiring more detailed assessment. Appropriate repair therefore begins by understanding how the defect develops, rather than immediately choosing a repair material.

A sound engineering report distinguishes what was observed, what was measured, what was inferred and what could not be resolved without further investigation. Those limits matter for asset maintenance and decision-making. They become particularly important when the defect involves a warranty, contractual responsibility or a dispute.

1. Define the question and the scope of the appointment

Before the visit, establish the purpose. Is the task an initial inspection, identification of a cause, a safety assessment, development of repair options, a quantity estimate or documentation of a condition for a contractual matter? Each purpose calls for a different level of inspection, testing and analysis.

The scope should also identify accessible areas, constraints and excluded work. Visual inspection must not be presented as a comprehensive assessment of concealed elements. A local test result should not be extended to the whole building without an appropriate sampling basis.

2. Collect the history and records

Request the available drawings, calculations, specifications, geotechnical reports, construction and quality records, photographs from earlier stages, maintenance and leakage records, and details of alterations and previous repairs. A timeline can help connect the first appearance of a defect with an event such as system operation, rainfall, an alteration or neighbouring work.

Interviews help establish the pattern, but information from the parties should be identified as such and checked against documents and physical evidence wherever possible. Conflicting accounts should not be resolved by impression alone.

3. Document the condition on site

Begin with a systematic inspection, moving from the general condition to individual details. Use a location plan and photographs with a scale, orientation and reference number, and take measurements where needed. For cracks, record their form, direction, width, continuity and relationship to joints, openings and structural elements. Counting cracks alone is insufficient.

For damp, record its boundaries and height, odours, salts, the condition of finishes, possible water sources and ventilation conditions. A ceiling stain does not necessarily mean that the source is directly above it: water may travel through a layer or void before becoming visible.

If indications of immediate danger appear, promptly communicate a clear precautionary recommendation to the person authorised to act, such as restricting access or obtaining an urgent specialist assessment. Where structural safety or life safety may be affected, refer the condition immediately to an appropriately licensed specialist engineer and the responsible decision-maker for precautionary action. A general article or visual inspection is not a substitute for assessing the particular condition. Safety action must not wait for the final report.

4. Develop hypotheses that can be tested

After inspection, develop several hypotheses rather than jumping to the first explanation. Identify the evidence supporting and contradicting each hypothesis, and the investigation that could distinguish between them. For damp, possible hypotheses include:

  • A pressurised service leak: it may continue without rainfall and follow the route of the service.
  • Waterproofing failure: it may coincide with rainfall or washing and appear at penetration details.
  • Condensation: it relates to a cold surface, air humidity, ventilation and operating conditions.
  • Rising damp or lateral water migration: it relates to levels, materials and the water pathway.

This approach reduces trial-and-error treatment that temporarily hides the symptom while allowing it to return.

Classify the conclusion according to the strength of the evidence: a confirmed, probable or possible cause, or an unresolved finding. Explain what could change the conclusion and identify the limits of coverage, sampling and inaccessible areas.

5. Select investigations and tests

Choose investigation tools to answer the question. They may include moisture or temperature measurements, nondestructive testing, limited opening-up, laboratory sampling or crack-movement monitoring. Each tool has limits, an accuracy range and conditions of use. A single instrument reading is not enough to identify the cause.

Field instrument results are indicators to be interpreted in relation to the material, measurement depth, calibration and environmental conditions. One moisture reading does not establish the water source, and one crack-width measurement does not establish that the crack is stable. When monitoring cracks, record the temperature, date and fixed measurement points. The specialist should define the monitoring period and escalation criteria. For contractual matters, preserve sample identities, locations, dates, chain of custody and laboratory results.

The investigation plan must be proportionate to the consequences of the decision. A limited repair may require a local check, whereas a decision about strengthening, evacuation or a substantial financial dispute requires a more detailed scope, analysis and review by the appropriate specialists.

6. Analyse the root cause

Distinguish between:

  • The defect: the unacceptable or nonconforming condition.
  • The deterioration mechanism: the process that produced the damage, such as water ingress or differential movement.
  • The immediate cause: the detail, construction practice or operating condition that allowed the mechanism to develop.
  • Contributing factors: maintenance, the environment, an alteration or a delayed response.
  • The effect: consequences for safety, serviceability, appearance, service life or cost.

A defect may have more than one cause. A noncompliant detail does not, by itself, prove that it caused the damage. Explain the technical link between the condition and the outcome.

7. Design the repair and verify its effectiveness

The recommendation should address the cause and restore the required performance, rather than simply conceal the visible effect. Compare options for effectiveness, disruption to use, expected service life, maintenance and risk. Repair documents should cover surface preparation, materials, details, work sequence, quality control and testing.

Where the conditions or material are uncertain, a trial area can be useful. Inspect its performance before extending the repair. Define a monitoring plan after repair: what will be measured, when will it be checked, and what will constitute success?

What makes an engineering report defensible?

The report should record the appointment, scope and limitations; documents reviewed; inspection dates; methods and instruments; observations and results; analysis and options; conclusions with an appropriate degree of certainty; and recommendations and priorities. Separate facts from opinions and attach the supporting photographs, location plans and referenced results.

Our article on when an engineering expert report is needed explains the distinction between a general report and one intended to support a decision or dispute file. An asset condition assessment approach is also useful when the task is to prioritise many elements rather than diagnose a single defect.

Common mistakes

  • Naming the symptom as the cause—for example, saying that “damp is caused by damp”.
  • Describing photographs without location plans or measurements.
  • Recommending a repair material before understanding the damage pathway.
  • Generalising one sample result to the entire building.
  • Failing to review previous repairs and why they did not work.
  • Using conclusive language when the evidence is limited.
  • Confusing technical opinion with the determination of legal liability without the necessary scope and expertise.

Worked example: damp returns after repainting

In a hypothetical case, a stain appears near a window after rainfall and the repair contractor immediately proposes repainting and local waterproofing. Diagnosis begins by recording when it appears, the direction of the rain, joint conditions and the possible water pathway. The possibility of another source is also investigated before reaching a conclusion: the stain may mark where water exits, rather than where it enters.

The specialist develops a staged investigation or a local water-leakage test appropriate to the condition, protecting components and defining the observations and stopping criteria. Uncontrolled flooding or pressure testing that could increase the damage is inappropriate. After addressing the cause supported by the evidence, define a verification method and follow-up period suited to the mechanism and conditions, then repair the affected finishes.

When is more than one discipline needed?

Indications of movement or concrete deterioration call for an appropriately scoped structural engineering assessment. Suspected service leaks may require input from MEP engineers. An engineering assessment and technical report brings together the findings and their limits. Engineering expert support for claims and disputes can help organise facts and evidence where the appointment concerns a dispute. The appearance of a defect alone does not establish who caused it or determine legal liability.

Executive takeaway

Engineering diagnosis is a process of testing hypotheses. It starts with a clear question and scope, brings together the history, observations and measurements, compares possible causes, and leads to a repair linked to the damage mechanism and a verification plan. This evidence chain supports better-informed, safety-conscious decisions and helps reduce repeated repairs that treat the appearance while leaving the cause unresolved.

Professional references and limits of application

The Arabic source records a general reference review on 8 September 2026. The official Saudi Building Code Center landing page below was read on 2 November 2026 and is retained as a reference entry point. This does not verify a particular code provision or edition, establish a diagnosis method or replace a project-specific investigation by an appropriately qualified specialist. Check the applicable code, controlled issue and project requirements for the particular appointment. The worked example is illustrative and does not report the outcome of an AYM project.

Discuss a technical investigation scope

Does the defect return after every repair? Ask AYM to define a technical investigation scope that explains the possible cause, options and limits of the conclusions.

FROM TECHNICAL READING TO A CLEAR DECISION

Turn the engineering question into a defined scope.

Share the project stage, available documents, and the decision you need. Our team will identify the appropriate technical review and deliverables.

Discuss your requirement Explore our services