Construction Security | 2026-09-04 | 24 min read

Field Guide: Construction Site Security Plan for BC Projects

Build a site-specific construction security plan for a BC project, with clear ownership, risk controls, post orders, escalation procedures, reporting, and a downloadable template.

A construction site security plan should make the site easier to run, not add another document that nobody uses.

For a general contractor, developer, project manager, superintendent, or site-security lead in British Columbia, the useful version is a live operating document. It identifies what must be protected, who controls access, what happens after hours, what guards or patrols are authorized to do, who receives an urgent call, what gets recorded, and when the plan must change.

This guide explains how to build that document from mobilization through handover. It includes a phase-by-phase planning method, a practical review checklist, and a downloadable blank template that can be adapted to the project.

This is general security-planning information, not legal, occupational health and safety, fire-code, insurance, engineering, privacy, or contract advice. A security plan does not replace the project’s required safety program, emergency procedures, fire-safety arrangements, traffic-control plan, permits, or qualified professional advice. Confirm responsibilities and requirements with the owner, prime contractor, employers, insurer, legal and privacy advisers, local authority, and other responsible project leads.

Quick Answer

A practical construction site security plan should answer ten questions:

What property, people, information, equipment, materials, and project areas are within scope?
Who owns the plan, who approves it, and who can authorize a change?
Which threats and vulnerabilities matter at the current construction phase?
Where are the controlled boundaries, gates, restricted zones, and high-value areas?
How are workers, visitors, deliveries, vehicles, keys, codes, and after-hours access managed?
Which controls are physical, procedural, technological, or provided by guards and patrols?
What are the written post orders and limits for every security assignment?
What should happen during an incident, and who is called at each level?
What reports, logs, images, and corrective actions must be retained—and for how long?
Which project milestones or incidents trigger a review?

There is no single BC law that makes one generic construction security template suitable for every project. The plan may be required by a contract, owner, lender, insurer, internal policy, risk assessment, or project condition. It should always be site-specific and should clearly separate private-security responsibilities from workplace-safety and public-authority responsibilities.

What a Construction Site Security Plan Is—and Is Not

A construction site security plan is the project’s agreed method for preventing, detecting, documenting, and escalating security problems. It may address theft, unauthorized entry, vandalism, deliberate damage, after-hours access, key and credential control, equipment exposure, gate routines, suspicious activity, and security-system alarms.

The plan is not simply a list of hardware. Cameras, fencing, lighting, locks, alarms, guards, and patrols are controls inside the plan. The document must explain why each control is used, who maintains it, what happens when it fails, and how a problem is escalated.

It is also not the site-specific safety plan. WorkSafeBC distinguishes responsibilities among owners, prime contractors, employers, supervisors, and workers. At a multiple-employer workplace, the owner is the prime contractor unless another person is designated through a written agreement; the prime contractor coordinates occupational health and safety activities and establishes a compliance system. Those statutory responsibilities cannot be reassigned casually to a security provider. See WorkSafeBC’s roles, rights and responsibilities, its prime-contractor information sheet, and section 24 of the Workers Compensation Act occupational health and safety provisions.

Keep the boundaries visible:

Document or Function | Primary Purpose | Relationship to the Security Plan

Construction site security plan | Protect property, control authorized access, define security response, and document activity | The subject of this guide

Occupational health and safety program or site-specific safety plan | Identify and control hazards to workers and other persons at the workplace | Security personnel must receive relevant orientation and follow it; security does not own the whole program

Emergency response and evacuation procedures | Direct actions during medical, fire, environmental, rescue, utility, or other emergencies | Security may notify, guide access, preserve a route, or follow an assigned procedure without taking over qualified response roles

Fire-safety plan or fire-watch procedure | Address fire prevention, system impairment, evacuation, and authority requirements | Include only the security interface; confirm requirements with the authority having jurisdiction and qualified fire-safety leads

