Three words appear more often than any others in the Shadow operations vocabulary: designed, built, and staffed. They appear in how we describe a security program, how we evaluate a venue's existing posture, and how we frame the question a new client should be asking of any provider they are considering. They are not interchangeable. Each verb describes a distinct phase of work, requires a distinct kind of expertise, and produces a distinct deliverable. A program that is strong in one or two of the three is not a complete protection program. It is a partial program, and the gaps are almost always where incidents happen.
What it means to design a security program.
Design is the intelligence and planning phase. It begins before the operations order, before the site walk, before any staffing decisions are made. Design asks: What is the threat environment for this principal, in this venue, during this operational window? What are the specific risk categories that apply, and at what confidence level? What does the principal's profile generate in terms of threat actor interest, and what does the venue's configuration present in terms of structural vulnerability?
A designed program has a threat picture at its foundation. It has a route architecture that reflects the specific layout of the specific venue rather than a standard template. It has a medical posture that is matched to the event's risk profile and crowd size rather than a standard deployment. It has a communications protocol, a command hierarchy, and a decision authority framework that is explicit rather than assumed. Most importantly, it has contingencies: documented responses to the three most likely failure scenarios, rehearsed before they are needed.
Most providers do not design programs. They template them. They take a standard format that has worked in similar contexts and apply it to the current engagement with whatever adjustments are obvious. This works until the engagement has a characteristic that the template does not account for, and every engagement has at least one. The provider that designed the program will adapt. The provider that templated it will not know what they are missing until they are looking for it in real time.
"Designed means you started with the threat. Built means you built to it. Staffed means the people on the floor understand both."
What it means to build a security program.
Building is the translation of the design into executable operational infrastructure. The operations order is built from the threat picture and the site walk. Routes are walked and timed. Hard rooms are identified, documented, and confirmed accessible. Coordination with venue operations, local law enforcement, and medical services is established before show day. The communications architecture is tested. The staffing brief is written with specificity: each position knows their primary responsibility, their contingency trigger, and their escalation protocol.
A built program is one that a new team member can be briefed into in under an hour and understand completely. Not because it is simple; the operational architecture of a properly built program is not simple, but because it is documented with precision. The operations order is not a summary. It is a governing document. It contains what needs to happen at each stage of the principal's movement, who is responsible for each decision point, and what happens when the primary plan fails at each stage.
Providers who skip the build phase often have strong design instincts and capable teams. What they produce is a strong improvisation. An improvised program can look identical to a built program in conditions where nothing goes wrong. The difference appears when something does go wrong and the team needs to execute under pressure from a shared document rather than individual judgment. Shared documents exist in built programs. Strong improvisation is still improvisation.
What it means to staff a security program.
Staffing is the final and most visible phase, and the one most commonly confused with the entirety of the work. Staffing is not headcount. It is not bodies at positions. It is the selection and placement of people who understand the design and have been briefed into the build, positioned where the operational architecture requires them to be, with the specific knowledge and authority their position requires.
A staffed program has people at positions who know why they are there. They know what they are watching for, what their trigger conditions are, and what they do when those conditions are met. They have been briefed on the threat picture at a level appropriate to their position. They know the hard rooms. They know the escalation chain. They have been told, specifically, what the non-obvious risks are for this engagement and why.
When a program is designed, built, and staffed, the team on the floor is not covering a position. They are executing a plan that was built to address the actual threat environment of the specific engagement they are working. The difference between that team and a team that was deployed without a built plan is not visible in normal conditions. In abnormal conditions, it is everything. Designed, built, and staffed is not a phrase. It is the minimum standard. Ask every provider you are considering whether they can account for all three.