ArchHubBABOOMDownload

Jurisdiction codes and authority submission register

BBM-STD-57 · V0.3 · Determine the actual project jurisdiction and applicable instruments before setting design criteria or releasing a submission.

Download WordFormsAll standards

Ribbon tools that apply it: 9-1-3 Readiness

BBM-STD-57-CODES_AND_SUBMISSIONS-V0.3 | Office standard | 5 November 2026 | V0.3 | Private controlled WIP draft for office review and adoption

1 Purpose and source ownership#

Determine the actual project jurisdiction and applicable instruments before setting design criteria or releasing a submission. Maintain one code/applicability register and one linked submission/dependency register. This pack covers and. The design director owns the applicability decision with competent specialists; the authority liaison maintains service/checklist evidence. No library entry, BIM model or information-acceptance record is a permit.

Use BBM-STD-51 §3 as the one edition register, rights and controlled identity, BBM-STD-85 for UAE authority requirement detail and submission steps, and BBM-STD-55 for scoped appointments, including the consultant of record and authority portal submitter. The editable registers provide blank tables, a fictional SYN-P001 example, change records and adverse release cases. Actual site, appointments, code clauses and authority confirmations are project activation inputs.

The shared codes library index is READ-ONLY. Its current location is held once, as the codes-library asset row in the BBM-STD-51 Master index; at 4 November 2026 the path is 02-LIBRARIES\04-REFERENCES\00-CODES-AND-REGULATIONS\CODES-INDEX.csv (share folders renamed 2026-11-04). Cite the register row, not a hard-coded path. Link to its row, edition and evidence; do not create a competing library index or write to the share. Its header and first DMT building/energy-code records were read on 16 October 2026. A downloaded file and recorded hash prove library identity, not current legal adoption or site applicability.

2 Project jurisdiction and applicability#

RecordRequired project entry
Project and landProjectID, plot/site-plan ID and revision, emirate, municipality, master-development/free-zone boundary and permitted use
AuthoritiesPlanning/building-permit authority, fire authority, infrastructure/service/NOC authorities and competent liaison functions
ScopeNew/existing/alteration/fit-out/infrastructure, occupancy, phases, appointment discipline scope and relevant exclusions
InstrumentsApplicable law, planning conditions, building/fire/accessibility/environmental codes, rating/permit instruments and actual adoption basis
EvidenceControlled official source, edition, clause, effective date, applicability reasoning, specialist decision, verification date and clarification status

The InstrumentID is the BBM-STD-51 §3 register ID (for example ED-DBC); this register does not keep its own edition list. The Codes table records InstrumentID, jurisdiction/authority, title/edition, clause or service-checklist item, scope, effective and verification dates, official source URL, library row/path/hash where available, specialist, approval/clarification status and affected BoD criterion/submission IDs. Unknown applicability stays Unverified. Record a reason and authority for N/A; silence does not mean exemption. National/international publications, local adoption instruments and project planning conditions are separate records.

Instrument (BBM-STD-51 ID)Edition fact (from the register)Applies toDetail
ED-DBCDubai Building Code (Decree 45/2021) as amended by DM Administrative Resolution No. 225 of 2024 (13 Aug 2024); apply the DBC plus all DM amending resolutions in force at permit submissionDubai buildings under DM permitting; BoD criteria citing the DBC link hereBBM-STD-85
ED-DXB-LAW-3-2026Dubai Law No. 3 of 2026 on the Quality and Safety of Buildings (emirate law), issued 27 Feb 2026, in force 60 days after Official Gazette publicationExisting Dubai buildings: Quality & Safety Certificate after 20 years from completion, valid 10 years (5 years if 40+ years); an asset-life obligation, not a design-permit ruleBBM-STD-75, 76, 85
ED-DM-11-9-1DM circular (11-9-1) of 2026, 1 Oct 2026, applying ED-DXB-LAW-3-2026, with guidance manual 11-9-1-1 (May 2026)Existing Dubai buildings 20 or more years from completion, on DM notice: Building Quality and Safety Certificate after an appointed engineering office's assessment against the DM technical checklist; valid 10 years (under 40 years) or 5 years (40+); renewal in the last 90 days before expiryBBM-STD-75 §7, BBM-STD-85 §4
ED-UAE-FLSUAE Fire & Life Safety Code of Practice, September 2018 edition, plus the emirate authority's amendments current at project start, recorded in the BEPAll UAE projects; Fire_Rating perBBM-STD-85
ED-ADIBCThe ADIBC edition published by DMT and in force at project start (2013 edition at 2026-11-04)Abu Dhabi buildingsBBM-STD-85
ED-ESTIDAMAEstidama Pearl: private projects minimum 1 Pearl; government-funded minimum 2 PearlAbu Dhabi building permitsBBM-STD-81, 85
ED-ALSAFATAl Sa'fat 2nd edition (Jan 2023): Silver Sa'fa mandatory for all new buildings in DubaiDubai new buildingsBBM-STD-81, 85