Traffic-control plan | Manage vehicles, workers, and public-road or work-zone traffic | A fixed security post does not automatically authorize a guard to perform trained traffic-control work

Environmental, hazardous-material, rescue, or permit plans | Manage specialized project risks and compliance | Cross-reference only the information security personnel need to work safely and escalate correctly

The WorkSafeBC construction project checklist is a useful starting point for understanding the broader regulatory responsibilities around a BC construction project. It is not a construction security template and should not be represented as one.

Assign Ownership Before Choosing Controls

The uploaded draft assumed the superintendent or project manager is always the plan owner. That is common, but it is not universal. Contract structure, project scale, corporate policy, and the owner-prime-contractor relationship may assign security governance differently.

Before drafting, name these functions:

Function | What Must Be Clear

Plan owner | Maintains the controlled document and coordinates updates

Approver | Accepts the plan, resources, and material revisions

Site authority | Makes day-to-day site decisions and confirms who may enter

Security contact | Coordinates the contracted security scope and post orders

After-hours decision-maker | Can answer an urgent call and authorize a practical response

Privacy contact | Reviews collection, access, retention, and disclosure of personal information

Safety contact | Provides orientation, hazards, restricted areas, and emergency information relevant to security workers

Systems owner | Maintains cameras, alarms, lighting, communications, access-control devices, and outage procedures

Records custodian | Controls access to reports, logs, footage references, and plan versions

One person may fill several functions on a small project. The important part is that the names, alternates, authority limits, and contact methods are written down.

The security provider should own its internal staffing, supervision, training, licence checks, and service records. It may help develop post orders and recommend practical controls. It should not be described as the owner of the entire construction project’s safety, emergency, insurance, or risk-governance obligations.

Start With Document Control

The first page of the plan should identify the document before it describes the site.

Include:

project name and civic address
owner and prime contractor, where applicable
plan owner and approver
version number
issue date and effective date
next scheduled review
distribution list
classification or handling note if the plan contains sensitive site information
change log showing the date, author, reason, approver, and affected sections

Avoid putting sensitive access codes, alarm credentials, camera passwords, or unnecessary personal information into every copy. Use controlled appendices or separate secure systems for information that only certain recipients require. Printed copies should have an owner and a replacement process so an outdated plan is not left in the site trailer after a revision.

Build a Security Risk Register

A risk register turns a general concern into a decision. It should be short enough to review and specific enough to assign action.

For each risk, record:

asset, zone, operation, or information at risk
credible event or threat
vulnerability or enabling condition
existing controls
potential consequence to the project
risk priority using the organization’s approved method
additional treatment
action owner and target date
residual risk and approval
review trigger

Do not copy a numeric formula from another company unless your organization understands and approves it. A simple low-medium-high method can work if the criteria are defined. A more formal matrix may be appropriate for a larger project. What matters is that the same method is applied consistently and that action is tied to the result.

Examples of project-specific entries might include:

Current Condition | Security Question | Possible Treatment to Assess

Temporary fence line moves for excavation | Can the site still be closed and verified at the end of shift? | Defined closure check, temporary barrier standard, photo verification, and named repair escalation

High-value equipment remains in an open laydown area | Who confirms keys, immobilization, parking position, and after-hours condition? | Equipment register, key control, designated zone, patrol checkpoint, or dedicated coverage during the exposure window

Multiple trades receive the same gate code | Can authorization be revoked without disrupting the whole site? | Individual credentials, time-limited codes, approved after-hours list, and documented deactivation

Public route runs beside incomplete work | Is the boundary clear, stable, visible, and within the permitted site footprint? | Barrier inspection and immediate escalation to the site authority; do not assign a guard to redesign traffic control

Camera power or cellular service is unreliable | How will alarms be verified during an outage? | Health-check alerts, outage contact, backup method, and temporary physical coverage based on risk

Plan by Construction Phase, Not Just by Address

