Soil investigation and the Saudi Building Code: verify your requirements

Identify the applicable reference, not just a code number

Ask the engineer to identify the code edition and provisions used for your project, together with any relevant authority requirements. The official Saudi Building Code catalogue is a starting place for locating code publications, including the soil and foundations subject. It is not a substitute for reading and applying the relevant provisions. Preserve the reference in the project brief so later reviewers can see which basis informed the investigation and design.

Connect the requirement to the actual building

Give the engineer a consistent description of the building, plot and proposed works. Ask how those facts influence the information required from the investigation. The useful response should explain the connection to your project rather than repeat a general claim that all houses need the same package. Where the design is provisional, record the assumptions that may need another review. This is especially important before a significant feature becomes fixed in the design.

Know who checks the submission requirements

Ask which party will confirm the current requirements for the relevant application or approval and who will submit the soil documents when required. Keep this administrative responsibility separate from authorship and technical review of the report. An investigation provider, designer and application representative may perform different tasks. Write their responsibilities next to the documents they handle, so the owner does not discover that each assumed another party would verify the submission route.

Translate compliance into an investigation brief

Request a written brief that bidders can answer, prepared or reviewed by the competent professional. It should identify the required outputs and any project information the provider needs before confirming its proposal. Technical investigation quantities and methods should remain with the specialist. The owner can then compare whether each offer responds to the same brief. If a bidder proposes a different scope, ask for its rationale and refer that difference to the engineer.

Ask for a review trail

When the report arrives, ask the responsible engineer to record whether the agreed requirements have been addressed and what remains unresolved. Keep technical queries and the provider’s responses with the issued report. If a revised issue is produced, identify the superseded version clearly. A compliance statement becomes more useful when the file shows who reviewed the evidence and which limitations were considered, rather than relying on a stamp or a generic declaration in isolation.

Resolve conflicting advice before awarding work

In a hypothetical case, two providers cite different editions or propose different investigation scopes. Do not choose between them by confidence of presentation alone. Send the discrepancy to the appointed engineer and request a written basis for the project requirement. Ask whether the difference concerns an applicable rule, a design assumption or a provider’s preferred service. That distinction helps you obtain the right clarification before paying for work that may not answer the design brief.

Review the basis when the project changes

Keep a change log for alterations that may affect the assumptions given to the investigating team. Ask the engineer whether the existing report remains adequate when the proposal changes; do not infer that a previously accepted document covers every later development. Before a new submission, confirm the current procedure with the relevant official channel. Retain the original basis and the later decision together so the record explains continuity, rather than silently replacing one version with another.

Continue reading

• Engineering supervision cost: compare visits and services
• Engineering office fees: which services may be separate?
• How to appoint an engineering office for an Al Ahsa home