SAIS approval is not handled as a single submission at the end of a project.
For facilities regulated by the Supreme Authority for Industrial Security (SAIS), formerly known as HCIS, the approval path is structured through defined stages. Each stage has a specific purpose, and each one provides the basis for the stage that follows.
This staged approach is important because security and safety requirements cannot be added to a project as isolated items after the main decisions have already been made. They must be developed in sequence, beginning with the regulatory basis of the facility and ending with readiness for operation.
The process starts with facility categorization.
As explained in Part 3 of this series, the Business Criteria Analysis (BCA) determines the facility category. Once the category is approved, the project team can identify the applicable security and safety requirements, the expected level of protection, and the documentation depth required by SAIS.
Without this foundation, the project does not yet have a reliable basis for security planning or design.
After categorization, the project moves into the stage where the security basis is developed. This is where the facility is assessed, the relevant risks are understood, and the protection philosophy begins to take shape. The project team defines how the facility should be protected before translating that logic into drawings, systems, and technical details.
This distinction matters.
A drawing is not compliant simply because it shows cameras, access control devices, gates, or barriers. A compliant security design must reflect the approved category, the nature of the facility, the risk basis, the operational requirements, and the intended protection strategy. Drawings that are prepared without this foundation may look complete, but still fail to reflect the security logic expected for a SAIS-regulated facility.
Once the security basis is clear, design development can proceed on firmer ground.
At this stage, the requirements begin to take practical form. The project team addresses perimeter protection, access control, gates, vehicle and pedestrian movement, security zoning, surveillance coverage, control room requirements, safety interfaces, emergency coordination, and the infrastructure required to support the security systems.
The purpose is not merely to show equipment on a layout.
The purpose is to demonstrate that the facility design can support the approved security and safety requirements. Security must fit the site layout, the operational flow, the engineering assumptions, and the way the facility is expected to operate.
This is also where the SAIS stages help manage project responsibilities.
Owners, project managers, designers, security consultants, contractors, system integrators, and operators may all be involved at different points. If the approval stages are not clearly understood, responsibility can easily become fragmented. Drawings may be prepared before the regulatory basis is confirmed. Contractors may price or execute works based on incomplete assumptions. Operators may receive facilities that are not yet aligned with readiness requirements.
A structured approval path reduces these risks.
It clarifies what must be established first, what must be designed next, what must be coordinated during implementation, and what must be demonstrated before operation. The value of the staged process is that it prevents the project from moving forward on disconnected assumptions.
The final objective is operational readiness.
SAIS compliance does not end when a design is prepared. A regulated facility must be able to operate with the required level of security and safety. This requires more than approved drawings. It requires installed systems, operational procedures, security staffing, testing, documentation, coordination, and readiness to function together as one operating framework.
A well-managed SAIS-regulated project therefore follows a logical sequence.
Facility categorization establishes the regulatory basis. Security studies define the protection logic. Design development translates the requirements into drawings, systems, infrastructure, and specifications. Implementation alignment helps ensure that what is delivered remains consistent with what was approved. Operational readiness confirms that the facility can function under the required security and safety framework.
For owners and developers, understanding this sequence is essential.
It helps them plan the approval path before major commitments are made. It supports the appointment of the right expertise at the right time. It also prevents SAIS compliance from being treated as a late-stage response to comments, when it should have been built into the project path from the beginning.
This is the practical role of SAIS project stages.
They do not exist only to divide the approval process into administrative steps. They provide a disciplined path for moving from facility understanding to security studies, from studies to design, from design to implementation, and from implementation to operational readiness.
At Saudi Ansary Security Consultancy LLC (SASECON), we support SAIS-regulated projects by managing this path from the correct starting point.
Our work covers facility categorization, security studies, design alignment, regulatory documentation, coordination with project teams, and operational readiness requirements.
By treating the SAIS stages as a structured project path, not as separate approval events, SASECON helps owners and developers move through the process with clearer direction, better coordination, and a stronger basis for successful approval.
In Part 5 of this series, we will examine why security studies must come before security design in SAIS-regulated projects.