The same property can require very different controls over six months. A plan should state which project phases are anticipated and which change automatically triggers review.

Project Phase | Typical Security Change to Review

Mobilization | Temporary boundary, site trailer, initial keys, early deliveries, limited lighting, and incomplete communications

Excavation and civil work | Moving fence lines, open access for machinery, remote equipment parking, fuel, and changing ground conditions

Structure | Vertical access, scaffolding, multiple entrances, larger crews, incomplete doors, and materials distributed across floors

Building enclosure | Doors and openings become securable, access routes change, interior blind spots increase, and credentials may need zoning

Mechanical, electrical, and finishes | More portable and high-value materials arrive; keys, suites, panels, and restricted rooms multiply

Testing and commissioning | Permanent systems interact with temporary systems; alarm calls, trades, owner representatives, and access permissions change

Deficiency and handover | Fewer workers remain, finished areas are vulnerable to damage, access must be revoked, and records or keys transfer to the owner

Use milestones rather than arbitrary calendar intervals when possible. Review the plan when fencing moves, a new gate opens, permanent doors are installed, cameras or alarms change, the site begins night work, a high-value delivery arrives, a holiday shutdown starts, an incident reveals a weakness, or responsibility transfers.

Map the Site and Define Security Zones

A site map should help a new authorized person understand the assignment without exposing more information than necessary.

The controlled security map may show:

approved site boundary
vehicle and pedestrian gates
delivery and waiting areas
site office and security post
emergency access route and muster point, as supplied by the responsible safety lead
restricted and high-value zones
equipment, fuel, tool, and material storage areas
camera fields of view or alarmed areas where disclosure is appropriate
lighting and communication gaps
guard patrol checkpoints
areas a guard must not enter because of hazards or authorization limits
approved parking and after-hours work zones

Do not let the map become a substitute for the site walk. Confirm whether a gate can actually be locked, whether a checkpoint can be reached safely, whether a radio or phone works in each area, and whether the guard’s route conflicts with active equipment or restricted work.

Define Access Control Without Repeating the Access-Control Guide

The security plan should summarize the authorized process; the detailed procedure can sit in an appendix or separate access-control document.

At minimum, state:

the normal worker entrance and delivery entrance
who issues and revokes credentials
acceptable identification or authorization methods
visitor approval and escort rules
delivery windows, exceptions, and refusal/escalation steps
vehicle access and parking restrictions
key, fob, card, and gate-code control
after-hours authorization and the person who may approve a change
process for lost, shared, or unreturned credentials
sign-in and sign-out records, including the purpose and retention rule
actions when someone cannot be verified

A guard should never have to guess whether a subcontractor’s verbal claim overrides the current authorized list. The plan needs an approver and a reachable alternate.

For a deeper gate, visitor, delivery, credential, and after-hours checklist, use Zentra’s construction site access control guide. That article remains the detailed access-control resource; this plan links the procedure to the broader governance and response system.

Protect Equipment and Materials Through Assigned Routines

The plan should identify high-priority assets and the control owner without publishing an unnecessary shopping list of valuables.

Depending on the project, the asset-control appendix may include:

equipment identifier, serial number, VIN, or internal asset number
authorized operator or custodian
normal storage or parking zone
key and spare-key location
immobilization or lock requirement
end-of-shift verification
delivery and removal record
exception process for off-site repair, transfer, or early pickup
person who investigates a discrepancy

Security can verify visible conditions specified in the post orders—for example, whether an agreed gate is closed, a seal appears intact, or a listed machine is in its assigned zone. Security should not be instructed to operate equipment, enter an unsafe area, inspect a technical system beyond training, or certify a condition outside its competence.

For broader theft-prevention methods, link readers to Zentra’s construction site security guide for BC and construction theft guide. Keep the present plan focused on responsibility, verification, and recordkeeping.

Choose Coverage From the Required Outcome

