
Fire protection planning starts with a clear project scope and named responsibility for each system and interface. Before comparing quotations, developers and HSE / MEP managers should establish who prepares the design, coordinates connected trades, submits documents, installs the work and provides acceptance evidence. Equipment lists alone leave these questions unanswered.
A useful proposal connects the building’s requirements to defined deliverables. It identifies exclusions and assigns the work between packages, including alarm interfaces, supporting electrical supplies, building penetrations and testing. This guide provides a planning framework for that discussion across Saudi building projects.
Project qualification: Applicable codes, editions, authority requirements and technical arrangements must be confirmed by the appointed qualified Saudi fire protection professional for the specific building and approval route. The example responsibilities below are planning suggestions requiring contractual confirmation; they do not allocate statutory duties.
Define The Project Before Selecting Systems
Prepare a short project brief before asking suppliers to price. Record the building use, location, development stage and whether the work concerns a new building, refurbishment or tenant fit-out. Include available drawings, existing approvals and the boundaries between landlord and tenant work. Identify who can answer questions about existing installations.
Describe unusual spaces and activities so the designer can assess them. A commercial kitchen, equipment room or storage area may need a different evaluation from the surrounding accommodation. Record what is stored or operated rather than choosing a suppression technology from a product name. System suitability belongs in the professional design review.
List the information still missing and assign an owner and due date. Where existing drawings cannot be relied upon, ask the consultant to define the survey needed. A quotation based on unverified conditions should state its assumptions and explain how later findings will be handled. This makes competing proposals easier to compare fairly.
Establish The Applicable Design And Approval Basis
The Saudi Building Code’s official catalogue identifies SBC 801 as the Saudi Fire Protection Code. Its published scope includes protection against fire and explosion hazards, emergency and evacuation planning, and firefighting systems. The catalogue description is a starting reference; it does not determine the complete design requirements for an individual project.
Reference: Saudi Fire Protection Code — SBC 801
Ask the responsible professional to document the applicable code editions, referenced standards, occupancy assumptions and authority review route. Record who checks this basis and who manages submission comments. Do not treat an unqualified “NFPA compliant” statement as a complete explanation of what a proposal includes or how compliance will be demonstrated.
Professional responsibilities also deserve a current check. Civil Defense announced updated safety-officer responsibility regulations in February 2026. Confirm the actual regulation and its applicability before assigning statutory duties to an HSE manager or another employee. A project coordination chart cannot replace that assessment.

