Security Concepts for Buildings and Properties
Assess risks, define protection objectives, describe measures – a concept that holds in an emergency and stands up to scrutiny.
Why many security concepts fail when it matters
A security concept is often written under time pressure: an authority asks for it, an insurer requires it, a tender calls for it. What comes out of this is frequently a document that exists on paper – but does not describe the actual situation on site.
The typical weaknesses are always the same. Risks are taken from a template instead of from a site inspection. Protection objectives stay vague, so there is no way to check later whether they were met. And the measures do not fit the way the site operates, so they are worked around in daily practice.
A concept that nobody follows protects nobody.
What sets our concepts apart from a template
From the site inspection, not from a template
We look at the site before we write. Access routes, processes, times, staffing – the risk analysis is built on what is actually there.
Verifiable for third parties
Authorities, insurers and supervisory bodies need to be able to follow how you arrived at your protection objectives. We document the reasoning, not just the result.
For service providers as well
Security companies have to submit concepts in tenders. We know what clients look for, because we have sat on their side of the table.
From the site inspection to the finished concept
The building blocks build on one another: without a risk analysis there are no robust protection objectives, and without protection objectives no justified measures. If you need a complete concept, you commission the whole chain. Often less is enough – an outside view of an existing document, for example, before it goes to an authority.
Risk analysis
Systematic recording of the risks on site: structural conditions, use, visitor traffic, operating hours, previous incidents.
Defining protection objectives
Setting out what the concept is meant to achieve – in a form that can be verified later.
Drafting the concept
Measures covering organisation, technology and staffing, matched to your processes and your budget.
Alarm and emergency planning
Who does what when something happens. Reporting lines, responsibilities, cooperation with the emergency services.
Liaison with authorities
Support in dealings with the local regulatory office (Ordnungsamt), fire service and police – including follow-up requirements.
Ongoing revision
A concept ages with the site. We review it regularly and adapt it as use changes.
Beyond the document
A security concept only takes effect once the people on site know it. On request we support the briefing of staff, run exercises and check after a year whether the procedures described hold up in daily practice. That is the part that goes beyond submitting a document to an authority – and the part that makes the difference when it matters.
The questions we are asked most often
What does a security concept cost?
Costs depend on the size of the site, the type of use and the scope. A concept for a single administrative building comes to considerably less than one for a property with visitor traffic and shift operation. In a free initial consultation you receive a concrete estimate.
When is a security concept required?
There is no general obligation. It is usually required for a specific reason: by licensing authorities for events, by insurers as a condition, by clients in tenders, or as a result of the risk assessment under German occupational health and safety legislation (Arbeitsschutzrecht). Whether an obligation applies in your case is a legal question – one for your legal advisers, not for us. We prepare the concept itself on technical grounds.
How long does it take to prepare?
For a clearly defined site, expect four to six weeks from the site inspection. Larger properties, or coordination with several authorities, extend this accordingly.
How often does a concept need updating?
Whenever the situation changes: conversion work, new use, altered operating hours, an incident. Independently of that, we recommend a review every two years – not least because the expectations of authorities and insurers shift over time.
Do I need a security concept if I am tendering for a security service?
Not necessarily, but it helps considerably. Without a concept, a tender usually describes only presence times and qualifications – the effort, not the objective. With a concept you can set out what the service is actually meant to achieve, and bids become comparable. The reverse also applies: if you are already tendering and do not yet have a concept, both can be developed in parallel. We have a dedicated section on tendering for security services.
Further reading
Articles on this topic from our blog.
Building Security Concepts: Five Points Where They Usually Fail
You need a security concept. Let us talk it through.
In an initial consultation we clarify what is required, what your site needs and how we would proceed. Free of charge and without obligation.
Request consultation