The plan should define the outcome before selecting a guard schedule or technology package.

Site Condition | Coverage Model to Assess | Planning Question

One controlled gate with continuous authorized traffic | On-site guard or access-control post | Can one post verify access without abandoning the gate for other duties?

Closed, well-defined site needing periodic exterior verification | Mobile patrol | Which gates, fence sections, storage areas, lighting conditions, and exceptions must each visit document?

High-consequence or repeated after-hours activity | Dedicated guard, additional posts, technology, or a hybrid | Is continuous observation required, and can the assignment be performed safely?

Monitored intrusion alarm with a practical keyholder process | Alarm response | Who may enter, what areas may be checked, and what triggers police, maintenance, or client escalation?

Temporary fire-system impairment or authority-directed fire watch | Separate fire-watch procedure and confirmed staffing | What does the authority having jurisdiction, fire-protection lead, or approved plan require?

Short high-value delivery or holiday shutdown | Time-limited guard, patrol, lock-up, or hybrid coverage | What is the exact exposure window, and when should temporary coverage end?

There is no universal guard-to-acre, guard-to-worker, or patrol-frequency ratio. Distance, visibility, access volume, hazards, communications, response options, previous incidents, and the consequence of a missed condition all matter.

Zentra’s construction security service, security guards, mobile patrol, and alarm response pages explain the service categories. The separate construction security cost guide explains pricing factors without crowding this planning guide.

Write Post Orders That a Guard Can Actually Follow

Post orders translate the plan into shift-level instructions. Each post should have a purpose, authorized duties, limits, schedule, contacts, and reporting standard.

Include:

post name, location, hours, and relief process
required security-worker licence and site orientation
guard arrival, sign-in, equipment, and communications check
fixed responsibilities and patrol route
checkpoints and what condition is being verified
authorized access list and exception method
restricted and prohibited areas
site hazards and personal protective equipment identified by the responsible site lead
working-alone check-in procedure where applicable
routine, urgent, and emergency escalation
incident, access, patrol, key, and shift-report requirements
evidence-preservation instruction that prioritizes personal safety and public-authority direction
handover and end-of-shift process
person authorized to change the order

In BC, contracted security companies generally need the appropriate security business licence, and individuals doing security work generally need the appropriate worker licence unless an exemption applies. The Security Services Act also requires a licensed security business to use workers licensed for the kind of security work performed. Verify the current requirements through the Province’s security business licensing page, security worker licensing page, and the Security Services Act.

The plan should not call a private guard “law enforcement,” imply police powers, or authorize weapons or coercive actions outside law, licence conditions, training, company policy, and contract scope. Urgent threats, violence, fire, medical emergencies, and crimes in progress belong with 911 and the appropriate public authority.

Protect Guards Working Alone or After Hours

Construction security often operates when the site is empty or lightly staffed. That makes worker-safety planning inseparable from assignment design.

WorkSafeBC states that employers must have procedures to ensure the well-being of workers who work alone or in isolation and that lone workers must be able to obtain assistance during injury or emergency. Its working-alone resources should be reviewed by the responsible employer.

The site-security plan should interface with—but not replace—the employer’s procedure. Confirm:

communication method and known dead zones
check-in frequency and missed-check procedure established by the employer
supervisor or monitoring contact
emergency access and accurate site address
hazards, restricted areas, and safe patrol route
weather, lighting, temporary power, excavation, equipment, and fall exposures
washroom, shelter, and welfare arrangements
conditions that require a route, post, or task to stop
escalation when violence or confrontation risk may be present

WorkSafeBC’s OHS Regulation Part 4 addresses working alone and workplace violence, including risk assessment where violence-related injury risk may be present. A security contract does not remove the employer’s obligations.

Set Camera and Data Rules Before Collection Starts

Construction cameras may capture workers, visitors, neighbours, public routes, vehicle plates, access events, and audio. “Keep everything as long as possible” is not a privacy plan.

