Planning for protective services is not uniform across the private security industry. Part of this comes from practitioner diversity in background, experience, and training. Part of it is structural: no single authority regulates doctrine or planning methodologies across the industry.
It is easy to find a guide on conducting an executive protection advance. It is likewise easy to find comprehensive guidance on security planning for events, motorcade operations, residential security, and similar protective functions. These guides are useful, but they are usually tailored to one type of operation and approach planning through that specialized lens. CISA’s venue guidance, for example, provides venue operators with security measures selected according to factors such as risk, size, location, complexity, and cost.
The result of the aforementioned disuniform approach is an industry with numerous specialized playbooks, but no widely accepted foundation for analyzing missions across protective-security domains at the tactical level.
One possible remedy is to draw from the mission-analysis framework used in the U.S. Army’s Troop Leading Procedures (TLP). Military units do not create a new planning process for every type of mission. Instead, they use a common process and adjust the focus based on the situation.
Within TLP, small-unit leaders analyze six mission variables commonly known as METT-TC:
- Mission
- Enemy
- Terrain and weather
- Troops and support available
- Time available
- Civil considerations
These variables help small-unit leaders organize relevant information, understand how different conditions affect the mission, and develop a plan appropriate to the situation. Because METT-TC was designed for military operations, however, it requires some translation before being applied to the protective operations common in private security.
Adapting the Mission Variables for Private Security Operations
Mission: What must be accomplished, for whom, why, and under what constraints? Define the client’s objective, conditions for success, acceptable risk, and the detail’s specified, implied, and essential tasks.
Threats and hazards: Who or what could interfere with the mission or harm the protectee? Consider threat capabilities and intent, along with the most likely and most dangerous courses of action. The analysis should also include accidents, medical emergencies, severe weather, equipment failure, operational disruption, and client-generated risk.
Terrain and environment: How will the operating environment affect the detail? Consider road conditions, traffic, visibility, weather, entrances and exits, crowd movement, communications coverage, observation, access, response, and control.
Personnel, equipment, and support: Who is available, what can they do, and what do they need? Account for staffing, authorities, skills, vehicles, communications, medical resources, vendors, law enforcement, and other supporting organizations.
Time available: How much time remains before execution, and how much is available during each phase? Identify hard times, planning windows, movements, transitions, response windows, and the latest points at which key decisions can be made.
Third parties: Who must be coordinated with, and who could affect – or be affected by – the detail? Consider venue personnel, employees, residents, attendees, bystanders, media, public-safety agencies, legal restrictions, privacy, culture, reputation, and business operations.
This framework will not produce the same plan for every protective operation. But that is partially the point. The value this adapted framework brings is that it gives practitioners a consistent way to understand the mission before selecting tactics, assigning personnel, or reaching for an event-specific protection checklist. The goal is not one security plan for every mission, nor should it ever be. The goal here is to have a common way – language or method, if you will – to understand any mission before building the specific plan for it.
Putting the Framework into Practice for Security Teams
For practitioners, the next step does not need to be complicated. Apply the framework when planning the next detail, use it to structure the mission brief, and revisit it during the after-action review. Over time, the terminology and questions can be refined to fit the organization and its services. Even if the industry never adopts a single doctrine, individual organizations can still build a more consistent way to think, plan, and communicate across protective operations.
If your organization needs a more consistent approach to planning protective operations, Convoy Group can help you develop mission-planning processes, briefing formats, and training tailored to your security team and services.