How to Prepare a Commercial Security Project Brief

A clear project brief helps facilities teams explain their needs and compare security proposals on the same basis. Use the following sections as a working outline before speaking with a provider.

1. Property and operating context

Describe the building, outdoor areas, occupancy, hours and planned changes. Include a simple floor plan showing entrances, loading areas, restricted rooms and important movement routes.

2. Problems and desired outcomes

List the incidents, blind spots or unreliable equipment that prompted the project. Describe what staff need to know or do: identify an arrival, investigate a delivery, restrict an entrance or receive a fault notification.

3. Existing systems and infrastructure

Gather an equipment inventory, available drawings, support contacts and known faults. Record available power, network connections and cable routes. Identify who owns administrator accounts; do not put passwords into a general project brief.

4. Workflows and responsibilities

Who approves access and removes former users?
Who receives notifications and maintains contact lists?
Who may review recordings or export an event?
How are visitors, contractors and late deliveries handled?

5. Constraints and proposal questions

Record work hours, budget parameters, decision dates and operational interruptions to avoid. Ask providers to identify assumptions, exclusions, recurring charges, equipment reuse requirements and responsibilities for supporting work.

6. Acceptance and handover

Choose representative tasks to demonstrate before completion. Request equipment records, labeled locations, staff training, agreed settings and support procedures. Assign a person to keep permissions and documentation current.

Copy this outline into your project notes

Project owner: Who approves scope, answers site questions and accepts completed work?
Location and operating hours: Which building, shared areas and work windows are included?
Priority problem: What specific activity, access issue or equipment fault must be addressed?
Desired result: What should authorized staff be able to see, control or retrieve?
Existing equipment: What is known, what needs inspection and what must remain operational?
Constraints: Which areas, interruptions, budget limits and deadlines affect the work?
Acceptance evidence: Which demonstration or record will show the agreed result?
Open questions: What requires a site visit, technical review or written clarification?

Example: turn a vague request into an observable task

“Improve loading-area cameras” leaves providers guessing. A more useful brief could state: “Authorized staff need to find a specified delivery event, review the agreed loading-area views and export a playable clip.” The proposal should then define the relevant locations, image detail, lighting conditions, retention, permissions and export method.

This is an illustrative requirement, not a claim about an installed system. The facility team and provider still need to agree measurable acceptance conditions. Record anything dependent on an inspection as an assumption rather than silently treating it as included.

Compare exceptions before comparing totals

For each proposal, mark every requested item as included, excluded or awaiting clarification. Separate one-time work from subscriptions and support charges. Check who provides network access, power, lifts, permits where applicable and repairs to finishes. Keep a dated revision of the brief so every provider prices the same scope.

Using the completed brief

Share the brief through an agreed channel and keep detailed security drawings and account information restricted. For a property-specific discussion, continue to NERSA’s security assessment page. Browse the regional planning directory for related resources.