The federal, Alberta, and British Columbia privacy commissioners advise private organizations to identify the purpose of overt surveillance, consider less privacy-invasive alternatives, limit collection, provide notice, secure the information, control access, and establish retention and destruction practices. Review their joint Guidelines for Overt Video Surveillance in the Private Sector before setting camera scope or retention.

The plan should identify:

accountable organization and privacy contact
documented purpose for each camera or data stream
field of view and areas intentionally excluded
signage and notice
whether audio is disabled or separately justified and reviewed
who can view live feeds and recordings
access authentication and audit controls
event export and evidence-handoff process
retention period tied to the documented purpose and legal/contract requirements
secure deletion and decommissioning at handover
process for privacy questions, access requests, or complaints

Do not publish passwords, network diagrams, blind spots, or detailed camera specifications in broadly distributed versions of the plan. Place sensitive technical information in a controlled appendix.

Build an Incident and Escalation Procedure

The plan needs a usable response method, not a promise that security will “handle everything.”

Use a simple decision structure:

Protect life and personal safety. Call 911 for an immediate threat, violence, fire, medical emergency, or crime in progress.
Observe and verify only when safe and authorized. Do not require a guard to enter a hazard area or confront a person.
Notify the designated contact. Use the current site escalation list and alternate.
Protect the scene and information. Avoid disturbing potential evidence; follow police, fire, or site-safety direction.
Document facts. Record time, location, observations, actions, notifications, and relevant images without speculation.
Assign corrective action. The responsible project lead decides repairs, access changes, coverage changes, or follow-up.
Review the plan. Update the risk register and affected post orders when the incident exposes a gap.

Define terms such as “routine,” “urgent,” and “emergency” for the project. State who is called, expected callback time, what the guard does if nobody answers, and what information the report must include. Never place a private client call ahead of 911 when there is an immediate emergency.

The Canadian Centre for Occupational Health and Safety emergency-planning guide explains why emergency planning should be based on potential events, decision sequences, resources, communications, and responsibilities. Use it for the broader workplace emergency process; keep the security escalation procedure aligned with that process.

Reporting and Documentation

A professional security service should leave a factual operational record. The plan should say which records are required, who receives them, how quickly they are delivered, who may access them, and when they are corrected or retained.

Depending on the assignment, records may include:

shift start and finish
guard or patrol identifier
post, route, and areas checked
gate, fence, door, lock, seal, lighting, alarm, and visible camera condition
arrivals, visitors, deliveries, denials, and approved exceptions
keys, credentials, and equipment issued or returned
observed damage, trespass signs, unusual activity, or outages
photographs where appropriate and authorized
person notified, time of notification, and direction received
incident-report reference
outstanding corrective action
shift handover note

Separate observations from conclusions. “North vehicle gate open approximately 30 cm at 22:14; no person visible; site contact notified at 22:17” is more useful than “site was insecure.” Reports should not contain rumours, unnecessary personal details, diagnoses, or accusations.

Create a correction process. A report should not be silently overwritten after delivery. Preserve the original entry, identify the correction, explain why it was made, and record who approved it when the system permits.

Zentra Field Note: The Plan Usually Fails at the Handoff

Many site-security gaps appear between routines rather than inside them.

The day crew believes the last subcontractor will close a moved fence panel. The subcontractor assumes the superintendent will do it. The mobile patrol sees the gap but the post order only says “check perimeter,” with no repair contact or priority. A report is sent the next morning, after the exposure window has passed.

The fix is not automatically more guard hours. It is a defined handoff:

who declares the site ready for after-hours coverage
what open work or approved access remains
which gates, openings, systems, and high-value zones changed that day
what the guard or patrol must verify first
who can authorize an exception
which condition requires an immediate call instead of a routine report

This daily transition belongs in the plan and in the shift record.

Construction Site Security Plan Review Checklist