The rating rows are statutory minimums, not optional targets. Record the required level, submission stage and evidence for each in the project register; the higher of the statutory minimum and any client target applies.

Applicable law and binding authority conditions cannot be waived by a client instruction or office standard. Contractual hierarchy is recorded by the actual commercial/legal owner. A technical team escalates conflicting instruments or an uncertain transition to the competent specialist/authority; it does not choose the more convenient edition. Preserve the previous project baseline and exact clarification receipt.

3 Separate UAE authority profiles#

ProfileResearched source boundaryProject decision still required
Dubai Municipality / DMBIM instruments (BBM-STD-51): circulars 196 (2013) and 207 (2015), historical (ED-DM-196-207); 9-1-1 of 2021 on applying BIM (ED-DM-9-1-1); 9-1-2 of 13 Oct 2023 (ED-DM-9-1-2): Open BIM per the Dubai BIM Standard from 1 Jan 2024 above 20 floors (ARC) / 40 floors (STR), 20,000 m² (ARC) / 30,000 m² (STR), specialised buildings and government projects; 9-1-3 of 15 Jan 2026, effective 1 Apr 2026 (ED-DM-9-1-3): ARC + STR BIM with the permit for new buildings above G+12 or 15,000 m² or more, listed alterations (add/remove floors, +1,500 m² or more, full redesign, change of main use, relocation on plot) with the application, other alterations final BIM before the completion certificate; drawings extracted from the modelThreshold test record: storeys, built area, alteration type, building use → BIM permit Yes/No with instrument IDs. Profile = the IFC schema, export setup and attribute matrix stated in the current Dubai BIM Standard (ED-DUBAI-BIM-STD), checked at project start and recorded in the BEP; openBIM IFC, zipped, within the portal upload limit; portal validation evidence retained. Exchange profile SYN-X-AUTH in BBM-STD-54; steps in BBM-STD-85
Abu Dhabi DMT / ADMADM BIM Code of Practice (Oct 2020; cover v1, headers v1.1), BIM Documentation Guidelines for Infrastructure v1.0 (Oct 2020) and Infrastructure BIM Object Catalogue v2.0 (May 2021) (ED-ADM-BIM); ADIBC (ED-ADIBC). The guidelines and catalogue are infrastructure documentsEstablish whether the appointment/project adopts them; do not apply them automatically to every building or other emirate. Record the CoP cover/header revision discrepancy. No universal Abu Dhabi building-permit BIM threshold has been established
Abu Dhabi building permits / BINAADMT officially reports the BINAA construction-permitting platform and BIM/AI integrationConfirm the actual current municipality service, project route, checklist, model/schema and receiving capability; no universal building BIM threshold is inferred
Dubai Development Authority / DDACurrent Final Design Approval service places final design approval before building permit and lists project-specific supporting material; DDA Circular 400 Drawings Submission Standards, 29 Sep 2021 (ED-DDA-CIRC-400) sets A1 DWF, monochrome and discipline-tab/sheet-naming conventionsVerify DDA jurisdiction/site plan, the current service/circulars and conditional NOCs; where the current service checklist differs from Circular 400, the checklist governs. Do not substitute a DM or ADM profile
Fit-out routes (DDA, DM, Civil Defence, Abu Dhabi)Per project: each authority's current fit-out service; titles not confirmed from a primary sourceRecord authority, fit-out service URL, checklist revision and verification date per route before use (BBM-STD-62 §5 route table)
UAE Civil Defence / FLSUAE Fire & Life Safety Code of Practice, September 2018 edition (ED-UAE-FLS), plus emirate authority amendments current at project startApproved fire consultant route, fire NOC dependency (DEP-…F), applicable amendments recorded in the BEP, verification date
Security systems (Dubai SIRA)ED-SIRA: no primary source confirmedSecurity-system drawings follow the current SIRA/DM requirement for the plot, confirmed at permit stage; classified per BBM-STD-87
Other free-zone authoritiesPer projectRecord authority, current service URL, profile and verification date before use; do not substitute another authority's profile
Utilities (e.g. DEWA, ADDC, AADC)Per project (ED-UTILITY-REGS)Record utility, NOC service URL, profile and verification date; NOC dependency rows in section 4
Roads and transport authorityPer projectRecord authority, NOC service URL, profile and verification date

