Services / 02
Design &
requirements.
Review security intent early enough to influence layouts, operational interfaces and procurement decisions.
What we examine
Translate security objectives into questions the design team can resolve. Review boundaries, access routes, visitor and contractor flows, loading interfaces and the separation of critical spaces.
Consider how access control, detection, surveillance and operational response are intended to work together. Record assumptions about staffing, supervision, network dependencies and degraded operation.
Support procurement with functional requirements, evidence requests and acceptance questions. Product selection should follow a defined operational need, with installation detail and regulated design retained by the appropriate specialists.
Outputs
What you take
away.
- Security requirements registerTraceable requirements linked to operational objectives and agreed scenarios.
- Drawing review commentsLocation-referenced observations, coordination questions and decisions requiring owner input.
- Zoning and movement reviewA review of proposed boundaries, access permissions and person or material flows.
- Procurement clarification scheduleFunctional requirements, vendor questions and proposed evidence for acceptance.
- Decision and responsibility logOpen matters, accountable parties and dependencies before the next project milestone.
Inputs to agree
The evidence behind the review.
- Current site, architectural and security-system drawings
- The operational brief, security objectives and project stage
- Owner requirements, tenancy assumptions and design constraints
- Relevant specifications and proposed procurement packages
Scope boundary
A defined level of assurance.
This is advisory review, not engineer-of-record design, stamped drawings, code approval, blast engineering or certification. Fire and life safety, egress and system compliance must be resolved with the qualified design team and relevant authorities.
Deliverables, review depth, information handling and any follow-up are confirmed in a written scope before work begins.
Start with the question