Separate Fire Protection Into Clear Work Packages
Detection And Alarm
Define the proposed alarm package through its design documents and boundaries. Ask which layouts, device schedules, cabling information and interface records will be supplied. Clarify whether the price covers engineering, equipment, installation, programming, submission support and testing, or only selected activities. Assign responsibility for coordination with other trades.
MTC describes related documentation and integration work on its fire alarm services page. Confirm the precise deliverables in the project proposal.
Suppression And Water Based Systems
Ask the designer to identify which protection systems are required and the basis for their selection. Then define the package boundaries around equipment, distribution, supporting services and specialist works. Where relevant to the approved design, clarify responsibility for water supplies, pump interfaces, electrical connections and associated construction work.
The fire suppression service scope provides a starting point for discussing MTC’s engineering and coordination services. The appointed professional must confirm the system selection and project requirements.
Passive Protection And Building Interfaces
Include a separate discussion of barriers, doors, penetrations and related building work where relevant to the fire strategy. Record who details openings, who installs the specified protection and who supplies inspection evidence. Do not assume these activities sit within the active-system contractor’s price. Identify tenant and base-building boundaries before works begin.
Map System And Interface Responsibilities
Use a responsibility map during tender clarification. Replace the suggested roles below with appointed organisations and named contacts. For each row, record who designs, supplies, installs, coordinates, reviews and witnesses the work. Separately identify any authority involvement required by the confirmed project approval route.
| System or Interface | Suggested Lead and Delivery Parties | Review or Witness | Evidence to Agree |
|---|---|---|---|
| Alarm and connected systems | Alarm design lead; alarm contractor and connected trades | Consultant or appointed reviewer | Interface schedule and agreed test records |
| Suppression and supplies | Suppression design lead; specialist and supporting trades | Consultant or appointed reviewer | Design documents and defined supply boundaries |
| HVAC or smoke control interface | Fire strategy lead with mechanical and controls designers | Coordinating consultant | Approved interface logic and witnessed results |
| Doors and access control | Architectural and relevant system designers; door and controls trades | Appointed design reviewer | Door/interface schedule and test evidence |
| Penetrations and firestopping | Relevant designer; opening trade and specialist installer | Appointed inspection party | Approved details and location records |
| Integrated testing and handover | Named coordinator; all participating contractors | Appointed witness and client representative | Test plan, results and outstanding issue record |
For every interface, add an unresolved-boundary field to the working record. For example, an alarm contractor may include an interface module while the mechanical package assumes another party will complete the connection. Record the gap, nominate the parties who must resolve it and update the agreed scope before ordering. This example illustrates procurement coordination; it does not specify a safe control sequence.
Discuss the mechanical side through the HVAC coordination scope where that service forms part of the project. Confirm signal ownership, drawings and testing participants with the responsible designers.
Separate monitoring from control in the interface record. Ask the design team to state what information is exchanged and which approved document governs the intended response. Do not infer a life-safety function from a dashboard graphic or a generic description of building management integration.
Compare Proposals On The Same Scope
Issue the same brief and clarification questions to every bidder. Compare their written inclusions against the agreed work packages. Mark each item Included, Excluded or Clarification Required, and request supporting references. Avoid filling gaps with assumptions based on a contractor’s brochure or an informal conversation.
| Comparison Item | Evidence to Request |
|---|---|
| Design and submissions | Deliverable list, responsible designer and submission/comment scope |
| Equipment and installation | Schedules, quantities, installation boundaries and supporting works |
| System interfaces | Named parties, interface schedule and coordination allowances |
| Testing and acceptance | Test scope, participating trades, witness arrangements and records |
| Handover and exclusions | Document register, training scope, exclusions and unresolved items |
Ask bidders to distinguish design responsibility from installation supervision and supply. A package may cover one activity without covering the others. Record who handles revisions after coordination changes, who updates documents and how variations will be agreed. Commercial evaluation becomes more useful when price differences can be traced to scope differences.
Check claimed credentials and project eligibility through the appropriate current verification route. A website statement about compliance does not establish approval for your building. Keep evidence of the proposed team’s relevant authorisations and competence with the procurement record, subject to the requirements confirmed by the project reviewer.
Agree Testing And Handover Evidence Early
Define the test and document requirements while preparing the scope. Ask the appointed reviewer to distinguish individual system tests from checks involving several building systems. Identify the coordinator, participants, witness arrangements and process for closing defects. The approved design and applicable requirements must govern technical test procedures and acceptance criteria.
Prepare a handover register showing each required record, its author, reviewer and status. Depending on the agreed scope, records may include approved drawings, installation information, test reports, equipment documentation, operating information and training records. Identify which documents remain outstanding and who can accept or reject their closure evidence.
Where appropriate, discuss the building commissioning scope to establish how cross-system checks and evidence will be coordinated. Confirm that any fire-related commissioning tasks are explicitly included.
For a tenant fit-out, record interfaces with the landlord’s systems and who controls access to existing records and installations. Agree how proposed changes will be reviewed before work affects shared systems. Transfer the accepted records to the responsible operating team at handover. Detailed maintenance schedules and workflows sit outside this project-planning guide.
Discuss Your Project Scope With MTC
Bring your project brief, available drawings, system boundaries and unresolved interface questions to the scope discussion. Ask MTC to identify the services offered, deliverables, exclusions and coordination responsibilities in writing, with the applicable design and approval basis confirmed by the responsible professional.
Review MTC’s fire protection services and request a project-specific scope discussion before comparing final proposals.
Frequently Asked Questions
Can One Contractor Cover Every Fire Protection Work Package?
A single organisation may propose several services, but the contract should identify exactly which activities it undertakes and which require other parties. Ask for named responsibility for design, supporting works, interfaces, submissions and testing. The appointed professional should confirm any qualification or authorisation requirements applicable to the proposed arrangement.
What Should A Developer Provide Before Requesting A Proposal?
Provide the building use, project stage, available drawings, existing approval records and intended work boundaries. Include landlord or tenant constraints and known specialist spaces. Identify missing information openly. Ask the consultant to define any surveys or design inputs needed before a bidder can establish a dependable scope and price.
Who Should Resolve Gaps Between Fire Alarm And HVAC Packages?
Nominate a coordination lead in the project appointments and involve both responsible designers and delivery teams. They should resolve the boundary through documented scope clarification and the approved design. Record the agreed responsibilities, updated documents and testing participants. Do not leave a safety-related interface to an undocumented site assumption.
Does Equipment Approval Establish Compliance Of The Complete Installation?
Equipment documentation alone does not establish that the overall project meets its applicable requirements. Ask the appointed reviewer what design, installation, interface and test evidence is needed for the specific building. Confirm the required approval route separately. Product evidence should form part of that assessment rather than replace it.
How Should Tenant Fit Out Responsibilities Be Separated From The Base Building?
Record the landlord’s and tenant’s work boundaries, existing-system information, review contacts and access arrangements before procurement. Identify every proposed connection or alteration affecting shared systems. Assign design, installation and testing responsibilities in writing, with professional review of the proposed changes. Keep accepted revisions and handover records available to the operating team.