The live DDA Final Design Approval page identifies architectural/structural/mechanical drawings, appointment evidence and technical supporting material, with conditional utility, traffic, fire and other NOCs. The workbook records these as a candidate package profile, not a universal nationwide checklist. Older static service cards differ from the current page; retain their dates and seek confirmation rather than merge them into an invented mandatory list. No authority processing duration, charge or project threshold is assumed here.

4 Stage and submission dependency map#

SubmissionIDs use the series SUB-<project>-<route><nn> (e.g. SUB-SYN-PER), the AuthoritySubmissionID the MIDP Exchanges table carries. Track each design approval, construction permission, inspection, connection, completion and occupancy decision as its own record, with authority/service, prerequisites, exact revisions, confirmed review-cycle source and gate. Maintain StageID, SubmissionID, InstrumentIDs, exact authority/service/profile revision, prerequisites, content list, NOC dependencies, producing/checking/authorising party, actual dates, receipt, comments, conditions, expiry and closure evidence. Separate planned, submitted, approved, conditionally approved, rejected and expired states, plus Unverified for an unconfirmed requirement; this set is canonical and is listed once in BBM-STD-93 §7. "Not applicable" is an applicability decision and "Superseded" a record flag, not states. Store the real decision and its scope; an upload receipt proves submission only.

GateCandidate contents and prerequisitesRelease decision
Concept / planningCurrent plot/site plan, permitted-use/planning baseline, design brief/options and the authority's actual concept service requirementsProject authority liaison verifies the route and concept decision; stage name alone is not consent
Permit / final designRequired drawings/models/calculations and reports, including the BIM model where ED-DM-9-1-2 / ED-DM-9-1-3 apply (drawings extracted from the model); scoped consultant appointments; current service checklist; applicable NOCs and prior design approvalsAll applicable prerequisite conditions and package-profile checks complete; statutory decision remains with authority
Construction activityValid permit for the exact activity/phase, approved design revision, specialist/deferred submissions, inspection/NOC requirements and conditionsCompetent project owner confirms permission for this activity; a permit for another scope is insufficient
Completion / operationRequired inspections, as-built/record information (final BIM before the completion certificate where ED-DM-9-1-3 requires it), tests/certificates, service clearances and closed conditions under the actual service; Civil Defence / FLS records per the record group in BBM-STD-75 §4 and the authority route in BBM-STD-85 §5Confirm actual completion/occupation permissions; information handover acceptance does not confer occupation permission

These four office gate labels are mapping categories: the authority-gate family, mapped against the office stage gates (Manual §2.1) and the BoD gates G0–G5 (BBM-STD-12) in BBM-STD-93. The approval state set in this section and §2 is the canonical approval status vocabulary; BBM-STD-12 C4 maps to it through BBM-STD-93. They do not prescribe a nationwide statutory sequence or equate RIBA stages with permits. RIBA 0–7 remains the planning context in BBM-STD-12. Each authority's actual sequence and conditional dependencies take precedence.

4.1 Fictional dependency example#

SYN-P001 is hypothetically inside DDA jurisdiction. Plot SYN-PLOT-001 and every candidate profile require confirmation. The selected fictional route is SUB-SYN-CON01 concept, then SUB-SYN-FD01 Final Design Approval, then SUB-SYN-PER01 building permit, then SUB-SYN-CONST01 scoped construction activity and SUB-SYN-COMP01 completion/operation permission. Final Design Approval is a design decision and never the building permit. Each record has its own candidate ProfileID and stage-specific MIDP row. None is submitted or approved; the concept predecessor is a scenario assumption requiring project-route confirmation.

DependencyIDFictional prerequisiteOwner and effect
DEP- / DEP-Concept decision and verified site-plan validity before SUB-SYN-FD01Authority liaison; affected submission Hold while unknown
DEP-SYN-02F / DEP-SYN-02UFire-design and utility NOC applicability/receipt for SUB-SYN-FD01Separate fire lead and utility liaison owners; conditional applicability requires evidence
DEP- / DEP-Actual Final Design Approval decision plus verified building-permit profile/prerequisites before SUB-SYN-PER01Authority liaison; the current building-permit service/profile remains unconfirmed
DEP-SUB-SYN-PER01 valid permit and conditions for SUB-SYN-CONST01Authorised construction decision owner; information acceptance cannot close this dependency
DEP-Required inspections/certificates and conditions for SUB-SYN-COMP01Completion liaison; record actual decision and permitted use separately

