Saudi Building Code Requirements for Finishing Works

Saudi Arabia has a national building code — the Saudi Building Code, or SBC — that governs construction across structural design, fire and life safety, mechanical and electrical systems, and general building requirements. Most discussion of it, understandably, focuses on structural engineering and fire safety at the design stage, because that's where the code's requirements are most obviously load-bearing in the literal sense, and where a design consultant is already deeply engaged before a single trade mobilizes on site. What gets discussed far less is how much of it actually lands in the finishing scope: the trades that come last on site and are, not coincidentally, the trades that determine whether code-relevant details like guarding, fire separation, slip resistance and accessible routes are genuinely delivered or quietly compromised in the rush to hand over on schedule. This guide stays deliberately general about the code itself — it exists, it's real, and it's administered nationally — without citing specific clause or section numbers that vary by building type, occupancy and edition, and are better confirmed with the design consultant or code authority on any given project rather than taken from a summary written for a general audience. The purpose here is to explain where finishing decisions and code compliance actually intersect in practice, because that intersection is where a genuinely competent finishing contractor earns its fee and a careless one creates a liability that surfaces years later.

Life-safety details that live inside the finishing scope

Guarding at stairs, balconies and floor openings — safety railings, in practical terms — is a genuine finishing-adjacent scope item, not a separate structural afterthought; it's why "stair and opening safety railings" sits inside Ashlaar's own architectural finishing capability alongside plaster, flooring and ceilings rather than under structural works. Fire-rated and properly smoke-sealed partition assemblies matter because a fire rating on a drawing only means something if the partition, the door, and the penetrations through it for cabling and ductwork are actually built and sealed to match — a gap around a cable tray through an otherwise-rated wall defeats the purpose entirely, and it's the finishing and MEP trades working together on site, not the structural drawing sitting in a folder, that determine whether that happens correctly. Slip-resistant flooring specification in wet, public or heavily trafficked areas is a finishing material decision with a direct life-safety consequence, not a purely aesthetic one, and the right slip rating for a pool deck, a hospital corridor and a shaded outdoor walkway in Saudi Arabia's climate are genuinely different choices, not one generic "non-slip tile" answer.

Accessibility and universal design

Public and institutional buildings generally need to provide genuinely accessible routes — ramps at appropriate gradients, adequate door and corridor clearances, and accessible sanitary fittings — and finishing trades are where this either gets delivered correctly or quietly compromised on site, often for reasons that have nothing to do with bad intent and everything to do with a missed coordination step. A flooring transition with an unplanned lip at a doorway, hardware that's technically installed but at the wrong height or operating force, a vanity or fixture positioned without the clearance the design intended: these are finishing-stage decisions, made by the trades physically installing the last few centimetres of a building, and they determine whether an accessible design on paper is actually an accessible building in practice. A design consultant can specify every dimension correctly and still end up with a non-compliant threshold if the tiling and joinery trades on site aren't working from, and being checked against, the same drawing. This is precisely the kind of detail that's cheap to get right during installation and genuinely expensive to correct afterward, once a floor is laid, grouted and sealed around a fixture that sits a few centimetres out of position.

Waterproofing and moisture as a code and durability issue, not just a nice-to-have

Wet-area waterproofing in bathrooms and kitchens, and roof waterproofing more broadly, exist to prevent exactly the kind of sustained water ingress that later becomes a structural durability issue or a health and mould concern — which is why it's treated as a life-safety and building-performance matter in a serious code framework, not an optional upgrade a client can trim to save cost without consequence. In a Saudi institutional building specifically, the combination of intensive occupancy, heavy MEP and plumbing density in wet cores, and the long service life expected of a government asset makes this more than a theoretical concern — a leak that surfaces years later in a school or a hospital corridor is disruptive in a way it simply isn't in a single private villa. This sits directly inside Ashlaar's own real scope — wet-area waterproofing and roof treatment with foam concrete and waterproofing are both explicit line items under its architectural finishing and external works capabilities — precisely because the same team responsible for the visible flooring, tiling and roof finish is also the team best placed to get the waterproofing beneath it right the first time, rather than treating it as a separate trade with no stake in what happens to the surface above it.

Why this is a coordination problem, not just a specification-reading problem

Code compliance in finishing work isn't only about selecting the right material off a spec sheet — it's about sequencing, and sequencing is where good intentions on paper break down in practice. Waterproofing has to be inspected and, ideally, tested before tiling covers it for good. Fire-stopping around cable and duct penetrations has to be completed before a ceiling closes over it, at a point in the programme when the crew doing the ceiling work has every incentive to move fast and little incentive to double-check someone else's trade. Railing anchor points have to be cast or fixed correctly before cladding or finishes hide the structure behind them, because retrofitting an anchor into finished stone or a completed facade is a genuinely difficult and expensive correction. This is exactly where a finishing contractor's own technical and quality-assurance function earns its keep — catching a missed fire-stop, an under-height railing, or an untested waterproofing membrane before it's buried behind a finished surface, rather than discovering it in a defects inspection months after handover, when fixing it means undoing finished work that was never the problem in the first place.

What good compliance practice actually looks like on site

Defined inspection points before covering up critical work — sign-off on a waterproofing membrane before screed goes over it, sign-off on fire-stopping before a ceiling closes, sign-off on railing anchors before cladding proceeds, each one recorded rather than assumed. A documented defects and snagging process at handover, rather than an informal walk-through where issues get noted verbally and half-remembered by the time anyone follows up. Photographic records of the work that's about to be hidden — a waterproofing membrane, a fire-stop detail, a railing anchor — kept on file so that a question two years later doesn't require opening up a finished wall to answer it. None of this is exotic — it's ordinary good practice on any well-run site — but it requires a contractor to actually have a quality function capable of holding these checkpoints, rather than treating programme speed as the only thing that matters and quality sign-off as a formality to rush through.

Where this connects to Ashlaar's own scope

Architectural finishing at Ashlaar explicitly includes stair and opening safety railings and wet-area waterproofing as line items, executed by the same team responsible for the flooring, partitions and ceilings immediately around them — the kind of scope visible in the multi-level balconies and guarded walkways found in institutional buildings like Prince Sultan University of Engineering in Al Kharj, where guarding at every level change is a genuine, everyday part of the finishing programme rather than an isolated detail added at the end. A dedicated resource focused specifically on the safety-railing scope covers the code-compliance angle for that detail in more depth; the broader point here is that supervision and consultancy's quality and safety role exists precisely to hold these checkpoints across the whole finishing programme, not just one detail of it, and that role is staffed continuously rather than assembled only when an inspection is scheduled.

The practical takeaway: when you're agreeing a finishing scope of work, ask for the code-relevant details explicitly — railings at every opening and change of level, fire-stopping at every penetration, waterproofing sign-off before covering, accessible clearances at fixtures and thresholds — rather than assuming they're automatically bundled into a general "finishing to code" line that nobody has actually itemized. A contractor with a real technical and quality function will already be planning around these checkpoints as a matter of course; asking simply confirms it, in writing, before the work that would hide any gap gets underway, and gives you something concrete to point back to if a question ever comes up after handover. None of this replaces a design consultant's own code sign-off, and it shouldn't be treated as though it does — it's a second, practical layer of assurance at the point where code compliance actually gets built, not just drawn.