Before approving the plan, confirm:

The plan has an owner, approver, version, issue date, distribution list, and change log.
The project address, boundaries, phases, operating hours, and scope are accurate.
Security is clearly separated from safety, emergency, fire, traffic-control, and public-authority functions.
A current security risk register identifies actions, owners, dates, and review triggers.
The site map matches current gates, routes, restricted zones, hazards, and storage areas.
Worker, visitor, delivery, vehicle, credential, key, and after-hours access procedures are defined.
High-priority equipment and material controls have named owners and verification routines.
Guard, patrol, alarm, and technology choices are tied to required outcomes.
Every guard post has written instructions, limits, escalation, and reporting requirements.
Relevant licences and business status have been verified for the contracted security scope.
Security personnel receive site orientation and applicable PPE, communication, and working-alone procedures.
Camera and access-record practices have documented purposes, safeguards, access limits, and retention rules.
The escalation list has alternates and has been tested.
911 is the first call for immediate threats and emergencies.
Report recipients, delivery times, record access, correction, retention, and follow-up are defined.
Review triggers cover phase changes, new gates, system outages, high-value deliveries, shutdowns, incidents, and handover.
Sensitive appendices and outdated printed copies are controlled.

Download the BC Construction Site Security Plan Template

The template is a structured planning aid. It must be adapted to the project and reviewed by the people responsible for safety, contracts, insurance, privacy, fire protection, and other applicable requirements.

How Zentra Handles Construction Security Planning

Zentra begins with the assignment conditions rather than a generic guard package.

The planning conversation typically covers:

project address, stage, boundaries, access points, and operating hours
known incidents, high-priority assets, and after-hours exposure
authorized site contacts and escalation limits
guard, patrol, alarm-response, or temporary-coverage outcomes
site orientation, hazards, restricted areas, communications, and working-alone arrangements supplied by the responsible project leads
post orders, patrol checkpoints, access exceptions, and incident procedures
shift, patrol, incident, and handover reporting expectations
review triggers and the person who approves a service change

Zentra may recommend on-site guards, mobile patrol, alarm response, or a blended model when the site conditions support it. Fire watch is treated as a separate assignment and is used only when the requirement, scope, patrol frequency, documentation, and cancellation authority are confirmed. See Zentra’s fire watch service for that distinction.

Zentra does not promise that security eliminates theft, loss, delay, injury, or liability. The goal is a clear, supportable service scope with professional field presence, timely escalation, and documented activity.

Information to Prepare Before Requesting Coverage

Provide enough information to plan safely without distributing unnecessary confidential material:

site address and project phase
requested dates, times, and risk window
current map and controlled entrances
active trades, expected visitors, and delivery windows
restricted zones and relevant hazards
equipment or material areas requiring specific checks
access approval and after-hours exception process
emergency, urgent, and routine contacts with alternates
required reports and recipients
communication coverage and site-welfare arrangements
current alarm, camera, lighting, and gate conditions
insurer, contract, owner, or authority requirements that affect the security scope

Projects in Chilliwack and the Fraser Valley can also review Zentra’s construction site security in Chilliwack and Chilliwack security company pages for local service context. Remote and semi-rural projects should use the Hope and Fraser Canyon construction security guide to assess travel, communications, keyholder, and response constraints.

About This Guide

This guide was prepared by Zentra Protection for British Columbia owners, developers, general contractors, project managers, superintendents, and site teams seeking a practical method for construction security planning.

It was reviewed against Zentra’s current construction content to avoid duplicating the existing theft-prevention, access-control, provider-selection, response, remote-site, and cost guides. The planning and legal context was checked on September 4, 2026 against current WorkSafeBC, Province of British Columbia, BC Laws, Canadian and BC privacy-commissioner, and CCOHS sources.

The article distinguishes official requirements from Zentra’s operational recommendations. It does not claim legal review, insurer approval, or a universal industry standard. Project-specific requirements should be confirmed with the responsible professionals and authorities.