The example identifies dependency ownership without inventing an actual permit, statutory code value or authority assurance. Record the applicable profile's model format/schema, coordinate basis (BBM-STD-86 register key), property/checklist scope, drawing/signature requirements, any Arabic-language text requirement stated in the authority's current checklist (none is assumed; text rules in BBM-STD-66 §3), uploader eligibility and portal validation evidence before release. A filename extension is not a submission profile.

5 BoD criteria and information exchanges#

BBM-STD-12 Basis of Design Report and its approval/criteria workbook retain the design-criterion and approval-tracker ownership. Do not copy their criterion values into a second technical source. This register controls applicability/source and submission profiles; the project BoD/workbook controls the linked criterion value, unit, method and evidence. Both records carry the same InstrumentID/source revision and ChangeID where changed.

Trace fieldSynthetic trace and validation
Criterion sourceCR- → INS-SYN-DDA01, candidate final-design checklist; project criterion is submission readiness, not an invented engineering value
BoD recordSYN-BOD-001 R01 is a fictional project row to be populated under BBM-STD-12; no claim that the office master contains a real project approval
ExchangeEX-SYN-FD01 / DEL-SYN-FD01 / SUB-SYN-FD01; actual date and appointment-specific EIR to be allocated
Plan linkFictional MIDP-SYN-STAGES01 row FD-01; other gates have their own CON-01, PER-01, ACT-01 and CMP-01 rows
Source and change joinCandidate source revision SYN-PROFILE-R01 and baseline CH-SYN-BASE01 join Codes, Profiles and Criterion trace. A proposed CH-SYN-CODE01 revision R02 stays pending until approved and propagated
Separate decisionsTechnical package check; LAP submission authorisation; recipient information acceptance; authority statutory approval, each with its own actor/date/evidence

For a design change, the discipline specialist assesses all affected criteria, drawings/models, NOCs, permit conditions and dependent exchanges. The authority liaison obtains required clarification/resubmission; task leads and LAP propagate the same ChangeID through EIR/BEP/TIDP/MIDP. Do not record authority approval from an internal review outcome.

6 Change alerts and release checks#

At project mobilisation, each affected submission and material rule/site/use/design change, the liaison checks the official service/circular source, adopted edition and effective date. Record old/new source version, verification date, affected rows, specialist impact decision, required action/owner, notifications and receiving acknowledgment. Office default watch: check authority circular and service pages monthly and at every stage gate and submission (DM issued BIM circulars in Oct 2023 and Jan 2026). A project may shorten this interval, but not lengthen it without BIM Manager approval. This template invents no authority SLA. The controlled change record is the alert evidence, not a second code library.

Adverse caseRequired response
Latest library PDF exists but adoption/effective date is unknownHold affected criterion/release; obtain the competent applicability decision
ADM infrastructure profile is assigned to a Dubai building without adoption evidenceReject the profile mapping; determine actual authority and appointment scope
NOC is uploaded but receipt/decision/expiry does not cover this submissionKeep dependency open; verify current valid evidence
Package is accepted as information but the statutory permit is absentInformation decision may stand; construction/occupation permission remains Hold
Authority changes the checklist after a prior concept exchangeAssess affected scope and transition/clarification; update linked baselines before the next applicable release

The release reviewer checks all applicable instruments and clauses, current package profile, prerequisite/NOC ownership, actual valid approvals/conditions, BoD source joins and MIDP delivery joins. Unresolved applicable code or submission profile blocks the affected release. Explicitly accepted non-applicability is recorded with evidence. Office adoption, actual authority confirmation, live portal submission and project approvals are NOT EXECUTED in this template.

References#

Document history
VersionDateChange
V0.12026-10-16First controlled draft
V0.32026-11-05Standard watch no. 1: §2 instrument row ED-DM-11-9-1, DM circular 11-9-1 of 2026 applying Dubai Law No. 3 of 2026; R7 cites the circular
V0.22026-11-04closure: DM BIM circulars and permit threshold test; DBC + AR 225/2024 and Dubai Law 3/2026 rows; UAE FLS 2018 profile; Estidama and Al Sa'fat statutory minimums; ADM BIM CoP, Object Catalogue, ADIBC rows; further authority profile rows; codes library path via BBM-STD-51, 04-REFERENCES rename; monthly circular watch; editions now cited by BBM-STD-51 §3 IDs; detail in BBM-STD-85 + cross-doc pointer pass + template alignment (..148) + folder names without dots