A SAIS-regulated project is not approved by design alone.

The Security Risk Assessment, security concept, design criteria, drawings, and technical requirements establish the security basis of the project. They define what must be protected, how security measures should be organised, and what the project must achieve before it can move toward operational readiness.

But the approved design is only part of the journey.

At Stage Three of the project, the work moves from studies, drawings, specifications, and approvals into execution-level development and site implementation. This is where the approved security concept must be translated into real systems, structures, interfaces, documents, tests, and operating arrangements.

This is also where the SAIS-approved Security Contractor becomes a decisive factor.

In SAIS-regulated projects, the approved Security Contractor is not a late-stage installer brought in only to supply equipment. The contractor is a partner in the success of the project and in supporting its path toward authority approval.

The reason is simple: SAIS compliance is not achieved by installing security products. It is achieved by implementing approved security requirements correctly.

The difference is compliance, not installation.

Many contractors can install cameras, gates, barriers, access-control devices, or ELV systems.

That does not mean they understand SAIS requirements.

A SAIS-regulated facility operates under a different security framework. Its required security measures are linked to the facility classification, the approved Security Risk Assessment, the security design basis, and the requirements applicable to facilities under SAIS supervision.

The SAIS-approved Security Contractor understands that every security element is part of a regulated security system. The issue is not simply whether a camera works, whether a gate opens, or whether a fence has been installed. The issue is whether each measure has been implemented in line with the approved design, required specifications, installation requirements, testing requirements, and operational readiness expectations.

This is where ordinary installation and compliance-based implementation separate.

An ordinary contractor may focus on delivering items. A SAIS-approved Security Contractor understands the compliance purpose behind those items.

The contractor must understand the consultant’s outputs.

The Security Consultant’s work does not produce drawings only.

It produces the security basis of the project: the Security Risk Assessment, design criteria, security concept, preliminary design, technical requirements, security drawings, equipment schedules, operational assumptions, manpower interfaces, and Security Organization considerations.

The SAIS-approved Security Contractor is distinguished by its ability to read these outputs correctly and understand their purpose.

The approved contractor understands why the perimeter has been designed in a certain way, why access points are controlled, why vehicle screening is required, why certain areas require surveillance, why specific detection measures are included, and how these elements work together as part of a defense-in-depth approach.

This understanding is essential. A contractor who does not understand the consultant’s outputs may reduce the approved design into a list of materials.

That is a serious risk in regulated security projects.

The design is not a shopping list. It is a security concept translated into technical requirements.

Approved drawings must become compliant execution.

Security drawings in SAIS-regulated projects are part of the approved security basis. They are not general project illustrations.

Once implementation begins, the contractor must develop the execution-level details needed to build the approved design correctly. This includes shop drawings, installation details, equipment submittals, method statements, project schedules, POQ-related requirements, testing arrangements, training requirements, and handover records.

Weak execution at this stage can undermine the project.

A device may be installed in the wrong location. A camera may fail to cover the intended field of view. A gate may not support the required access-control logic. A barrier may not match the approved vehicle-control concept. A control-room system may be delivered without the operational functions needed for monitoring, alarm handling, reporting, and response.

These issues may not be obvious during installation. They usually appear later, during review, testing, commissioning, readiness assessment, or authority-related checks.

By then, correction may require redesign, replacement, reinstallation, additional works, additional cost, and project delay.

This is why the execution stage must be controlled by a contractor who understands the approved security basis, not only the equipment catalogue.

Security requirements are not generic products.

One of the most damaging mistakes in SAIS-regulated projects is treating required security measures as normal market products.

A security fence in a regulated project is not simply a boundary fence. It may need to meet defined requirements for resistance, durability, anti-corrosion protection, fixing details, foundations, installation quality, and integration with surveillance, lighting, patrol, detection, and response arrangements.

If an ordinary contractor treats that fence as a standard fence, the result may look acceptable from a distance but fail the purpose for which it was required.

The same principle applies to gates, barriers, access-control points, cameras, intrusion detection, control-room systems, and other physical security measures.

The correct product matters, but in SAIS-regulated projects, compliance also depends on the correct specification, installation, integration, testing, documentation, and handover.

The SAIS-approved Security Contractor understands that compliance is not only about what is installed. It is also about how it is specified, installed, tested, documented, and handed over.

The wrong contractor can make compliance expensive.

The risk of appointing an unsuitable contractor is not limited to poor workmanship.

The larger risk is that the project may appear to be progressing while compliance gaps are being built into the facility.

This is one of the most difficult situations for an owner or project manager. Materials have been procured. Systems have been installed. Site progress has been reported. But later review reveals that the implementation does not fully support the approved design or SAIS expectations.

At that point, the owner may face repeated reviews, corrective submissions, replacement of materials, removal of installed works, reinstallation, delayed testing, delayed commissioning, delayed readiness, and difficulty progressing toward approval.

A lower initial price can become expensive when it creates non-compliant execution.

In SAIS-regulated projects, the wrong contractor can turn a clear approved design into a costly recovery exercise.

The approved contractor supports the path to authority approval.

The SAIS-approved Security Contractor contributes to the project far beyond installation.

Its work must be reviewable, testable, traceable, and defensible. The contractor must support the documents, submittals, installation details, testing records, training requirements, and handover evidence needed to demonstrate that the approved security design has been implemented properly.

This matters because the facility must eventually show that its security measures are not only installed, but ready for operation.

The contractor helps transform the approved security concept into a real security operation that can be inspected, tested, documented, and operated.

This is why the SAIS-approved Security Contractor is a partner in the success of the project and in achieving authority approval.

The consultant and contractor protect different parts of the project.

The Security Consultant and the Security Contractor do not perform the same role.

The consultant protects the compliance basis.
The contractor protects the execution quality.

The consultant defines, reviews, and confirms alignment with the approved security requirements. The contractor develops the execution-level details, supplies the approved equipment, performs installation, prepares the required contractor documents, supports testing and commissioning, and contributes to readiness.

When these roles are understood, the project is more likely to move from design approval to operational readiness without unnecessary rework.

When the roles are confused, problems appear. The contractor may attempt to change the design without understanding the security basis. The owner may assume that installation equals compliance. The project may move too far before gaps are discovered.

Clear role separation and proper coordination are essential.

SASECON’s approach to Security Contractor coordination.

At Saudi Ansary Security Consultancy LLC (SASECON), we view the SAIS-approved Security Contractor as an essential partner in delivering successful SAIS-regulated projects.

Our role begins by helping owners and project teams establish a compliant security basis and develop the required security studies and design outputs. We also support owners before contractor appointment by assisting in the technical evaluation of SAIS-approved Security Contractors.

This may include reviewing the contractor’s approval and qualification documents, relevant project experience, execution capability, technical understanding, and market reputation. It may also include reviewing the contractor’s proposed implementation approach, equipment compliance, documentation capability, testing arrangements, training requirements, and readiness support.

This helps the owner assess the contractor not only from a commercial perspective, but also from a compliance, technical, and project-risk perspective.

The purpose is not only to select a contractor who can complete installation.

The purpose is to select a contractor who can achieve compliant implementation.

For owners and project managers, appointing a SAIS-approved Security Contractor is not a minor procurement decision. It is a strategic project decision that affects compliance, cost, schedule, authority approval, and operational readiness.

In Part 11 of this series, we will examine how contractor documents in Stage Three support compliant execution and readiness.