Official Sources

Final Thoughts

A construction site security plan is useful when it turns changing project conditions into clear ownership, practical controls, executable post orders, timely escalation, and a reliable record.

Start with the boundary between security and the project’s other responsibilities. Assign the plan owner. Build the risk register. Map the current phase. Define access, assets, post orders, incident procedures, and records. Then review the document whenever the site changes—not only after something goes wrong.

If a BC construction project needs practical security coverage, Zentra Protection can help scope guards, patrols, alarm response, access support, and reporting around the actual site conditions.

Contact Zentra Protection

Frequently Asked Questions

What is a construction site security plan?

A construction site security plan is a site-specific document that identifies security risks, assigns responsibilities, defines access and asset controls, sets security-service instructions, establishes incident escalation and reporting, and states when the plan must be reviewed.

Is a written construction site security plan legally required in BC?

There is no single rule that makes one generic security-plan format mandatory for every BC construction project. A plan may be required by a contract, owner, lender, insurer, internal policy, authority, or project-specific risk. Separate occupational health and safety, emergency, fire, permit, and other legal requirements may apply. Confirm the project’s obligations with the responsible professionals and authorities.

Who should own the construction security plan?

The owner should be the person or function authorized by the project’s governance and contracts to maintain and coordinate the plan. It may be a project manager, superintendent, corporate security lead, or another designated person. The decision should be written; it should not be assumed.

Is a construction security plan the same as a site-specific safety plan?

No. A security plan addresses deliberate or unauthorized events, access, assets, security systems, guards, patrols, escalation, and security records. A site-specific safety plan addresses occupational hazards and safety responsibilities. The documents must coordinate, but security does not replace the safety program.

What should a construction site security plan include?

Include document control, responsibilities, scope, a risk register, site map and zones, access procedures, asset controls, service and system design, post orders, worker-safety interfaces, incident escalation, reporting, privacy and record rules, review triggers, and approval.

How often should the plan be reviewed?

Set a project-specific schedule and milestone triggers. Review when the phase changes, a gate or boundary moves, systems change, a high-value delivery arrives, hours change, a shutdown begins, an incident reveals a gap, or responsibility transfers.

Can a security company write the whole plan for the contractor?

A provider can contribute security expertise, site observations, service recommendations, post orders, escalation processes, and reporting standards. The project owner, prime contractor, employers, and other responsible parties must retain their own legal, safety, contract, privacy, and operational responsibilities.

When is mobile patrol enough for a construction site?

Mobile patrol may fit a closed site needing periodic gate, perimeter, lighting, storage-area, or exterior-condition checks. It may not fit a site requiring continuous gate control, immediate on-site intervention, or observation across a high-consequence exposure window. Decide from the required outcome and site conditions.

What should construction security post orders include?

Post orders should state the post purpose, hours, authorized duties, patrol route, checkpoints, access rules, restricted areas, site hazards, communications, working-alone procedure, escalation contacts, reporting, handover, and who may change the instructions.

How should cameras and recordings be addressed?

Document the purpose, accountable organization, field of view, notice, access restrictions, security safeguards, retention and deletion, evidence export, and privacy-contact process. Review current OIPC BC guidance and obtain project-specific privacy advice.

What should be included in a construction security report?

Record the date and time, post or patrol, areas checked, relevant site conditions, authorized access activity, exceptions, observed damage or unusual activity, notifications, direction received, incident reference, and follow-up. Separate facts from assumptions.

Does Zentra provide construction site security planning and coverage in BC?

Zentra can review the proposed security assignment, help define guard or patrol outcomes, develop post orders and reporting expectations, and provide licensed security coverage where the site, schedule, duties, safety conditions, and service availability can be supported. The project team remains responsible for its broader legal, safety, fire, insurance, privacy, and contract obligations.

Related Zentra Services